ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 13e: In place migration XP to Windows 7
Back to main menu
Config Mgr is the only product that can carry out an in-place migration of XP to Windows 7 while retaining user data.
Part 13e of my Config Mgr 2012 SP1 Step by Step Guide details how to do this.
(Note that I carried out the process below pre-SP1 so there are references to WAIK. This has now been replaced with WADK).
The process is carried out as follows:
1. Create USMT Package
2. Create migration Task Sequence
3. Prepare test device and collection
4. Deploy the Task Sequence
5. Client migration
1. Create USMT Package (Note that this package is automatically created in Config Mgr 2012 SP1)
Locate the USMT folder in C:\Program Files\Windows AIK\Tools
Copy the folder to your Sources folder. This USMT folder will be used to create a Config Mgr package.
Right click Packages and choose "Create Package"
Browse to the source folder
Name the package and click Next
Choose "Do not create a program"
Click Next to create the USMT package. Don't forget to distribute it to the DPs. (not necessary in SP1)
2. Create refresh Task Sequence
Edit: Read this first before continuing. Some of these steps now cause this error in later versions of SCCM and USMT.
C:\_SMSTaskSequence\Packages\HOP00001\x86\migapp.xml ##ERROR## --> /nocompress /hardlink[gle=0x00000006]
An option is specified more than once and is ambiguous
Remove the steps
"Set USMT Additional Capture Options"
and
"Set USMT Additional Restore Options"
(These options were for ConfigMgr 2007 and used to work in ConfigMgr 2012 RTM - they don't seem to work any more).
and tick the box: "Capture locally by using links instead of copying files" (in the Capture User Files and Settings" step).
Right click Task Sequences and choose to "Create a new task sequence"
Choose to "Install and existing image package"
Name the task sequence and choose a boot image.
Choose your image and enter the licensing and local administrator details.
Note the important setting here - ensure the "Partition and format the target computer" box is unticked.
Configure the domain, OU and domain-join account.
Choose the Config Mgr client package.
Choose to "Capture user settings" and select the USMT package. In this case we will not use the State Migration Point (this is more suitable in a computer replace scenario).
Choose to "Save user settings locally". This is called hard linking.
Select your Software Update preference
Select any Config Mgr Applications you require.
Confirm your settings and click Next.
Click Close
Note that the task sequence has been created.
Right click the TS and choose Edit.
Choose to migrate all.
Note the Local State Location
Add a New Task Sequence Variable (Set USMT Additional Capture Options)
Configure the new variable as shown
Variable: OSDMigrateAdditionalCaptureOptions
Value: /nocompress /hardlink
Verify the USMT package and settings
Verify the OS image settings. Note that there is no "Partition Disk" stage in this TS.
Verify licensing information and local administrator account settings.
Verify domain, OU and domain-join account.
Verify Config Mgr Client package
Add a New Task Sequence Variable (Set USMT Additional Restore Options)
Variable: OSDMigrateAdditionalRestoreOptions
Value: /nocompress /hardlink
Verify USMT restore settings
Edit: Read this first before continuing. Some of these steps now cause this error in later versions of SCCM and USMT.C:\_SMSTaskSequence\Packages\HOP00001\x86\migapp.xml ##ERROR## --> /nocompress /hardlink[gle=0x00000006]
An option is specified more than once and is ambiguous
Remove the steps
"Set USMT Additional Capture Options"
and
"Set USMT Additional Restore Options"
(These options were for ConfigMgr 2007 and used to work in ConfigMgr 2012 RTM - they don't seem to work any more).
and tick the box: "Capture locally by using links instead of copying files" (in the Capture User Files and Settings" step).
3. Prepare test device and collection
Test XP device with test file saved to desktop .
Note existing profiles.
Test Collection containing test device.
4. Deploy the Task Sequence
Right click the task sequence and select Deploy
The "Deploy Task Sequence Wizard" starts. Select the TS and the test collection.
Choose "Required"
Choose "As soon as possible"
Click Next to continue.
5. Client migration
XP device with test file on desktop.
Manually retrieve "Machine Policy" (not required - saving time)
Notified that software is available
The task sequence starts and sets the Local State Location.
User data is being captured by USMT and saved to the Local State location (scanstate.exe)
Manifest files are being downloaded. They are required for USMT to be able to capture all user settings.
Computer now downloads the boot images and restarts (will boot into Windows PE).
Stages boot image
Restarts
Computer boots into Windows PE
Downloads image file
The computer hard drive could not be formatted as the user data has been saved (hard linked) to the "Local State location" and would be lost. The remainder of the drive is now wiped.
OS image is applied
Computer restarts
Config Mgr client installs and initialises
User data is restored by USMT (loadstate.exe)
Windows 7. Note test file on desktop.
Config Mgr is the only product that can carry out an in-place migration of XP to Windows 7 while retaining user data.
Part 13e of my Config Mgr 2012 SP1 Step by Step Guide details how to do this.
(Note that I carried out the process below pre-SP1 so there are references to WAIK. This has now been replaced with WADK).
The process is carried out as follows:
1. Create USMT Package
2. Create migration Task Sequence
3. Prepare test device and collection
4. Deploy the Task Sequence
5. Client migration
1. Create USMT Package (Note that this package is automatically created in Config Mgr 2012 SP1)
Locate the USMT folder in C:\Program Files\Windows AIK\Tools
Copy the folder to your Sources folder. This USMT folder will be used to create a Config Mgr package.
Right click Packages and choose "Create Package"
Browse to the source folder
Name the package and click Next
Choose "Do not create a program"
Click Next to create the USMT package. Don't forget to distribute it to the DPs. (not necessary in SP1)
2. Create refresh Task Sequence
Edit: Read this first before continuing. Some of these steps now cause this error in later versions of SCCM and USMT.
C:\_SMSTaskSequence\Packages\HOP00001\x86\migapp.xml ##ERROR## --> /nocompress /hardlink[gle=0x00000006]
An option is specified more than once and is ambiguous
Remove the steps
"Set USMT Additional Capture Options"
and
"Set USMT Additional Restore Options"
(These options were for ConfigMgr 2007 and used to work in ConfigMgr 2012 RTM - they don't seem to work any more).
and tick the box: "Capture locally by using links instead of copying files" (in the Capture User Files and Settings" step).
Right click Task Sequences and choose to "Create a new task sequence"
Choose to "Install and existing image package"
Name the task sequence and choose a boot image.
Choose your image and enter the licensing and local administrator details.
Note the important setting here - ensure the "Partition and format the target computer" box is unticked.
Configure the domain, OU and domain-join account.
Choose the Config Mgr client package.
Choose to "Capture user settings" and select the USMT package. In this case we will not use the State Migration Point (this is more suitable in a computer replace scenario).
Choose to "Save user settings locally". This is called hard linking.
Select your Software Update preference
Select any Config Mgr Applications you require.
Confirm your settings and click Next.
Click Close
Note that the task sequence has been created.
Right click the TS and choose Edit.
Choose to migrate all.
Note the Local State Location
Add a New Task Sequence Variable (Set USMT Additional Capture Options)
Configure the new variable as shown
Variable: OSDMigrateAdditionalCaptureOptions
Value: /nocompress /hardlink
Verify the USMT package and settings
Verify the OS image settings. Note that there is no "Partition Disk" stage in this TS.
Verify licensing information and local administrator account settings.
Verify domain, OU and domain-join account.
Verify Config Mgr Client package
Add a New Task Sequence Variable (Set USMT Additional Restore Options)
Variable: OSDMigrateAdditionalRestoreOptions
Value: /nocompress /hardlink
Verify USMT restore settings
Edit: Read this first before continuing. Some of these steps now cause this error in later versions of SCCM and USMT.C:\_SMSTaskSequence\Packages\HOP00001\x86\migapp.xml ##ERROR## --> /nocompress /hardlink[gle=0x00000006]
An option is specified more than once and is ambiguous
Remove the steps
"Set USMT Additional Capture Options"
and
"Set USMT Additional Restore Options"
(These options were for ConfigMgr 2007 and used to work in ConfigMgr 2012 RTM - they don't seem to work any more).
and tick the box: "Capture locally by using links instead of copying files" (in the Capture User Files and Settings" step).
3. Prepare test device and collection
Test XP device with test file saved to desktop .
Note existing profiles.
Test Collection containing test device.
4. Deploy the Task Sequence
Right click the task sequence and select Deploy
The "Deploy Task Sequence Wizard" starts. Select the TS and the test collection.
Choose "Required"
Choose "As soon as possible"
Click Next to continue.
5. Client migration
XP device with test file on desktop.
Manually retrieve "Machine Policy" (not required - saving time)
Notified that software is available
The task sequence starts and sets the Local State Location.
User data is being captured by USMT and saved to the Local State location (scanstate.exe)
Manifest files are being downloaded. They are required for USMT to be able to capture all user settings.
Stages boot image
Restarts
Computer boots into Windows PE
Downloads image file
The computer hard drive could not be formatted as the user data has been saved (hard linked) to the "Local State location" and would be lost. The remainder of the drive is now wiped.
OS image is applied
Computer restarts
Config Mgr client installs and initialises
User data is restored by USMT (loadstate.exe)
Windows 7. Note test file on desktop.
No comments:
Post a Comment