Windows 10 Upgrade with MDT–A Walkthrough

So I wanted to test an in-place upgrade for upgrading Windows 7 to Windows 10. 

Working in an education environment I know I have the following to contend with:

1. BIOS and not UEFI machines
2. Roaming Profiles and Redirected Documents implemented
3. Precious Teaching data to preserve

First, the test bed.  I create a Generation 1 (BIOS) virtual machine on an UpgradeTest VM.  I install some education apps, add the machine to the domain and add in some data to preserve.

image

Once built I log on with my domain account.

I can see my user profile has been created on the server: image

I can see that the Sync Centre is present indicating my redirected documents are working and my education applications are present.

image

I have placed four files into my ‘Documents’ library and synchronised them with the server.  Now I will take a snapshot of the machine so I have a point in time to refer back to.

Moving over to my MDT server I’m going to create a new folder within my Task Sequences called Upgrade and then create a new task sequence in there…

imageimage

Give the sequence a Task Sequence ID  and a Task Sequence Name and then select a Standard Client Upgrade Task Sequence

imageimage

Choose your Windows 10 Enterprise (or other image) and select to Do not specify a product key at this time

imageimage

Set a Full Name, Occupation and Internet Homepage and set a local admin password

imageimage

Moving over to our Windows 7 Enterprise VM I’m going to launch the LiteTouch wizard from the Windows 7 test bed machine and just run the task sequence and see what happens….
(find the litetouch.vbs file within the scripts folder of your deploymentshare and launch it)

image

Every MDT Situation is different (and by that I mean everyone’s customsettings.ini file will be different) so there may be different options for you to select after choosing your task sequence.  Depending on which windows you’ve chosen to skip or not will determine what you see next.  I followed through mine and set it off.

image

Surely it cant be that easy, right?

image

No…. Surely not….

I logged in using my domain account once the machine had booted up.

image

Ok, so there are my files, my sync partnership is in place my programs are on (and still work as they should) and everything seems just fine.

image

I cant find anything wrong so far and I am blown away at how simple that is.

Update: 06.01.16 – Haven’t found anything wrong so rolled with it. Works every time.

Jonathan.

Comments (1) -

can I with a single server with mdt do this process? Or I need sccm 2012 installed on a domain?

Add comment