MDT2013 Batch Upgrade Win7 client to Win10

The previous time test passed MDT2013, upgrading the Win7 client to Win10, and upgrading office2010 to office2016 Plus, preserving the original user's profile. There was no time to write articles, today just Saturday, the process is now recorded, then read.

Demand:
Upgrade Win7 SP1 ent (PRO) to Win10 ent (PRO) with MDT2013, and upgrade office2010 from the original client to the office2016 plus version, Requires that user profiles and other applications (Outlook, and so on) are not affected by the upgrade.

Environment Introduction:
1, MDT version: mdt8450,adk1803;
2, client version: WIN7 SP1 Enterprise Edition/Professional Edition;
3, WIN10 version: Win10 1803 Enterprise Edition/Professional Edition;
4. Office version: Office2016 ProPlus;

The implementation steps are as follows (pre-upgrade user data backup before upgrading):

First, server-side configuration

1, MDT,ADK Installation

Prepare a Windows Server 2012R2 server, rename the server to MDT, and add the domain. Install WDS (Windows Deployment Services), download, install the latest version of MDT and ADK (mdt8450,adk1803)

2. New Deploymentshare Sharing

In the MDT management console, create a new Deploymentshare share.
As required, import the WIN10 operating system ISO (upgrade Win7 to WIN10 requires the type of standard WINDOWS10 Iso,import downloaded from the Windows Volume Licensing Center must be full set of source files).

3. New Upgrade WIN10 sequence

Select a standard Windows upgrade sequence, such as:

Select the WIN10 operating system you want to use

4. Import office2016 Application

Set up, view imported office2016 app properties

Set office2016 Silent Install command

Configuring Custom Tools


Select Delete Previous version (after the system upgrade is complete, the office2010 in the original Win7 system will be deleted)

Customizing features that need to be installed

Save the custom settings, be sure to save to the Updates folder, and in order to setup in the Updates folder in a heap of files (may also contain patches, etc.) priority recognition, the recommended custom installation parameter file name of the first word check "0"

You can create two task sequences, one for WIN10 Enterprise Edition, and one for Win10 Professional Edition.

5. Rules and Bootstrap settings

Set up the rules and bootstrap files for deployment, and the MDT logs can not be logged

6. Set Deploymentshare shared folder permissions

7. Update Deployment Share

To this, the server-side configuration is complete.

Second, the client to perform the upgrade

1, check the original Win7 client system version

You can see that the client operating system version that you currently need to upgrade is Win7 Enterprise Edition and has been added to the domain.

2. Access the MDT Server shared folder

Run-Enter: \\mdt.desit.cn\deploymentshare$\Scripts access the MDT Server shared folder, locate and run the Litetouch.vbs script file, and enter the administrator account password to execute the script.
Replace the mdt.desit.cn with the FQDN or IP address of the real MDT server.

3. Select the task sequence

Note: Win7 Enterprise Edition clients can only be upgraded to WIN10 Enterprise Edition, Win7 Professional client can only be upgraded to WIN10 Professional Edition. The Win7 family upgrade is not supported, and you cannot upgrade the 32-bit Win7 to 64-bit win10,win7 without SP1 patches, you need to make a good SP1 patch in advance.

If the client version is Win7 Pro, select upgrade to WIN10 Enterprise or Win7 Enterprise, and select Upgrade to Win10 Pro, the following error will appear:

Tick whether to install the office2016 Plus program

4. Perform system upgrade

5. View the upgrade results

In general, it takes about 1-2 hours to perform the upgrade process.

6. Check the status of the upgraded client system

As you can see, the current operating system has been upgraded to WIN10 Enterprise Edition, and the domain status is unchanged.

The original Win7 operating system files remain in the C drive Windows.old

Check that the Office version is upgraded successfully.

View the currently logged on user

Note: After upgrading, there is no option to revert to the previous version, that is, no fallback to Win7 after upgrading the system.

7. Outlook Side Check

Under the win10 operating system , Exchange MAPI mode, the Outlook side connection may appear with the following error:

Client network configuration If you do not fill out a real-world gateway address, the Exchange Server is outlook2016 through Exchange Mode, such as an escalation error.

Pop3/owa connection without error, mail send and receive normal.

After adding a real-world gateway address, the connection is OK.

In general, Win7 is upgraded to the WIN10 operating system, and most Windows drivers are integrated into the operating system by default, and some drivers can be manually installed as needed or imported via MDT based on the model.

In addition, PXE does not see the upgrade sequence, which means that the Win7 operating system upgrade cannot be done in PXE mode.

The above method mainly relies on the network to realize the Win7 system upgrade, the efficiency of the batch upgrade operating system is affected by the bandwidth. You can install media such as a USB flash drive, you need to make media media through MDT, and copy media to a USB flash drive. However, instead of entering the USB flash drive when the client is powered on (because the upgrade sequence is not visible), the system upgrade is performed by opening and running the Litetouch.vbs in the USB scripts folder after powering on.

MDT2013 Batch Upgrade Win7 client to Win10