Refresh scenario. Windows XP to Windows 7

[ZA_IT]

I have a couple of questions on deploying Windows 7. Using MDT 2010, WAIK 2.0 and SCCM 2007 R2 SP2 (RC). I'm primarily working with a refresh scenario (wipe and load) moving from Windows XP to Windows 7.

 

- Will USMT 4 work on XP doing a scanstate with hard link? Hoping to save time and not use server space to store the user state.

 

- Will the wipe and load scenario execute successfully if I use Wake on LAN / PXE boot into Windows PE? Specifically will USMT successfully gather the user state in PE or must the USMT scanstate run in Windows XP.

 

 

Does anyone have an example task sequence for this refresh scenario or know where I can find one?

[anyweb]

hi there

 

Will USMT 4 work on XP doing a scanstate with hard link? Hoping to save time and not use server space to store the user state.

 

yes it will

 

 

Will the wipe and load scenario execute successfully if I use Wake on LAN / PXE boot into Windows PE? Specifically will USMT successfully gather the user state in PE or must the USMT scanstate run in Windows XP.

 

I run USMT scanstate from Within windows XP, here is an example of a hardlinking task sequence from XP to 7

 

ts_windows_with_hardlinking.zip (from Jannes)

 

of course you will have to replace the packages mentioned in the TS with your own, and here's some info from Peter's blog about hardlinking

 

 

cheers

niall

[ZA_IT]

Hi

 

Thanks a million for the reply! Everything works well up until after the image has been applied and SCCM installed. The process then reboots to the Windows 7 logon screen (Press CTRL + ALT + DEL) and doesn't automatically logon and restore user state.

 

If I manually log on then the the task sequence does not resume.

 

I assume something needs to be changed in the unattend.xml file but have no idea how to get the thing to logon and resume with the USMT loadstate.

 

Any advice?

[anyweb]

we'd need to see your smsts.log file to see what has failed

[Eswar Koneti]

Hi,

My setup is running with SCCM SP2,MDT 2010.I testing out on Upgradaing Win XP to Win7.Advertised TS on to the collection where it has XP machines to promote to Win 7.When i ran the TS,It fails in giving the error 0x00004005 while it is capturing the network settings.

This issue is happening bcz of USMT version.Attached is the Log file.win7 requries USMT 4.0 which was added to TS and winxp is wotks with USMT 3.0.I am not sure to get it work .any information on this ?

smsts.log

[Peter van der Woude]

USMT 4.0 works for Restoring and Capturing Windows 7 and also works for Capturing Windows XP.

[anyweb]

and here's yet another post about how to do it (hardlinking etc)

 

http://myitforum.com/cs2/blogs/nbrady/archive/2010/01/26/migrating-windows-xp-to-windows-7-using-hardlinking-setting-up-a-demo.aspx

[Eswar Koneti]

Okay,are there any findings from the smsts.log file.I have gone through the 2 Ts's (SMP and Hardlink).are there any scripts needs to be added for the Task Actions ? I imported the Hardlink TS and given the packages according to it.I ran it on WinXP os and system get restarted,after some time ,it gives me the error01,later error 02 and keeps on restarting several times by giving the same error02.