sample XP to Windows 7 task sequences

[anyweb]

hi all,

 

as this is a common requirement, here are two Task Sequences I use for demoing Windows XP migrations to Windows 7,

 

Related Reading:-

 

OSDMigrateAdditionalCaptureOptions on Technet

OSDMigrateAdditionalRestoreOptions on Technet

 

Before you can use these sample task sequences you must have done the following Steps.

 

Using Computer Association add a computer to your Deploy XP collection, and then Deploy Windows XP to that computer. Once Deployed with XP you can use Direct Membership to add that computer to the Migrate XP to 7 Collection described below.

 

XP to Windows 7 Demo - X86 using Hardlinking

 

The first task sequence XP to Windows 7 Demo - X86 using Hardlinking.xml will migrate XP to Windows 7 using hardlinking

 

XP to Windows 7 Demo - X86 using Hardlinking.xml

 

XP to Windows 7 Demo - X86 using SMP

 

The second one uses a SMP *State Migration Point*

 

XP to W7 Demo - X86 using SMP.xml

 

simply import these task sequences into ConfigMgr, and replace the missing package references (configmgr X86 boot images, microsoft deployment 2010 settings, mdt2010 files, windows 7 autologin enable package, usmt4 package and the Windows 7 X86 WIM file itself).

 

 

See below screenshots to help you with that

 

 

Task Sequence References with hardlinking

 

 

 

Task Sequence References with SMP

 

 

and then advertise the task sequences to a migrate XP to Windows 7 collection

 

 

add computers to the Migrate XP to Windows 7 collection and kick off the appropriate TS via RAP.

[jortiz]

Still do not see it.

[Wave~Chaser]

Hi,

 

I used your xml file, but he PXE boot if greyed out. I need to be able to PXe boot the pc to this advertisement. How can I do that?

[danovich]

Same process if we are going to Win 7 x64 version?

[Peter van der Woude]

Correct. Just remember to use x64 version of scanstate/loadstate on x64 OS and x86 version on x86 OS.

[TechGuy83]

Thanks for the example. I used the hardlinking example as some profiles have large PST files stored within them.

 

I ran in to 1 minor issue, if you don't reset the computer account on AD then of course the machine will not join again. Some of our deployment guys were deleteing machines (which was most helpful) and then of course losing the group memberships.

 

I added a TS step using Netdom, part of the remote tools set available here http://www.microsoft...lang=en&id=7887 as SCCM SP2 uses winpe3 (win 7). Just copy the exe to a package and then run the command netdom reset machinename /domain:domainname

 

Hope that helps anyone running into issues re-joining the machine back to domain.

 

Thanks again

[retrosole]

Hi guys,

 

I was able to import the hardlink TS provided by anyweb, and it ran through fine with no errors. However, nothing was restored. The computer name stayed the same, and the "StateStore" folder is still in C. Everything else look like a fresh install of Win 7.

 

Note - we do redirect the user profiles to D in our XP and Win 7 images. I'm not sure if that is causing the problem, or I'm missing something else.

 

Thanks.

[hafiy]

I was unable to download the sample of .xml file (hardlink & SMP)..

 

I was planning to migrate Windows XP to Windows 7, without formatting the drive D, but before that I want to copy some important file from c:\windows\system32\ccm\inventory\a.mif file to D:\backup\

 

How can I do this, can anyone tell me how I want to create the TS?

Can I use the USMT package?

 

Please guide me

[TechGuy83]

Ok not sure if someone will beat me to it, hardlink is always a good option as its quick as no data is copied however if you have full device encryption like us you will have to first remove the encryption. And in our case then chain it to a desk in a locked room...

 

You need setup 3 TS variables with the following values, as follows:

OSDStateStorePath - %_SMSTSUserStatePath%

OSDMigrateAdditionalCaptureOptions - /hardlink /nocompress

OSDMigrateAdditionalRestoreOptions - /Hardlink /nocompress

 

After those 3 variables place a Capture User State step and select your USMT package (if you don't have use MDT to create one) and then select the 'radio button customize how user profiles are captured' and add the following files:

migapp.xml

migdocs.xml

miguser.xml

 

Now for capturing your MIF file, I have not tested this but it should work in theory as always test before going live. Add additional step of run command line and enter copy "c:\windows\system32\ccm\inventory\a.mif" "%OSDStateStorePath%\a.mif" /v /y this should then copy the file to the same as the hardlinked files.

 

Now restart in PE, do the normal for applying the windows 7 image but don't use the format and partition disk as the disk has a partition everything will be wiped apart from the hardlinked folder.

 

At the end a step Restore User State again add the USMT package, restore all captured user profiles with standard options. And of course copy back your a.mif file to the directory of choice.

 

That is how to do it with hardlinking.

 

This information has been taken from the example file attached at the beginning of the post. We have 1 additional step, I have created a VB script that resets the machine account on AD before restarting in PE so that the same machine account can be used to save having to re-add the machine to all the groups it once belonged to again.

 

I hope that helps you.

[hafiy]

I used the sample of hardlink TS but it seems like the profiles and files (excel, word, powerpoint, pst) is failed to restore. I don't know what is wrong

 

For Capture User State and Restore User State when I add the USMT package (x86 and x64), I choose to restore all captured user profiles with standard options only. But, I had change the miguser.xml file under USMT4.01 folder. Is this step ok?

 

Really appreciate any advice from expert!!

[tushard]

Hi Peter,

My .wim file is installed on another partition instead of C: (Where XP installed), means after Win 7 installed i have found installation dir d: instead of C: drive i am not using any sysprep or unattend.xml file as mentioned at top portion anyweb comments " you don't need it, it's nothing more than a customised unattend.xml file which you can Deploy 7 without "