Escolar Documentos
Profissional Documentos
Cultura Documentos
MICROSOFT
LEARNING
PRODUCT
6294A
Planning and Managing Windows 7 Desktop Deployments and Environments
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein. 2009 Microsoft Corporation. All rights reserved. Microsoft, Microsoft Press, Access, Active Desktop, Active Directory, ActiveSync, ActiveX, Aero, Authenticode, BitLocker, BizTalk, DirectX, Encarta, Excel, Forefront, Hyper-V, Internet Explorer, Microsoft Dynamics, MS, MSDN, MS-DOS, MSN, OneCare, OneNote, Outlook, PowerPoint, ReadyBoost, SharePoint, SmartScreen, SoftGrid, SpyNet, SQL Server, Visio, Visual Basic, Visual C#, Visual Studio, Win32, Windows, Windows Live, Windows Media, Windows Mobile, Windows NT, Windows PowerShell, Windows Server, Windows Vista, and Zune are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.
Module 1
Lab Instructions: Preparing to Deploy Windows 7 Business Desktops
Contents:
Lab A: Assessing the Computing Environment by Using the Microsoft Assessment and Planning Toolkit Exercise 1: Configure the Microsoft Assessment and Planning Toolkit Exercise 2: Use the Microsoft Assessment and Planning Toolkit to Create a Client Assessment Report Exercise 3: Analyze Inventory and Assessment Data Lab B: Recommending an Activation Strategy Exercise 1: Review the Activation Scenario 8 4 5 6
Lab A: Assessing the Computing Environment by Using the Microsoft Assessment and Planning Toolkit
Scenario
You are the team lead for the Windows 7 deployment project at Contoso Ltd. Contoso currently uses Windows Vista on the company desktop computers. You are planning for the Windows 7 deployment to take place within the next month. As part of the deployment process, you need to determine if there are any hardware compatibility issues with Windows 7. You will use the Microsoft Assessment and Planning Toolkit to help inventory, analyze, and then determine the necessary hardware upgrades.
Results: After this exercise, you will have MAP 4.0 configured on LON-CL2.
Exercise 2: Use the Microsoft Assessment and Planning Toolkit to Create a Client Assessment Report
Note: LON-DC1 is the computer running Windows Server 2008 R2 which is the domain controller and shared network location for the labfiles. LON-CL2 is the client computer running Windows 7.
Results: At the end of this exercise you will have collected a Windows 7 Readiness assessment and the Wizard will have created the Proposal and Assessment documents.
Question: How many client systems were inventoried? Question: How many systems are ready for Windows 7? Question: How many systems would be ready for Windows 7 with hardware upgrades?
Open the Windows7Assessment-<date-time> report just created. Question: Which clients are in the Meets minimum system requirements Category? Question: Which clients are in the Not Ready for Windows 7 Category? Question: What are the minimum upgrades required to the Not Ready for Windows 7 Category systems?
The QA network consists of 10 servers and over 100 Desktop systems. The servers for the QA network are located at the Corporate HQ location. The QA network includes clients at each of the regional offices and branch offices with an IT staff connected to the corporate headquarters through a VPN. The test network is isolated from the production network and the Internet and wholly resides in the Corporate Headquarters location. This network consists of 10 servers and 50 desktop systems. The systems in the test network are frequently rebuilt due to the nature of their use. The current network was built in a gradual fashion based on both growth and acquisitions. Because of this growth pattern, a consistent licensing model has not been deployed. A recent internal audit has revealed inadequacies with the existing licensing activation. The network is due for a technology refresh, and because of the issues revealed by the audit upper management has asked you to recommend an activation model that will provide the most efficient method of activating all systems while maintaining a documentable method of managing the licenses.
Module 2
Lab Instructions: Assessing Application Compatibility in Windows 7
Contents:
Lab A: Evaluating Application Compatibility Using the Microsoft Application Compatibility Toolkit Exercise 1: Installing and Configuring ACT Exercise 2: Collecting Application Inventory Exercise 3: Organizing the Application Inventory Exercise 4: Analyzing Application Inventory Results Lab B: Creating Application Compatibility Fixes Exercise 1: Identifying Application Compatibility Issues Exercise 2: Mitigating Application Issues
2 5 7 9 11 13
Lab A: Evaluating Application Compatibility Using the Microsoft Application Compatibility Toolkit
The main tasks for this exercise are as follows: 1. 2. Install ACT. Configure ACT settings.
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL1 is the computer running Windows 7. LON-VS1 is the computer running Windows Vista.
On the Settings tab, review the following configuration settings: SQL Server name SQL Database name Log Processing Service status Log Processing Service account Log Share and Log Share path
On the Preferences tab, review, but do not change, the following default configuration settings: Community Settings Update Settings
Open the Services console and confirm that the ACT Log Processing Service has started.
Results: After this exercise, ACT 5.5 will be installed and configured on LON-DC1.
Note: LON-DC1 is the computer configured with the Application Compatibility Toolkit. LON-VS1 is the Windows Vista computer that will have the Data Collection Package installed.
When to monitor application usage: Duration: 60 Minutes Where to output collected data: LON-DC1 (\\LON-DC1\ACTLogs)
Save as C:\Data\DataCollectionPKG.msi.
Open the Task Manager, click the Processes tab, and then click Show processes from all users. Provide Administrator credentials in the User Account Control box. On the Processes tab, verify that the data collection is running by looking for the actdcsvc.exe process.
Results: After this exercise, a data collection package is created and then it must be installed on LON-VS1.
Note: LON-DC1 is the computer configured with the Application Compatibility Toolkit. LON-VS1 is the Windows Vista computer that has reported its application inventory.
Assign Microsoft Office PowerPoint Viewer 2007 (English) and Microsoft Office Word Viewer 2003 to the Customer Service subcategory. Select Microsoft BackInfo and Office Diagnostics Service. On the Actions menu, click Assign Categories. Create a new category called System Utilities. Add a subcategory called Desktops. Assign BackInfo and Office Diagnostics Service to the Desktops subcategory.
Save the filter report as Business Critical Apps in the Documents folder. Clear the filter to display all applications. Click the Toggle Filter button to close the Filter pane.
Results: After this exercise, application memory will be categorized and prioritized.
The main tasks for this exercise are as follows: 1. 2. Track application status. Create a custom issue.
Note: LON-DC1 is the computer configured with the Application Compatibility Toolkit. LON-VS1 is the Windows Vista computer that has reported its application inventory.
10
Click Save and then click the Solutions tab. Add a solution with the following options: Title: Office Diagnostics Service Fix Solution Type: Application has an update Solution Details: Install the latest Service Pack
Close all windows to return to the main Application Compatibility Manager window.
Results: After this exercise, the application status is tracked and a custom issue is created.
11
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL1 is the computer running Windows 7 with the Stock Viewer application installed.
12
13
Note: LON-DC1 is the computer configured with the Application Compatibility Toolkit. LON-CL1 is the Windows 7 computer that has the Stock Viewer application installed.
Click Launch. In the User Account Control box, type Administrator and then type the password: Pa$$w0rd. Click Yes at the prompt. Test the following tasks to record compatibility issues: Click OK on the Permission denied box. Click Trends. Click the Tools menu and then click Options.
14
Click Continue to close the error. Click the Tools menu and then click Show Me a Star.
Close the Stock Viewer application. Review the following tabs: File, Registry, Token, Name Space, and Other Objects. Note that these are the errors that were detected while SUA was monitoring the application. On the Mitigation menu, apply the mitigations.
15
Click Fix and provide the following information: Name of the program to be fixed: StockViewer Program file location: C:\Program Files\StockViewer\StockViewer.exe Compatibility Modes: None Compatibility Fixes: ElevateCreateProcess ForceAdminAccess LocalMappedObject VirtualizeHKCRLite
Name the database StockViewerFix and save it to C:\Data\StockViewerFix. Click Fix and provide the following information: Name of the program to be fixed: Star Program file location: C:\Program Files\StockViewer \DWM Compositing Rendering Demo.exe Compatibility Modes: None Compatibility Fixes: WinXPSP2VersionLie
Click Save. Right-click StockViewerFix, and then click Install. Close the Compatibility Administrator.
16
Module 3
Lab Instructions: Evaluating Windows 7 Deployment Methods
Contents:
Exercise 1: Planning a Windows 7 Deployment for a Small Network Exercise 2: Planning a Windows 7 Deployment for a Larger Network Exercise 3: Planning a Windows 7 Deployment for a Large Network Exercise 4: Planning a Windows 7 Deployment for an Enterprise Network 3 8 13 18
Bobby Moore, the manager of the Production department, wants to replace his existing Windows Vista workstations with Windows 7. You are tasked with creating the documents that detail the steps required to enable this deployment. You have been liaising with Charlotte Weiss in the IT Department for more information.
Supporting Documentation
E-mail thread of correspondence with Charlotte:
Ed Meadows
From: Sent: To: Subject: Hey Ed, That plant is fairly small, and it is located on the edge of Slough. The computers there all have static IP addresses as there is no DHCP provision. They have a single server that is running Windows Server 2008, configured as an RODC. The link to the head office in London is sometimes down, so it helps facilitate logons. That server also hosts all shared data. I hope that helps. Regards, Charlotte. ----- Original Message ----From: Ed Meadows [ed@contoso.com] Sent: 28 June 2009 10:52 To: Charlotte@contoso.com Subject: Network Services Hi Charlotte, As you may be aware, Bobby Moore wants us to come up with a plan for upgrading/migrating his Windows Vista computers throughout the Production department. Initially, he is talking about around ten computers in the production plant over at Slough. Can you please advise what network services we have in-place over there? Thanks, Ed Charlotte Weiss [charlotte@contoso.com] 28 June 2009 11:01 ed@contoso.com Re: Network Services
Ed Meadows
From: Sent: To: Subject: Hey Ed, Well, the departmental and corporate information is on the server, but the users Documents folder is not redirected; it is all local. Regarding custom applications, the whole of production uses a number of custom apps. At Slough, these applications are installed on some of the workstations, but not all. All workstations are installed with the standard office productivity suite: Excel, Word, and some with PowerPoint. If you need anything else, let me know. Charlotte. ----- Original Message ----From: Ed Meadows [ed@contoso.com] Sent: 15 July 2009 09:30 To: Charlotte@contoso.com Subject: Slough plant upgrade Hi Charlotte, You mentioned in the last email that Slough has a file server for shared data. What about user data, and I am especially thinking about application settings (custom dictionaries, email folders, and the like), and any other personal information? What I am concerned about, is how to deal with user data during the upgrade/migration, depending on the way we decide to go. Oh, and one other thing. Do you know if there are any custom applications installed at Slough? Thanks, Ed Charlotte Weiss [charlotte@contoso.com] 15 July 2009 09:51 ed@contoso.com Re: Slough plant upgrade
Slough Production Plant: Windows 7 Upgrade Proposal Document Reference Number: EM3007 Document Author Date Ed Meadows July 30
Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the Slough production plant. To migrate applications and user data during the upgrade process. Additional Information There are ten computers currently running Windows Vista at the Slough plant. The staff at Slough works in three shifts. This means that at some point in the day, all computers are not being used. 1. Is deployment by using WDS suitable in this situation? Why or why not?
2.
3.
4.
5.
How would you propose to handle user state data and application settings?
(continued)
Slough Production Plant: Windows 7 Upgrade Proposal Proposals
Supporting Documentation
E-mail thread of correspondence with Charlotte:
Ed Meadows
From: Sent: To: Subject: Attachment: Ed, Hammersmith has a larger number of workstations but there is an opportunity here. Unlike Slough, these machines are quite old and are due for replacement in the coming months. If we are going to be deploying a new OS, perhaps we can bring that replacement forward? Regarding applications, due to the reasonable link between Hammersmith and the head office, most settings are managed through Group Policy including application deployment. Having said that, most user-state data is still local we have not configured any folder redirection policies. To help with the infrastructure questions, I have attached a Visio diagram of Hammersmiths network in addition to a description of the services provided there. If you need anything else, ping me. Charlotte. ----- Original Message ----From: Ed Meadows [ed@contoso.com] Sent: 4 August 19:03 To: Charlotte@contoso.com Subject: Hammersmith Charlotte, Thanks for getting Slough operational. Quick work! I have just heard from Bobby again. He wants to get Hammersmith upgraded as soon as possible. What can you tell me about the infrastructure there? Also, as with last time anything I need to know about the applications deployed there, and the location of user-related data? Charlotte Weiss [charlotte@contoso.com] 5 August 2009 08:10 ed@contoso.com Re: Hammersmith Hammersmith.doc; Hammersmith.vsd
Ed
10
Contents of Hammersmith.doc: Twenty-five workstation computers installed with Windows Vista Enterprise edition. A single network printer is required. Windows Server 2008 Enterprise Edition (Server Core) deployed with the following roles: Domain Controller/Global Catalog DNS DHCP single scope to allocate addresses in the appropriate subnet. DFS-R used to distribute SYSVOL and the standard office applications. Shared folders used to store departmental data.
11
Hammersmith Production Plant: Windows 7 Upgrade Proposal Document Reference Number: EM1008 Document Author Date Ed Meadows August 10
Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the Hammersmith production plant. To ensure that user data is migrated as part of the upgrade process. To ensure that there is minimal downtime of the workstations at the Hammersmith plant, they are in constant use. Additional Information There are 25 computers running Windows Vista at the Hammersmith plant. The computers at Hammersmith are in constant use. 1. Is deployment by using WDS suitable in this situation? Why or why not?
2.
3.
4.
How would you propose to handle user state data and application settings?
12
(continued)
Hammersmith Production Plant: Windows 7 Upgrade Proposal Proposals
13
14
Supporting Documentation
E-mail thread of correspondence with Charlotte:
Ed Meadows
From: Sent: To: Subject: Attachment: Ed, Thanks and it was my pleasure. With regard to Reading, I have attached a couple of files you might find useful. There are lots of workstations, but all are a standard configuration. They work in three shifts down at Reading, so we need to think of a way of quickly deploying to the available computers during their respective downtime. Let me know if you need more information than the attachments provide. User data and settings are stored locally. Charlotte. ----- Original Message ----From: Ed Meadows [ed@contoso.com] Sent: 15 August 10:15 To: Charlotte@contoso.com Subject: Reading upgrades Charlotte, Good work down at Hammersmith! Bobby wants to complete the departmental upgrade. It is all at one site: Reading, or just outside Reading. Before I can complete the plan, I need to know a little more about the site. How many computers are located there? What network services are available? It might be nice if we can go for a little less of a hands-on approach with this deployment. Also, I do not know how much information you have on the location of user related data and settings. Thanks in advance, Charlotte Weiss [charlotte@contoso.com] 15 August 11:59 ed@contoso.com Re: Reading upgrades Reading.doc; Reading.vsd
Ed
15
Contents of Reading.doc: One hundred and fifty workstation computers installed with Windows Vista Enterprise in one of three subnets. A single network printer is provided in each subnet. Fundamental network services are provided on a backbone, including DHCP, DFS with replication from head office, DNS, and there is a local DC/GC. Each subnet hosts a Windows Server 2008 Enterprise Edition (Server Core) server deployed with the following roles: File Services Application Server
16
Production Department: Windows 7 Upgrade Proposal Document Reference Number: EM0109 Document Author Date Ed Meadows September 1
Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the rest of the production department based at the Reading plant. Additional Information There are 150 computers running Windows Vista at the Reading plant. At any time, around one third of all computers are not in use. The computers are all in one of three subnets, with core services on the backbone. Each subnet has its own file server that hosts shared data and applications. 1. Is deployment by using WDS suitable in this situation? Why or why not?
2.
3.
4.
How would you propose to handle user state data and application settings?
17
(continued)
Production Department: Windows 7 Upgrade Proposal Proposals
18
19
Supporting Documentation
E-mail thread of correspondence with Ryan Ihrig:
Ed Meadows
From: Sent: To: Subject: Attachment: Hi Ed, The best I can do is send over the network documentation. It is attached to this message. It will answer all of your questions. Regarding the applications, all workstations in each department has a standardized build, although the build varies from department to department. Finally, in terms of user data, we use folder redirection to store user settings and data onto the appropriate server; there is no user data stored locally. Ryan. ----- Original Message ----From: Ed Meadows [ed@contoso.com] Sent: 1 December 2009 17:55 To: Ryan@contoso.com Subject: Contoso Windows 7 upgrade Ryan, I have been working with Charlotte on a project to upgrade the computers in the Production department. We now need to upgrade the rest of the computers in Contoso, and I understand that you head up the support team at Kensington. I need to know what network infrastructure we have there so I can determine the appropriate deployment method. I also need an idea of how the workstations are distributed around the network. Finally, can you provide information about the applications on each computer and information about where user data resides, in other words, locally or on a server? Ryan Ihrig [Ryan@contoso.com] 2 December 2009 08:50 ed@contoso.com Re: Contoso Windows 7 upgrade Kensington.doc; Kensington.vsd
Many thanks, Ed
20
Contents of Kensington.doc: Each floor of the head office consists of two VLANs, each with 75 workstations. All workstations are connected to an Ethernet switch, and each VLAN has a Windows Server 2008 Enterprise Edition (Server Core) file server to support local data and applications. There are ten floors in the building, so that is approximately 1,500 workstation computers. To provide for core infrastructure services, there are four domain Windows Server 2008 Enterprise edition servers that provide the following services: DHCP DNS AD-DS, Global Catalog AD-CS DFS-R
In addition, there are two Windows Server 2008 Enterprise Edition (Server Core) servers installed with the Hyper-V role to support additional corporate services. There are three departments in Kensington: IT, Marketing, and Research. Contoso occupy the bottom two floors, Marketing is on the top four floors, and the rest of the floors are occupied by Research. Applications are deployed as part of a thick operating system build; those applications that fall outside of the scope of this departmental build are deployed using an Organizational Unit-based Group Policy Object (OU-based GPO). All user data is stored on local file servers by using folder redirection settings from GPOs. All workstations support PXE-boot. Kensington.vsd partial network diagram:
21
Contoso: Windows 7 Upgrade Proposal Document Reference Number: EM1712 Document Author Date Ed Meadows December 17
Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the Contoso organization. To deploy applications as part of the upgrade and ensure that all user data and settings are accessible after the upgrade. Additional Information There are 1,500 computers running Windows Vista at the Kensington head office. The staff at Kensington usually works standard office hours 9.00 a.m. until 5.30 p.m. 1. Do you envisage using deployment images?
2.
3.
4.
5.
How would you propose to handle user state data and application settings?
22
(continued)
Contoso: Windows 7 Upgrade Proposal Proposals
Module 4
Lab Instructions: Designing Standard Windows 7 Images
Contents:
Exercise 1: Planning the Imaging Strategy for a Branch Office Network Exercise 2: Planning the Imaging Strategy for an Enterprise Network 4 9
Job Aid
You might find the following job aid useful when determining the appropriate imaging strategy.
Supporting Documentation
E-mail thread of correspondence with Bobby Moore:
Charlotte Weiss
From: Sent: To: Subject: Charlotte, You are right that many of the computers have an identical build, but not all. Within the 25 computers at the plant, there are several distinct builds. Although application maintenance is done with GPOs, the line speed to the head office has proved inadequate for large application installations. It might be worth having a word with Ryan Ihrig at Kensington for the technical details. I have copied him in on this. I hope that helps. Regards Bobby. ----- Original Message ----From: Charlotte Weiss [charlotte@contoso.com] Sent: 12 August 2009 08:42 To: bobby@contoso.com Subject: Hammersmith Upgrade: Images Bobby, As you know, we are planning to upgrade the Hammersmith plant computers to Windows 7. The new workstations are arriving next week. Can you help me understand what applications are installed on which computers? The way I remember it, they were all identical and all applications are being deployed with GPOs. Can you confirm this? Thanks, Charlotte Bobby Moore [bobby@contoso.com] 12 August 2009 10:35 charlotte@contoso.com; ryan@contoso.com Re: Hammersmith Upgrade: Images
Charlotte Weiss
From: Sent: To: Subject: Charlotte, Bobby is correct; the line speed and reliability prohibit excessive use of GPOs for managing applications. At Hammersmith, they use Microsoft Office 2007 Professional on all computers. They also use a custom design program on about half of the machines. In addition, some of the computers also use some plant management software that runs in a VM; it is quite old, and the VM provides a DOS/Windows 3 environment that enables it to run. One other thing: Hammersmith is rather pressed for storage; their Server Core box is due for a disk upgrade shortly, so until then, try to conserve space. Good luck. Ryan. ----- Original Message ----From: Bobby Moore [bobby@contoso.com] Sent: 12 August 2009 10:35 To: charlotte@contoso.com; ryan@contoso.com Subject: Re: Hammersmith Upgrade: Images Charlotte, You are right that many of the computers have an identical build, but not all. Within the 25 computers at the plant, there are several distinct builds. Although application maintenance is done with GPOs, the line speed to the head office has proved inadequate for large application installations. It might be worth having a word with Ryan Ihrig at Kensington for the technical details. I have copied him in on this. I hope that helps. Regards Bobby. Ryan Ihrig [ryan@contoso.com] 12 August 2009 11:00 charlotte@contoso.com; bobby@contoso.com Re: Re: Hammersmith Upgrade: Images
Hammersmith Production Plant: Desktop Image Document Reference Number: CW1408 Document Author Date Charlotte Weiss August 14
Requirement Overview Design a Windows 7 image strategy that supports the deployment of the new operating system to newly delivered computers at the Hammersmith plant. Conserve server storage because the server will not be getting a disk upgrade in the near future and has limited capacity. Minimize support staff effort during the rollout. There are 25 computers in total, all of which use Office 2007 Professional. All computers connect to a printer, the driver for which is not in the current driver store in Windows 7. Ten computers use a custom line-of-business application that runs within a virtual machine; currently, the guest OS runs within Virtual PC 2007. The remaining group of 15 computers runs another LOB application that runs natively within Windows Vista. Additional Information 1. Will you use a standard image(s) or create a custom image(s)?
4. How will you handle the printer driver and required updates and patches?
5. How will you create the images that you plan to implement?
(continued)
Hammersmith Production Plant: Desktop Image Proposals
In addition, there are two Windows Server 2008 Enterprise Edition (Server Core) servers installed with the Hyper-V role to support additional corporate services. There are three departments in Kensington: IT, Marketing, and Research. IT occupies the bottom two floors, Marketing is on the top four floors, and the rest of the floors are occupied by Research. The specification of the computers installed varies from department to department, and within each department. All departments use departmental LOB applications; consequently, few computers are identically configured. Most, although not all, computers are installed with some elements of the Microsoft Office 2007 suite. Specifics depend on many factors, including security group membership of the user and the physical location of the computer. All computer settings are managed extensively with GPOs. This includes application deployment, update management, and security settings. The main tasks for this exercise are as follows: 1. 2. Read the scenario. Update the Kensington Head Office: Desktop Image document with your planned course of action.
10
Kensington Head Office: Desktop Image Document Reference Number: RI0201 Document Author Date Ryan Ihrig January 2
Requirement Overview Design a Windows 7 image strategy that supports the deployment of the Windows 7 operating system to all computers at the Kensington head office. Storage space on the file servers is not restricted. There is spare network bandwidth to support the deployment process. It is desirable to use GPOs to perform as much centralized management of computers as possible. Additional Information 1. Will you use a standard image(s) or create a custom image(s)?
4. How will you handle the various drivers, updates, and patches?
5. How will you deploy the images that you plan to implement?
11
(continued)
Kensington Head Office: Desktop Image Proposals
Module 5
Lab Instructions: Deploying Windows 7 by Using Windows AIK Contents:
Lab A: Installing the Windows Automated Installation Kit Exercise 1: Installing the Windows Automated Installation Kit Exercise 2: Identifying Resources and Tools Included with the Windows Automated Installation Kit Lab B: BuildingaReferenceImageUsingWindowsSIMandSysprep Exercise 1: Building a Custom Answer File by Using Windows SIM Exercise 2: Installing a Reference Computer from a DVD Using a Custom Answer File Exercise 3: Generalizing a Reference Computer by Using Sysprep Lab C: CreatingWindowsPEBootMedia Exercise 1: Adding Packages to Windows PE Exercise 2: Creating a Bootable Windows PE ISO Image Exercise 3: Starting the Windows PE Operating System Environment Lab D: CapturingandApplyingaWindows7ImageUsingImageX Exercise 1: Capturing an Image Using ImageX Exercise 2: Apply an Image Using ImageX Lab E: ServicingImagesby using DISM Exercise 1: Service an Offline WIM Image 3 4 7 12 13 16 18 19 21 23 25
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer.
Exercise 2: Identifying Resources and Tools Included with the Windows Automated Installation Kit
Scenario
Your manager has asked you to hold a meeting to explain the functions of the WAIK to the rest of the department. To prepare for this meeting, you need to review the resources and tools that are included with the Windows Automated Installation Kit. The main tasks for this exercise are as follows: 1. 2. 3. Examine the Windows Automated Installation Kit Start Menu folder. Examine the Windows Automated Installation Kit folder structure. Examine the Windows Automated Installation Kit Users Guide.
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer.
In addition to these settings, to assist with the customization process, you will need to install the system in Audit mode and have the system auto-log on five times. The main tasks for this exercise are as follows: 1. 2. 3. 4. 5. Mount the external media on LON-CL2. Create a new answer file. Add and configure windows settings. Validate the answer file. Unmount the external media on LON-CL2.
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer.
windowsPE
(continued)
Component x86_Microsoft-Windows-Setup\ImageInstall\OSImage \InstallTo x86_Microsoft-Windows-Setup\UserData x86_Microsoft-Windows-International-Core-WinPE x86_Microsoft-Windows-Shell-Setup\OEMInformation x86_Microsoft-Windows-Shell-Setup\OOBE x86_Microsoft-Windows-Shell-Setup\Autologon x86_Microsoft-Windows-Deployment\Reseal Configuration Pass windowsPE
All the settings you added must appear in the Answer File pane. Select and configure each setting as specified in the following table.
Component x86_Microsoft-Windows-International-CoreWinPE Value InputLocale = en-US SystemLocale = en-US UILanguage = en-US UILanguageFallback = en-US UserLocale = en-US UILanguage = en-US WillShowUI = OnError DiskID = 0 WillWipeDisk = true Extend = true Order = 1 Type = Primary
10
(continued)
Component Microsoft-Windows-Setup \DiskConfiguration \Disk\ModifyPartitions\ModifyPartition Value Active = true Format = NTFS Label = Windows Letter = C Order = 1 PartitionID = 1 WillShowUI = OnError DiskID = 0 PartitionID = 1 AcceptEula = true FullName = Administrator Organization = Contoso WillShowUI = OnError HelpCustomized = false Manufacturer = Contoso IT Group SupportHours = 9 - 5 SupportPhone = 555-9988 SupportURL = http://Technet.Microsoft.Com Enabled = true LogonCount = 5 Username = Administrator Password = Pa$$w0rd ForceShutdownNow = false Mode = Audit NetworkLocation = Work ProtectYourPC = 1
Microsoft-Windows-Shell-Setup\OOBE
11
12
Exercise 2: Installing a Reference Computer from a DVD Using a Custom Answer File
Scenario
After creating the answer file, you will build the reference computer. To accomplish this, you will install Windows 7 on LON-IMG1 from a DVD and use the answer file that you saved to the Diskette drive in the previous exercise. When you start a blank computer with a Windows DVD and a completed answer file, the operating system will be installed without user input. The main tasks for this exercise are as follows: 1. 2. Mount the external media on LON-IMG1. Start LON-IMG1.
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer. LON-IMG1 is the computer that will be used to install a fresh installation of Windows 7 using the custom answer file.
13
Exercise 3 can be completed with either 6294A-LON-IMG1 or 6294A-LON-IMG2, depending on available time. LON-IMG2 is used as the name in the exercise task steps.
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-IMG1 or LON-IMG2 is the computer that will be used to install applications and be prepared for imaging using Sysprep.
14
15
16
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer.
17
18
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer.
19
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer. LON-IMG1 or LON-IMG2 is the computer that will be used as the reference system.
20
21
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer. LON-IMG1 or LON-IMG2 is the computer that will be used as the reference system.
22
Note: The capture process will take approximately 20 minutes. To save time, the remainder of the lab will use an image that has already been prepared.
23
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer. LON-CL3 is the computer that will receive the new image.
24
Type Assign letter=C and press ENTER. Type Exit and press ENTER.
After the installation is complete, verify the following: Open computer properties to determine if the manufacturer and IT support information match the values used in the UnattendAnswer script. The custom applications are installed.
Shutdown LON-CL3.
Results: After this exercise, the image will be deployed to LON-CL3 and the customizations verified.
25
26
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the domain services. LON-CL2 is the computer running Windows 7 that will be used as the technician computer.
Setup
Before starting this lab, copy the LON-REF.wim file from the \\LON-DC1\Labfiles\Mod5\Image folder to the C:\Images folder on LON-CL2.
27
Module 6
Lab Instructions: Deploying Windows 7 by Using Windows Deployment Services
Contents:
Exercise 1: Designing the Windows Deployment Services Environment Exercise 2: Installing and Configuring the Windows Deployment Services Server Role Exercise 3: Adding Boot and Install Images to WDS Exercise 4: Provisioning Drivers by Using WDS Exercise 5: Deploying a Desktop Operating System Using WDS 3 7 9 10 12
Supporting Documentation
E-Mail from Adam Carter:
Ed Meadows
From: Sent: To: Subject: Hey Ed, Since the Marketing department has been chosen for the Windows 7 deployment pilot program, I think it would be great if we could deploy a Windows Server 2008 R2 Windows Deployment Services server role. We have a server named LON-DC1 that can be used for the server role. All of the new client computers will be PXEenabled. However there are some considerations that I will list below: LON-DC1 also hosts the DHCP server role for the department. LON-DC1 has two volumes: Drive C: which is 80 percent full, and Drive E:, which is only 10 percent full. The Marketing department does not have any special image requirements other than a default installation (all settings will be configured postdeployment). We do plan on deploying 64-bit laptops in the next few weeks. I have an updated driver for the VX 6000 Lifecam that I will have available for when we need it. To ensure security, we need to make sure that only known or approved computers can be installed over the network. We will start off with only a couple of computers, but do think about how we can scale WDS so that we have availability and also minimize network congestion. Adam Carter [Adam@contoso.com] 28 June 2009 11:01 ed@contoso.com Re: Windows Deployment Services for the Marketing Department
Windows Deployment Services Design and Configuration Document Reference Number: WDS2009 Document Author Date Requirement Overview To install and configure Windows Deployment Services server role. To deploy Windows 7 to the new Marketing department computers. Additional Information You have purchased 10 new computers for the Marketing department. The Marketing department has a single server name LON-DC1. 1. Since LON-DC1 also hosts the DHCP server role, how does this affect the Windows Deployment Services server role? Ed Meadows 2nd August
2.
3.
What types of images are required for your deployment? How can you organize the install images for future deployment with other departments?
4.
(continued)
Windows Deployment Services Design and Configuration 5. What specific platform considerations do you have for your deployment?
6.
What are some ways that you can provide availability and minimize network congestion?
Exercise 2: Installing and Configuring the Windows Deployment Services Server Role
Scenario
Your first step for the Windows 7 deployment is to install and configure the WDS server role. You will use the information gathered from the Windows Deployment Services Design and Configuration document. The main tasks for this exercise are as follows: 1. 2. Install the Windows Deployment Services server role. Configure Windows Deployment Services.
Note: LON-DC1 is the computer that is to be configured with the WDS server role.
PXE Server Initial Settings: Respond to all client computers (known and unknown) Require administrator approval for unknown computers: selected Add images to server now: Not selected
Results: After this exercise, you have installed and performed initial configuration tasks for the WDS server role.
Note: LON-DC1 is the computer that is configured with the WDS server role.
Results: After this exercise, you have added the default boot and install images from the Windows 7 DVD media to WDS.
10
Note: LON-DC1 is the computer that is configured with the WDS server role.
Available Driver Packages: Accept default selections. Driver Groups: Create a new driver group named: VX6000 Lifecam
11
Results: After this exercise, you have added a driver package to WDS and created a driver deployment filter.
12
Note: LON-DC1 is the computer that is configured with the WDS server role. LON-CL3 is a network client that does not contain any operating system.
13
Module 7
Lab Instructions: Deploying Windows 7 by Using Lite Touch Installation
Contents:
Lab A: Planning and Configuring MDT 2010 Exercise 1: Planning the MDT Lite Touch Environment Exercise 2: Installing MDT 2010 and Additional Component Files Exercise 3: Creating an MDT 2010 Deployment Share Lab B: Deploying Windows 7 by Using Lite Touch Installation Exercise 1: Configuring the MDT 2010 Deployment Share Exercise 2: Deploying Windows 7 and Capturing an Image of the Reference Computer Exercise 3: Configuring MDT 2010 to Deploy Windows 7 to the Target Computer Exercise 4: Deploying Windows 7 to the Target Computer 11 14 16 18 3 8 10
Supporting Documentation
E-mail thread with Jonas:
Adam Carter
From: Sent: To: Subject: Adam, You know my philosophy on this, keep it uncomplicated and reduce the opportunity for errors. I know there were a few complaints when we had to reimage several systems in Seattle after that virus outbreak but the company policy remains, all Contoso related files are to be stored on a server. Since we use roaming profiles I do not see the need to migrate profiles for users. Since there is nothing critical on the client systems I do not think we need to worry about that feature either. For the time being we are going to continue deploying applications to the client systems post installation. Unless purchasing changes their policies we do not want to deploy any applications until the requesting department has secured their licenses. As for the rest of the features, I like the idea of deploying from a central image and since we are not giving the users local administrative rights we need to include any drivers they might need, for instance the IntelliPoint drivers for the Microsoft Mice we use in our department. Keep in mind not all the custom applications have been tested in a 64 bit environment yet. If anything else comes up just use your best judgment and we can discuss it at the next meeting. Thanks, Jonas Jonas Brandel [jbrandel@contoso.com] 17 July 2009 2:30 PM Adam Carter [acarter@contoso.com] Re: Automated Windows 7 deployment
----- Original Message ----From: Adam Carter [acarter@contoso.com] Sent: 17 July 2009 11:15 AM To: Jonas Brandel [jbrandel@contoso.com] Subject: Re: Automated Windows 7 deployment Jonas, I have had a chance to download the Microsoft Deployment Toolkit. I am not sure if you are aware of all the features in the Toolkit. Besides deploying Windows 7 we could do the following: Partially Automated Deployment of Windows 7 (Lite-Touch) Fully Automated Deployment of Windows 7 (Zero-Touch) Deploy Windows 7 from an Image Deploy Applications Pre-Install device Drivers Migrate User Profiles Enable BitLocker on deployed systems
I know you want a report at the next department meeting. Do you have a preference for the features that we evaluate before then? Thanks, Adam ----- Original Message ----From: Jonas Brandel [jbrandel@contoso.com] Sent: 15 July 2009 09:30 AM To: Adam Carter [acarter@contoso.com] Subject: Automated Windows 7 deployment Adam, As discussed in the last planning meeting we are looking at rolling out Windows 7 next quarter. I want you to download the Microsoft Deployment Toolkit and evaluate it for use in automating the deployment of Windows 7. Thanks, Jonas
Microsoft Deployment Toolkit PlanningJob Aid Information Rationale for the Decision 32 bit Windows 7 64 bit Windows 7 What Operating 32 Windows Server System are you going 2008 R2 to deploy? 64 bit Windows Server 2008 R2 Question What System is going to be deployed as the Technicians system? Are you going to be deploying Applications? What MDT additional components are you going to install? Where will you store your distribution files? Windows 7 client Windows 2008 R2 server Yes No MAP WAIK USMT Local Deployment Share Remote Deployment Share
(continued) Microsoft Deployment Toolkit PlanningJob Aid Information Rationale for the Decision Will you be deploying Yes any drivers not included with No Windows 7? Question Will you deploy across the network, with removable media, or both? Network Removable Media New Computer Upgrade Existing Computer Refresh Computer Replace Computer Full OS File Set Custom WIM Professional Ultimate Business Enterprise Multiple Activation Key (MAK} Key Management Service(KMS)
Which Deployment Scenario will you use? Will you deploy a full set of operating system files or a custom Windows Imaging Format (WIM)? Which product editions will you deploy? How will you handle product keys and licensing?
Results: After this exercise you have planned your MDT 2010 deployment.
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL2 is the computer running Windows 7 that will contain MDT 2010.
Question: What category is the Windows Automated Installation Kit in and what is the status?
Results: After this exercise you should have installed Windows AIK and verified the installation.
10
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL2 is the computer running Windows 7 that contains MDT 2010.
Results: After this exercise you should have created a new deployment share.
11
12
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL2 is the computer running Windows 7 that contains MDT 2010.
13
(continued)
On this wizard page OS Settings Do this Full Name: Admin Organization: Contoso LTD. Do not specify an Administrator password at this time Review the Summary. Click Finish.
14
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL2 is the computer running Windows 7 that contains MDT 2010.
Note: For the Lab the LiteTouchPE_x86.iso file has already been copied to the host machine.
f Task 2: Start the reference computer with the LTI bootable media
To deploy using the Lite Touch Installation you need to mount the boot image to the reference computer and boot it into the WinPE environment. On LON-IMG1, mount C:\Program Files\Microsoft Learning\6294 \drives\LiteTouchPE_x86.iso. Start LON-IMG1.
15
Select a task sequence to execute on this computer Configure the computer name Join the computer to a Domain or workgroup Specify whether to restore user data Language and other preferences Set the Time Zone Specify whether to capture an image Ready to begin
Accept the default selections. Accept the default selections. Capture an image of this reference computer
Click Begin.
Review the Deployment Summary page for any errors, click Finish, and turn off LON-IMG1.
Results: After this exercise you should have created the LTI bootable media and started LON-IMG1 to complete the deployment wizard.
16
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL2 is the computer running Windows 7 that contains MDT 2010.
17
Standard Client Task Sequence WIN7_REFERENCEDDRIVE in WIN7_REFERENCE WIN7_REFERENCE.wim Accept the default selections. Full Name: Organization: Admin Contoso LTD.
Admin Password
Administrator Password: Pa$$w0rd Please confirm Administrator Password: Pa$$w0rd Review the summary. Click Finish.
Summary Confirmation
Results: After this exercise you should have added the captured image to the deployment workbench and created a task sequence for the target computer.
18
Note: LON-DC1 is the computer running Windows Server 2008 R2. LON-CL2 is the computer running Windows 7 that contains MDT 2010. LON-CL3 is the computer that will be installed with a new copy of Windows 7.
Specify Credentials for connecting to network shares Select a task sequence to execute on this computer Configure the computer name
LON-CL3
19
(continued)
On this wizard page Join the computer to a Domain or workgroup Specify whether to restore user data Language and other preferences Set the Time Zone Specify the BitLocker configuration Ready to begin Do this Join a domain Domain: Contoso Accept the default selections.
Click Begin.
Review the Deployment Summary page for any errors; and then click Finish and turn off LON-CL3.
Module 8
Lab Instructions: Deploying Windows 7 by Using Zero Touch Installation
Contents:
Exercise 1: Planning the Zero Touch Installation Environment Exercise 2: Preparing the Zero Touch Installation Environment Exercise 3: Configuring Deployment Packages and System Images Exercise 4: Configuring and Advertising a Client Task Sequence 3 7 9 13
Supporting Documentation
E-Mail from Max Stevens:
Ed Meadows
From: Sent: To: Subject: Hi Ed, For the pending Windows 7 deployment for the Research Department, I think we should take advantage of our existing Configuration Manager environment and use Zero Touch Installation. Here are some considerations for you to think about: The current Configuration Manager solution uses Configuration Manager 2007 SP1 R2. We have not used operating system deployment features previously and so we will need to install and configure all that is required. You do not have to be concerned about the Configuration Manager architecture, however you do need to consider what is required for operating system deployments. I think we should also integrate MDT 2010 functionality in order to use some of its advanced task sequences. The Configuration Manager site server is called LON-SVR1. It contains Windows Server 2008 R2. Max Stevens [Max@contoso.com] 3 August 2009 08:01 ed@contoso.com Re: Zero Touch Deployment for the Research Department
LON-DC1 is the domain controller, which also hosts the DHCP server role. We will start off with a pilot deployment of 5 computers. I have already created a Collection named Windows 7 Pilot Deployment that we can use. We will be initially deploying 50 bare metal computers using a custom image, however for the pilot deployment, we will just use the standard Windows 7 media and default boot images. We plan on deploying 64-bit laptops in the next few months. I have an updated driver for the VX 6000 Lifecam that I would like to have available for when we need it. All newly deployed clients need to be managed by Configuration Manager 2007.
Before you start to configure the Zero Touch Installation solution, can you please answer the questions on the Zero Touch Installation Design and Configuration worksheet for me to review? Thanks and regards Max.
Zero Touch Installation Design and Configuration Document Reference Number: ZTI2009 Document Author Date Ed Meadows 3rd August
Requirement Overview To install and configure a ZTI using MDT 2010 and System Center Configuration Manager 2007 SP2. To deploy Windows 7 to the new Research department computers.
(continued)
Zero Touch Installation Design and Configuration Additional Information You have purchased 50 new computers for the Research department. 1. Given the high-level explanation of the existing Configuration Manager environment, is the current version of Configuration Manager sufficient? What do you need to do in order to incorporate MDT 2010 into the solution?
2.
What do you need to do to LON-SVR1 in order to support clients booting over the network?
3.
How do you ensure that all newly deployed clients are managed by Configuration Manager?
4.
What steps must you perform from the Configuration Manager Console to prepare the Operating System Image to be deployed to clients?
5.
What is your final main task for configuring ZTI from within the Configuration Manager console?
Note: LON-DC1 is the computer configured as a domain controller. LON-SVR1 is the computer that is to be configured with MDT 2010 and installed with the WDS server role. LON-DC1 is also assigned the PXE service point role.
On LON-SVR1, under the Site Systems node, install the PXE service point role with the following options: Fully Qualified Domain Name: LON-SVR1.CONTOSO.COM System Role Selection: PXE service point PXE Service Point Configuration: open all required ports Allow this PXE service point to respond to incoming requests: Enabled Enable unknown computer support: Enabled Require a password for computers to boot using PXE: Not Enabled Respond to PXE requests on all network interfaces: Selected Delay (seconds): 0
Note: LON-DC1 is the computer configured as a domain controller. LON-SVR1 is the computer that is configured with Configuration Manager 2007.
Expand Packages, expand Microsoft Configuration Manager Client Upgrade 4.0 ALL, and then click Distribution Points. Right-click Distribution Points and then use the New Distribution Points Wizard to distribute the package to the LON-SVR1 distribution point. (Do not select the LON-SVR1\SMSPXEIMAGES$ distribution point because this one is used for the PXE boot environment.)
10
Expand Operating System Images, expand Windows 7 ENTERPRISE, and then click Distribution Points. Right-click Distribution Points, and then use the New Distribution Points Wizard to distribute the package to the LON-SVR1 distribution point. (Do not select the LON-SVR1\SMSPXEIMAGES$ distribution point because this one is used for the PXE boot environment.)
11
Expand Operating System Install Packages, expand Windows 7 ENTERPRISE, and then click Distribution Points. Right-click Distribution Points and then use the New Distribution Points Wizard to distribute the package to the LON-SVR1 distribution point. (Do not select the LON-SVR1\SMSPXEIMAGES$ distribution point because this one is used for the PXE boot environment.)
12
In the console pane, click the Drivers node. In the details pane, select both drivers. Right-click the selected drivers and then click Add or Remove Drivers to Packages. In the Add or Remove Drivers to Packages dialog box, select the check box next to Driver List. Select the check box next to Update distribution points when finished, and then click OK.
Results: After this exercise, you have added all required images and created required packages for the client deployment task sequence.
13
Note: LON-DC1 is the computer configured as a domain controller. LON-SVR1 is the computer that is configured with Configuration Manager 2007.
On the Details page, configure the following options: Join a domain: Selected Domain: Contoso.com Account: Username: Contoso\Administrator Password: Pa$$w0rd
14
On the Capture Settings page, select This task sequence may be used to capture an image, and configure the following settings: Capture destination: \\LON-DC1\Labfiles\Source\Win7.wim Capture account: Username: Contoso\Administrator Password: Pa$$w0rd
On the Boot Image page, configure the following options: Specify an existing boot image package: Boot image (x86)
On the MDT Package page, configure the following options: Create a new Microsoft Deployment Toolkit Files Package: selected Package source folder to be created: \\LON-DC1\Labfiles\MDTFiles
On the MDT Details page, configure the following options: Name: MDT Source Files Version: 1.0 Language: English Manufacturer: Microsoft Comments: <Current Date>
On the OS Image page, configure the following options: Specify an existing OS install package: Selected Select a Package: Windows 7 Enterprise
On the Client Package page, configure the following options: Specify an existing ConfigMgr client package: Selected Select a Package: Configuration Manager Client Upgrade
On the USMT Package page, configure the following options: Create a new USMT package: Selected Path to USMT executables and related files: C:\Program Files\Windows AIK\tools\USMT
15
On the USMT Details page, configure the following options: Name: MDT USMT Package Version: 1.0 Language: English Manufacturer: Microsoft Comments: Current Date
On the Settings Package page, configure the following options: Create a new settings package: Selected Package source folder to be created: \\LON-DC1\Labfiles\MDTFiles
On the Settings Details page, configure the following options: Name: MDT Settings Files Version: 1.0 Language: English Manufacturer: Microsoft Comments: <Current Date>
On the Sysprep Package page, select No Sysprep package is required. Click Next to begin the creation of the packages and task sequence. After the Task Sequence is created, click the Task Sequences node, right-click Windows 7, and then click Edit. Take note of, but do not change, the various tasks that make up the Windows 7 task sequence.
16
Microsoft MDT USMT Package 1.0 English Do not select the LON-SVR1\SMSPXEIMAGES$ distribution point because this one is used for the PXE boot environment. Wait a few minutes before continuing with the next task.
Schedule Mandatory assignments: As soon as Possible Ignore maintenance windows when running program: Enabled Program rerun behavior: Always rerun program Leave all other defaults
Distribution Points Access content directly from a distribution point when needed by the running task sequence: Enabled Leave all other defaults Interaction: Leave all defaults Security: Leave all defaults
In the console pane, expand the Computer Management\Collections node. Right-click the Unknown Computers collection and verify that the Windows 7 Deployment task sequence has been advertised to this collection.
17
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Module 9
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Contents:
Lab A: Migrate User State by Using WET (Optional) Exercise 1: Preparing the WET Source Files Exercise 2: Capturing User State Information from a Source Computer Exercise 3: Loading User State Information to a Destination Computer Lab B: Migrating User State Using USMT 4.0 Exercise 1: Planning for the User State Migration Exercise 2: Creating USMT Migration Scripts Exercise 3: Capturing and Restoring User State by Using USMT Lab C: Migrating User State Using Hard-Link Migration Exercise 1: Performing a Hard-Link Migration 20 10 15 17 3 5 7
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Lab Instructions: Migrating User State by Using WET and USMT 4.0
The main tasks for this exercise are as follows: Put WET on a network share.
Note: LON-DC1 is the computer that is running Windows Server 2008 R2. LON-CL1 is the computer running Windows 7, and LON-VS1 is the computer running Windows Vista.
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Has Windows Easy Transfer already saved your files from your old computer to an external hard disk or USB flash drive?: No Do you need to install Windows Easy Transfer on your old computer?: I need to install it now How do you want to install Windows Easy Transfer on your old computer?: External hard disk or shared network folder Browse for folder: \\LON-DC1\Data
Lab Instructions: Migrating User State by Using WET and USMT 4.0
The main tasks for this exercise are as follows: Capture settings from LON-VS1.
Note: LON-DC1 is the computer that is running Windows Server 2008 R2. LON-CL1 is the computer running Windows 7, and LON-VS1 is the computer running Windows Vista.
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Profiles to be migrated: Contoso\Don Excluded items from the profile: Music, Saved Games, Videos Password: Pa$$w0rd Save your Easy Transfer file: \\LON-DC1\Data\DonProfile
Close WET.
Results: After this exercise, you should have captured user state information for Don and stored the information at \\LON-DC1\Data.
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Note: LON-DC1 is the computer that is running Windows Server 2008 R2. LON-CL1 is the computer running Windows 7. And LON-VS1 is the computer running Windows Vista.
Use the Windows Easy Transfer Reports to view the Transfer report and the Program report. Log off LON-CL1.
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Lab Instructions: Migrating User State by Using WET and USMT 4.0
10
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Supporting Documentation
E-mail from Max Stevens:
Ed Meadows
From: Max Stevens [Max@contoso.com] Sent: 10 August 2009 08:01 To: ed@contoso.com Subject: Re: User State Migration for the new Research Department Windows 7 computers Hi Ed, We have 10 new Windows 7 computers that are being deployed within the Research department. The people that are receiving the new computers have asked whether they can have their user state migrated from their old computers. What I want you to do is use USMT 4.0 to help with the user state migration. Here are some additional things to consider: The old computers are all Windows Vista 32-bit computers. All computers have the 2007 Office system installed. Windows Vista Gadget settings should not be migrated from Windows Vista to the new Windows 7 computers. The contents of the Shared Video, Shared Music, and Shared Pictures folders should not be migrated from Windows Vista to the new Windows 7 computers.
Lab Instructions: Migrating User State by Using WET and USMT 4.0
11
We have a custom folder named ResearchApp that has to be migrated from all the old computers to the new Windows 7 computers. All domain profiles that are on each existing computer should be migrated to the new system. There is a local service account on each Windows Vista computer called DBService that will also have to be migrated to the new Windows 7 computers. Each Windows Vista computer has a local account called LocalAdmin. This account should not be migrated to the new Windows 7 computers. Please make sure that all encrypted files are also migrated from the old computers to the new computers. You can use \\LON-DC1\Data as a location to store the data store during the migration task. The data store should be compressed in order to minimize space. Since there is no confidential information on these specific computers, we do not need the migration store encrypted.
To help you organize your migration plan, please use the USMT Planning Job Aid before you start the migration task. Thanks and regards Max.
12
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Question
Lab Instructions: Migrating User State by Using WET and USMT 4.0
13
(continued) Question User State Migration PlanningJob Aid Department Name: __________________ Information Details Local accounts Accounts to be migrated Domain accounts
Custom files or folders to migrate Are there any encrypted files to consider? Yes No
14
Lab Instructions: Migrating User State by Using WET and USMT 4.0
(continued) Question User State Migration PlanningJob Aid Department Name: __________________ Information Details Config.xml MigApp.xml XML files to be used in the migration MigUser.xml MigDocs.xml Custom xml file Custom xml file
Results: After this exercise, you have a plan on how you will migrate the user state from the old Windows Vista computers to Windows 7.
Lab Instructions: Migrating User State by Using WET and USMT 4.0
15
Note: LON-DC1 is the computer that is running Windows Server 2008 R2. LON-CL1 is the computer running Windows 7 and LON-VS1 is the computer running Windows Vista.
Change to drive F and then create a Config.xml file by using the following command: scanstate /i:migapp.xml /i:miguser.xml /genconfig:config.xml
At the command prompt type notepad config.xml to view the config.xml file.
16
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Modify the xml code to exclude the following from the migration: Gadgets Shared Video Shared Music Shared Pictures
Hint: For each of the folders, look for component displayname and then change the migrate attribute to No.
Results: After this exercise, you have created and modified XML files that you need for the User state migration task.
Lab Instructions: Migrating User State by Using WET and USMT 4.0
17
Note: LON-DC1 is the computer that is running Windows Server 2008 R2. LON-CL1 is the computer running Windows 7 and LON-VS1 is the computer running Windows Vista.
18
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Change to drive F and restore user state on the destination computer by using the following command:
Loadstate \\LON-DC1\Data /i:migapp.xml /i:miguser.xml /i:folders.xml /ue:LocalAdmin /ui:DBService /lac:Pa$$w0rd /lae
Lab Instructions: Migrating User State by Using WET and USMT 4.0
19
20
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Note: LON-DC1 is the computer that is running Windows Server 2008 R2. LON-VS1 is the computer that is running Windows Vista.
Install Windows 7 using the following options: Do not get the latest updates for installation Installation type: Custom (advanced)
Lab Instructions: Migrating User State by Using WET and USMT 4.0
21
After the installation is complete, provide the following options: Default Country, Time and currency, and Keyboard layout User name: Alan Computer name: LON-VS1 Password: Pa$$w0rd Help protect your computer: Use recommended settings Time and date settings: default Computers current location: Work network
Change to drive F and capture user state with the following command:
Scanstate C:\store /o /hardlink /nocompress /i:migapp.xml /i:miguser.xml /offlineWinOld:c:\Windows.old\Windows
At the command prompt load user state by using the following command:
Loadstate C:\store /lac /lae /i:migapp.xml /i:miguser.xml /sf /hardlink /nocompress
22
Lab Instructions: Migrating User State by Using WET and USMT 4.0
Module 10
Lab Instructions: Designing, Configuring, and Managing the Client Environment
Contents:
Lab A: Designing and Configuring the Client Environment Exercise 1: Designing a Client Environment Exercise 2: Implementing a Client Configuration Lab B: Troubleshooting GPO Issues Exercise 1: Resolving a GPO Application Problem 15 3 9
Note: Your instructor may run elements of this lab as a class discussion.
Supporting Documentation
Contents of Summary.doc: Contoso implements a standard desktop build across the various departments within the organization; each department has a slightly different initial desktop build. Many standard office productivity applications are deployed as part of this build; however, some line-of-business applications must be additionally deployed after the desktop deployment process. The following table summarizes the Contoso domain-level settings; these settings must not be overridden by lower-level settingsthat is, they must be enforced.
Setting Enforce password history Minimum password length Value 12 passwords remembered 6 characters
(continued)
Setting Account lockout duration Account lockout threshold Reset account lockout counter after Inbound firewall rule Application Restrictions Value 30 minutes 3 attempts 30 minutes Enable ICMPv4 on only domain profile Only allow scripts signed by Microsoft to execute Auto-start Application identity http://lon-dc1
Aside from these domain-level settings, it is important that the following departmental settings are observed where they do not conflict with the domain settings.
Department IT Applications Office Visio Drive mappings \\lon-dc1\Data Security settings Desktop Documents redirected to departmental shared folder on LON-DC1
Research
\\lon-dc1\Data
Marketing Production
Note: It is vital that IT department users can run scripts than are not signed by Microsoft.
Group Policy Objects for Contoso Document Reference Number: EM1109 Document Author Date Requirement Overview To determine which Group Policy Objects are required, and linked to which Active Directory objects, in order to address the domain and departmental requirements in the Summary document. You may use the Contoso GPO.vsd diagram to sketch your answer if you wish. Your plan should include how you intend to address each desired setting; that is, which policy or, where necessary, which preference setting. Additional Information 1. Where will you configure the domain-level settings outlined in the Summary document? Ed Meadows November 2009
2.
What impact does the fact that IT users must be able to run unsigned scripts have on your GPO strategy?
3.
How will you handle application deployment for the various departments?
4.
How will you restrict the Production department users from running Internet Explorer?
5.
(continued)
Group Policy Objects for Contoso 6. How do you intend to manage the IT departments requirement for a standard Documents folder?
7.
Sketch, or document, the intended GPO and how they are linked to AD DS objects on the supplied diagram. Indicate which settings will be configured by which object. Note: It is not necessary to detail the precise GPO settings.
Proposals Either complete this section, or else use the Contoso GPO.vsd diagram to document your plan.
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which is the domain controller for Contoso. LON-CL1 and LON-CL2 are both computers running Windows 7.
10
Edit the Default Domain Policy. In Group Policy Management Editor, navigate to User Configuration/Policies /Windows Settings/Internet Explorer Maintenance/URLS. From Important URLs, configure the Home page URL: http://lon-dc1 In Group Policy Management Editor, navigate to Computer Configuration /Policies/Windows Settings/Security Settings/Windows Firewall with Advanced Security/Windows Firewall with Advanced Security LDAP://CN={GUID}. Create a new custom inbound rule that allows ICMPv4 packets for the domain profile. Call the rule Allow ping.
11
In the Group Policy Management Editor, navigate to User Configuration /Preferences/Windows Settings/Drive Maps. Create a new Mapped Drive: Location box, type \\lon-dc1\data. Select the Reconnect check box. In the Use list, click G. Click the Common tab. Configure Item-level targeting for Domain. NetBIOS domain name: CONTOSO.
In the Group Policy Management Editor, navigate to Computer Configuration /Policies/Windows Settings/Security Settings/System Services. Configure the Application Identity service to start automatically. Close Group Policy Management Editor.
f Task 6: Move the two desktop computers into the appropriate OUs
Open Active Directory Users and Computers. Move the LON-CL1 computer from the Computers container to the IT organizational unit. Move the LON-CL2 computer from the Computers container to the Production organizational unit. Close Active Directory Users and Computers.
12
13
Close all open windows. Switch to the LON-CL2 computer. Open a command prompt, and at the Command Prompt, type copy con test.vbs and press ENTER. At the Command Prompt, type msgbox test and press ENTER. At the Command Prompt, press F6, and then press ENTER. At the Command Prompt, type test.vbs and press ENTER. Verify that an unsigned script did not run. Click OK. Close all open windows.
Results: After this exercise, you have implemented the domain-level elements of your GPO plan.
Important: Do not restart the virtual machines. You will need them for the subsequent lab.
14
15
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which is the domain controller for Contoso. LON-CL1 and LON-CL2 are both computers running Windows 7.
16
At the OK to logoff? (Y/N) prompt, type N and press ENTER. Restart the computer. Log on to the LON-CL1 virtual machine as CONTOSO\Ryan with a password of Pa$$w0rd. Switch to the LON-CL2 computer and log off. And then log on to the LON-CL2 virtual machine as CONTOSO\administrator with a password of Pa$$w0rd. Open a command prompt, and in the Command Prompt, type gpupdate /force and then press ENTER. At the OK to logoff?. (Y/N) prompt, type N and press ENTER. Restart the computer. Log on to the LON-CL2 virtual machine as CONTOSO\Jens with a password of Pa$$w0rd.
17
In the Internet Explorer dialog box, click Add. In the Trusted sites dialog box, click Add, and then click Close.
18
Click the Settings tab, and then click show all. Which settings are being applied by the Default Domain Policy?
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Module 11
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Contents:
Lab A: Determining the Application Deployment Method Exercise 1: Determining the Application Deployment Method Lab B: Customizing the Microsoft Office Professional Plus 2007 Installation Exercise 1: Creating a Setup Customization File Lab C: Planning and Managing Updates by Using WSUS Exercise 1: Planning Group Policy Automatic Update Settings Exercise 2: Configuring Automatic Update Settings by Using Group Policy Exercise 3: Approving and Deploying an Update by Using WSUS 12 16 18 7 2
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Supporting Documentation
E-Mail from Adam Carter:
Ed Meadows
From: Sent: To: Subject: Hi Ed, Along with the Windows 7 deployment, the Marketing department has a number of application requirements. I know that there are a number of options for providing these applications. I need you to determine the most appropriate method. I have outlined a list of requirements for you to assist in your planning. I am also providing a worksheet for you to fill out that will help organize and document your decisions. Here is the list of comments and requirements: All members of the Marketing department need to have Microsoft Office 2007 Professional Plus installed on their workstations. We have a network installation point already set up in the department, and so we want to be able to maintain full control of the customization and deployment processes for this application. All members of the Marketing department need to have Adobe Reader installed on their workstations. This is actually an organization-wide policy and so you have to consider the best method to deploy this throughout the entire company. Several users have reported that they use customized templates that required Office 2003. I want them all upgraded to the 2007 Office system, however you need to think of a way that we can still provide Office 2003 to these users for when they need it. Contoso has an Active Directory domain. Contoso has deployed Configuration Manager 2007, although it is currently only used for inventory reports. We do not administer the Configuration Manager 2007 environment. Adam Carter [Adam@contoso.com] 01 Sept 2009 10:05 ed@contoso.com Re: Application Deployment for the Marketing Department
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Application Deployment Worksheet Document Reference Number: AD2009 Document Author Ed Meadows
Requirement Overview Determine the most appropriate method for deploying corporate and departmental applications. Questions 1. Does the current infrastructure support any automated deployment methods?
2.
What are the advantages and disadvantages of the current deployment options available to Contoso?
3.
Based upon Adams requirements, which method should you consider to deploy the 2007 Office system?
4.
Based upon Adams requirements, which method should you consider to deploy Adobe Reader?
5.
What can you do to ensure that Office 2003 is still available for users that require the use of the customized templates?
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
The main tasks for this exercise are as follows: 1. 2. 3. Configure the Setup category. Configure the Features category. Install the 2007 Office system using the Setup Customization File.
Note: LON-DC1 is the computer running Windows Server 2008 R2 and which contains the Microsoft Office network installation point. LON-CL1 is the computer running Windows 7.
Create a new setup customization file for the Microsoft Office Professional Plus 2007 product. Configure the following for the Setup category: Default installation path: ProgramFilesFolder\Microsoft Office Organization: Contoso Additional network sources: LON-SVR2 Licensing and user interface: I accept the terms in the License Agreement: selected Display level: Basic Completion notice: selected
Remove previous installations: Default Office Security Settings: Add \\LON-DC1\Data and all subfolders as a trusted location. Modify Setup Properties: HIDEUPDATEUI configured to be True.
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Feature installation states: Configure Microsoft Office Publisher and Microsoft Office Access as Not Available. Also configure Microsoft Office Excel Sample Files as Not Available.
f Task 3: Install the 2007 Office System using the Setup Customization
File
Log on to LON-CL1 as Contoso\Administrator with the password of Pa$$w0rd. Install the 2007 Office system from the following location: \\LON-DC1\Labfiles\Office2007\setup.exe. After the installation is complete, verify that your customizations are implemented.
Results: After this exercise, you have created a Microsoft Office setup customization file and saved it in the Updates folder on the network installation point. You then installed the 2007 Office system and verified that the setup customization file was applied during installation.
10
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
11
12
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
13
Supporting Documentation
E-Mail from Adam Carter:
Ed Meadows
From: Sent: To: Subject: Hi Ed, Now that we have deployed Windows 7, we need to determine how to best deploy operating system and software updates to the client computers. Here is a summary of my thoughts and requirements: There is a Windows Server Update Services 3.0 deployment project underway. We should request for our department to be included. I would like all of our department computers to have their own approval and deployment of software updates. All of our department client computers need to contact the WSUS server instead of the Internet in order to receive updates. Please research which Group Policy settings need to be configured and fill out the Group Policy Settings Configuration Request attached to this email. All updates need to be automatically downloaded and installed on client computers every day at 5:00PM. All client computers should check for updates at least every 8 hours. Adam Carter [Adam@contoso.com] 15 Sept 2009 9:00 ed@contoso.com Re: Windows updates for the Marketing Department
14
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Group Policy Settings Configuration Request Details Individual requesting GPO changes Technical reason for GPO change Scope of management for the requested GPO Setting Name Configuration
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
15
16
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Note: LON-DC1 is the computer running Windows Server 2008 R2 where you configure the GPO. LON-CL1 is the client computer running Windows 7.
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
17
Specify intranet Microsoft update service location: Set the intranet update service for detecting updates: http://LON-DC1 Set the intranet statistics server: http://LON-DC1
f Task 2: Verify that the Automatic Updates policy settings have applied
Log on to LON-CL1 with the user name Administrator and the password Pa$$w0rd. Open a command prompt and type gpupdate /force to update Group Policy. Open Windows Update and click Change settings. Notice the information message at the top of the window stating that some settings are managed by the system administrator. Also notice that some of the configuration settings are grayed out.
Results: After this exercise, you have configured Group Policy to automatically apply Windows Update configuration settings to client computers.
18
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
Note: LON-DC1 is the computer running Windows Server 2008 R2 which has WSUS installed. LON-CL1 is the client computer running Windows 7.
Lab Instructions: Planning and Deploying Applications and Updates to Windows 7 Clients
19
Approve the installation for the following Critical Updates: Update for the Office System (KB967642)
On LON-CL1, use Windows Update to check for updates. Install any updates that are found.
Results: After this exercise, you have approved and deployed an update using WSUS 3.0.
Module 12
Lab Instructions: Deploying Windows 7 Challenge Scenario
Contents:
Lab A: Planning an End to End Windows 7 LTI Deployment Exercise 1: Planning the MDT Lite Touch Environment Lab B: Deploying Windows 7 Using the LTI Deployment Plan Exercise 1: Performing a Network Assessment Exercise 2: Configuring MDT 2010 for an LTI Deployment Exercise 3: Configuring WDS for a PXE and Multicast Deployment Exercise 4: Configuring an MDT 2010 Deployment Share Exercise 5: Creating the Reference Computer Exercise 6: Preparing the Deployment Task Sequences Exercise 7: Performing an Upgrade on Target Computers 10 13 14 16 20 22 25 2
Supporting Documentation
E-Mail from Jonas:
Adam Carter
From: Sent: To: Subject: Adam, Your MDT presentation was impressive. I apologize for notifying you on such short notice, but Wendy Richardson, the IT VP, has decided that the Akron office needs to be upgraded immediately to Windows 7 to support another initiative she has in the works. Unfortunately, this upgrade will need to occur before the end of the fiscal year and there is simply not a lot of budget dollars left to make this happen, so you will need to do everything remotely. I know you are not familiar with the Akron office, so here is a quick rundown. There are 30 desktop systems in the office and one Domain Controller. Currently, all users save all their work locally. The office has a budget for a file sever next fiscal year. As a result, you will need to preserve everyones local information during the migration because there is not enough bandwidth to have the users save their files to the corporate servers. We need a migration plan from you by the end of the week that includes the following: 1) A plan for assessment of the systems in the Akron office. 2) A list of criteria for determining if systems need to be upgraded or replaced in the Akron office. The office manager is definitely getting a new system; however, there is only 5000 U.S. dollars budgeted for hardware upgrades to get all systems to a level where they can run Windows 7 effectively. If a memory and/or hard drive upgrade will get a users system to a Windows 7 recommended level, that will be preferred instead of replacement. 3) A plan to deploy all systems over the course of a single weekend. There will be local assistance available, but do not plan for any technical savvy. The local support person will probably not be a lot of assistance beyond unpacking and plugging in new systems, power cycling the systems, and pushing a few keys. In addition, the office manager does not want to keep this person in the office on a weekend any longer than is absolutely necessary. Jonas Brandel [jbrandel@contoso.com] 17 July 2009 2:30 PM Adam Carter [acarter@contoso.com] Re: Automated Windows 7 deployment
4) New systems will require Office 2007 to be deployed. 5) Include drivers for all client hardware not included in Windows 7. 6) A recovery plan if anything goes awry. Thanks, Jonas Brandel
f Task 2: Use the following decision tree and checklist to help facilitate
the creation of the deployment plan
Create a deployment plan using the following aids.
64 Bit
32 Bit
Required Components
Install MDT
Install WAIK
Planning Components
YES
Install MAP
YES
Installation Components
NO
Install ACT
Prepare CD/DVDs
Media
Deploying OS through?
NETWORK
Configure DHCP
PXE Boot
MultiCast Deployment? NO
YES
Prepare WDS
YES
To Page 2
From Page 1
YES
YES
ACT
Local Deployment Share Remote Deployment Share
CD Network Share
Yes No
Yes No Network Removable Media New Computer Upgrade Existing Computer Refresh Computer Replace Computer Full OS File Set
Custom WIM
Are you going to allow users to choose Yes their own operating system, applications, locale, time No zone, and administrative password?
Professional Which product editions will you deploy? Ultimate Business Enterprise How will you handle product keys and licensing? Multiple Activation Key (MAK) Key Management Service(KMS)
10
11
4. 5.
Review the Windows 7 Readiness Assessment Reports. Shut down the Vista computers.
Note: LON-DC1 is the computer running Windows Server 2008 R2 which provides domain services. LON-CL2 is the client computer that will contain the Microsoft Assessment and Planning Toolkit. LON-VS1, and LON-VS2 are both client computers to be assessed.
12
Open Hyper-V Manager and modify the RAM allocation for 6294A-LON-VS2 to be 768MB.
Results: After this exercise, you have installed and run the Microsoft Assessment and Planning Toolkit and customized the administrators profile on the Vista systems.
13
Note: LON-DC1 is the computer running Windows Server 2008 R2 which provides domain services. LON-CL2 is the client that will be used as the technician computer.
Results: After this exercise, you have the Microsoft Deployment Toolkit and the Windows Automated Installation Kit on LON-CL2.
14
Note: LON-DC1 is the computer running Windows Server 2008 R2 which provides domain services and WDS services.
15
Results: After this exercise, the Windows Deployment Services has been installed and configured on LON-DC1 and a share for the deployment share has been created.
16
Note: LON-DC1 is the computer running Windows Server 2008 R2 which provides domain services and WDS services. LON-CL2 is the client used as the technician computer.
17
18
19
Results: After this exercise, a Deployment Share has been created and configured on the LON-DC1 system.
20
Note: LON-DC1 is the computer running Windows Server 2008 R2 which provides domain services and WDS services. LON-CL2 is the client used as the technician computer.
21
Join the computer to a workgroup Do not restore user data Install Microsoft Office 2007
Note: For this lab a license key is not be provided when installing Microsoft Office 2007. Because of this you are prompted to perform the Microsoft Office installation manually.
Results: After this exercise, a reference computer has been created and captured.
22
Note: LON-DC1 is the computer running Windows Server 2008 R2 which provides domain services and WDS services. LON-CL2 is the client used as the technician computer.
Customize the Akron USMT Capture properties with the following: Disable the Wipe Disk task.
Note: The Wipe Disk task is disabled in order to save time in the lab environment.
23
On the MDT Deployment Share (\\LON-DC1\DeploymentShare$) Properties, edit the CustomSettings.ini file as follows:
[Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y UserDataLocation=NETWORK SkipAppsOnUpgrade=NO SkipCapture=NO SkipAdminPassword=YES SkipProductKey=YES
24
Results: After this exercise, the tasks used to capture the user state and deploy the new images have been created.
25
Note: LON-DC1 is the computer running Windows Server 2008 R2 which provides domain services and WDS services. LON-CL2 is the client used as the technician computer. LON-VS1, LON-VS2, and LON-VS3 are the computers that will be upgraded.
Note: While the scenario calls for a backup, you are not creating a backup as a timesaving step. Note: If you receive an 800704C3 error, use the IP Address 10.10.0.10 instead of Contoso for the Domain name.
26
On the host computer, connect to each Vista - Virtual Machine and start it. On the host computer, start the virtual machine to be deployed. After the PXE boot is finished, complete the Deployment Wizard with the following, use defaults where not specified: Install a new Operating System Username: Administrator Password: Pa$$w0rd Domain: Contoso Deploy Windows 7 to Akron Configure the computer name: LON-VS1a and LON-VS1b Join the Contoso domain Restore user data from \\LON-DC1\Data\VS1 and \\LON-DC1\Data\VS2
Note: To re-use the computer name, reset or delete the existing computer object in Active Directory. Note: To monitor the multicast environment, on LON-DC1, open the Windows Deployment Services Console. Expand LON-DC1.Contoso.com, expand Multicast transmissions, and select MDT DeploymentShare. You may have to refresh the node to view the multicast entries.
27
Perform the following steps while the image is deploying to the systems. On LON-DC1, in the WDS Console, configure LON-DC1.Contoso.com Properties with the following: On the Boot tab, set Always continue the PXE boot for both known and unknown systems.
Note: Failing to complete this step will cause the deployed system to re-enter the PXE environment on startup.
Results: After this exercise, the Vista systems have been replaced with Windows 7 and the user profiles have been migrated.
Module 1
Lab Answer Key: Preparing to Deploy Windows 7 Business Desktops
Contents:
Lab A: Assessing the Computing Environment by Using the Microsoft Assessment and Planning Toolkit Exercise 1: Configure the Microsoft Assessment and Planning Toolkit Exercise 2: Use the Microsoft Assessment and Planning Toolkit to Create a Client Assessment Report Exercise 3: Analyze Inventory and Assessment Data Lab B: Recommending an Activation Strategy Exercise 1: Review the Activation Scenario 7 3 4 5
Lab A: Assessing the Computing Environment by Using the Microsoft Assessment and Planning Toolkit
Scenario
You are the team lead for the Windows 7 deployment project at Contoso Ltd. Contoso currently uses Windows Vista on the company desktop computers. You are planning for the Windows 7 deployment to take place within the next month. As part of the deployment process you need to determine if there are any hardware compatibility issues with Windows 7. You will use the Microsoft Assessment and Planning Toolkit to help inventory, analyze, and then determine the necessary hardware upgrades.
Exercise 2: Use the Microsoft Assessment and Planning Toolkit to Create a Client Assessment Report
f Task 1: Run the Windows 7 Readiness Assessment Wizard
1. 2. 3. In the Discovery and Readiness pane, click Inventory and Assessment Wizard. Review the Computer Discovery Methods page and then click Next. Configure the Active Directory Credentials page with the following: Domain: Contoso.com Domain Account: Contoso\Administrator Password: Pa$$w0rd Click Next. Review the Active Directory Options page and then click Next. On the Windows Networking Protocols page ensure the following: Workgroups and Windows domains to include in the inventory: Contoso Click Next. On the WMI Credentials page, click New Account. Fill in the Inventory Account page with the following: Domain name: Contoso Account name: Administrator Password: Pa$$w0rd Confirm password: Pa$$w0rd Click Save. On the WMI Credentials page, click Next. On the Summary page, click Finish.
4. 5.
6. 7.
8. 9.
10. Once the inventory is complete, on the Status page, click Close.
Q. What are the minimum upgrades required to the Not Ready for Windows 7 Category systems? A. Answers will vary based on the final VMs 6. 7. Close the Windows7Assessment-<date-time> report. Close all open windows.
A recent internal audit has revealed inadequacies with the existing license activation. The network is due for a technology refresh and due to the issues revealed by the audit Upper Management has asked you to recommend an activation model that will provide the most efficient method of activating all systems while maintaining a documentable method of managing the licenses.
Module 2
Lab Answer Key: Assessing Application Compatibility in Windows 7
Contents:
Lab A: Evaluating Application Compatibility Using the Microsoft Application Compatibility Toolkit Exercise 1: Installing and Configuring ACT Exercise 2: Collecting Application Inventory Exercise 3: Organizing the Application Inventory Exercise 4: Analyzing Application Inventory Results Lab B: Creating Application Compatibility Fixes Exercise 1: Identifying Application Compatibility Issues Exercise 2: Mitigating Application Issues
3 5 7 9 12 13
Lab A: Evaluating Application Compatibility Using the Microsoft Application Compatibility Toolkit
Computers in this lab
Before you begin the lab, you must start the virtual machines. The virtual machines used at the start of this lab are: 6294A-LON-DC1 6294A-LON-CL1 6294A-LON-VS1
2. 3. 4. 5. 6. 7.
8. 9.
On the Configure Your Log File Location page, next to Share as, ensure the ACTLogs is entered, and then click Next. On the Configure Your ACT Log Processing Service Account page, ensure that Local System is selected, and then click Next.
10. On the Congratulations page, clear the check mark next to Automatically check for updates on launch, and then click Finish. The Microsoft Application Compatibility Manager console opens. 11. On the Tools menu, click Settings. 12. In the Settings box, on the Settings page, verify that LON-DC1 is configured as the SQL Server, and that ACTDB is configured as the Database. 13. Under Log Processing Settings, verify that a check mark is visible next to This computer is configured as a Log Processing Service. 14. Verify that the Log Processing Service Account is configured as a Local System Account. 15. Verify that the Log Share is configured to be \\LON-DC1\ACTLogs. 16. Click the Preferences tab. 17 Under Community Settings, verify that a check mark is visible next to Yes, I want to join the ACT Community. 18. Under Update Settings, ensure that the check box next to Notify me when a newer version of ACT is available is cleared. Normally you would select this; however, the virtual computer is not connected to the Internet, so it will remain cleared for this exercise. 19 To close the Settings box, click OK. 20. Click Start, point to Administrative Tools, and then click Services. 21. Verify that the Act Log Processing Service has started. If it is not started, rightclick the service, and then click Start. 22. Close the Services console.
5.
6.
Under When to monitor application usage, for Duration, configure 60 Minutes. In production, you will want to set this for at least 35 days to capture sufficient detail. Under Where to output collected data, ensure that the Output Location shows LON-DC1 (\\LON-DC1\ACTLogs). From the File menu, click Save and Create Data Collection Package. Save the file as DataCollectionPKG.msi in C:\Data.
7. 8.
The DataCollectionPKG installation runs. Close the Explorer window. Right-click the Taskbar, and then click Task Manager. Click the Processes tab. Click Show processes from all users. In the User Account Control dialog box, provide the following credentials and then click OK: User name: Administrator Password: Pa$$w0rd
9.
On the Processes tab, verify that the data collection is running by looking for the actdcsvc.exe process.
9.
10. Click the Actions menu, and then click Assign Categories. 11. In the Assign Categories dialog box, click the Category List button. 12. Click Add on the Categories side, and then type Line of Business. 13. Click Add on the SubCategories side, type Customer Service, and then click OK. 14. In the Assign Categories box, select the Customer Service sub-category, and then click OK. 15. Select the following applications: Microsoft BackInfo Office Diagnostics Service
16. Click the Actions menu, and then click Assign Categories. 17. In the Assign Categories dialog box, click the Category List button.
18. Click Add on the Categories side, and then type System Utilities. 19. Click Add on the SubCategories side, type Desktops, and then click OK. 20. In the Assign Categories box, select the Desktops sub-category, and then click OK.
10. In the Set Deployment Status box, click Mitigating, and then click OK.
10
5. 6. 7.
After you have saved the new issue, click the Solutions tab. On the toolbar, click Add Solution. In the Add Solution dialog box, enter the following, and then click Save: Title: Office Diagnostics Service Fix Solution Type: Application has an update Solution Details: Install the latest Service Pack
8. 9.
Close all windows to return to the main Microsoft Application Compatibility Manager window. Close the Microsoft Application Compatibility Manager.
11
12
On the Stock Viewer toolbar, click Trends. Click the Tools menu, click Options, and then click OK. Click the Tools menu, and then click Show Me a Star. Click OK to close the Unsupported Version box. Close the Stock Viewer application.
13
2. 3. 4. 5. 6.
On the Warning dialog box, click Yes. On the Permission denied dialog box, click OK. On the Stock Viewer toolbar, click Trends. An error appears.
10. On the Error box, click OK. 11. Click the Tools menu and then click Options. An unhandled exception error appears. 12. Click Continue to close the error. 13. Click the Tools menu, and then click Show Me a Star. An error appears stating that the application requires Windows XP. 14. Click OK to close the Unsupported Version box. 15. Close the Stock Viewer application. 16. In the Standard User Analyzer window, review the following tabs: File, Registry, Token, Name Space, Other Objects. Note that these are the errors that were detected while SUA was monitoring the application. 17. Click the Mitigation menu, and then click Apply Mitigations. 18. On the Mitigate AppCompat Issues, click Apply.
14
In the left pane, expand Installed Databases. Under Installed Databases, expand AppCompat Shims for StockViewer.exe. Notice that this was installed by the SUA. Expand Applications and then click the application GUID entry. Notice the types of compatibility fixes that were applied when the SUA was used. Right-click AppCompat Shims for StockViewer.exe, click Uninstall, and then click OK. In the left pane, expand Custom Databases, and then click New Database(1) [Untitled_1]. On the toolbar, click Fix.
15
10. In the Create New Application Fix box, on the Program Information page, provide the following and then click Next: Name of the program to be fixed: StockViewer Program file location: C:\Program Files\StockViewer\StockViewer.exe
11. On the Compatibility Modes page, click None, and then click Next. 12. On the Compatibility Fixes page, select the following, and then click Next: ElevateCreateProcess ForceAdminAccess LocalMappedObject VirtualizeHKCRLite
13. On the Matching Information page, click Finish. 14. On the toolbar, click Save. 15. In the Database Name box, type StockViewerFix, and then click OK. 16. In the Save Database box, type C:\Data\StockViewerFix, and then click Save. 17. On the toolbar, click Fix. 18. In the Create New Application Fix box, on the Program information page, provide the following information, and then click Next: Name of the program to be fixed: Star Program file location: C:\Program Files\StockViewer\DWM Compositing Rendering Demo.exe
19. On the Compatibility Modes page, click None, and then click Next. 20. On the Compatibility Fixes page, select WinXPSP2VersionLie, and then click Next. 21. On the Matching Information page, click Finish. 22. On the toolbar, click Save. 23. Right-click StockViewerFix, click Install, and then click OK. 24. Close the Compatibility Administrator.
16
Module 3
Lab Answer Key: Evaluating Windows 7 Deployment Methods
Contents:
Exercise 1: Planning a Windows 7 Deployment for a Small Network Exercise 2: Planning a Windows 7 Deployment for a Larger Network Exercise 3: Planning a Windows 7 Deployment for a Large Network Exercise 4: Planning a Windows 7 Deployment for an Enterprise Network 2 5 7 9
Slough Production Plant: Windows 7 Upgrade Proposal Document Reference Number: EM3007 Document Author Date Ed Meadows 30th July
Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the Slough production plant. To migrate applications and user data during the upgrade process.
(continued)
Slough Production Plant: Windows 7 Upgrade Proposal Additional Information There are 10 computers running Windows Vista at the Slough plant. Following research with the staff at Slough, you have determined that they work in three shifts; this means that at some point in the day, all computers are not being used. 1. Is deployment by using WDS suitable in this situation? Why or why not? Answer. WDS is not suitable; the network is not provided with a DHCP server, which is a requirement of deploying WDS. 2. Would the use of WAIK be beneficial in the Slough plant upgrade? Answer. Depending upon the deployment method selected, it might be helpful to use Windows SIM, a Windows AIK tool, to help to automate the installation of Windows 7. By associating an answer file with a standard image (.WIM file in the \sources folder) Windows 7 could more easily be deployed. The answer file could be saved to a memory stick for use during an interactive installation. The degree of automation depends upon the options configured in the answer file. 3. How would you propose to handle the installation of custom applications? Answer. Assuming that you decide to perform an in-place upgrade, there would be no need to re-install applications; they would still be present on the system. If you opted to perform a wipe and load installation, it would be necessary to deploy the custom applications. Since not all workstations at Slough have these applications installed, it might be easiest to install them manually where necessary. However, existing GPO might be responsible for these custom application deployments. 4. How would you propose to deploy standard office productivity applications? Answer. Assuming that you decide to perform an in-place upgrade, there would be no need to re-install applications; they would still be present on the system. If you opted to perform a wipe and load installation, it would be necessary to deploy the standard office productivity applications. An existing GPO might be responsible for deploying standard office productivity applications.
(continued)
Slough Production Plant: Windows 7 Upgrade Proposal 5. How would you propose to handle user state data and application settings? Answer. If an in-place upgrade is performed, then user data and application settings would be retained. If a wipe and load deployment is performed, then it will be necessary to migrate user data and settings by using either USMT or WET. The file server at Slough could be used to store the data and settings during the migration process. Proposals The infrastructure does not support the use of WDS. However, you could still choose to deploy an operating system image locally, perhaps by using imageX. Given that there are a small number of computers, and that each computer has a slightly different build, creating a single, standard image might prove challenging. The easiest approach would be to perform either an in-place upgrade in which all applications, user data, and settings are retained. Alternatively, a wipe and load deployment could be implemented; this would necessarily involve backing up user data and settings, re-installing the required applications, and then restoring the user data and settings. Either USMT or WET could be used to migrate these data and settings.
Hammersmith Production Plant: Windows 7 Upgrade Proposal Document Reference Number: EM1008 Document Author Date Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the Hammersmith production plant. To ensure that user data is migrated as part of the upgrade process. To ensure that there is minimal downtime of the workstations at the Hammersmith plant; they are in constant use. Additional Information There are 25 computers running Windows Vista at the Hammersmith plant. Following research with the staff at Hammersmith, you have determined that their computers are in constant use. 1. Is deployment by using WDS suitable in this situation? Why or why not? Answer. No. Although DHCP and DNS are both present on the network, Server Core does not support the WDS Server role. Ed Meadows 10th August
(continued)
Hammersmith Production Plant: Windows 7 Upgrade Proposal 2. How would you propose to handle the installation of custom applications? Answer. Application deployment is currently configured through GPO. There is no need to deploy the custom applications manually. 3. How would you propose to deploy standard office productivity applications? Answer. Application deployment is currently configured through GPO. There is no need to deploy the office productivity applications manually. 4. How would you propose to handle user state data and application settings? Answer. User data and settings must be migrated as these exist locally on each computer. The precise method depends upon which deployment method is selected. As Charlotte has suggested the computers are due to be replaced, it would be possible to perform a clean installation or apply a local image to each new computer. After applications are deployed by GPO, user data and settings could be migrated by using either USMT (using the local server for storage during migration), or else by using WETwith a direct cable connection between the computers. Proposals Either perform a local installation from DVD, perhaps using an answer file generated from Windows SIM, or else create a standard desktop image using a source computer, sysprep, and imageX. Essentially, you are creating a thin image as all applications are deployed by GPO. Once each computer has been deployed, migrate the user data from the old desktop computer to the new desktop computer.
Production Department: Windows 7 Upgrade Proposal Document Reference Number: EM0109 Document Author Date Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the rest of the production department based at the Reading plant. Additional Information There are 150 computers running Windows Vista at the Reading plant. At any one time, around a third of all computers are not in use. The computers are all in one of three subnets, with core services on the backbone. Each subnet has its own file server that hosts shared data and applications. 1. Is deployment by using WDS suitable in this situation? Why or why not? Answer. Yes, the WDS role could be deployed onto one of the servers on the backbone network; Server Core does not support the WDS role, so they could not provide the WDS service. Ed Meadows 1st September
(continued)
Production Department: Windows 7 Upgrade Proposal 2. How would you propose to handle the installation of custom applications? Answer. The desktop computers are using a standard configuration. This means that the applications could be included as part of the OS deployment. A custom image file could contain all the custom applications required by the workstations. 3. How would you propose to deploy standard office productivity applications? Answer. Standard office productivity applications can be included in the custom build. 4. How would you propose to handle user state data and application settings? Answer. Given the large number of users involved, and the fact that user data is stored locally, USMT would be the preferred method of migrating user data. The adjacent file server could store the settings during the migration process. Proposals Given the large number of standard workstations, creating a custom image that includes the required applications would seem the sensible deployment method. Implement WDS on one of the backbone servers, and then create a custom image for deployment. Add the image, and a relevant boot image, to the server. Configure the appropriate method of deployment on WDS; choose either scheduled-cast, or auto-cast. Visit the appropriate workstation, and connect it to the WDS server by using PXE-boot.
Contoso: Windows 7 Upgrade Proposal Document Reference Number: EM1712 Document Author Date Ed Meadows 17th December
Requirement Overview To replace the Windows Vista operating system with Windows 7 for all computers in the Contoso organization. To deploy applications as part of the upgrade, and to ensure that all user data and settings are accessible after the upgrade. Additional Information There are 1,500 computers running Windows Vista at the Kensington head office. Staff at Kensington usually work only standard office hours9.00 am until 5.30pm. 1. Do you envisage using deployment images? Answer. Yesit enables the deployment to take place more quickly. Performing an interactive installation on 1,500 computers would not be efficient.
10
(continued)
Contoso: Windows 7 Upgrade Proposal 2. If so, how many images would you propose using? Answer. There are three departments at Kensington. Assuming they all have different requirements, three images would be logical. It would be worth investigating how different the builds are, as GPO has been used for application deployment in the Production department; a single corporate image might be feasible. 3. What additional services would you need to support your proposal? Answer. Given the large number of workstations, and the possibility of multiple images, using MDT might be sensible. At the very least, WDS should be considered to help with image deployment. If ZTI is envisaged, either SCCM or SMS would be required. 4. How would you propose to deploy standard office productivity applications? Answer. MDT supports the deployment of applications. Alternatively, the image deployed could contain the necessary applications. 5. How would you propose to handle user state data and application settings? Answer. LTI deployments support Upgrade deployment methods, as well as Refresh computer methods. In the case of the Upgrade method, user data and settings are retained. However, most, if not all, user data and settings are stored in redirected folders configured through GPO. Proposals Use MDT to create either LTI or ZTI installations depending upon the degree of automation required. MDT supports the degree of customization and the diversification of the different computers installed throughout the head office. Features such as support for additional Out-of-box drivers, application deployment, and the management of user state data make it the logical choice for larger deployments.
Module 4
Lab Answer Key: Designing Standard Windows 7 Images
Contents:
Exercise 1: Planning the Imaging Strategy for a Branch Office Network Exercise 2: Planning the Imaging Strategy for an Enterprise Network 2 5
Requirement Overview Design a Windows 7 image strategy that supports the deployment of the new operating system to newly delivered computers at the Hammersmith plant. Conserve server storage as the server wont be getting a disk upgrade in the near future and has limited capacity. Minimize support staff effort during the rollout. There are 25 computers in total, all of which use Office 2007 Professional. All computers connect to a printer, the driver for which is not in the current driver store in Windows 7.
(continued)
Hammersmith Production Plant: Desktop Image Requirement Overview (continued) 10 computers use a custom line-of-business application that runs within a virtual machine; currently, the guest operating system runs within Virtual PC 2007. The remaining group of 15 computers runs another LOB application that runs natively within Windows Vista. Additional Information 1. Will you use a standard image(s), or else create a custom image(s)? Answer. Standard images require no storage on the server as you can use the images in the sources folder on the product DVD. An answer file could be used to automate the installation process. However, following deployment of the image, two separate builds would need to be created to support the two distinct sets of users; those with the Linux application, and those with the Windows custom LOB application. In addition, the standard image would not include the printer driver or the Office 2007 application. A custom image would be a suitable choice. 2. How many images do you envisage needing? Answer. One hybrid image. This image would contain the operating system, the required drivers, and the Office 2007 application. 3. Do you envisage using thin, thick, or hybrid images? Answer. A hybrid image balances disk consumption on the server, and the need to deploy application with the OS. To support the two distinct sets of users with a thick image would require two images one with the DOS application, and the other with the Windows LOB application. These applications could be deployed postinstallation, possibly by using GPO. 4. How will you handle the printer driver and required updates and patches? Answer. These would be included as part of the hybrid image.
(continued)
Hammersmith Production Plant: Desktop Image 5. How will you create the images that you plan to implement? Answer. A source computer is built, and relevant drivers, patches, updates, and common applications are installed. Sysprep.exe is run to remove identifying characteristics, and then imageX.exe is used to capture the image, possibly to the server. If storage is very scarce, then the image could be stored on removable media. 6. Will you deploy the applications as part of the image(s)? Answer. The common applications will be part of the hybrid image. The custom LOB applications will be deployed by using GPOs from the local file server. Proposals The server lacks sufficient storage to host multiple images. The line speed prohibits extensive use of GPOs to initially deploy larger applications. Two standard builds exist. To balance these requirements, a single hybrid image should be used that includes the necessary drivers, updates, patches, and the Office applications used on all computers. Once the deployment is complete, GPO settings will be used to deploy the custom LOB applications to the appropriate computers. GPOs will also be used to configure and maintain the computers after deployment.
Requirement Overview Design a Windows 7 image strategy that supports the deployment of the Windows 7 operating system to all computers at the Kensington head office. Storage space on the file servers is not restricted. There is spare network bandwidth to support the deployment process. It is desirable to use GPOs to perform as much centralized management of computers as possible. Additional Information 1. Will you use a standard image(s), or else create a custom image(s)? Answer. Some degree of customization might be desirable. 2. How many images do you envisage needing? Answer. A single thin image.
(continued)
Kensington Head Office: Desktop Image 3. Do you envisage using thin, thick, or hybrid images? Answer. Thin images, using System Center Configuration Manager and supporting infrastructure to deploy applications, updates, drivers, and patches after the installation of the image. 4. How will you handle the various drivers, updates, and patches? Answer. By using Configuration Manager and supporting technologies. 5. How will you deploy the images that you plan to implement? Answer. ZTI by implementing MDT with Configuration Manager. 6. Will you deploy the applications as part of the image(s)? Answer. No. They will be deployed post-installation. Proposals Since Configuration Manager exists on the network, and GPOs are used to manage client computers, and given also that many builds exist within the Contoso head office, it is suggested that the use of thin client images is appropriate. Applications, updates, and drivers can be deployed after the images are deployed. In addition, MDT and SCCM can migrate the user state data and settings to complete the deployment process.
Module 5
Lab Answer Key: Deploying Windows 7 by Using Windows AIK
Contents:
Lab A: Installing the Windows Automated Installation Kit Exercise 1: Installing the Windows Automated Installation Kit Exercise 2: Identifying Resources and Tools Included with the Windows Automated Installation Kit Lab B: BuildingaReferenceImageUsingWindowsSIMandSysprep Exercise 1: Building a Custom Answer File by Using Windows SIM Exercise 2: Installing a Reference Computer from a DVD Using a Custom Answer File Exercise 3: Generalizing a Reference Computer by Using Sysprep Lab C: CreatingWindowsPEBootMedia Exercise 1: Adding Packages to Windows PE Exercise 2: Creating a Bootable Windows PE ISO Image Exercise 3: Starting the Windows PE Operating System Environment Lab D: CapturingandApplyingaWindows7ImageUsingImageX Exercise 1: Capturing an Image Using ImageX Exercise 2: Apply an Image Using ImageX Lab E: ServicingImagesby usingDISM Exercise 1: Service an Offline WIM Image 3 4 6 11 12 14 16 16 17 19 21
10. Close the Welcome to Windows Automated Installation Kit page. 11. Close the Explorer window.
Exercise 2: Identifying Resources and Tools included with the Windows Automated Installation Kit
f Task 1: Examine the Windows Automated Installation Kit Start Menu
folder
1. Click Start, point to All Programs, click Microsoft Windows AIK. Question: Which applications are represented in the Start Menu? Answer: Deployment Tools Command Prompt, Windows System Image Manager and the Volume Activation Management Tool. 2. Right-click Deployment Tools Command Prompt select Run as Administrator. Question: Most of the WAIK Tools are command line based, what happened to the PATH when you opened the Deployment Tools Command Prompt? Answer: The path was updated to include the dism, oscdimg and imagex tools. 3. Close the Administrator: Deployment Tools Command Prompt.
4.
Double-click one of the platform folders (such as the x86 folder). Question: Which executables are present in the platform folder? Answer: bcdboot.exe, imagex.exe, intlcfg.exe, oscdimg.exe, wdsmcast.exe, WimMountInstall.exe and wimserv.exe.
2. 3. 4. 5. 6. 7. 8.
windowsPE
3.
All the settings you added must appear in the Answer File pane. Select and configure each setting as specified below.
Component x86_Microsoft-Windows-InternationalCore-WinPE Value InputLocale = en-US SystemLocale = en-US UILanguage = en-US UILanguageFallback = en-US UserLocale = en-US UILanguage = en-US
WillShowUI = OnError
DiskID = 0 WillWipeDisk = true Extend = true Order = 1 Type = Primary Active = true Format = NTFS Label = Windows Letter = C Order = 1 PartitionID = 1 WillShowUI = OnError
DiskID = 0 PartitionID = 1 AcceptEula = true FullName = Administrator Organization = Contoso WillShowUI = OnError
Microsoft-Windows-Setup \UserData\ProductKey
(continued)
Component Microsoft-Windows-Shell-Setup \OEMInformation Value HelpCustomized = false Manufacturer = Contoso IT Group SupportHours = 9 - 5 SupportPhone = 555-9988 SupportURL = http://Technet.Microsoft.Com Enabled = true LogonCount = 5 Username = Administrator Password=Pa$$w0rd ForceShutdownNow = false Mode = Audit NetworkLocation = Work ProtectYourPC = 1
Microsoft-Windows-Shell-Setup\OOBE
10
11
Exercise 2: Installing a Reference Computer from a DVD Using a Custom Answer File
f Task 1: Mount the external media on LON-IMG1
1. 2. 3. 4. 5. 6. On the host computer, in the Hyper-V Manager, right-click 6294A-LON-IMG1 and click Settings. In the Settings for 6294A-LON-IMG1 dialog box select DVD Drive. Select the Image File: radio button and specify the image file C:\Program Files\Microsoft Learning\6294\Drives\Windows7_32bit.ISO. In the Settings for 6294A-LON-IMG1 dialog box select Diskette Drive. Select the Virtual floppy disk (.vfd) file: radio button and specify the file: C:\Program Files\Microsoft Learning\6294\Drives\UnattendAnswer.vfd. In the Settings for 6294A-LON-IMG1 dialog box click OK.
In order to save time, you can revert 6294A-LON-IMG1 and then start 6294A-LONIMG2 which is a pre-staged virtual machine saved at the point where the installation has completed. You can either wait for LON-IMG1 to finish installing or continue on to Exercise 3 with LON-IMG2. The following exercise assumes that 6294A-LON-IMG2 is used.
12
13
5.
14
2. 3.
15
3.
Type the following: [ExclusionList] \temp In Notepad, click the File menu, and select Save As. In the Save as Type field, select All Files. Browse to the C:\winpe_x86\iso\ folder. In the File name: field type wimscript.ini and click Save. Close Notepad.
4. 5. 6. 7. 8.
16
4.
17
18
Note: The capture process will take approximately 20 minutes. To save time, the remainder of the lab will use an image that has already been prepared.
6.
19
20
5. 6.
After the Image is applied, type Exit and then press ENTER to restart the computer. When LON-CL3 restarts, complete the Set Up Windows Wizard with the following options: Country or region: Default User Name: LocalAdmin Computer name: LON-CL3 Password: Pa$$w0rd I accept the license terms: Selected Updates: Use recommended settings Time and date: Default Location: Work network
7. 8. 9.
Open computer properties to verify the Manufacturer and IT support information match the values used in the UnattendAnswer script. Verify the custom applications are installed. Shutdown LON-CL3.
21
Setup
Before starting this lab, copy the LON-REF.wim file from the \\LON-DC1\Labfiles\Mod5\Image folder to the C:\Images folder on LON-CL2.
2. 3. 4. 5. 6. 7.
22
Module 6
Lab Answer Key: Deploying Windows 7 by Using Windows Deployment Services
Contents:
Exercise 1: Designing the Windows Deployment Services Environment Exercise 2: Installing and Configuring the Windows Deployment Services Server Role Exercise 3: Adding Boot and Install Images to Windows Deployment Services Exercise 4: Provisioning Drivers by Using Windows Deployment Services Exercise 5: Deploying a Desktop Operating System Using Windows Deployment Services 3 5 7 9 11
Requirement Overview To install and configure Windows Deployment Services server role. To deploy Windows 7 to the new Marketing department computers. Additional Information You have purchased 10 new computers for the Marketing department. The Marketing department has a single server name LON-DC1. 1. Since LON-DC1 also hosts the DHCP server role, how does this affect the Windows Deployment Services server role. Answer. During the WDS configuration you will need to select the Do not listen on port 67 check box and configure DHCP option 60. 2. Where should you configure the Remote Installation Folder Location? Answer. Since Drive C is 80% full, the Remote Installation Folder Location will be placed at E:\RemoteInstall.
(continued)
Windows Deployment Services Design and Configuration 3. What types of images are required for your deployment? How can you organize the install images for future deployment with other departments? Answer. For this deployment you will need the default boot image and the default install image from the Windows 7 media. The install image will be placed within a Marketing Image Group specifically for the Marketing department. 4. How will you configure WDS to ensure security? Answer. You will configure WDS to respond to all known and unknown computers. However to increase security, you will require administrator approval for all unknown computers. 5. What specific platform considerations do you have for your deployment? Answer. All 64-bit laptops will have the VX 6000 Lifecam Drivers installed. Desktop computers do not require this driver. 6. What are some ways that you can provide availability and minimize network congestion? Answer. Install the Transport Server role service to provide multitasking capabilities. This will help minimize network congestion. To provide availability you can use Distributed File System to help replicate and provide availability for the Remote Installation Folder. Multiple WDS servers may also help in providing a distributed WDS environment.
Exercise 2: Installing and Configuring the Windows Deployment Services Server Role
f Task 1: Install the Windows Deployment Services server role
1. 2. 3. 4. 5. 6. 7. 8. 9. Log on to LON-DC1 as Contoso\Administrator using the password Pa$$w0rd. In the Task Bar, click the Server Manager button. In the Server Manager console, in the left-hand console pane, click Roles. In the details pane, in the Roles Summary section, click Add Roles. The Add Roles Wizard starts. On the Before You Begin page, click Next. On the Select Server Roles page, select the check box next to Windows Deployment Services and then click Next. On the Overview of Windows Deployment Services page, click Next. On the Select Role Services page, ensure that both Deployment Server and Transport Server are selected and then click Next. On the Confirm Installation Selections page, click Install.
10. On the Installation Results page, click Close. 11. Close the Server Manager console.
3. 4.
5. 6.
On the Remote Installation Folder Location page, under Path type E:\RemoteInstall and then click Next. On the DHCP Option 60 page, select the following options and then click Next: Do not listen on port 67 Configure DHCP option 60 to PXEClient
7.
On the PXE Server Initial Settings page, select Respond to all client computers (Known and unknown). Also select the check box next to Require administrator approval for unknown computers. Click Next. On the Operation Complete page, remove the check mark next to Add images to the server now and then click Finish.
8.
4. 5. 6. 7. 8.
On the Image File page, under File location, type D:\sources\install.wim and then click Next. On the Available Images page, under Name, ensure that Windows 7 ENTERPRISE is selected. Ensure that the check box is selected next to Use the default name and description for each of the selected images. Click Next. On the Summary page, click Next. The install image is added to Windows Deployment Services. Click Finish.
10
5.
In the Add Filter box, configure the following and then click Add: Filter Type: Chassis Type Operator: Equal to Value: Laptop
6. 7.
In the Add Filter box, click OK. In the VX 6000 Lifecam Properties box, click OK.
11
In the Select the Operating system you want to install page, click Next.
10. In the Where do you want to install Windows? page, click Next. The Windows 7 installation begins. It will take approximately 20 minutes to complete the installation.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
Module 7
Lab Answer Key: Deploying Windows 7 by Using Lite Touch Installation
Contents:
Lab A: Planning and Configuring MDT 2010 Exercise 1: Planning the MDT Lite Touch Environment Exercise 2: Installing MDT 2010 and Additional Component Files Exercise 3: Creating an MDT 2010 Deployment Share Lab B: Deploying Windows 7 by Using Lite Touch Installation Exercise 1: Configuring the MDT 2010 Deployment Share Exercise 2: Deploying Windows 7 and Capturing an Image of the Reference Computer Exercise 3: Configuring MDT 2010 to Deploy Windows 7 to the Target Computer Exercise 4: Deploying Windows 7 to the Target Computer 9 12 14 16 3 6 8
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
Question
What System is going to be deployed as the Technicians system? Are you going to be deploying Applications?
USMT
Since you are evaluating automated installations you need to install the WAIK. Per Jonass E-mail user state will not be migrated. Since we are deploying new systems we do not need to use the Assessment and Planning toolkit.
(continued) Question Microsoft Deployment Toolkit PlanningJob Aid Information Rationale for the Decision For this evaluation you will Local Deployment ; create the deployment share on Share the LON-CL2 system. Remote Deployment Share Per Jonass e-mail the Microsoft Yes ; IntelliPoint drivers will be preNo installed. Both, removable media will be Network ; used to start the evaluation systems and the files will be deployed across the network. Removable Media
Where will you store your distribution files? Will you be deploying any drivers not included with Windows 7? Will you deploy across the network, with removable media, or both?
; ;
New Computer
Refresh Computer
; ;
Replace Computer Will you deploy a full set of operating system files or a custom Windows Imaging Format (WIM)? Full OS File Set Custom WIM
A new installation of a Windows operating system is deployed to a new computer. User state is not migrated. The current Windows operating system on the target computer is upgraded to the deployed operating system. A computer is refreshed, including computers that must be re-imaged. User state may be migrated. One computer replaces another computer. User state is migrated. Full OS deployment for the reference computer and a custom WIM file for the client (target) computers.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
(continued) Question Microsoft Deployment Toolkit PlanningJob Aid Information Rationale for the Decision Professional Ultimate Business Enterprise ; Multiple Activation A license key will not be Key (MAK} provided in the Answer file. KMS would be used to activate any Key Management systems required longer than 3 ; Service(KMS) days.
7. 8. 9.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
10. In the New Deployment Share Wizard, on the Allow Image Capture page click Next. 11. In the New Deployment Share Wizard, on the Allow Admin Password page click Next. 12. In the New Deployment Share Wizard, on the Allow Product Key page click Next. 13. In the New Deployment Share Wizard, review the Summary page and then click Next. 14. In the New Deployment Share Wizard, review the Confirmation page and then click Finish.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
10
7. 8. 9.
In the Actions pane, click Import Operating System. In the Import Operating System Wizard, on the OS Type page select the Full set of source files radio button and then click Next. In the Import Operating System Wizard, on the Source page type D:\ and then click Next.
10. In the Import Operating System Wizard, on the Destination page, click Next. 11. In the Import Operating System Wizard, on the Summary page, click Next.
Note: The import takes approximately 3 minutes.
12. In the Import Operating System Wizard, review the Confirmation page, and then click Finish.
2. 3. 4. 5.
2.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
11
3.
In the New Task Sequence Wizard, on the General Settings page set the following: Task sequence ID: WIN7_REFERENCE Task sequence name: Deploy Windows 7 to LON-IMG1 and then click Next. In the New Task Sequence Wizard, on the Select Template page, specify the Standard Client Task Sequence, and then click Next. In the New Task Sequence Wizard, on the Select OS page, specify the Windows 7 Enterprise in Windows 7 x86 install.wim, and then click Next. In the New Task Sequence Wizard, on the Specify Product Key page, click Next. In the New Task Sequence Wizard, on the OS Settings page set the following: Full Name: Admin Organization: Contoso LTD. and then click Next. In the New Task Sequence Wizard, on the Admin Password page, select the Do not specify an Administrator password at this time radio button, and then click Next. In the New Task Sequence Wizard, on the Summary page, click Next.
4. 5. 6. 7.
8.
9.
10. In the New Task Sequence Wizard, on the Confirmation page, click Finish.
2. 3. 4. 5.
12
Note: For the Lab the LiteTouchPE_x86.iso file has already been copied to the host machine.
f Task 2: Start the reference computer with the LTI bootable media
1. 2. 3. 4. 5. 6. 7. 8. On the host computer, in the Hyper-V Manager, right-click 6294A-LON-IMG1, and then click Settings. In the Settings for 6294A-LON-IMG1 dialog box, click DVD Drive. Select the Image File: radio button and specify the image file C:\Program Files\Microsoft Learning\6294\drives\LiteTouchPE_x86.iso. In the Settings for 6294A-LON-IMG1 dialog box, click OK. On the host computer, in the Hyper-V Manager, right-click 6294A-LON-IMG1 and then click Connect. In the 6294A-LON-IMG1 - Virtual Machine Connection window, click the Start button. In the Welcome Windows Deployment page, click Run the Deployment Wizard to install a new Operating System. On the User Credentials page, specify the following: Username: Administrator Password: Pa$$w0rd Domain: Contoso Click OK. On the Windows Deployment Wizard Select a task sequence to execute on this computer page, select Deploy Windows 7 to LON-IMG1, and then click Next.
9.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
13
10. On the Windows Deployment Wizard Configure the computer name page, type LON-IMG1, and then click Next. 11. On the Windows Deployment Wizard Join the computer to a domain or workgroup page, click Next. 12. On the Windows Deployment Wizard Specify whether to restore user data page, click Next. 13. On the Windows Deployment Wizard, Language and other preferences page click Next. 14. On the Windows Deployment Wizard Set the Time Zone page, click Next. 15. On the Windows Deployment Wizard Specify whether to capture an image page, select Capture an image of this reference computer, and then click Next. 16. On the Windows Deployment Wizard Ready to begin page, click Begin.
Note: The entire process takes approximately 1 hour to complete.
17. Review the Deployment Summary page for any errors, click Finish, and then turn off LON-IMG1.
14
2. 3. 4.
5. 6. 7.
8.
In the Import Operating System Wizard, review the Confirmation page, and then click Finish.
2. 3.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
15
4. 5.
In the New Task Sequence Wizard, on the Select Template page, specify the Standard Client Task Sequence, and then click Next. In the New Task Sequence Wizard, on the Select OS page, specify the WIN7_REFERENCEDDRIVE in WIN7_REFERENCE WIN7_REFERENCE.wim, and then click Next. In the New Task Sequence Wizard, on the Specify Product Key page, click Next. In the New Task Sequence Wizard, on the OS Settings page set the following: Full Name: Admin Organization: Contoso LTD. and then click Next. In the New Task Sequence Wizard, on the Admin Password page, specify Pa$$w0rd as the Administrator Password and Please confirm Administrator Password, and then click Next. In the New Task Sequence Wizard, on the Summary page, click Next.
6. 7.
8.
9.
10. In the New Task Sequence Wizard, on the Confirmation page, click Finish.
16
9.
10. On the Windows Deployment Wizard Configure the computer name page, type LON-CL3, and then click Next. 11. On the Windows Deployment Wizard Join the computer to a domain or workgroup page, select the Join a domain radio button. In the Domain: field, type Contoso, and then click Next. 12. On the Windows Deployment Wizard Specify whether to restore user data page, click Next. 13. On the Windows Deployment Wizard Language and other preferences page, click Next.
LabAnswerKey:DeployingWindows7byUsingLiteTouchInstallation
17
14. On the Windows Deployment Wizard Set the Time Zone page, click Next. 15. On the Windows Deployment Wizard Specify the BitLocker configuration page, click Next. 16. On the Windows Deployment Wizard Ready to begin page, click Begin.
Note: The entire process takes approximately 20 minutes to complete.
17. Review the Deployment Summary page for any errors, and then click Finish and turn off LON-CL3.
Module 8
Lab Answer Key: Deploying Windows 7 by Using Zero Touch Installation
Contents:
Exercise 1: Planning the Zero Touch Installation Environment Exercise 2: Preparing the Zero Touch Installation Environment Exercise 3: Configuring Deployment Packages and System Images Exercise 4: Configuring and Advertising a Client Task Sequence 3 5 8 12
Requirement Overview To install and configure a Zero Touch Installation using MDT 2010 and System Center Configuration Manager 2007 SP2. To deploy Windows 7 to the new Research department computers. Additional Information You have purchased 50 new computers for the Research department. 1. Given the high-level explanation of the existing Configuration Manager environment, is the current version of Configuration Manager sufficient? What do you need to do in order to incorporate MDT 2010 into the solution? Answer. You will need to upgrade the existing Configuration Manager installation to SP2 in order to support Windows 7 ZTI deployments. In order to integrate MDT 2010, you will need to install the Microsoft Deployment Toolkit and then run the Configure ConfigMgr Integration wizard. 2. What do you need to do to LON-SVR1 in order to support clients booting over the network? Answer. You will need to install the Windows Deployment Services server role on LON-SVR1. You will also need to install the Configuration Manager PXE service point.
Zero Touch Installation Design and Configuration 3. How will you ensure that all newly deployed clients are managed by Configuration Manager? Answer. You will create a Software Distribution Package that contains the Configuration Manager Client. This package will be referenced during the deployment and installed on the client. 4. What steps must you perform from the Configuration Manager Console to prepare the Operating System Image to be deployed to clients? Answer. Your first step is to add the operating system image to the Configuration Manager environment. Your second step is to distribute the images to all required distribution points. Your next series of tasks is to create and distribute an Operating System Install Package. 5. What will be your final main task for configuring LTI from within the Configuration Manager console? Answer. You need to create a Microsoft Deployment Task Sequence that will reference pre-created packages and images as required. You will then advertise the task sequence to the Windows 7 Pilot Deployment Collection.
10. On the Completing the Microsoft Deployment Toolkit 2010 Setup Wizard page, click Finish. 11. Close the MDT window.
Click Finish.
2. 3. 4.
5. 6. 7.
8. 9.
In the console pane, right-click \\LON-SVR1 and then click New Roles. The New Site Role Wizard starts. On the General page, ensure that Specify a fully qualified domain name is selected, and that LON-SVR1.CONTOSO.COM is entered in the Intranet FQDN text box. Leave all other default selections, and then click Next.
10. On the System Role Selection page, select the check box next to PXE service point, and then click Next. 11. On the PXE Service Point Configuration box, click Yes to open the required ports. 12. On the PXE General page, configure the following, and then click Next: Allow this PXE service point to respond to incoming requests: Enabled Enable unknown computer support: Enabled Require a password for computers to boot using PXE: Not Enabled Respond to PXE requests on all network interfaces: Selected Delay (seconds): 0
13. On the PXE Database page, leave all default settings, and then click Next. 14. On the Summary page, click Next. 15. On the Wizard Completed page, click Close.
10. On the Welcome page, click Next. 11. On the Copy Package page, select LON-SVR1, and then click Next. (Do not select LON-SVR1\SMSPXEIMAGES$ as this is the PXE boot distribution point.) 12. On the Wizard Completed page, click Close.
2. 3. 4. 5. 6. 7. 8. 9.
10. On the General page, fill in the following information, and then click Next: Name: Windows 7 ENTERPRISE Version: RTM Comment: <Current date>
11. On the Summary page, click Next. 12. On the Wizard Completed page, click Close. 13. In the console pane, expand the Operating System Images node, and then expand the Windows 7 ENTERPRISE node. 14. Under the Windows 7 ENTERPRISE node, right-click Distribution Points, and then click New Distribution Points. The New Distribution Points Wizard starts. 15. On the Welcome page click Next. 16. On the Copy Package page, select LON-SVR1, and then click Next. (Do not select LON-SVR1\SMSPXEIMAGES$ as this is the PXE boot distribution point.) 17. On the Wizard Completed page, click Close.
10
3. 4.
On the Summary page, click Next. On the Wizard Completed page, click Close. In the console pane, expand the Operating System Install Packages node, and then expand the Windows 7 ENTERPRISE node. Under the Windows 7 ENTERPRISE node, right-click Distribution Points, and then click New Distribution Points. The New Distribution Points Wizard starts. On the Welcome page, click Next.
9.
10. On the Copy Package page, select LON-SVR1, and then click Next. (Do not select LON-SVR1\SMSPXEIMAGES$ as this is the PXE boot distribution point.) 11. On the Wizard Completed page, click Close.
11
5. 6. 7. 8.
On the Add Driver to Packages page, click Next. On the Add Driver to Boot Images page, click Next. On the Summary page, click Next. On the Wizard Completed page, click Close.
In the Driver package source field, type \\LON-DC1\Labfiles\Drivers, and then click OK. In the console pane, click the Drivers node. In the details pane, select the two drivers that are listed. Right-click the selected drivers and then click Add or Remove Drivers to Packages. In the Add or Remove Drivers to Packages dialog box, select the check box next to Driver List. Select the check box next to Update distribution points when finished, and then click OK.
12
On the Details page, fill in the following information, and then click Next: Join a domain: Selected Domain: Contoso.com Account: Username: Contoso\Administrator Password: Pa$$w0rd User name: Client1 Organization name: Contoso
On the Capture Settings page, select This task sequence may be used to capture an image, configure the following settings, and then click Next: Capture destination: \\LON-DC1\Labfiles\Source\Win7.wim Capture account: Username: Contoso\Administrator Password: Pa$$w0rd
7. 8. 9.
On the Boot Image page, ensure that Specify an existing boot image package is selected, and then click Browse. On the Select a Package dialog box, select Boot image (x86), click OK, and then click Next. On the MDT Package page, select Create a new Microsoft Deployment Toolkit Files package.
13
10. In the Package source folder to be created field, type \\LONDC1\Labfiles\MDTFiles, and then click Next. 11. On the MDT Details page, fill in the following information, and then click Next: Name: MDT Source Files Version: 1.0 Language: English Manufacturer: Microsoft Comments: <Current date>
12. On the OS Image page, select Specify an existing OS install package, and then click Browse. 13. On the Select a Package dialog box, select Windows 7 ENTERPRISE, click OK, and then click Next. 14. On the Client Package page, ensure that Specify an existing ConfigMgr client package is selected, and then click Browse. 15. On the Select a Package dialog box, select Configuration Manager Client Upgrade, click OK, and then click Next. 16. On the USMT Package page, select Create a new USMT package. 17. Under Path to USMT executables and related files, ensure that C:\Program Files\Windows AIK\tools\USMT is entered. 18. Under Package source folder to be created, type \\LON-DC1\Labfiles \USMT, and then click Next. 19. On the USMT Details page, fill in the following information, and then click Next: Name: MDT USMT Package Version: 1.0 Language: English Manufacturer: Microsoft Comments: <Current date>
20. On the Settings Package page, select Create a new settings package.
14
21. In the Package source folder to be created field, type \\LON-DC1\Labfiles \MDTFiles, and then click Next. 22. On the Settings Details page, fill in the following information, and then click Next: Name: MDT Settings Files Version: 1.0 Language: English Manufacturer: Microsoft Comments: <Current date>
23. On the Sysprep Package page, select No Sysprep package is required, and then click Next. 24. On the Summary page, click Next. 25. After the wizard is finished, click the Task Sequences node, and then rightclick Windows 7. Click Edit. Take note ofbut do not changethe various tasks that make up the Windows 7 task sequence. 26. Click Cancel to close the Windows 7 Task Sequence Editor.
4. 5.
6. 7.
15
8.
Under the Microsoft MDT Source Files 1.0 English node, right-click Distribution Points, and then click New Distribution Points. The New Distribution Points Wizard starts. On the Welcome page, click Next.
9.
10. On the Copy Package page, select LON-SVR1, and then click Next. (Do not select LON-SVR1\SMSPXEIMAGES$ as this is the PXE boot distribution point.) 11. On the Wizard Completed page, click Close. 12. In the console pane, expand the Microsoft MDT USMT Package 1.0 English node. 13. Under the Microsoft MDT USMT Package 1.0 English node, right-click Distribution Points, and then click New Distribution Points. The New Distribution Points Wizard starts. 14. On the Welcome page, click Next. 15. On the Copy Package page, select LON-SVR1, and then click Next. (Do not select LON-SVR1\SMSPXEIMAGES$ as this is the PXE boot distribution point.) 16. On the Wizard Completed page, click Close. 17. Wait a few minutes before continuing with the next task.
16
4.
On the Schedule page, configure the following, and then click Next: Mandatory assignments: As soon as possible Ignore maintenance windows when running program: Enabled Allow system restart outside of maintenance windows: Enabled Program rerun behavior: Always rerun program
5.
On the Distribution Points page, select Access content directly from a distribution point when needed by the running task sequence, and then click Next. On the Interaction page, leave the default settings, and then click Next. On the Security page click Next. On the Summary page, click Next. On the Wizard Completed page, click Close.
6. 7. 8. 9.
10. In the console pane, expand the Computer Management\Collections node. 11. Click the All Unknown Computers collection. 12. Right-click the All Unknown Computers collection, and then click Properties. 13. Click the Advertisements tab. Verify that the Windows 7 Deployment task sequence has been advertised to this collection. 14. Click OK to close the All Unknown Computers Properties page.
17
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
Module 9
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
Contents:
Lab A: Migrating User State by Using Windows Easy Transfer (Optional) Exercise 1: Preparing the Windows Easy Transfer Source Files Exercise 2: Capturing User State Information from a Source Computer Exercise 3: Loading User State Information to a Target Computer Lab B: Migrating User State by Using the User State Migration Tool 4.0 Exercise 1: Planning for the User State Migration Exercise 2: Creating USMT Migration Scripts Exercise 3: Capturing and Restoring User State by Using USMT Lab C: Migrating User State Using Hard-Link Migration Exercise 1: Performing a Hard-Link Migration 16 8 12 14 3 4 6
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
10. Click Open the folder where you saved Windows Easy Transfer. In the Data folder, verify that the files have been copied to the shared folder. 11. Close the Data folder. 12. Close Windows Easy Transfer.
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
10. Clear all of the checkboxes except for CONTOSO\Don. 11. Under CONTOSO\Don, click Customize. 12. Remove the check mark next to the following options: Music Saved Games Videos
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
13. Close the Customize list and then click Next. 14. In the Password and Confirm Password boxes, type Pa$$w0rd and then click Save. 15. In the Save Your Easy Transfer File window, in the File name box, type \\LON-DC1\Data\DonProfile and then click Save. Windows Easy Transfer begins to save the files to the Data folder. 16. When the save is complete, click Next. 17. Click Next and then click Close. 18. Log off of LON-VS1.
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
10. In the Windows Easy Transfer Reports box, take note of what was transferred successfully as listed on the Transfer report tab. 11. Click the Program report tab and take note of the information related to programs. Close the Windows Easy Transfer Reports box. 12. In the Windows Easy Transfer box, click Close. 13. Log off of LON-CL1.
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
Lab B: Migrating User State by Using the User State Migration Tool 4.0
Computers in this lab
Before you begin the lab, you must start the virtual machines. The virtual machines used at the start of this lab are: 6294A-LON-DC1 6294A-LON-VS1 6294A-LON-CL1
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
User State Migration PlanningJob Aid Department Name: ___Research Department__ Question Information Details Computers are being replaced with PC Refresh new hardware containing Windows Migration Scenario PC 7. ; Replacement 32 bit As per the email message from Max Windows XP Stevens, all of the old computers are Windows Vista 32-bit computers. 64 bit Windows XP 32 bit Which Operating Windows ; System are you Vista migrating user state 64 bit from? Windows Vista 32 bit Windows 7 64 bit Windows 7 32 bit As per the email message from Max Windows XP Stevens, the new operating system will be 32-bit Windows 7. 64 bit Windows XP 32 bit Which Operating Windows Vista System are you migrating user state 64 bit to? Windows Vista 32 bit ; Windows 7 64 bit Windows 7 Remote migration store location: Local Store \\LON-DC1\Data Migration Store Type Remote Store ;
10
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
(continued) User State Migration PlanningJob Aid Department Name: ___Research Department__ Question Information Details Compression is enabled by default, Compressed? ; Migration Store we will leave it at the default settings. Options Encryption is not required as per the Encrypted? email from Max Stevens. Local Local account named DBService ; accounts needs to be migrated. Accounts to be migrated All domain accounts will be migrated. Local account named LocalAdmin must NOT be migrated. All computers have Microsoft Office 2007 installed. The settings will be migrated, but not the applications themselves. The applications will need to be installed on the new computers.
Domain accounts
; ; ;
Custom files or folders to migrate Are there any encrypted files to consider?
ResearchApp
Yes No
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
11
(continued) User State Migration PlanningJob Aid Department Name: ___Research Department__ Question Information Details All Settings Windows Vista Gadgets should not except for be migrated. components ; listed in the Shared Video folder should not be details migrated. section. Operating system Shared Music folder should not be settings to migrate migrated.
Config.xml MigApp.xml
; ; ; ;
Needed to specify exceptions such as the gadgets, and shared folders. Needed on both the ScanState and LoadState commands in order to migrate application settings. Needed on both the ScanState and LoadState to migrate the user profile information such as user folders, files, and file types. Not required. Create a custom xml file called folders.xml that will contain information on migrating the Researchapp folder.
12
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
6. 7.
8. 9.
Under the Documents node, modify the line to match the code shown below:
component displayname="Shared Video" migrate="no"
Under the Documents node, modify the line to match the code shown below:
component displayname="Shared Music" migrate="no"
10. Under the Documents node, modify the line to match the code shown below:
component displayname="Shared Pictures" migrate="no"
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
13
2.
3.
14
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
This will take several minutes to complete. 6. When the Loadstate task completes, log off of LON-CL1.
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
15
16
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
4. 5.
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
17
6. 7. 8. 9.
On the Get important updates for installation page, click Do not get the latest updates for installation. On the Please read the license terms page, click the check box next to I accept the license terms and then click Next. On the Which Type of installation do you want? page, click Custom (advanced). On the Where to you want to install Windows? page, click Next.
10. At the Install Windows warning prompt, click OK. Windows begins the installation. This will take approximately 30 minutes. 11. After the installation is complete, at the Set Up Windows page, click Next to accept the default Country, Time and currency, and Keyboard layout. 12. In the Type a user name box type Alan. 13. In the Type a computer name box, type LON-VS1. Click Next. 14. In the Set a password for your account page, type Pa$$w0rd in all three text boxes. Click Next. 15. On the Help protect your computer and improve Windows automatically page, click Use recommended settings. 16. On the Review your time and date settings page, click Next. 17. On the Select your computers current location page, click Work network. Windows 7 starts.
18
Lab Answer Key: Migrating User State by Using WET and USMT 4.0
5.
At the command prompt, type the following and then press ENTER:
Scanstate C:\store /o /hardlink /nocompress /i:migapp.xml /i:miguser.xml /offlineWinOld:c:\Windows.old\Windows
This will take several minutes to complete. 6. At the command prompt, type the following and then press ENTER:
Loadstate C:\store /lac /lae /i:migapp.xml /i:miguser.xml /sf /hardlink /nocompress
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
Module 10
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
Contents:
Lab A: Designing and Configuring the Client Environment Exercise 1: Designing a Client Environment Exercise 2: Implementing a Client Configuration Lab B: Troubleshooting GPO Issues Exercise 1: Resolving a GPO Application Problem 12 2 6
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
Group Policy Objects for Contoso Document Reference Number: EM1109 Document Author Date Requirement Overview To determine which Group Policy Objects are required, and linked to which Active Directory objects, in order to address the domain and departmental requirements in the Summary document. You may use the Contoso GPO.vsd diagram to sketch your answer if you wish. Your plan should include how you intend to address each desired setting; that is, which policy or, where necessary, which preference setting. Additional Information 1. Where will you configure the domain-level settings outlined in the Summary document? Answer. Most of those settings can be configured as part of the default domain policy. 2. What impact does the fact that IT users must be able to run unsigned scripts have on your GPO strategy? Answer. It will be necessary to create an additional policy that contains the Application Restrictions as these cannot apply to the IT department, but all other settings must be enforced down the tree. 3. How will you handle application deployment for the various departments? Answer. No two departments have the same application requirements; Marketing has no special application needs, but the other three departments do. Create a GPO for application deployment and link it to the relevant organizational units. Ed Meadows November 2009
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
(continued)
Group Policy Objects for Contoso 4. How will you restrict the Production department users from running Internet Explorer? Answer. Modify the GPO linked to the Production department OU to have an Application Control Policy (AppLocker) that blocks Internet Explorer. 5. Will you handle drive mappings using preferences or a logon script? Answer. Either would work. The advantage of using a preference is that a single preference on the Default Domain Profile could be targeted to particular organizational units. This negates the need to duplicate the setting in three different GPOs. 6. How do you intend to manage the IT departments requirement for a standard Documents folder? Answer. Folder redirection on the IT department GPO. 7. Sketch, or document, the intended GPO and how they are linked to AD DS objects on the supplied diagram. Indicate which settings will be configured by which object. Note: it is not necessary to detail the precise GPO settings.
Proposals 1. Modify the Default Domain Policy: a. Configure account policies b. Configure firewall rule to allow ping on domain profile c. Configure Application Identity service to automatic startup d. Configure Internet Explorer homepage e. Configure targeted preference for computers in all but Production department for a drive mapping
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
(continued)
Group Policy Objects for Contoso 2. 3. 4. 5. 6. Enforce this policy Create a new domain-level policy with an AppLocker policy that prevents all scripts except those signed by Microsoft from running. Block inheritance on the IT OU to ensure the script restriction does not apply. Create departmental level GPO for Research: a. Deploy Apps (One Note and Visio) Create departmental level GPO for IT: a. Deploy Visio b. Configure folder redirection for Documents 7. Create departmental level GPO for Production: a. Deploy custom app b. Block Internet Explorer from running
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
4.
3. 4. 5. 6. 7. 8. 9.
10. In the File name box, type C:\windows\system32\slmgr.vbs, and then click Open. 11. In the Publisher Exception dialog box, drag the slider to Publisher, and then click OK. 12. On the Exceptions page, click Next.
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
13. On the Name and Description page, click Create. 14. In the AppLocker dialog box, click Yes. 15. Close Group Policy Management Editor.
1. 2.
In Group Policy Management, right-click Default Domain Policy, and then click Edit. In Group Policy Management Editor, expand User Configuration, expand Policies, expand Windows Settings, expand Internet Explorer Maintenance, and then click URLS. In the results pane, double-click Important URLs. Select the Customize Home page URL check box, and in the Home page URL: box, type http://lon-dc1, and then click OK. Under Computer Configuration, expand Policies, expand Windows Settings, expand Security Settings, expand Windows Firewall with Advanced Security, and then expand Windows Firewall with Advanced Security LDAP://CN={GUID}. In the navigation tree, click Inbound Rules, and then right-click Inbound Rules. Click New Rule. On the Rule Type page of the New Inbound Rule Wizard, select Custom and then click Next. On the Program page, click Next.
3. 4. 5.
6. 7. 8. 9.
10. On the Protocol and Ports page, in the Protocol type list, click ICMPv4, and then click Next. 11. On the Scope page, click Next. 12. On the Action page, click Allow the connection and then click Next.
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
13. On the Profile page, clear the Private and Public check boxes, and then click Next. 14. On the Name page, in the Name box, type Allow Ping, and then click Finish. 15. In the Group Policy Management Editor, under User Configuration, expand Preferences, expand Windows Settings, and click Drive Maps. 16. Right-click Drive Maps, click New, and then click Mapped Drive. 17. In the New Drive Properties dialog box, in the Location box, type \\lon-dc1\data. 18. Select the Reconnect check box. 19. In the Use list, click G. 20. Click the Common tab. 21. Select the Item-level targeting check box, and then click Targeting. 22. In the Targeting Editor dialog box, click New Item. 23. In the list, click Domain. 24. In the NetBIOS domain name box, type CONTOSO, and then click OK. 25. In the New Drive Properties dialog box, click OK. 26. Under Computer Configuration, expand Policies, expand Windows Settings, expand Security Settings, and click System Services. 27. In the results pane, double-click Application Identity. 28. In the Application Identity Properties dialog box, select the Define this policy setting check box, click Automatic, and then click OK. 29. Close Group Policy Management Editor.
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
f Task 6: Move the two desktop computers into the appropriate OUs
1. 2. 3. 4. 5. 6. 7. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers. In Active Directory Users and Computers, in the navigation tree, expand Contoso.com, and then click Computers. In the results pane, right-click LON-CL1, and then click Move. In the Move dialog box, click IT, and then click OK. In the results pane, right-click LON-CL2, and then click Move. In the Move dialog box, click Production, and then click OK. Close Active Directory Users and Computers.
10. Click Start, and in the Search programs and files box, type cmd, and press ENTER.
10
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
11. In the Command Prompt, type gpupdate /force, and then press ENTER. 12. At the OK to logoff? (Y/N) prompt, type N and press ENTER. 13. Restart the computer. 14. Log on to the LON-CL2 virtual machine as CONTOSO\Jens with a password of Pa$$w0rd.
5. 6. 7. 8. 9.
10. At the Command Prompt, type test.vbs and press ENTER. Verify that an unsigned script ran successfully. Click OK. 11. Close all open windows. 12. Switch to the LON-CL2 computer. 13. Click Start, and in the Search programs and files box, type cmd and press ENTER.
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
11
14. At the Command Prompt, type copy con test.vbs and press ENTER. 15. At the Command Prompt, type msgbox test and press ENTER. 16. At the Command Prompt, press F6, and then press ENTER. 17. At the Command Prompt, type test.vbs and press ENTER. Verify that an unsigned script failed to run. Click OK. 18. Close all open windows.
Important: Do not restart the virtual machines. You will need them for the subsequent lab.
12
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
13
7. 8. 9.
Log on to the LON-CL1 virtual machine as CONTOSO\Ryan with a password of Pa$$w0rd. Switch to the LON-CL2 computer. Log off, and then log on to the LON-CL2 virtual machine as CONTOSO\administrator with a password of Pa$$w0rd.
10. Click Start, and in the Search programs and files box, type cmd and press ENTER. 11. In the Command Prompt, type gpupdate /force and then press ENTER. 12. At the OK to logoff? (Y/N) prompt, type N and press ENTER. 13. Restart the computer. 14. Log on to the LON-CL2 virtual machine as CONTOSO\Jens with a password of Pa$$w0rd.
5. 6. 7.
14
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
10. In the Trusted sites dialog box, click Add twice, and then click Close.
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
15
2. 3. 4. 5. 6.
16
Lab Answer Key: Designing, Configuring, and Managing the Client Environment
5.
Which settings are being applied by the Default Domain Policy? Answer: Account Policies Account Policies Local Policies System Services\Application identity Public Key Policies Windows Firewall with Advanced Security\inbound rule Internet Explorer Maintenance\home page Preferences\drive mapping
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
Module 11
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
Contents:
Lab A: Determining the Application Deployment Method Exercise 1: Determining the Application Deployment Method Lab B: Customizing the Microsoft Office Professional Plus 2007 Installation Exercise 1: Creating a Setup Customization File Lab C: Planning and Managing Updates by Using WSUS Exercise 1: Planning Group Policy Automatic Update Settings Exercise 2: Configuring Automatic Update Settings by Using Group Policy Exercise 3: Approving and Deploying an Update by Using WSUS 9 11 13 6 2
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
Requirement Overview Determine the most appropriate method for deploying corporate and departmental applications. Questions 1. Does the current infrastructure support any automated deployment methods? Answer. Yes, the current infrastructure has an Active Directory infrastructure which supports Group Policy software deployment. The infrastructure also contains Configuration Manager 2007, which includes software deployment features.
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
(continued)
Application Deployment Worksheet 2. What are the advantages and disadvantages of the current deployment options available to Contoso? Answer. Active Directory Group Policy is a relatively simple method for deploying software, however it does have a couple of disadvantages such as the lack of reporting and it only supports MSI or ZAP files. Configuration Manager 2007 provides extensive reporting and supports all types of installation files, however it is quite a bit more complex to deploy and configure than Group Policy. 3. Based upon Adams requirements, which method should you consider to deploy the 2007 Office system? Answer. Configuration Manager would be the best way to deploy the 2007 Office system; however Adam states that he wants to maintain full control of the customization and deployment processes. In this case, it is best to store the setup files on a network installation point, create a customized installation file that will provide silent installation capabilities, and perform installation tasks from the installation point itself. Group Policy might be considered, however the 2007 Office system is not recommended to be deployed using Group Policy. 4. Based upon Adams requirements, which method should you consider to deploy Adobe Reader? Answer. Since Adobe Reader is an organization-wide requirement, the best method would be to deploy this application using Configuration Manager 2007. However since it is currently only being used for inventory purposes, Group Policy would be the next best method as long as an MSI file is available for the application. You may also consider installing the application in the desktop image, since it is quite a small application.
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
(continued)
Application Deployment Worksheet 5. What can you do to ensure that Office 2003 is still available for users that require the use of the customized templates? Answer. Since the 2007 Office system does not easily co-exist with multiple versions, there are a number of ways to provide access to Office 2003. One method is to use application virtualization to provide Office 2003 applications. This will ensure that all versions do not interfere with each other and allow for the use of all customized templates. Another method is to publish Office 2003 applications as a Terminal Services RemoteApp. An added advantage of using RemoteApp is that users will be able to access Office 2003 over the Internet if needed. One final method might be the use of Windows XP mode for Windows 7. This would allow for the publishing and usage of Office 2003 from a virtual machine installed on the Windows 7 desktop.
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
5. 6. 7. 8. 9.
10. In the left pane, click Licensing and user interface. 11. Select the I accept the terms in the License Agreement check box. 12. Next to Display level, select Basic, and then ensure that the check mark next to Completion notice is enabled. Note that usually you would also enter a volume license key; however, for this exercise it will not be configured in the Setup customization file. 13. In the left navigation pane, click Remove previous installations. Ensure that Default Setup behavior is selected, which will remove all earlier versions of installed programs. 14. In the left navigation pane, click Office security settings. 15. Under Add the following paths to the Trusted Locations list, click Add. 16. In the Specify Security Locations dialog box, in the Application drop-down menu, select Microsoft Office Word. In the Path box type, \\LON-DC1\Data.
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
17. Click to enable the check box next to Subfolders of this location are also trusted. Click OK. 18. In the left navigation pane, click Modify Setup Properties and then click Add. 19. In the Name box type HIDEUPDATEUI. 20. In the Value box type True and then click OK.
10. Double-click Disallow Convert Document (Excel, PowerPoint, Word). 11. In the Disallow Convert Document (Excel, PowerPoint, Word) Properties box, click Enabled, and then click OK. 12. At the bottom of the details pane, clear the Migrate user settings check box. 13. In the left navigation pane, click Set feature installation states. 14. In the details pane, expand Microsoft Office, click the grey box next to Microsoft Office Publisher, and then click Not Available. 15. In the details pane, click the grey box next to Microsoft Office Access, and then click Not Available.
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
16. In the details pane, expand Microsoft Office Excel, click the grey box next to Sample Files, and then click Not Available. 17. On the File menu, click Save. 18. Browse to E:\Labfiles\Office2007\Updates. Name the file Research, and then click Save. 19. Close the Office Customization Tool, and then click Yes to quit.
f Task 3: Install the 2007 Office System Using the Setup Customization
File
1. 2. Log on to LON-CL1 as Contoso\Administrator with the password of Pa$$w0rd. Click Start, and then in the Search programs and files box type \\LON-DC1\Labfiles\Office2007\setup.exe, and then press ENTER. The installation begins. This will take 10-15 minutes to complete. After the installation is complete, verify that your customizations are implemented.
3.
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
10
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
Marketing Department
Setting Name
Configuration
Configure automatic updating: 4 Auto download and schedule the install Scheduled install day: 0 Every day Scheduled install time: 17:00
Group Policy Setting Requested Specify intranet Microsoft update service location
Set the intranet update service for detecting updates: http://LONDC1 Set the intranet statistics server: http://LON-DC1
8 hours
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
11
In the details pane, double-click Specify intranet Microsoft update service location.
10. In the Specify intranet Microsoft update service location dialog box, click Enabled. 11. Under Options configure the following and then click OK: Set the intranet update service for detecting updates: http://LON-DC1 Set the intranet statistics server: http://LON-DC1
12. In the details pane, double-click Automatic Updates detection frequency. 13. In the Automatic Updates detection frequency dialog box, click Enabled.
12
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
14. Under Options configure the following and then click OK: Interval (hours): 8
15. Close the Group Policy Management Editor. 16. Close Group Policy Management.
f Task 2: Verify that the Automatic Updates policy settings have applied
1. 2. 3. 4. 5. 6. 7. Log on to LON-CL1 with the user name Administrator and the password Pa$$w0rd. Click Start, and then in the Search programs and files box, type cmd and then press ENTER. At the command prompt type gpupdate /force and then press ENTER. Close the command prompt. Click Start, and then in the Search programs and files box, type Windows Update. In the search results, under Programs, click Windows Update. On the Windows Update page, click Change settings. Notice the information message at the top of the window stating that some settings are managed by the system administrator. Also notice that some of the configuration settings are grayed out. On the Change settings page, click Cancel and then close Windows Update. Close the Control Panel.
8. 9.
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
13
3. 4. 5. 6. 7. 8. 9.
10. Close the Update Services console. 11. On LON-CL1, click Start, and then in the Search programs and files box, type Windows Update.
14
Lab Answer Key: Planning and Deploying Applications and Updates to Windows 7 Clients
12. In the search results, under Programs, click Windows Update. 13. On the Windows Update page, click Check for updates. 14. Click Install Updates.
LabAnswerKey:DeployingWindows7ChallengeScenario
Module 12
Lab Answer Key: Deploying Windows 7 Challenge Scenario
Contents:
Lab A: Planning an End to End Windows 7 LTI Deployment Exercise 1: Planning the MDT Lite Touch Environment Lab B: Deploying Windows 7 Using the LTI Deployment Plan Exercise 1: Performing a Network Assessment Exercise 2: Configuring MDT 2010 for an LTI Deployment Exercise 3: Configuring WDS for a PXE and Multicast Deployment Exercise 4: Configuring an MDT 2010 Deployment Share Exercise 5: Creating the Reference Computer Exercise 6: Preparing the Deployment Task Sequences Exercise 7: Performing an Upgrade on Target Computers 8 10 12 14 19 21 24 2
f Task 2: Use the following decision tree and checklist to help facilitate
the creation of the deployment plan
Create a deployment plan using the following aids.
LabAnswerKey:DeployingWindows7ChallengeScenario
64 Bit
32 Bit
Required Components
Install MDT
Install WAIK
Planning Components
YES
Install MAP
YES
Installation Components
NO
Install ACT
Prepare CD/DVDs
Media
Deploying OS through?
NETWORK
Configure DHCP
PXE Boot
MultiCast Deployment? NO
YES
Prepare WDS
YES
To Page 2
From Page 1
YES
YES
LabAnswerKey:DeployingWindows7ChallengeScenario
MicrosoftDeploymentToolkitJobAid
Microsoft Deployment Toolkit Planning
Microsoft Deployment Toolkit PlanningJob Aid Question What Operating System are you going to deploy? What System is going to be deployed as the Technicians system? Are you going to be deploying Applications? What MDT additional components are you going to install? Where will you store your distribution files? Information 32 bit Windows 7 64 bit Windows 7 32 Windows Server 2008 R2 64 bit Windows Server 2008 R2 Windows 7 client Windows 2008 R2 server Yes No MAP WAIK USMT ACT Local Deployment Share Remote Deployment Share ; ; LON-CL2 is a 32 bit Windows 7 Enterprise Edition Details 32 bit Windows 7 Enterprise Edition
; ; ; ; Office 2007 needs to be deployed to all systems. System compatibility needs to be checked. WAIK contains the ImageX and USMT 4.0 files. The Remote Server LON-DC1 is going to be used as the deployment Share
(continued) Microsoft Deployment Toolkit PlanningJob Aid Question What is your imaging and source file strategy? Do you want to back up computers before deployment? Will you be deploying any drivers not included with Windows 7? Will you deploy across the network, with removable media, or both? Which Deployment Scenario will you use? Information CD Network Share Yes No Yes No ; ; ; All systems will be PXE booted and deployed from a network share. Yes Windows IPoint and LifeCam drivers need to be installed. Details All systems will be PXE booted and deployed from a network share. Systems should be captured prior to deployment.
Network
Removable Media New Computer Upgrade Existing Computer Refresh Computer Replace Computer
; ; Some computers are scheduled to be upgraded to Windows 7 and some are scheduled for replacement.
LabAnswerKey:DeployingWindows7ChallengeScenario
(continued) Microsoft Deployment Toolkit PlanningJob Aid Question Will you deploy a full set of operating system files or a custom Windows Imaging Format (WIM)? Are you going to allow users to choose their own operating system, applications, locale, time zone, and administrative password? Which product editions will you deploy? How will you handle product keys and licensing? Information Details A Full OS Set will be used to create the Reference Computer and the Custom WIM created from the reference computer will be used for the general deployment.
Custom WIM
Yes
No
Professional Ultimate Business Enterprise Multiple Activation Key (MAK) Key Management Service(KMS)
; ;
4.
LabAnswerKey:DeployingWindows7ChallengeScenario
5.
On the Windows Networking Protocols page ensure the following: Workgroups and Windows domains to include in the inventory: Contoso Click Next. On the WMI Credentials page, click New Account. Fill in the Inventory Account page with the following: Domain name: Contoso Account name: Administrator Password: Pa$$w0rd Confirm password: Pa$$w0rd Click Save. On the WMI Credentials page, click Next. On the Summary page, click Finish.
6. 7.
8. 9.
10. Once the inventory is complete, on the Status page, click Close.
On the host computer, in the Hyper-V Manager, right-click 6294A-LON-VS2, and then click Settings. In the Settings for 6294A-LON-VS2 dialog box, click Memory. In the RAM field, type 768. In the Settings for 6294A-LON-VS2 dialog box, click OK.
10
5. 6. 7. 8.
LabAnswerKey:DeployingWindows7ChallengeScenario
11
3. 4. 5. 6. 7. 8. 9.
On the Welcome to the Windows Automated Installation Kit Setup Wizard page click Next. On the License Terms page, select the I Agree radio button, and then click Next. On the Select Installation Folder page, review the defaults and then click Next. On the Confirm Installation page, click Next. On the Installation Complete page click Close. Close the Welcome to Windows Automated Installation Kit page. Close the Explorer window.
12
LabAnswerKey:DeployingWindows7ChallengeScenario
13
7. 8.
On the Operation Complete page, clear the Add images to the server now check box, and then click Finish. Close the Windows Deployment Services MMC.
14
10. In the New Deployment Share Wizard, review the Confirmation page, and then click Finish.
LabAnswerKey:DeployingWindows7ChallengeScenario
15
3.
2. 3. 4. 5. 6. 7. 8. 9.
16
2. 3. 4.
7. 8.
LabAnswerKey:DeployingWindows7ChallengeScenario
17
9.
In the Import Operating System Wizard, on the Source page, type D:\, and then click Next.
10. In the Import Operating System Wizard, on the Destination page, click Next. 11. In the Import Operating System Wizard, on the Summary page, click Next. 12. In the Import Operating System Wizard, review the Confirmation page, and then click Finish.
2. 3. 4. 5. 6.
2. 3.
4.
18
5. 6. 7.
In the New Task Sequence Wizard, on the Select OS page, specify the Windows 7 Enterprise in Windows 7 x86 install.wim, and then click Next. In the New Task Sequence Wizard, on the Specify Product Key page, click Next. In the New Task Sequence Wizard, on the OS Settings page configure the following: Full Name: Admin Organization: Contoso LTD. and then click Next. In the New Task Sequence Wizard, on the Admin Password page, select the Do not specify an Administrator password at this time radio button, and then click Next. In the New Task Sequence Wizard, on the Summary page, click Next.
8.
9.
10. In the New Task Sequence Wizard, on the Confirmation page, click Finish.
2. 3. 4. 5.
LabAnswerKey:DeployingWindows7ChallengeScenario
19
10. Select the Boot tab, and then select both Always continue the PXE boot radio buttons. 11. Click OK.
20
5.
On the Windows Deployment Wizard, Select a task sequence to execute on this computer page, select Deploy Windows 7 to LON-IMG1, and then click Next. On the Windows Deployment Wizard, Configure the computer name page, type LON-IMG1, and then click Next. On the Windows Deployment Wizard, Join the computer to a domain or workgroup page, click Next. On the Windows Deployment Wizard, Specify whether to restore user data page, click Next. On the Windows Deployment Wizard, Language and other preferences page, click Next.
6. 7. 8. 9.
10. On the Windows Deployment Wizard, Set the Time Zone page, click Next. 11. On the Windows Deployment Wizard, Select one or more applications to install page, check Microsoft Office 2007, and then click Next. 12. On the Windows Deployment Wizard, Specify whether to capture an image page, click Capture an image of this reference computer, and then click Next. 13. On the Windows Deployment Wizard, Ready to begin page, click Begin.
Note: The installation and WIM file create can take up to two hours. For this lab, a license key will not be provided when installing Microsoft Office 2007. Because of this you will be prompted to perform the Microsoft Office installation manually. To view the Microsoft Office installation window, you may need to move the Installation Progress dialog box.
14. Review the Deployment Summary page for any errors and then click Finish. 15. Turn off LON-IMG1.
LabAnswerKey:DeployingWindows7ChallengeScenario
21
2. 3. 4.
5. 6. 7. 8.
2. 3.
4. 5. 6. 7.
22
8. 9.
Select the Task Sequence tab, and select the Wipe Disk task. Select the Options tab.
10. Check the Disable this Step check box. 11. Click OK.
Note: The Wipe Disk task is disabled in order to save time in the lab environment.
12. Right-click MDT Deployment Share (\\LON-DC1\DeploymentShare) and select Properties. 13. On the Rules tab, modify the CustomSettings.ini file as follows: [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y
UserDataLocation=NETWORK SkipAppsOnUpgrade=NO SkipCapture=NO SkipAdminPassword=YES SkipProductKey=YES 14. On the MDT Deployment Share (\\LON-DC1\DeploymentShare) Properties window, click OK.
2.
LabAnswerKey:DeployingWindows7ChallengeScenario
23
3.
In the New Task Sequence Wizard, on the General Settings page, set the following: Task sequence ID: AKRON_DEPLOY Task sequence name: Deploy Windows 7 to Akron and then click Next. In the New Task Sequence Wizard, on the Select Template page, specify the Standard Client Task Sequence, and then click Next. In the New Task Sequence Wizard, on the Select OS page, specify the AKRON_REFERENCEDDRIVE in AKRON_REFERENCE AKRON_REFERENCE.wim, and then click Next. In the New Task Sequence Wizard, on the Specify Product Key page, click Next. In the New Task Sequence Wizard, on the OS Settings page set the following: Full Name: Admin Organization: Contoso LTD. and then click Next. In the New Task Sequence Wizard, on the Admin Password page, specify Pa$$w0rd as the Administrator Password and Please confirm Administrator Password, and then click Next. In the New Task Sequence Wizard, on the Summary page, click Next.
4. 5.
6. 7.
8.
9.
10. In the New Task Sequence Wizard, on the Confirmation page, click Finish.
2. 3. 4. 5.
24
5.
Note: While the scenario calls for a backup, you are not creating a backup as a time saving step.
6.
On the Specify credentials for connecting to network shares page; specify the following: Username: Administrator Password: Pa$$w0rd Domain: Contoso Click Next.
Note: If you receive an 800704C3 error, use the IP Address 10.10.0.10 instead of Contoso for the Domain name.
LabAnswerKey:DeployingWindows7ChallengeScenario
25
7.
Note: If you receive an error message indicating that a connection cannot be made to the deployment share, you will need to start over with step 2 above. Instead of using the \\LON-DC1\DeploymentShare\Scripts\LiteTouch.wsf path, use \\10.10.0.10\DeploymentShare\Scripts\LiteTouch.wsf. If you do this, you will need to click Open to run the remote script. You will also receive error messages indicating that you have multiple connections to a server using the same user name. The installation should complete successfully.
8.
Review the Deployment Summary page for any errors, and then click Finish and turn off the system.
26
9.
On the Windows Deployment Wizard, Select a task sequence to execute on this computer page; select Deploy Windows 7 to Akron, and then click Next.
10. On the Windows Deployment Wizard, Configure the computer name page, type LON-VS1a, and then click Next.
Note: To re-use the computer name reset or delete the existing computer object in Active Directory.
11. On the Windows Deployment Wizard, Join the computer to a domain or workgroup page, select the Join a domain radio button. In the Domain: field type Contoso, and then click Next. 12. On the Windows Deployment Wizard, Specify whether to restore user data page, select the Specify a location radio button and type \\LON-DC1\Data \VS1 and then click Next. 13. On the Windows Deployment Wizard, Language and other preferences page, click Next. 14. On the Windows Deployment Wizard, Set the Time Zone page, click Next. 15. On the Windows Deployment Wizard, Select one or more applications to install page, click Next. 16. On the Windows Deployment Wizard, Specify the BitLocker configuration page, click Next. 17. On the Windows Deployment Wizard, Ready to begin page, click Begin. 18. Repeat steps 7 through 17 on 6294A-LON-VS2 replacing the references to VS1 in steps 10 and 12 with VS2.
Note: To monitor the multicast environment, on LON-DC1 open the Windows Deployment Services Console. Expand LON-DC1.Contoso.com, expand Multicast transmissions and select MDT DeploymentShare. You may have to refresh the node to view the multicast entries.
Perform the following steps while the image is deploying to the systems: 19. On LON-DC1; click Start, point to Administrative Tools, and click Windows Deployment Services. 20. Right click LON-DC1.Contoso.Com, and select Properties.
LabAnswerKey:DeployingWindows7ChallengeScenario
27
21. Select the Boot tab, and then select both Require the user to press the F12 key to continue the PXE boot radio buttons. 22. Click OK.
Note: Failing to complete this step will cause the deployed systems to re-enter the PXE environment on reboot.
After the image has completed deploying: 23. Review the Deployment Summary page for any errors and then click Finish.