StepChange Debt Charity

Step

Action

1

Check Microsoft for latest release versions, we should be doing this every quarter regardless of win 10 version so it applies the cumulative updates within the version.

2

Usually, preparing a new OS image in MDT is straightforward but since the downloaded version of ISO only has a install.esd which includes all versions of Windows 10 edition we need to a bit more work to get it ready.

3

*(Make sure you have a memory stick with at least 16Gb free on it)*

You can do this from either your PC or the deployment PC

Download and run the Windows 10 Media Creation Tool to create the installation media (memory Stick) in ISO format.

2. Extract files to the deployment server, the USB stick you downloaded the ISO will need to be inserted into the deployment server if downloaded on an alternative machine.

Right-click the ISO file just downloaded and choose Mount to mount the image into a local drive.

Create a sub folder in the Software folder on the root of C and make a copy of the mounted drive to the folder.

 3. Create install. wim from install.esd

Open an elevated Command Prompt window and run the DISM command to locate the right image to convert first.

C:\>cd "Software"

C:\Software>cd "ISO 20H2"

C:\Software\ISO 20H2>DISM /Get-WimInfo /WimFile:sources\install.esd

Since we are preparing for the Pro version, index 6 is what is needed. Now run the following to create the install.wim file.

C:\Software\ISO 20H2>DISM /Export-Image /SourceImageFile:sources\install.esd /SourceIndex:6 /DestinationImageFile:sources\install.wim /compress:max /CheckIntegrity

This created the install.wim file in the same folder as install.esd.

4. MDT Setup 1 – Add Image

Now let’s open Deployment Workbench (MDT Console), right-click Operating System and choose Import Operating System.

Select the Full set of source files of the image folder that contains the install.wim file we just managed to create. There is NO need to check the Move the files option.

Give it a unique name for the image, and your done for the import, next, next and Finish.

5 – Part1 - MDT Import the new OS into the current build task sequence for new imaged machines.

• Click in Task Sequence Tab
• Expand the Install folder
• Select the Install Operating System. In the right side click Browse

• Select the Operating System which imported.
• Click OK

Now you are ready to Deploy the updated Windows Image.

NOTE THIS PART IS STILL TO BE TESTED AND MAY NOT REMAIN PART OF THIS SOP

5 – Part2. MDT Set up A New Task Sequence to upgrade already built\imaged machines 

Right-click Task Sequences and choose New Task Sequence.

Put in a unique Task sequence ID, Name and some description if needed.

Then, select Standard Client Upgrade Task Sequence as the selected Template.

Pick the Operating System image we just imported.

Go through the rest of the steps and provide a local admin password when prompted. And that’s it for creating a new upgrade task sequence.

6. Client Upgrade

Now in a workstation that needs to upgrade, go to the shared deployment location and run LiteTouch.vbs from the scripts folder.

\\Deployment01\c$\Windows Deployment Environment\Production\Scripts

Select the 21H2 Upgrade option and go through the rest without changing anything. If you have any applications that you’d like to update the same time, you can choose them from the Applications section. Click Begin to start.

And that’s about it. Personally, for feature updates like 1903 and 20H2, I’d prefer upgrading through MDT than WSUS. Yes, it takes a few more steps to get prepared but once everything is in place, the upgrade process is much smoother and faster.

End

End Process Over