Migrating data in refresh scenarios – Microsoft Surface 3 User Manual

Page 162

Advertising
background image

© 2014 Microsoft

Page 162

UDDir=%OSDComputerName%

This will create a folder with the computer name on the share UserData on the deployment server. The user credentials

specified in the rules or when launching the Windows Deployment Wizard must have write permission to this share.

Note: The replace computer task sequence requires no image files and thus is very lightweight. A potential solution to

allow the rules for the deployment share to remain unaltered while providing a separate experience for running the
replace computer task sequence is to create offline boot media with the replace computer task sequence.

Rules must also be configured for the deployed computer to select the backed-up data. As with the retiring computer,

the MAC address can be used to isolate the rules to the replacement computer. The following rules are very similar to
those used to back up the user state, with the exception of adding the UDDir rule, which indicates the folder where the
backup resides. The computer name of the deployed computer will likely not match the computer name of the retiring
computer, so to ensure that the correct directory is used, the computer name of the retiring computer should be
explicitly defined.

[00:00:00:00:00:00]
SkipComputerBackup=YES
SkipUserData=YES
UserDataLocation=NETWORK
UDShare=\\SP3ProdDeploy\UserData
UDDir=RetiringComputer

Migrating Data in Refresh Scenarios

In some scenarios, a new operating system image may be deployed to an existing computer that will continue to be

used by the same user. This is the refresh scenario, where the user’s data should be restored to the same system where
it is backed up. The replace scenario rules will still work for a refresh scenario, but can be greatly simplified and
performance increased by using hardlink storage of the user data. With hardlink storage, the user’s data is not removed
from the system but kept on the storage device and restored when the new image has been deployed.

Unlike the replace scenario, a replace computer task sequence is not required to back up user data. Modify the [Surface

Pro 3] section of the rules for the production deployment share shown in the

Customizing Rules for Automation section

of Chapter 5

to match the following configuration:

[Surface Pro 3]
SkipTaskSequence=YES
TaskSequenceID=SP3Win8.1EntCst
SkipComputerBackup=YES
SkipUserData=YES
UserDataLocation=AUTO
UDShare=\\SP3ProdDeploy\UserData
UDDir=%OSDComputerName%

These rules specify that the Surface Pro 3 deployment task sequence should be run on all Surface Pro 3 models boot

from this media and that any user data should be backed up using hardlinks if possible, or the network location if it is
not possible. When UserDataLocation is set to AUTO, the deployment process will determine if there is enough room

Advertising