SCCM 2012 - Upgrade clients from Windows 7 to 10

I proceeded to copy and paste some articles parts from this official Microsoft article and other non Microsoft tutorials:


Revised content for the Windows 10 in-place upgrade via task sequence for Configuration Manager

How to upgrade to Windows 10 using the task sequence in System Center 2012 R2 Configuration Manager

Upgrade to Windows 10 with System Center 2012 R2 Configuration Manager

System Center 2012 R2 Configuration Manager SP1 adds support to manage and deploy Windows 10. Although it does not include built-in support to perform an in-place upgrade from Windows 7, Windows 8, or Windows 8.1 to Windows 10, you can build a custom task sequence to perform the necessary tasks.

Create the task sequence

To help with this process, the Configuration Manager team has published a blog that provides a sample task sequence, as well as the original blog that includes the instructions for setting up the task sequence. To summarize, here are the tasks you need to perform:
  1. Download the file that contains the sample task sequence and related scripts. Extract the contents onto a network share.
  2. Copy the Windows 10 Enterprise RTM x64 media into the extracted but empty Windows vNext Upgrade Media folder.
  3. Using the Configuration Manager Console, right-click the Task Sequences node, and then choose Import Task Sequence. Select the file that you extracted in Step 1.
  4. Distribute the two created packages (one contains the Windows 10 Enterprise x64 media, the other contains the related scripts) to the Configuration Manager distribution point.
For full details and an explanation of the task sequence steps, review the full details of the two blogs that are referenced above.
If you want to upgrade pcs/laptops mantaining same settings you need to utilize, inside SCCM 2012, this USMT tool too:
USMT (User State Migration Tool) is a nice utility from Microsoft that is used to migrate a user profile from one operating system to the next. A USMT Hardlink deployment refers to a Windows OS Deployment (to the same hardware) where we’ll create a local offline copy of the user profile, apply the new OS (without cleaning the disk) and then injecting the user profile back to that machine. In the situation of say Windows XP to Windows 7, USMT Hardlink was our only option (As there was no In-Place Upgrade). The same goes for a 32-bit verions of Windows-whatever (7,8,8.1) to Windows 10 64-bit.