1 / 30

WCL308 Migrate XP to Windows 7 Without Loosing any User or Application Settings

WCL308 Migrate XP to Windows 7 Without Loosing any User or Application Settings. Rhonda Layfield Sr Consultant / Trainer Deployment Done Right. Maintain users data and settings Maintain application settings. Migrate XP to Windows 7. XP Migration “Refresh” Scenario.

dirk
Download Presentation

WCL308 Migrate XP to Windows 7 Without Loosing any User or Application Settings

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WCL308 Migrate XP to Windows 7 Without Loosing any User or Application Settings Rhonda Layfield Sr Consultant / Trainer Deployment Done Right

  2. Maintain users data and settings Maintain application settings Migrate XP to Windows 7

  3. XP Migration “Refresh” Scenario Gather Application Information 1 Configure MDT Application Information 2 Begin MDT Deployment Wizard 3 Get list of Applications Configured 4 XP SP2/SP3 USMT Gathers User and Application Settings (local store) 6 MDT 2010 U1 Deployment Server List & Registry Scan = New list “Pre Selected” 5

  4. XP Migration “Refresh” Scenario 7 Boots to WinPE - Win 7 is Installed USMT Applies User and Application Settings (local store) 9 Applications are Installed from MDT DS 8 Windows 7 XP SP2/SP3 MDT 2010 U1 Deployment Server

  5. Log on as a standard user for read only mode HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall Gather Application Information 1 • Uninstall key name

  6. .Exe’s are easy – the application name is obvious .Msi’s are displayed as GUID’s – look for the DisplayName Gather Application Information 1 .MSI .EXE

  7. Copy Key Name to Notepad Gather Application Information 1

  8. Title

  9. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FC7BACF0-1FFA-4605-B3B4-A66AB382752D}HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FC7BACF0-1FFA-4605-B3B4-A66AB382752D} This is the piece you want: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FC7BACF0-1FFA-4605-B3B4-A66AB382752D} If your doing a lot of applications at one time: XMLNotepad = {FC7BACF0-1FFA-4605-B3B4-A66AB382752D} NetMon 3.3 = {365C5A10-6561-454F-B975-56EA878D0A06} Office 2007 = {90120000-002A-0000-1000-0000000FF1CE} Gather Application Information 1

  10. Performed on the deployment server Within the deployment workbench Add an application Open the properties of the application On the Details tab Input the Uninstall registry key name Configure MDT Application Information 2

  11. Fact Finding Mission on XP and Configure MDT DW

  12. Create the script that will search for applications Create LTIAppDetect.vbs script Copy and paste the contents from Michael’s blog http://blogs.technet.com/mniehaus/default.aspx?p=2 or download LTIAppDetect.vbs from http://www.deploymentdr.com/Download.html Copy the LTIAppDetect.vbs script into your deployment share’s Scripts folder Configure MDT Application Information 2

  13. Configure MDT to look for applications - edit the properties of your deployment share From within the Deployment Workbench / Properties of your deployment share / Rules tab [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipAppsOnUpgrade=YES SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES Configure MDT Application Information 2

  14. Add LTIAppDetect.vbs [Settings] Priority=Default Properties=MyCustomProperty [Default] UserExit=LTIAppDetect.vbs OSInstall=Y SkipAppsOnUpgrade=YES SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES Configure MDT Application Information 2

  15. Configure Deployment Workbench With Application Information

  16. Launch LiteTouch.vbs from the XP workstation Map a drive to your deployment server: Net use P: \\ServerName\DeploymentShareName\Scripts Deployment server = DeploySrv Deployment share = DeploymentShare$ Net use P: \\Deploysrv\DeploymentShare$\Scripts Then from the P: drive double click on LiteTouch.vbs OR Start / Run / Begin MDT Deployment Wizard 3

  17. Launch The Deployment Wizard

  18. Get a list of Applications Configured These are the applications you configured on the deployment server in the deployment workbench List & Registry Scan = New list “Pre Selected” The list of configured applications on the deployment server and the list of applications from the XP registry are compared to create a third list The third list is the list of applications displayed as pre selected during the deployment process Steps 4 and 5 – You won’t see these 4 5

  19. User State Migration Tool V4.0 gathers existing user data, settings and application settings This is called “Users State” User State is stored locally scanstate.exe C:\MININT\StateStore /v:5 /o /c /hardlink /nocompress /efs:hardlink /i:C:\MININT\USMT\MigApp.xml /i:C:\MININT\USMT\MigDocs.xml /l:C:\MININT\SMSOSD\OSDLOGS\USMTcapture.log /progress:C:\MININT\SMSOSD\OSDLOGS\USMTcapture.prg USMT Gathers User and Application Settings 6

  20. Boots to WinPE - Windows 7 is Installed Windows 7 is installed Applications are Installed from MDT Deployment Share Applications selected from the “Select one or more applications to install” page (Windows Deployment Wizard) are installed Steps 7 and 8 – Task Sequence Performs These: 7 8

  21. USMT applies previously gathered user data, settings and application settings loadstate.exe /v:5 /c /lac /hardlink /nocompress /i:C:\MININT\USMT\MigApp.xml /i:C:\MININT\USMT\Migdocs.xml /l:C:\MININT\SMSOSD\OSDLOGS\USMTrestore.log C:\MININT\StateStore /progress:C:\MININT\SMSOSD\OSDLOGS\USMTrestore.prg USMT Applies Locally Stored Settings 9

  22. Mandatory Applications

  23. If you don’t want a person to be able to de-select an application during deployment… Edit LTIAppDetect.vbs script Set oApplications = oEnvironment.ListItem("Applications") To: Set oApplications = oEnvironment.ListItem("MandatoryApplications") Make Applications Mandatory

  24. If you rename your newly migrated machine the old name still exists in AD So, you might want to clean that up by deleting the old machine name Clean Up Active Directory Users and Computers

  25. XP Migration “Replace” Scenario Boots to WinPE - Win 7 is Installed 4 USMT Applies User and Application Settings (stored on MDT server) Add applications to DW 1 Applications are Installed from MDT DS 6 5 2 Begin MDT Deployment Wizard XP SP2/SP3 Windows 7 USMT Gathers User and Application Settings (stored on MDT server) 3 MDT 2010 U1 Deployment Server

  26. New Hardware Store users state on a server (not locally) Need a new task sequence created Use the “Standard Client Replace Task Sequence” template Start from XP Choose the Standard Client Replace TS Users state is captured Machine boots to Winpe Successful user state stored – Finish Boot the new machine using MDT WinPE Restore user data, settings and application settings Replace Scenario Steps

  27. Demo Title Name Title Group demo

  28. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

  29. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related