Upload
stephen-rose
View
21.523
Download
2
Tags:
Embed Size (px)
DESCRIPTION
This is the Windows XP and Office 2003 to Windows 7 and Office 2010 Migration Presentation from the Get On The Bus Tour
Citation preview
Deploying An Optimized Windows DesktopStephen RoseSr. Community Manager – Windows Commercial
Who Am I?
15 years as an IT Pro2 time Microsoft MVP – Setup and DeploymentMCSE and MCT since 1997What do I do?
The Springboard Series on TechNetEditor of the Springboard Series InsiderThe Springboard Series on Windows® Team BlogTwitter- @MSSpringboard, @stephenlrose, @thebustourManager – Windows 7 Forums on TechNetWindows 7 Program Manager for the MVP programManage the STEP (Springboard Technical Experts Panel)
The Magic of The PiXiE Stick
My boss has XP. She needs Windows 7 before she
lands.
I have 10 machines I want to pilot Windows 7
on.
I want to enable my remote workers to migrate to Windows
7 without sending in their laptops.
Planning for Windows 7 and Office 2010
The Deployment Project…
Testing Process
InfrastructureRemediation
Image Engineering
ApplicationManagement
MigrationOfficeDeployment
Security
Deployment
OperationsReadiness
ProjectProcess and
Team Guidance
Business Casefor Deployment
Do I need to invest in test hardware, personnel,
and infrastructure?
Do I replace all of my users’ hardware?
Do I need to build and maintain an image for each hardware class?
Are my applications going to work?
Do my techs need to manually migrate everyone’s files at
their desk or in the lab?
Office, too? Does that mean more testing
and images?
How do I think about policies, data, and security now?
Do my users need to send their hardware to IT or be without
their PCs for a day?
How is this going to impact users and the helpdesk?
…It Depends
Windows architecture and deployment tools change for a reason
Test?Hardware?Image management?User data migration?
Hardware specs and application requirements pretty static for 3+ yearsSecurity updates are easier to integrate into the project
…What it Means
Refresh existing hardware - don’t wait for hardware replacementMake the process fast and not disruptive for usersTest wisely, but don’t expect things to break as often as beforeThat means fewer helpdesk calls than with previous OS deployments
The Migration Process
Plan Assess hardware and applications, and plan for the new features or services you want
Deliver Prepare applications, infrastructure, and images for deployment and migrate users
OperateExpand functionality coverage, transition applications, and manage the desktop environment
Windows Application Compatibility Tools
Application Compatibility ToolkitAsset Inventory ServiceMicrosoft Assessment and PlanningSystem Center Family
Application Compatibility ToolkitWindows Compatibility CenterCompatible Applications ListApplication Quality CookbookApplication Verifier
Application Compatibility ToolkitApplication VirtualizationApplication Quality CookbookVirtual Legacy Windows OS (MED-V, XP Mode)
Test & Mitigate
AnalyzeCollect
Application Compatibility Toolkit (ACT) 5.6
Provides tools to inventory applications, hardware, and devices in the production environment
Synchronizes collected inventory with current application and hardware compatibility data from Microsoft
Includes tools to test and repair individual applications
Version 5.6 (release 5/11) adds x64 support for inventory, compatibility fixing, and standard user account issue detection
Application Compatibility Toolkit (ACT) 5.5
Office 2010 Compatibility Toolkit
Application Compatibility
New! Office Environment
Assessment Tool
(OEAT)
New! Office
2010 Compatibility
Inspector Tool
Content
Office Migration
Planning Manager (OMPM)
App Compat – Office Environment Assessment ToolIdentifying the add-ins & interfacing applications
Office Migration Planning Manager (OMPM)Evaluate, identify, & migrate Office files for OpenXML migration
Group PolicyOffice admin templates allow IT to control features available for end users
Office Customization ToolBuild deployment packages to fit business requirements
Windows Server 2008 R2 + KMS = Office 2010, Windows XP, Vista and 7 ActivationWhat it provides:
Better license managementVisibility of activationsConsistent activation approach for Windows and OfficeNOT monitored by Microsoft
What it requires:Plan for your activation method
• Key Management Service (KMS)• Multiple Activation Key (MAK)
How Is Our Demo Doing?
How Do They Work?...add your ingredients, create a build, and install
Microsoft Deployment Toolkit 2010 or System Center Configuration Manager 2007
Operating Systems
Applications
Drivers
Microsoft Deployment Toolkit
MDT 2010 Beta Version
Improving the Deployment Core
MigrationDeliveryImaging
Deployment Image Servicing and ManagementAdd/Remove Drivers and PackagesWIM and VHD Image Management
User State Migration ToolHard-link MigrationOffline File GatherImproved user file detection
Windows Deployment ServicesMulticastMultiple Stream TransferDynamic Driver Provisioning
Solutions to Prepare and Deploy
So How Does This Help You?
Saves time building and updating imagesThese are big files – we can now transfer them quicklyReduce the number of deployment serversMigrate gigabytes of user
state in minutes, not hours
More installs per dayMinimized end user disruptionKeep your existing hardware
=
Application Settings
FilesUser
Accounts
How Hard-Link Migration works?...index files, create links to each, map links to the right spots
Index of Hard-Links -
files don’t move
Application Settings
FilesUser
Accounts
Demo of Using Deployment Automation
Demo complete?
What Next?
© 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.