TechMentor Fall, 2011 - Automating User Data Migration Duing Windows 7 Migrations

  • 679 views
Uploaded on

Deploying Windows 7 is a snap when you’re doing it to a brand new computer. But brand new computers are only part of the problem. What you also need is Windows 7 migration and upgrades. You also …

Deploying Windows 7 is a snap when you’re doing it to a brand new computer. But brand new computers are only part of the problem. What you also need is Windows 7 migration and upgrades. You also want a solution that refreshes Windows 7 with a minimum of effort. Part of doing that requires automatically offloading user data from their old computer, then injecting it onto their new one. There are free tools from Microsoft to do this, and they’re even customizable! Microsoft MVP and deployment expert Greg Shields shares the secrets of Microsoft’s User State Migration Toolkit, a sometimes-missed solution for automating user data migration that you’ll absolutely want in your deployment solution.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
679
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
11
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • TechMentor Las Vegas 2011
  • TechMentor Las Vegas 2011

Transcript

  • 1. Windows 7 Deployment Deep Dive Automating User Data Migration from Old Desktop to New Greg Shields, MVP, vExpert Concentrated Technology www.ConcentratedTech.com
  • 2. How Far We’ve Come…
    • Installing Windows Deployment Server
    • Configuring Image Deployment
    • Deploying your First Image
    • Dealing with Drivers
    • Automating WinPE Boot Image
    • Automating the “Set Up Windows” Phase
    • Creating a Thick Image w. Applications
    • Installing Microsoft Deployment Toolkit
    • Silent Installations & Repackaging
    • Layering Applications atop Windows
    • Preserving User Data
  • 3. Step 11: Preserving Personality
    • Remember, we’re layering here!
      • Alright! Dead horse, really , really beaten by this point.
  • 4. Step 11: Preserving Personality
    • Remember, we’re layering here!
      • Alright! Dead horse, really , really beaten by this point.
    Secret Tip : Avoid re-layering configurations that are better managed via GPs / GPPs. Makes life easier both during and after the migration, as GPs & GPPs are long-lasting.
  • 5. Step 11: Preserving Personality
    • MDT’s User State Migration Toolkit handles capturing and replacing user data.
      • Built directly into MDT. Updatable.
      • Is easiest available when a deployment is started within the old operating system.
      • Launch this to begin: {server}deploymentshare$scriptsLiteTouch.vbs
    • Secret Trick : This script can be wrapped into an HTA, or deployed via a GPP for improved automation.
  • 6. Important Gotcha #1
    • Seriously, get off the XP will ya’?
  • 7. Important Gotcha #2
    • Seriously, get off the x86 will ya’?
    • You can migrate a 32-bit operating system to a 64-bit operating system.
    • However, you cannot migrate a 64-bit operating system to a 32-bit operating system.
  • 8. Use Case #1 – PC Refresh
    • … using a compressed migration store.
    • … using a hard-link migration store.
    • … using Windows.old & a hard-link migration store.
  • 9. Use Case #2 – PC Replacement
    • … using a manual network migration.
    • … using a managed network migration.
    • … using offline migration via Windows PE.
  • 10. Important Gotcha #3
    • USMT will not migrate the following settings…
      • Local printers, hardware-related settings, drivers, passwords, application binary files, synchronization files, DLL files, or other executable files.
      • Files and settings migrating between operating systems with different languages.
      • Customized icons for shortcuts.
      • Taskbar settings when the source computer is running Windows XP.
      • Network printers and some firewall settings when the source computer is running Windows XP.
  • 11. USMT’s Two Steps
    • State Capture Phase
      • Capture User State Initiates ZTIUserState.wsf /Capture
  • 12. USMT’s Two Steps
    • State Capture Phase
      • Capture User State Initiates ZTIUserState.wsf /Capture
    • State Restore Phase
      • Restore User State Initiates ZTIUserState.wsf /Restore
  • 13. USMT’s Two Steps
    • State Capture Phase
      • Capture User State Initiates ZTIUserState.wsf /Capture
    • State Restore Phase
      • Restore User State Initiates ZTIUserState.wsf /Restore
    • Both steps use settings (Rules) from CustomSettings.ini or within the MDT Database.
      • Do not modify ZTIUserState.wsf. Really.
      • Instead, customize the content it seeks to preserve.
  • 14. Automating USMT
    • Automating USMT requires answering its questions within MDT first.
      • This is done through the Rules tab under [Default].
  • 15. Customizing USMT, Where Things Get Hard
    • Three XML files are available out of the box:
    • MigApp.XML
      • Contains information about application settings to be migrated.
    • MigUser.XML
      • Will migrate user profiles in a more general sense.
      • Focuses first on documents in user profile, then globally by file extension.
    • MigDocs.XML
      • Used when tighter control over documents to be migrated is required.
  • 16. Customizing USMT, Where Things Get Hard
    • Three XML files are available out of the box:
    • MigApp.XML
      • Contains information about application settings to be migrated.
    • MigUser.XML
      • Will migrate user profiles in a more general sense.
      • Focuses first on documents in user profile, then globally by file extension.
    • MigDocs.XML
      • Used when tighter control over documents to be migrated is required.
    You will use MigUser.XML or MigDocs.XML, but not both . When in doubt, use MigUser.XML.
  • 17. DEMO: VIEWING THE MIGS
  • 18. What to Migrate?
    • Determine what to migrate.
      • End-user information, applications settings, operating-system settings, files, folders, and registry keys.
  • 19. What to Migrate?
    • Determine what to migrate.
      • End-user information, applications settings, operating-system settings, files, folders, and registry keys.
    • Adding things to migrate…
      • is typically done by creating one or more custom XML files.
      • You can alter the MIGs, but it gets complicated.
    • Removing things to migrate…
      • is done by creating and modifying a Config.XML file.
    Removing things is easier than adding them!
  • 20. Removing Items from Migration Not that Tough
    • USMT will migrate a standard set of items.
      • Removing items from migration requires modifying the MIGs with a Config.XML file.
    • First, create that Config.XML file.
      • Scanstate.exe /genconfig:<path>Config.XML /i:migapp.xml /i:miguser.xml
  • 21. Removing Items from Migration Not that Tough
    • Open Config.XML in a text editor (not IE).
  • 22. Removing Items from Migration Not that Tough
    • Open Config.XML in a text editor (not IE).
    STEPPING BACK: Consider this Config.XML file as a long list of all the possible things USMT could do . Its contents are based on the instructions outlined in the MIGs, along with any custom XML files you create (a process to be discussed in a minute). With it, you can note the things you don’t want USMT to do.
  • 23. Removing Items from Migration Not that Tough
    • Remove items by setting “migrate=no”.
  • 24. Adding Items to Migration Much more Difficult
    • Adding items to a migration requires creating one or more custom XML files.
      • These files contain the instructions telling USMT what must be migrated – across both files and registry keys.
      • You must hand-code these.*
      • * Sort of.
  • 25. Adding Items to Migration Much more Difficult
    • Adding items to a migration requires creating one or more custom XML files.
      • These files contain the instructions telling USMT what must be migrated – across both files and registry keys.
      • You must hand-code these.*
    • Adding items requires much of the same skills you learned in automatically deploying software.
      • Figuring out “what happened”.
  • 26. Adding Items to Migration Much more Difficult
    • Adding items to a migration requires creating one or more custom XML files.
      • These files contain the instructions telling USMT what must be migrated – across both files and registry keys.
      • You must hand-code these.*
    • Adding items requires much of the same skills you learned in automatically deploying software.
      • Figuring out “what happened”.
    • Custom migration files are typically called in MDT after calling the MIGs.
      • Doing custom work last ensures that supporting data is copied prior to custom data.
  • 27. Adding Items to Migration Much more Difficult Migrate all the files in C:UserDocuments and all subfolders, except for Sample.doc.
  • 28. Adding Items to Migration Much more Difficult Migrate all the files in C:UserDocuments and all subfolders, except for Sample.doc. Notice how <include> and <exclude> items are discretely configured…
  • 29. Adding Items to Migration Much more Difficult Secret Trick to migrate the “Presentations” folder, no matter where it resides on C:.
  • 30. Adding Items to Migration Much more Difficult Super Advanced Secret Trick : Use the .GenerateDrivePatterns method to migrate any folder named “Requests” anywhere.
  • 31. Adding Items to Migration Much more Difficult Migrate registry values found in this location, whether in HKCU or HKLM.
  • 32. Adding Items to Migration Much more Difficult <stuff> </stuff> Syntax here is absolutely important, including case-sensitivity. Bad syntax with XML means it no workey .
  • 33. XML Validation, Will it Work? You’ll Need Some Help Here…
  • 34. XML Validation, Will it Work? You’ll Need Some Help Here… An XSD file is used to validate an XML file. USMT comes with one in /USMT/x64/MigXML.XSD. Add it under Schemas and it will find errors.
  • 35. XML Validation, Will it Work? You’ll Need Some Help Here… USMT Builder is a third-party solution. Far easier! http://www.wintools.com.au/
  • 36. Integrating MIGs with MDT
    • Final step: Add the MIGs of importance to MDT.
      • Make sure to add them in the correct order.
  • 37. Argh! ScanStateArgs!
    • Not quite done.
      • We have decisions to make about how ScanState should operate, specifically which users to migrate ?
  • 38. Argh! ScanStateArgs!
    • Not quite done.
      • We have decisions to make about how ScanState should operate, specifically which users to migrate ?
      • /all – Migrate all users.
      • /ui:DomainNameUserName – Migrate this user.
      • /ui:ComputerNameLocalUserName – Migrate this user.
  • 39. Argh! ScanStateArgs!
    • Not quite done.
      • We have decisions to make about how ScanState should operate, specifically which users to migrate ?
      • /all – Migrate all users.
      • /ui:DomainNameUserName – Migrate this user.
      • /ui:ComputerNameLocalUserName – Migrate this user.
      • /uel:NumberofDays – Migrate users who have logged on within the NumberofDays.
  • 40. Argh! ScanStateArgs!
    • Not quite done.
      • We have decisions to make about how ScanState should operate, specifically which users to migrate ?
      • /all – Migrate all users.
      • /ui:DomainNameUserName – Migrate this user.
      • /ui:ComputerNameLocalUserName – Migrate this user.
      • /uel:NumberofDays – Migrate users who have logged on within the NumberofDays.
      • /ue:DomainNameUserName – Don’t migrate this user.
      • /ue:ComputerNameLocalUserName – Don’t migrate this user.
  • 41. Argh! ScanStateArgs!
    • These are most effective in combination.
      • /ue:*.* = Exclude everyone, including local users.
      • /ui:AUTODEPLOY* = Include all domain users.
      • /uel:60 = Include only those who logged on in last 60 days.
  • 42. Special Note: Hard Link Migrations
    • Network copies take time, lots of time.
    • Hard Link Migrations eliminate some network copies, reducing time to migrate.
      • Hard link migrations keep files stored on the source computer during the migration.
      • A hard link gives a file an additional path, which protects the file from deletion during the OS deployment.
      • Hard links are created only for files on the same volume.
      • The hard link migration store should be removed after the migration has completed (or files can’t be deleted!).
      • Works only (and by MDT default) with Refresh scenarios.
  • 43. Configuring Migration Method
    • The type of migration chosen is defined by the UserDataLocation value in MDT’s Rules tab.
      • AUTO will use Hard Link migrations for refreshes and a network share for replaces.
  • 44. Configuring Migration Method
    • The type of migration chosen is defined by the UserDataLocation value in MDT’s Rules tab.
      • AUTO will use Hard Link migrations for refreshes and a network share for replaces.
    • Suggest setting the following:
      • UserDataLocation=AUTO
      • UDShare=fileServerfileShare
      • UDDir=%OSDComputerName%
  • 45. Complete Automation! Upgrade Computer Scenario
  • 46. Complete Automation! Refresh Computer Scenario
  • 47. Windows 7 Deployment Deep Dive Automating User Data Migration from Old Desktop to New Greg Shields, MVP, vExpert Concentrated Technology www.ConcentratedTech.com