Migrate Your Windows XP Machines to Windows 7 Using Free Microsoft Deployment Tools

transcript

Migrate Your Windows XP Machines to Windows 7 Using Free Microsoft Deployment ToolsRhonda J. LayfieldSr. Technical ConsultantRJL, INC.

SESSION CODE: WCL311

IT industry since 1982US Navy for 7 yearsContribute articles to Windows IT Pro mag Setup and Deployment MVPDesktop Deployment Product Specialist (DDPS)Co-Author Windows Server 2003 R2 and Windows Server 2008 booksNEW Microsoft Deployment Book

Rhonda Layfield

What I’ll Cover4 scenariosMDT Installation and required softwareCreate a Deployment ShareImport Windows 7, applications, drivers and packagesCreate a task sequenceMigrate Applications

RefreshReplace/Bare Metal

Automate the Deployment Wizard

Bare MetalNew machines

RefreshKeeping the old hardware

Refreshing the OS on the existing machineReplace

Replacing existing hardware with newMaintaining user’s settings and data

UpgradeUnless your upgrading from Vista there is no direct upgrade path

Four Scenarios

XP Migration “Refresh” Scenario

MDT 2010 Deployment Server

XP SP2/SP3

1Gather Application Information

Configure MDT – OS & Application Information 2

USMT Gathers User and Application Settings (local store) 6

Boots to WinPE - Win 7 is Installed 7Applications are Installed 8USMT Applies User and

Application Settings (local store) 9

Get list of Configured Applications 4Begin MDT Deployment Wizard 3List & Registry Scan = New list 5Windows 7

DEMOMDT Network Deployment

MDT Installation Requirements

You can install MDT on:Vista SP1Windows 7Server 2003 SP2Server 2008Server 2008 R2

Windows Automated Installation Kit (WAIK) 2.0Required software is included in the WAIK

NET Framework 2.0MSXML 6.0MMC 3.0 if Server 2003

Refresh Scenario Step-By-StepsCreate a Deployment ShareImport Windows 7Add applications, drivers and packagesCreate a task sequenceFind existing applications from XPConfigure applications on the deployment serverUpdate Deployment ShareLaunch LiteTouch.vbs from the XP machineMDT scans for configured applicationsThe registry is scanned for existing applications

Refresh Scenario Step-By-StepsThe deployment wizard runs

USMT gathers existing application settingsThe machine boots to the MDT WinPEWindows 7 is installedApplications are installedUSMT applies application settings

Creating a Deployment Share The Deployment Share is the shared folder on the Deployment Server where target machines connect to perform the deploymentYou must create it

Old MDT created it for youBut it put it on the C: drive

Now you decide where to create it

MDTDeployment Server

Deployment Share

DEMOCreate a Deployment Share

Importing an Operating System

XP SP3Vista SP1 or laterWindows 7Windows Server 2003 R2Windows Server 2008 & R2

Supported OSs

Adding an Application

DEMOAdd an Application

Adding Drivers

Third party drivers

Adding Packages

OS patchesLanguage Packs

Create a Task SequenceA list of tasks to be run for your deploymentThe order in which the tasks will be runRun task sequences in two different ways

Standard Client TSLiteTouchPE_x86.isoWithin XP

Task SequencesStandard Client TS

Deploys a desktop operating system, applications, drivers and patches

Standard Client Replace TSBacks up the target machine before deploying an image including gathering users state information

DEMOCreate Task Sequences

Update the Deployment Share

Migrating Applications

ANNOUNCING

MDT and ApplicationsMDT does not perform any magic on your applicationsIf they don’t run on Windows 7

They won’t run on Windows 7 deployed by MDT 2010So, you’ll need to be sure you have tested your applications first!

Use Application Compatibility Toolkit (ACT)To get a list of applications that will or will not run on Windows 7To troubleshoot the applicationsTo fix the applications – mitigate using SHIMS

OrMicrosoft Assessment and Planning (MAP)

To get a list of applications that will or will not run on Windows 7

Find Existing Applications on XPLog on as a standard user for read only modeHKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall

Uninstall key name

Find Existing Applications.Exe’s are easy – the application name is obvious.Msi’s are displayed as GUID’s – look for the DisplayName

Copy the Key Name to Notepad

Copying the Key NameThis is what you’ll getHKEY_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}

Configure Applications on The Deployment ServerDW

– Application Properties– On the Details tab – Input the Uninstall

registry key name

Create The Script That Searches For ApplicationsCreate LTIAppDetect.vbs scriptCopy and paste the contents from Michael Neihaus’s blog http://blogs.technet.com/mniehaus/default.aspx?p=2or download LTIAppDetect.vbs from http://www.deploymentdr.com/Download.htmlThenCopy LTIAppDetect.vbs into your deployment share’s Scripts folder

Configure MDT to Look For ApplicationsEdit the Rules of your deployment shareThe Rules determine which pages are displayed by the deployment wizardDW right click deployment share Properties Rules tab

[Settings]Priority=DefaultProperties=MyCustomProperty [Default]OSInstall=YSkipAppsOnUpgrade=YESSkipCapture=YESSkipAdminPassword=NOSkipProductKey=YES

[Settings]Priority=DefaultProperties=MyCustomProperty [Default]UserExit=LTIAppDetect.vbsOSInstall=YSkipAppsOnUpgrade=YESSkipCapture=YESSkipAdminPassword=NOSkipProductKey=YES

Begin Migration by Launching LiteTouch.vbsFrom the XP workstation map a drive to your deployment server:

Start / Run / Deployment server = DeploySrv Deployment share = DeploymentShare$Scripts folderThen run LiteTouch.vbs

Applications Appear Pre-Selected

But someone could de-select itIf you don’t anyone to be able to de-select an applicationYou’ll need to make it “Mandatory”

Making Applications MandatoryEdit LTIAppDetect.vbsEdit LTIAppDetect.vbs scriptSet oApplications = oEnvironment.ListItem("Applications")To:Set oApplications = oEnvironment.ListItem("MandatoryApplications")

USMT Gathers Existing Application Settingsscanstate.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

Types of Files to Migrate - All Fixed Drives are Searched

.accdb

• .qel• .qph• .qsd• .rqy• .rtf• .scd• .sh3• .slk• .txt• .vl*

• .vsd• .wk*• .wpd• .wps• .wq1• .wri• .xl*• .xla• .xlb• .xls*

Settings That are Migrated

Accessibility settingsAddress bookCommand-prompt settings*Desktop wallpaperEFS filesFavoritesFolder optionsFontsUsers, Groups and Group memberships*Windows Internet Explorer® settings

* Settings not available for offline migration

More Settings That are Migrated

Microsoft Open Database Connectivity (ODBC) settingsMouse and keyboard settingsNetwork drive mapping*Network printer mapping*Offline files*Phone and modem optionsRAS connection and phone book (.pbk) files*Regional settingsRemote Access

The Last of The Settings That are Migrated*Taskbar settingsWindows MailMicrosoft Outlook Express Mail (.dbx) files are migrated from Windows XP*Windows Media PlayerWindows Rights Management

Application Settings Migrated

Adobe Acrobat Reader 9AOL Instant Messenger 6.8Apple iTunes 7, 8Apple QuickTime Player 7Apple Safari 3.1.2Google Chrome betaGoogle Picasa 3Google Talk betaIBM Lotus 1-2-3 9.8IBM Lotus Notes 8IBM Lotus Organizer 9.8IBM Lotus WordPro 9.8Intuit Quicken 2009

Money Plus Business 2008Money Plus Home 2008Mozilla Firefox 3Microsoft Office Access 2003, 2007Microsoft Office Excel 2003, 2007Microsoft Office FrontPage 2003, 2007Microsoft Office OneNote 2003, 2007Microsoft Office Outlook 2003, 2007Microsoft Office PowerPoint 2003, 2007Microsoft Office Publisher 2003, 2007Microsoft Office Word 2003, 2007Opera Software Opera 9.5Microsoft Outlook Express (mailbox file)

Last of the Apps

Microsoft Project 2003, 2007Microsoft Office Visio 2003, 2007RealPlayer Basic 11Sage Peachtree 2009Skype 3.8Windows Live Mail 12, 14Windows Live Messenger 8.5, 14Windows Live MovieMaker 14Windows Live Photo Gallery 12, 14Windows Live Writer 12, 14Windows Mail Vista onlyMicrosoft Works 9Yahoo Messenger 9Zune 3

Microsoft Office is Special

Cannot migrate from/to a different version of an applicationExcept for Microsoft Office

USMT can migrate from an earlier version to a laterMicrosoft Project settings are not migrated from Office 2003 to Office 2007

OS Settings NOT Migrated

Mapped network drivesLocal printersHardware-related settingsDriversPasswordsApplication binary filesSynchronization filesDLL files

• Executable files• Permissions for shared folders• Languages must match• Customized icons for shortcuts• Taskbar settings (Migrating from XP)

Migrating from XP

Internet Connection Firewall check box and settings are migratedAdvanced-configuration settings are not migrated because of increased security risks

Security LoggingICMP exceptions

Internet Connection Sharing setting is not migrated Could make the network less secure if migrated to the destination computer

The Network Connections user interface does not refresh properly until you log off or press F5

Windows 7 is InstalledWindows 7 should be added to MDT’s Deployment Workbench

USMT Applies Application Settingsloadstate.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

Network Location Page - BUG

Work AroundSet a Group Policy for Network Location

Computer Configuration / Windows Settings / Security Settings / Network List Manager Policies / All NetworksChange Network Location to “User cannot change location”

Hotfix coming - KB 2028749

Issues You Might Run IntoMultiple versions of an application

You could add an application to the DWConfigure the Uninstall Registry key for version 1

Add the same application to the DW againConfigure the Uninstall Registry key for version 2

BUTUSMT gathered application data for version 1 and might not be able to apply the settings to version 2

Applications and Bare Metal/Replace Scenarios

XP Migration “Replace” Scenario

MDT 2010 Deployment Server

XP SP2/SP3

1Gather Application Information

Configure MDT w/ Application Information 2

USMT Gathers User and Application Settings 5

Boots to WinPE - Win 7 is Installed 6Applications are Installed 7USMT Applies User and

Application Settings 8

List of Configured Apps “Pre-selected” 4

3Begin MDT Deployment Wizard

Windows 7

Bare Metal and Replace Scenario – With ApplicationsWhen applications are added to the MDT a random GUID is createdFind your application’s GUID

Open Windows Explorernavigate to your deployment share\Control folderOpen Applications.xmlExpand the application’s node (each application has it’s own application node)Cick on guid to see the MDT generated GUID in the details paneIf your using MDT 2010 Update 1 the application guid has been added to the properties of the application’s Details tab

From within the DW double click your application and go to the Details tab

Configuring MDT with Mandatory ApplicationsRight click your deployment share and choose PropertiesGo to the Rules tab

[Settings]Priority=DefaultProperties=MyCustomProperty [Default]OSInstall=YSkipAppsOnUpgrade=YESSkipCapture=YESSkipAdminPassword=NOSkipProductKey=YES

MandatoryApplications1={0992c971-a6b2-48d3-b34e-c96309bd4030}

Configuring Apps for Bare Metal and Replacement Scenarios

Clean Up ADUCIf you rename your newly migrated machine the old name still exists in ADSo, you might want to clean that up by deleting the old machine name

Automating MDT 2010Rules of the Deployment

Automate the Clients ExperienceChoose which pages are displayed during the deploymentSuppress the pages you do not want anyone to change or see like:

Product KeyAdministrator’s password

Properties of your deployment shareRules tab

F:\DeploymentShare\Control\Bootstrap.iniF:\DeploymentShare\Control\CustomSettings.ini

Bootstrap.ini[Settings]Priority=Default [Default]DeployRoot=\\DeploySrv\DeploymentShare$SkipBDDWelcome=YES

CustomSettings.ini[Settings]Priority=DefaultProperties=MyCustomProperty[Default]OSInstall=YScanStateArgs=/v:5 /o /cLoadStateArgs=/v:5 /c /lac /laeSkipAppsOnUpgrade=YESSkipCapture=YESSkipAdminPassword=YESAdminPassword=Swordfish1SkipProductKey=YESProductKey=11111-22222-33333-44444-55555

SkipDeploymentType=YESDeploymentType=REFRESHSkipDomainMembership=YESJoinDomain=DeploymentDomainAdmin=AdministratorDomainAdminDomain=DeploymentDomainAdminPassword=Swordfish1SkipUserData=yesUserDataLocation=AUTOSkipComputerBackup=YESSkipTaskSequence=YESTaskSequenceID=MIG_W7SkipComputerName=YES

CustomSettings.iniOSDComputerName=%SerialNumber%SkipLocaleSelection=YESUILanguage=en-USUserLocale=en-CAKeyboardLocale=0409:00000409SkipTimeZone=YESTimeZoneName=Eastern Standard TimeSkipApplications=YESUserID=AdministratorUserDomain=DeploymentUserPassword=Swordfish1

SkipBitLocker=YESSkipSummary=YES

DEMOShow Automated Rules

Then When You Run LiteTouch.vbs

No questions asked!

What We Covered…4 scenariosMDT Installation and required softwareCreated a Deployment ShareImport Windows 7, applications, drivers and packagesCreated a task sequenceMigrated Applications

RefreshReplace/Bare Metal

Automated the Deployment Wizard

Resources

www.microsoft.com/teched

Sessions On-Demand & Community Microsoft Certification & Training Resources

Resources for IT Professionals Resources for Developers

www.microsoft.com/learning

http://microsoft.com/technet http://microsoft.com/msdn

Learning

Migrate Your Windows XP Machines to Windows 7 Using Free Microsoft Deployment Tools

Documents