XP to Windows 7 with MDT
•Transferir como PPTX, PDF•
4 gostaram•9,413 visualizações
This is the Windows XP and Office 2003 to Windows 7 and Office 2010 Migration Presentation from the Get On The Bus Tour
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a XP to Windows 7 with MDT
Semelhante a XP to Windows 7 with MDT (20)
Mais de Stephen Rose
Mais de Stephen Rose (12)
Último
Último (20)
XP to Windows 7 with MDT
- 1. Deploying An Optimized Windows Desktop Stephen Rose Sr. Community Manager – Windows Commercial stephen.rose@microsoft.com
- 2. Who Am I? 15 years as an IT Pro 2 time Microsoft MVP – Setup and Deployment MCSE and MCT since 1997 What do I do? The Springboard Series on TechNet Editor of the Springboard Series Insider The Springboard Series on Windows® Team Blog Twitter- @MSSpringboard, @stephenlrose, @thebustour Manager – Windows 7 Forums on TechNet Windows 7 Program Manager for the MVP program Manage the STEP (Springboard Technical Experts Panel)
- 3. The Magic of The PiXiE Stick My boss has XP. She needs Windows 7 before she lands. I want to enable my remote workers to migrate to Windows 7 without sending in their laptops. I have 10 machines I want to pilot Windows 7 on.
- 5. Planning for Windows 7 and Office 2010
- 6. The Deployment Project… Do I need to invest in test hardware, personnel, and infrastructure? How is this going to impact users and the helpdesk? Do I replace all of my users’ hardware? Testing Process OperationsReadiness InfrastructureRemediation Do my users need to send their hardware to IT or be without their PCs for a day? Do I need to build and maintain an image for each hardware class? ProjectProcess andTeam Guidance Deployment Image Engineering Business Casefor Deployment How do I think about policies, data, and security now? Are my applications going to work? ApplicationManagement Office, too? Does that mean more testing and images? Security Do my techs need to manuallymigrate everyone’s files at their desk or in the lab? OfficeDeployment Migration
- 7. …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+ years Security updates are easier to integrate into the project
- 8. …What it Means Refresh existing hardware - don’t wait for hardware replacement Make the process fast and not disruptive for users Test wisely, but don’t expect things to break as often as before That means fewer helpdesk calls than with previous OS deployments
- 9. The Migration Process Assess hardware and applications, and plan for the new features or services you want Plan Prepare applications, infrastructure, and images for deployment and migrate users Deliver Expand functionality coverage, transition applications, and manage the desktop environment Operate
- 10. Windows Application Compatibility Tools Test & Mitigate Analyze Collect Application Compatibility Toolkit Asset Inventory Service Microsoft Assessment and Planning System Center Family Application Compatibility Toolkit Windows Compatibility Center Compatible Applications List Application Quality Cookbook Application Verifier Application Compatibility Toolkit Application Virtualization Application Quality Cookbook Virtual Legacy Windows OS (MED-V, XP Mode)
- 11. 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
- 12. Application Compatibility Toolkit (ACT) 5.5
- 13. Office 2010 Compatibility Toolkit New!Office Environment Assessment Tool (OEAT) Content Application Compatibility New!Office 2010 CompatibilityInspector Tool Office Migration Planning Manager (OMPM)
- 14. App Compat – Office Environment Assessment ToolIdentifying the add-ins & interfacing applications
- 15. Office Migration Planning Manager (OMPM)Evaluate, identify, & migrate Office files for OpenXML migration
- 16. Control Environment Build Package Define applications and preference Bundle supporting elements, i.e. Add-ins, languages, guides, etc. Office Customization Tool (OCT) Config.xml Enforce system wide policy Control Office application @ a granular level – over 4000 objects Group Policies – Office admin templates Realizing Office 2010 in Your Enterprise Deployment Many methods for delivering install packages (caching, MSI, scripts, SCE/SCCM, virtualization) Deployment method influences degree of control & monitoring Guidance Office Resource Kit (ORK) Security Guide TechNet Community TechNet Resource Centers
- 17. Group PolicyOffice admin templates allow IT to control features available for end users
- 18. Office Customization ToolBuild deployment packages to fit business requirements
- 19. Improved Application Virtualization SupportTighter integration with Microsoft App-V Potential to simplify deployment & management App-V investments improve support of Office 2010* Office 2010 requires App-V 4.6 available in H1 2010 App-V requires deployment specific sequencing Features improved with App-V 4.6/Office 2010 include: Outlook: Fast Search using Windows Desktop Search URL Protocol Handlers (Mailto, feeds, webcal(s)) Send to Mail integration Enable advanced account configuration SharePoint - Directly open/edit/save hosted documents OneNote - Send to OneNote print driver All - Activation model support *Click to Run offerings leverage App-V
- 20. Deployment Benefits of Application Virtualization Faster Delivery of Applications at Deploy Time Immediate Implementation Across Windows Versions Reduced Time for Testing and Packaging Minimize user disruption and speed up migration times with faster application delivery Get to a single OS image more easily with less work to automate application installation and less time needed to deliver applications Get value immediately as you work through your applications for Windows 7 deployment Implement App-V to Windows XP and Windows Vista users before Windows 7 is fully deployed Give users access to new applications before Windows 7 is delivered Reduce testing times with Application Isolation Speed up application packaging for deployment with App-V sequencing Sequence applications for compatibility across Windows versions
- 21. Desktop Virtualization and Compatibility Concerns
- 23. Windows Server 2008 R2 + KMS = Office 2010, Windows XP, Vista and 7 Activation What it provides: Better license management Visibility of activations Consistent activation approach for Windows and Office NOT monitored by Microsoft What it requires: Plan for your activation method Key Management Service (KMS) Multiple Activation Key (MAK)
- 24. How Is Our Demo Doing?
- 25. How Do They Work?...add your ingredients, create a build, and install
- 26. Microsoft Deployment Toolkit MDT 2010 Beta Version
- 27. Improving the Deployment Core Migration Delivery Imaging So How Does This Help You? Saves time building and updating images These are big files – we can now transfer them quickly Reduce the number of deployment servers Migrate gigabytes of user state in minutes, not hours Deployment Image Servicing and Management Add/Remove Drivers and Packages WIM and VHD Image Management User State Migration Tool Hard-link Migration Offline File Gather Improved user file detection Windows Deployment Services Multicast Multiple Stream Transfer Dynamic Driver Provisioning More installs per day Minimized end user disruption Keep your existing hardware = Solutions to Prepare and Deploy
- 28. Files User Accounts Application Settings 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 Files User Accounts Application Settings
- 29. Task-Sequenced Deployment EnginesAutomating the entire migration process System Center Configuration Manager 2007 Zero Touch Microsoft Deployment Toolkit (MDT) Lite Touch Masks the complexity of command line tools Windows OS Image Device Drivers Corporate Domain Applications User Data and Settings User Data and Settings Windows XP or Windows Vista New OS Image Installed Applications Installed Drivers Installed Old OS files deleted Join Domain Apply User State Deployment Task Sequence to Same PC – Fully Automated 30-90 Minutes All-Up
- 30. Demo of Using Deployment Automation Demo complete?
- 31. What Next?
- 33. © 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.
Notas do Editor
- Key MessageDeployment projects are divided into discreet tasks – or feature teams – to ensure that all prerequisites are in place and tested prior to the deployment taking place. Microsoft Deployment Toolkit provides guidance and tools to help automate key tasks, including:Hardware and software inventoryApplication inventory and compatibility analysisFile repository for centrally managing operating systems, applications, drivers, and packagesUser data and settings migration from the previous operating system to the deployed operating systemSecurity guidance for establishing a security strategy tailored to the new operating systemDeployment task sequencer for defining pre- and post-installation tasks
- Key Message: An overview of the Application Compatibility Tool and the ACM. The following is detailed info regarding the usage, options, and new features within the ACT and ACM.The Application Compatibility Manager (ACM) is a tool that enables you to configure, to collect, and to analyze your data, so that you can fix any issues prior to deploying a new operating system in your organization. When you configure the ACT using it’s wizard, the ACM automatically starts. Detailed info on ACM can be referenced at http://technet.microsoft.com/en-us/library/cc766464.aspx.You can use the ACT features to:Verify your application's, device's, and computer's compatibility with a new version of the Windows operating system, including determining your risk assessmentVerify a Windows update's compatibility, including determining your risk assessmentBecome involved in the ACT Community, including sharing your risk assessment with other ACT usersUse the provided developer and test tools to test your Web applications and Web sites for compatibility with new releases and security updates to Internet Explorer®, to determine potential compatibility issues due to the User Account Control (UAC) feature, to create compatibility fixes for your application compatibility issues, and to determine any potential application installation and setup issuesWhat’s New in ACT 5.5:Updated issue detection and supported operating systemsIntegration of data from the Windows Vista Compatibility CenterAbility to audit your application data and to selectively synchronize your applications with MicrosoftUpdated documentation for the Windows compatibility fixesAbility to customize your Quick Reports viewAbility to label your individual data-collection packagesRemoval of the Internet ExplorerCompatibility Evaluator (IECE)Ability to participate in the Customer Experience ProgramCompatibility EvaluatorsThe Application Compatibility Toolkit (ACT) includes several compatibility evaluators that can be deployed as part of a data-collection package to collect information from your client computers including:Inventory CollectorUser Account Control Compatibility Evaluator (UACCE)Windows Compatibility Evaluator (WCE)Update Compatibility Evaluator (UCE)Detailed info on each of these can be found at…http://technet.microsoft.com/en-us/library/dd638366.aspxTiming: Prepare for this discussion using the info above. This is a full-featured, in-depth tool and timing can run long unless an abbreviated subset of data is discussed. If the audience is particularly interested in this topic there is a large amount of info here, however a complete breakdown of the toolkit can be found at… *http://technet.microsoft.com/en-us/library/cc722055.aspx
- Key Message: An overview of the Application Compatibility Tool and the ACM. The following is detailed info regarding the usage, options, and new features within the ACT and ACM.The Application Compatibility Manager (ACM) is a tool that enables you to configure, to collect, and to analyze your data, so that you can fix any issues prior to deploying a new operating system in your organization. When you configure the ACT using it’s wizard, the ACM automatically starts. Detailed info on ACM can be referenced at http://technet.microsoft.com/en-us/library/cc766464.aspx.You can use the ACT features to:Verify your application's, device's, and computer's compatibility with a new version of the Windows operating system, including determining your risk assessmentVerify a Windows update's compatibility, including determining your risk assessmentBecome involved in the ACT Community, including sharing your risk assessment with other ACT usersUse the provided developer and test tools to test your Web applications and Web sites for compatibility with new releases and security updates to Internet Explorer®, to determine potential compatibility issues due to the User Account Control (UAC) feature, to create compatibility fixes for your application compatibility issues, and to determine any potential application installation and setup issuesWhat’s New in ACT 5.5:Updated issue detection and supported operating systemsIntegration of data from the Windows Vista Compatibility CenterAbility to audit your application data and to selectively synchronize your applications with MicrosoftUpdated documentation for the Windows compatibility fixesAbility to customize your Quick Reports viewAbility to label your individual data-collection packagesRemoval of the Internet ExplorerCompatibility Evaluator (IECE)Ability to participate in the Customer Experience ProgramCompatibility EvaluatorsThe Application Compatibility Toolkit (ACT) includes several compatibility evaluators that can be deployed as part of a data-collection package to collect information from your client computers including:Inventory CollectorUser Account Control Compatibility Evaluator (UACCE)Windows Compatibility Evaluator (WCE)Update Compatibility Evaluator (UCE)Detailed info on each of these can be found at…http://technet.microsoft.com/en-us/library/dd638366.aspxTiming: Prepare for this discussion using the info above. This is a full-featured, in-depth tool and timing can run long unless an abbreviated subset of data is discussed. If the audience is particularly interested in this topic there is a large amount of info here, however a complete breakdown of the toolkit can be found at… *http://technet.microsoft.com/en-us/library/cc722055.aspx
- OMPM – existing toolNew tools are OEAT and CIOEAT aimed at It Pros to scan desktops to get a view of add-ins and programs that interface with Office – this tool will verify with the ISV compatibility list, thus highlighting areas for drill downCI – targeted at developers to locate potential breaking points based on known changes being introduced
- The Office Migration Planning Manager (OMPM) is a resource provided by Microsoft to help customers and partners size up potential file migration issues.This slide is offered to provide a snapshot of what OMPM provides – the tools drill down module provides additional details this tool and how it can be leveraged.OMPM is a collection of tools that enables you to prepare your environment for migration to the 2010 Microsoft Office system. OMPM checks for, and reports on, file properties to help you analyze your environment and determine any issues that you might experience converting from Office 97-Office 2003 file formats to the new 2010 Office system file format. OMPM includes the following features: OMPM focuses primarily on converting old files to the new file formats. When OMPM shows an error or highlights a warning on a file; That does not mean the file will not open in the 2010 Office system (almost all older files can open in compatibility mode). It only means that saving it into the new Open XML format might cause problems. OMPM has 4 components discussed in more detail below: 1. Scanner 2. Database 3. Reporting Tools Seehttp://technet.microsoft.com/en-us/library/cc179179.aspx for additional information (Note only the Office 2007 is available until near Office 2010 RTM – this version can be used to begin assessments)
- The Office Migration Planning Manager (OMPM) is a resource provided by Microsoft to help customers and partners size up potential file migration issues.This slide is offered to provide a snapshot of what OMPM provides – the tools drill down module provides additional details this tool and how it can be leveraged.OMPM is a collection of tools that enables you to prepare your environment for migration to the 2010 Microsoft Office system. OMPM checks for, and reports on, file properties to help you analyze your environment and determine any issues that you might experience converting from Office 97-Office 2003 file formats to the new 2010 Office system file format. OMPM includes the following features: OMPM focuses primarily on converting old files to the new file formats. When OMPM shows an error or highlights a warning on a file; That does not mean the file will not open in the 2010 Office system (almost all older files can open in compatibility mode). It only means that saving it into the new Open XML format might cause problems. OMPM has 4 components discussed in more detail below: 1. Scanner 2. Database 3. Reporting Tools Seehttp://technet.microsoft.com/en-us/library/cc179179.aspx for additional information (Note only the Office 2007 is available until near Office 2010 RTM – this version can be used to begin assessments)
- Realizing Office 2010 – This is an opportunity area for partners to help customers package, deploy, and manage Office 2010At a high level there are 3 key areas to begin planning an Office installation – System, Application, and FilePartners have an opportunity to develop a packaged service offering to enable the customers to readily configure and management an Office 2010 deployment.Configuration of Office 2010 (focused on VL skus) enables partners to build a custom deployment package to fit the specific needs of the customer – this enables a consistent package of Office and supporting elements to be installed in a consistent manager. The Office Customization Tool (OCT) is the primary tool used to build these packages – additionally the config.xml element can be leveraged for some packaging such as MUI language packs. OCT is only offered with VL products – but it can activate features, enter MAK keys, set Outlook profiles, and more. The next slides will look at the tool in a bit more detail. Partners have the ability to help customers build or at least understand the options for using the OCT tool and help them design the best package.Controlling the environment is something to consider at time of deployment but also ongoing to keep system required actions in place – it can range from setting up trusted locations to automatically trust documents to de-activating select features of the Office applications. These settings are enforced for the user allowing the admin to keep the environment well managed.The actual deployment of Office, if well planned, is a very simple activity that can be carried in with various mechanisms. The selection of the method will be based on the size and scope of the deployment and the tools available for use. It is important to note that the more advanced methods used SCE or SCCM will make it possible to easily track the deployments in an environment.The partner has an opportunity to offers services to package these activities in a single seamless process for customers, enabling them to keep focused on their core business.
- Group Policy Admin templatesBy setting policies, you can define and maintain a particular Office 2010 configuration on users' computers. Unlike other customizations, such as default settings that are distributed in a transform (also known as an .mst file), policies are reapplied every time that a user logs on to the network. Alternatively, policies can be reapplied at some other interval that is set by the administrator. Users cannot edit the registry to change the policies. You can set policies that apply to the local computer (and to every user of that computer), or you can set policies that apply only to individual users. You set per-computer policies under Computer Configuration in the Group Policy snap-in. Per-computer policies are applied the first time that any user logs on to the network from that computer. You set per-user policies under User Configuration in the Group Policy snap-in. Per-user policies are applied when the specified user logs on to the network from any computer. To use an Office 2010 policy template, you must load the template in the Group Policy Microsoft Management Console snap-in.
- The Office Customization Tool (OCT) is used to create patches that customize the Office 2010 installation. The OCT patches are slipstreamed in at the install time, or can be applied post install for maintenance of existing installations: * Using the Office Customization Tool (OCT) * Using the Config.xml file as an override feature * Setting up command-line options * Enabling group policies Using the OCT to configure user settings establishes the initial default values for the settings. Users can modify most of the settings after Office is installed. You can use the OCT to provide default user settings for the following Office applications: * Microsoft Office Access 2010 * Microsoft Office Outlook 2010Printing Assistant * Microsoft Office Excel 2010 * Microsoft Office Groove 2010 * Microsoft Office InterConnect 2010 * Microsoft Office InfoPath 2010 * Microsoft Office 2010 system * Microsoft Office OneNote 2010 * Microsoft Office Outlook 2010 * Microsoft Office PowerPoint 2010 * Microsoft Office Project 2010 * Microsoft Office Publisher 2010 * Microsoft Office SharePoint Designer 2010 * Microsoft Office Visio 2010 * Microsoft Office Word 2010
- Often sold as silver bulletStill a maturing technology – related to consumer versions via Click to RunThis is virtualized desktop – this is just virtualizing the appsEnables coexistingSingle maintenance/deployment scenarioFYI - Core of work might be referred to as “office redistributable”Improvements to custom code at setupCreated a redistributable to facilitate volume activation when Office is virtualizedPerformance improvements that accrue to virtualized OfficeAlso, as a result of work done to build Click to Run offer, improved the App-V experience (also recognized through locally installed redistributable):
- Speaker Script:Let’s revisit our physical and manual migration. Remember how long that took?Now lets use Application Virtualization. We’ll start at 3:47 PM this time. Using Application Virtualization, we don’t actually “install” the application. That means that we don’t need to uninstall Office 2007 and to remove any remnants of the application, we have to delete it from our local application cache. Now I am deleting Office Word 2010 from my Application Virtualization local cache. Once that has been deleted, he just need to wait a moment for the application to be re-published for use.Now we can go to our start menu and see that Word 2010 is available and launch the application. Notice when we launch the application, App-V automatically looks for the most up-to-date version then launches the application. The application startup times are quite similar to the physically-installed version and within about one minute, we were able to launch the virtual instance of Word 2010, and the same would go for other Office 2010 programs. The application is streamed as it is launched with the most updated version and we can accomplish in about one minute what it previously took us about 20 minutes to do.
- Office Activation TechnologiesOffice Activation Technologies provide methods for activating products licensed under Microsoft Volume Licensing programs. Most Office Volume Licensing customers are familiar with Volume License Keys (VLKs) that were issued under a specific license agreement. This key effectively "bypassed" activation. For Office 2010, Office Activation Technologies help automate and manage the activation process while addressing the piracy and product key management problems that arose with keys issued for Office Enterprise 2007. You can use the following methods to activate Office 2010 by using Office Activation Technologies, which are the same methods used for Windows Vista and later versions of Windows.Key Management Service (KMS). KMS uses a KMS host key to activate a KMS host computer and establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation.Multiple Activation Key (MAK). With a MAK, clients activate Office 2010 online with Microsoft’s hosted activation servers or by telephone.A combination of KMS and MAK.KMS enables organizations to perform local activations for computers in a managed environment without each PC connecting to Microsoft individuallyThis Product Key allows multiple activations against the Clearing House or via a Proxy Activation Server. It is useful where customers do not want or require a Key Management Service In 2007 activation was only required for Retail and OEM.Now, ALL editions must be activated (physical and virtual)Privacy is of utmost importance. Data that is sent during activation is NOT traceable back to the computer or user. It is used to confirm you have a legally licensed copy of the software then aggregated for statistical analysis. It is NOT used to identify or contact you.Office Activation Technologies provide methods for activating products licensed under Microsoft Volume Licensing programs. Most Office Volume Licensing customers are familiar with Volume License Keys (VLKs) that were issued under a specific license agreement. This key effectively "bypassed" activation. For Office ”14”, Office Activation Technologies help automate and manage the activation process while addressing the piracy and product key management problems that arose with keys issued for Microsoft Office Enterprise Key Management ServiceA solution where an organization installs a Key Management Service onto their server infrastructure. The KMS is authenticated against the Microsoft Clearing House once. Special KMS Licenses are included in SKUs that support KMS which cause the Client (or Server) product to activate against the KMS instead of the Clearing House. Each product must re-activate against the KMS after a set period to ensure the product is still being used in the same licensed environment. Multi Activation Product KeyThis Product Key allows multiple activations against the Clearing House or via a Proxy Activation Server. It is useful where customers do not want or require a Key Management Service. The customer purchases one MAK Product Key per agreement. The number of activations per MAK can be increased during the life of the agreement up to a set limit. The process of increasing the MAK activation count is managed by OSIT and is outside the scope of this Spec.
- Key Message:Overview of deployment and assessment solutions. Briefly discuss these topics as being key pieces to the MS assessment and deployment process. Several components within will be discussed in further detail during the presentation.Timing:Brief high-level overview of process, time permitting. Transition:Setup for following Windows Vista investment options carrying forward and Windows 7 Upgrade options.