User migration in PXE boot

[firstcom]

Hello all,

 

I've been exploring migrating user data, windows settings and network settings whenever we perform a re-image (Win7->Win7)

 

The process seems to work when it's deployed and executed via Software Center, but not when it's performed directly from a PXE boot. I have my task sequence set to capture windows settings, capture network settings, and then begin the three step process of capturing the user files and settings.

 

However, in PXE, it never gets beyond Capture Network Settings. It crashes, with SMSTS.LOG saying "Request is not supported"

 

Do I need to do something additional to get this to work in PXE/offline media? What aspects of migrating settings and user data is not supported with PXE?

[Peter van der Woude]

For a capture in WinPE, make sure that you are using the option to capture in off-line mode.

[firstcom]

Thanks Peter! I did not even notice that option until you had mentioned it. Two questions:

 

1. It isn't even getting to that step before it crashes. In the event that I load the PC into a PXE session from the BIOS, it crashes on "Capture Network Settings" with the above error.

2. If I enable offline mode capture, will that impact the task sequence when I choose to remain online? If it detects a connection, will it still capture online, or always default to offline? Further, how does it capture it offline? Does it copy the files to the USB drive?

 

 

For a capture in WinPE, make sure that you are using the option to capture in off-line mode.

[Peter van der Woude]

You have to make sure that only supported steps are started in the different scenario's. To make sure that it happens, you can use task sequence variables. I did a post about that a while ago. There might be scenarios that are not covered,but it should give you an idea, see: http://www.petervanderwoude.nl/post/how-to-capture-user-files-and-settings-offline-winpe-or-online-fullos-using-hard-links-with-configmgr-2012-b2/

[firstcom]

Thanks Peter! This page was very helpful.

 

Does both hard-linking and the offline method work when you format and partition the hard drive offline? I'm considering a situation where we are at a low-bandwidth site that has a crashed physical device and want to start with a pretty clean slate.

 

You have to make sure that only supported steps are started in the different scenario's. To make sure that it happens, you can use task sequence variables. I did a post about that a while ago. There might be scenarios that are not covered,but it should give you an idea, see: http://www.petervanderwoude.nl/post/how-to-capture-user-files-and-settings-offline-winpe-or-online-fullos-using-hard-links-with-configmgr-2012-b2/

[Peter van der Woude]

Yes, hard-linking and offline capture can be used together.

 

One thing to keep in mind is that hard-linking stores pointers to files locally on a hard drive, that's what makes the process fast. That also means that there is no buildin method to store it on a network location, as copying hard-links simply copies the complete file instead of the pointer (which is logic as you can't point from a network location to something on the local hard drive).

[firstcom]

I am not all that familiar with hard-linking, but if I'm re-imaging a PC and having it partition and format the drive, how does it store the user and Windows data? On the local thumb drive? Obviously the data is stored before the format and is then restored afterwards... just wanting to confirm how it all works.

 

Thanks!

 

 

Yes, hard-linking and offline capture can be used together.

 

One thing to keep in mind is that hard-linking stores pointers to files locally on a hard drive, that's what makes the process fast. That also means that there is no buildin method to store it on a network location, as copying hard-links simply copies the complete file instead of the pointer (which is logic as you can't point from a network location to something on the local hard drive).

[anyweb]

no it does a special format called a WIPE where it removes everything on the hard drive except the data you want to save (via custom XML rules), that data is then saved in a special folder (statestore) and the task sequence then installs Windows on on the wiped drive, when done it restores the files that were hard linked back to their original place

 

here's an example custom xml file for doing just that

 

http://www.niallbrady.com/2012/08/16/migrate-me-to-windows-8/