Embed Size (px)
Citation preview
Agenda
USMT’s capabilitiesToolsCommand line options
How to customize USMT
USMT covers the initial 90%
Customization can handle the last 10%
Overview of USMT 4.0Features
Captures and restores dataFiles and foldersRegistry keysWindows settingsLocal user accounts and group memberships
Enterprise-targetedUses the same core engine as Windows Easy Transfer, without the GUI but with additional configurationProvided as part of the free Windows Automated Installation Kit
Don’t miss the documentation, it’s there…
Handles differences between OSes
Overview of USMT 4.0Features
Differentiating featuresHardlink migration
If your existing partition structure is going to be keptBlazingly fast
Offline migrationIf the current OS isn’t functional or if you just want to start the process from Windows PE
Volume shadow copy supportWhen online and not using hardlinks
Understanding of Windows component configurationSimplifies the migration of Windows settingsExtra steps may be needed for offline migrations (e.g. printers, network connections)Watch out for http://support.microsoft.com/kb/2018593 if using ConfigMgr
Overview of USMT 4.0Features
Built-in support for migrating application settingsOffice 2003, 2007Office 2010 with optional hotfix
http://support.microsoft.com/kb/2023591
Several other consumer-oriented applications, but not much else
Opportunity for customization
Automatic identification of data filesHelper function that looks at file associationsTakes care of many types of application data (but not settings)
Overview of USMT 4.0Scenarios
RefreshCapture user data from existing OS (ideally with hardlinks)Wipe old OS (ideally without reformatting or repartitioning)Install new OS and applicationsRestore user data
ReplaceCapture user data from existing computer to a network or USB driveDispose of existing computerDeploy OS to a new computerRestore user data from network or USB drive
Overview of USMT 4.0Requirements
Source OSWindows XP and aboveClient OSes only
Target OSWindows Vista and aboveClient OSes only
PlatformsEverything but x64 to x86
Overview of USMT 4.0Tools
ScanstateCaptures user state
LoadstateRestores user state
USMTUTILSCleanup hardlink state stores
Customizing USMT 4.0Basic command line options
Always specify a store path and loggingSCANSTATE.EXE C:\StateStore /L:c:\ScanState.log /V:5LOADSTATE.EXE C:\StateStore /L:c:\LoadState.log /V:5
Specify which migration manifests to use/i:MigApp.xml /i:MigDocs.xml/i:MigApp.xml /i:MigUser.xmlDon’t use MigDocs.xml and MigUser.xml togetherMigDocs.xml is preferred to avoid needing to create custom XML files to migrate additional document typesSpecify migration manifests on both Scanstate and Loadstate to ensure proper behavior
/O to overwrite an existing store, if already present/hardlink /nocompress /efs:hardlink to use hardlinks/offline /offlinewindir:c:\windows or /offline /offlinewinold:c:\windows.old for offline migrations/localonly to ignore USB drives, network drives
Customizing USMT 4.0Command line options for users
Include and exclude users/UI:DOMAIN\User to explicitly include/UE:DOMAIN\User to explicitly exclude/UEL:90 to specify only user profiles modified in 90 days/ALL (default) to include all usersWatch out for unexpected results from combinations of parameters:
http://blogs.technet.com/b/askds/archive/2009/11/30/understanding-usmt-4-0-behavior-with-uel-and-ue.aspx
Create users in new OS/LAC or /LAC:password to create new accounts/LAE to enable the newly-created accountsIf /LAC isn’t specified, USMT will fail when attempting to restore the account
Change domain or user name/MD:OldDomain:NewDomain to specify different domain/MU:OldDomain\OldUser:NewDomain\NewUser to specify different user
Customizing USMT 4.0Using Config.xml
The Config.xml file serves multiple purposesControls how to handle errorsSpecifies which components should or shouldn’t be migratedControls how local group memberships are migrated
It’s an optional file, but is recommendedGenerate a starting point using /genconfig:MyConfig.xml and include all the migration manifestsTurn off components you don’t want to migrate
migrate=“no”
Make additional customizationsError control, profile control, etc.
Customizing USMT 4.0Command line options with MDT and ConfigMgr
Set task sequence variables with options to addOSDMigrateAdditionalCaptureOptions, OSDMigrateAdditionalRestoreOptions (ConfigMgr)ScanStateArgs, LoadStateArgs (Lite Touch)
Don’t duplicate options provided by defaultDon’t add logging parametersUse the provided mechanism for adding deployment manifests
OSDMigrateConfigFiles (ConfigMgr), USMTMigFiles (Lite Touch)USMTConfigFile (Lite Touch)
Watch out for conflicting optionsSpecify “Customize how user profiles are captured” with ConfigMgr to get rid of “/all”Some options might not be possible (e.g. changing encryption)
Make sure you specify appropriate paths to filesUSMT won’t go looking for them outside of the current working directory
Customizing USMT 4.0Creating custom manifests
From simple through complexUnconditional excludeMigrating files, folders and registry keysAdding detection rulesRun commands and scriptsHelper functions
GenerateDrivePatternsGenerateDocPatternsStartService, StopService, RegisterFonts, KillExplorer, RestartExplorer
Basic Custom XML-file
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/filemig"> <component type="Application" context="System"> <displayName>File Migration Test</displayName> <role role="Data"> <rules context="System"> <include> <objectSet> <pattern type="File">C:\Demo1\* [filename.txt]</pattern> <pattern type="File">C:\Demo2\* [*]</pattern> </objectSet> </include> </rules> </role> </component> </migration>
Customizing USMT 4.0Troubleshooting common issues
USMT doesn’t support Office 2010Make sure you install the updatehttp://blogs.technet.com/b/mniehaus/archive/2011/02/02/usmt-4-0-support-for-office-2010.aspx
Bad user profiles can cause issues (delays, failures)Clean them up or tell USMT to ignore them with MIG_IGNORE_PROFILE_MISSING=1http://blogs.technet.com/b/deploymentguys/archive/2010/03/28/usmt-failures-due-to-bad-profile-list-entries.aspx http://blogs.technet.com/b/askds/archive/2011/04/14/usmt-pauses-at-quot-starting-the-migration-process-quot-for-many-minutes-then-works.aspx
OS settings don’t migrate with ConfigMgrWe talked about that one, MDT fixes it but you might need a fix for the fix, see Office 2010 link abovehttp://support.microsoft.com/kb/2018593
Customizing USMT 4.0Troubleshooting common issues
Printers, drive mappings, etc. don’t migrate offline
USMT migrates user data from removable drives even with /localonly
It migrates USB disks even with /localonly, use an unconditional excludehttp://blogs.technet.com/b/deploymentguys/archive/2009/04/29/excluding-usb-firewire-and-other-drives-from-usmt-capture.aspx
Shortcuts to files on network drives don’t migrateKnown issue, you can modify MigUser.xml to remove section with IgnoreIrrelevantLinks (but then all links are retained, even invalid ones)
USMT fails with some half-hour timezonesInstall the USMT update for Office 2010, it fixes this too
Q u e s t i o n s ?
Speaker Blog: http://blogs.technet.com/b/deploymentguys/
Email: [email protected]
Please don’t forget your evaluations …
Need more information on DMVMUGVisit www.dmvmug.com or send a question to [email protected]
