Performing hard-link migrations is the recommended action in Refresh Computer scenarios, and this is the default behavior of MDT 2010. For other scenarios, you can create the data stores within the MDT 2010 deployment share. However, creating a share for the data stores on a separate server is better than putting the data stores in the deployment share because it spreads the load and allows you to dedicate resources to user state migration more easily.
After creating the share for the data stores, you configure the data store location by customizing properties in each deployment share's CustomSettings .ini file, as shown in Figure 7-4 . To configure CustomSettings .ini, right-click a deployment share in Deployment Workbench and click Properties; then configure CustomSettings .ini on the Rules tab . You can also customize these properties in the MDT 2010 database. Table 7-3 describes these properties . For more information about CustomSettings .ini and the MDT 2010 database, see Chapter 12, "Deploying with Microsoft Deployment Toolkit."
table 7-3 USMT Properties in MDT 2010
The arguments passed to LoadState . MDT 2010 inserts the appropriate logging, progress, and data store parameters. If this value is not included in the settings file, ZTIUserState .wsf uses LoadStateArgs=/v:5 /c /lac.
The arguments passed to ScanState. MDT 2010 inserts the appropriate logging, progress, and data store parameters. If this value is not included in the settings file, ZTIUserState .wsf uses ScanStateArgs=/v:5 /o /c. Use the property USMTMigFiles to specify the .xml files to be used by Scanstate . exe instead of using the /i parameter in the ScanStateArgs property. This prevents the ZTIUserState script from potentially duplicating the same list of .xml files .
The network share in which to create data stores, such as UDDShare=\\server\MigData$. This value is ignored when performing hard-link migrations .
The folder where the user state migration data is stored This folder exists beneath the network shared folder specified in UDDShare. For example, UDDir=%ComputerName%. This value is ignored when performing hard-link migrations .
UserDataLocation=[6lan^ | AUTO | NETWORK | NONE]
The location in which user state migration data is stored:
■ BLANK For LTI, the Windows Deployment Wizard prompts for the storage location . For ZTI, this is the same as setting the property to NONE
■ AUTO MDT 2010 performs a hard-link migration.
■ NETWORK MDT 2010 creates the data store in the location designated by the UDDShare and UDDir properties
UDProfiles=Profileî, Profile2, ProfileN
A list of user profiles to save during the MDT 2010 State Capture phase by Scanstate. exe, such as UDProfiles=Administrator, Patrice, Dave .
NOTE You can also use removable media and local data stores during a user state migration by not setting the UserDataLocation value. The Windows Deployment Wizard will prompt you for the user data location. See the Toolkit Reference in MDT 2010 for more details about these properties.
Was this article helpful?