This post will be another one about capturing user files and settings, but this time with ConfigMgr 2012 B2. I hope everyone still remembers my post about capturing user files and settings in ConfigMgr 2007 (and especially how much work it was). Usually I’m not really into writing ‘step-by-step guides’, but this time I will make an exception. The reason why I’m making this exception is that I want to show how easy it’s done now. It’s becoming really close to just next-next-finish. There are only four packages needed for/ by this step-by-step:
- Boot image package
- ConfigMgr client package
- USMT 4.0 package
- Image package
When these packages are present, right-click the Task Sequence node and select Create Task Sequence. After that follow the step-by-step below.
|
On the Create a New Task Sequence page, select Install an existing image package and click Next |
 |
|
On the Task Sequence Information page, fill in a Task sequence name, Browse for the Boot image and click Next. |
 |
|
On the Install Windows page, browse for the Image package, uncheck Partition and format the target computer before installing the operating system, (optional) fill in a Product key, (optional) select Always use the same administrator password and click Next. Note: It’s really important to uncheck Partition and format the target computer before installing the operating system, because otherwise it’s not possible to store the data locally. |
 |
|
On the Configure Network page, (optional) select Join a domain, Browse for the Domain and Domain OU, Set an Account and click Next. |
 |
|
On the Install ConfigMgr page, Browse for the ConfigMgr client Package, (optional) fill in the Installation Properties and click Next. |
 |
|
On the State Migration page, select Capture user settings, Browse for the USMT Package, select Save user settings locally and click Next. |
 |
|
On the Install Updates page, click Next. Note: As these settings are not part of the step-by-step, they are left to default. |
 |
|
On the Install Applications page, click Next. Note: As these settings are not part of the step-by-step, they are left to default. |
 |
|
On the Summary page, click Next. |
 |
|
On the Progress page, just wait… |
 |
|
On the Confirmation page, click Close. |
 |
Now the basic task sequence is ready and it only needs a little bit of ‘tweaking’. This can be done with the Task Sequence Editor. Also notice that the basic task sequence already sets the ‘extra’ task sequence variable OSDStateStorePath.
|
Select the Capture Files and Settings Group, go to the Options tab and Remove the Conditions (or remove the whole top Group). Note: This is necessary to make it possible to also capture user files and settings in WinPE. |
 |
|
Select the Capture User Files and Settings Step (optional: change the name), select Copy by using file system access and check Continue if some files cannot be captured and Capture locally by using links instead of copying files. Now go to the Options tab and add the condition of _SMSTSInWinPE equals FALSE. Note: This is necessary to make this step only run in FullOS. |
 |
|
Add an extra Capture User State Step (optional: change the name), select Copy by using file system access and check Continue if some files cannot be captured, Capture locally by using links instead of copying files and Capture in off-line mode (Windows PE only). Now go to the Options tab and add the condition of _SMSTSInWinPE equals TRUE. Note: This is necessary to make this step only run in WinPE. |
 |
The task sequence is now done and ready to be deployed. The result is a task sequence that will do a hard-link migration in both, WinPE or FullOS.
