6418cd 6418c Enu Labmanual

8/12/2019 6418cd 6418c Enu Labmanual

1/137

O F F I C I A L M I C R O S O F T L E A R N I N G P R O D U C T

6418C

Lab Instructions and Lab Answer Keys:Deploying Windows Server 2008


2/137

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.

2010 Microsoft Corporation. All rights reserved.

Microsoft, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/orother countries.

All other trademarks are property of their respective owners.

Product Number: 6418C

Part Number: X17-41891

Released: 08/2010


3/137

Lab Instructions: Installing and ConfiguringWindows Server 2008 1

Module 1

Lab Instructions: Installing and ConfiguringWindowsServer 2008

Contents:Lab A:Planning to Install Windows Server 2008 (Optional)Exercise :Using the Microsoft Assessment and Planning Toolkit 3Lab B:Installing Windows Server and Configuring Post-InstallationSettingsExercise :Installing Windows Server 2008 R2 8Exercise 2:Configuring Server Core 9Exercise 3:Enabling Remote Management 11Lab C:Managing Roles and FeaturesExercise :Adding the Domain Name System and Dynamic HostConfiguration Protocol Server Roles 14

Exercise 2:Managing Server Core 15Lab D:Configuring Windows Server 2008 LicensingExercise :Planning Volume Activation 19


4/137

2 Lab Instructions: Installing and ConfiguringWindows Server 2008

Lab A: Planning to Install Windows Server 2008(Optional)

Lab Setup

For this lab, you will use the available virtual machine environment. Before you begin the lab, you must

complete the following steps:

1. On the host computer, click Start, point to Administrative Tools, and then click Hyper-V Manager.2. In Hyper-V Manager, click 6418C-NYC-DC1, and in the Actions pane, click Start.3. In the Actions pane, click Connect. Wait until the virtual machine starts. Click the CTRL+ALT+DELETE

button in the top, left corner of the Virtual Machine Connection window.

4. Log on using the following credentials: User name: Administrator Password: Pa$$w0rd Domain: Contoso

5. Repeat these steps for 6418C-NYC-SVR1and 6418C-NYC-CL1.


5/137


6/137


Task 3: Generate reports and proposals In the Actions pane, click Generate report/proposal.

Task 4: View saved reports and proposals1. In Microsoft Assessment and Planning Toolkit, on the Viewmenu, click Saved Reports and

Proposals.2. In Windows Explorer, double-click the spreadsheet whose title begins with

WS2008R2HardwareAssessment. When the User Namedialog box appears, click OK.

3. In Windows Explorer, double-click the document whose title begins with WS2008R2Proposal. Task 5: Analyze the detailed results

1. In Excel, on the Summarytab, how many computers do not meet requirements?2. On the ServerAssessmenttab, what were the names of the servers assessed?3. On the ServerInventorytab, do all servers meet the Windows Server readiness requirements?4. On the ServerAssessmenttab, what are the reasons given for nyc-svr1 not being Windows Server

2008 R2 capable?

5. What recommendations are made regarding these issues?6. Switch to Word and review the report.

Task 6: Suggest a course of actionNote:Your instructor may choose to perform this lab as a group discussion rather than an individualactivity.

Complete the Contoso Windows Server 2008 R2 Migration Proposal document.Contoso Windows Server 2008 R2 Migration Proposal

Document Reference Number:CW060510/2

Document Author

Date

Charlotte Weiss

6th May

Requirements Overview

Provide recommendations about any hardware or other changes required to support the migrationof all legacy servers to Windows Server 2008 R2.

Additional Information

The Microsoft Assessment and Planning Toolkit was used to perform readiness analysis. Summaryreports are available upon request.

Proposals

1. Does the NYC-SVR1.contoso.com computer meet the minimum hardwarerequirements for Windows Server 2008 R2?

2. Would you recommend any changes to the configuration of NYC-SVR1.contoso.com?

3. To which version of Windows Server 2008 R2 could this server be upgraded?

4. What roles are installed on the assessed computers? (Hint: examine the Worddocument produced by MAP on NYC-CL1 for further information.)


7/137


Results:After this exercise, you should have a completed Contoso Windows Server 2008 R2Migration Proposal document.

To prepare for the next labWhen you finish the lab, revert the virtual machines back to their initial state. To do this, complete the

following steps:

1. On the host computer, start Hyper-V Manager.2. Right-click 6418C-NYC-DC1 in the Virtual Machineslist, and then click Revert.3. In the Revert Virtual Machinedialog box, click Revert.4. Repeat these steps for 6418C-NYC-SVR1and 6418C-NYC-CL1.5. In the Virtual Machines pane, click 6418C-NYC-DC1, and then in the Actions pane, click Start.6. To connect to the virtual machine for the next lab, click 6418C-NYC-DC1, and then in the Actions

pane, click Connect.


8/137


Lab B: Installing Windows Server and ConfiguringPost-Installation Settings

Lab Setup



1. On the host computer, click Start, point to Administrative Tools, and then click Hyper-V Manager.2. In Hyper-V Manager, click 6418C-NYC-DC1, and in the Actions pane, click Start.3. In the Actions pane, click Connect. Wait until the virtual machine starts.4. Log on using the following credentials:

User name: Administrator Password: Pa$$w0rd Domain: Contoso

Lab Scenario

Following the publication of the Contoso, Ltd Windows Server 2008 R2 Migration Proposal document, you

have been tasked with performing the first of the server deployments. In this instance, it has been decided

that a local media-based installation should be performed. Once the installation is complete, you will

manually configure the servers post-installation settings as per the supplied documentation.

Supporting Documentation

E-Mail thread of correspondence with Ed Meadows:

Charlotte Weiss

From: Ed Meadows [[email protected]]

Sent: 1 May 2010 17:00

To: [email protected]


9/137


Subject: New Server Installation

Charlotte,

Please use the following information to install and configure the new server:

Language: EnglishTime and currency format: English (United States)

Keyboard or input method: US

Product: Windows Server 2008 R2 Enterprise (Server Core Installation)

Administrator password: Pa$$w0rd

Installation options

Server name: NYC-SVR-CORE

Domain name: Contoso.com

IP address: 10.10.10.30/16

Gateway: 10.10.10.1

DNS Server: 10.10.10.10

Post-installation configuration options:

Remote Desktop enabled for any version of Remote Desktop

Allow MMC Remote Management

Enable Windows PowerShell

Allow Server Manager Remote Management

Remote administration options:

DNS

DHCP

Roles and features

Regards,

Ed


10/137


Exercise 1: Installing Windows Server 2008 R2

Scenario

You have received an e-mail from your boss, Ed Meadows, with instructions on how to install a new

Windows Server 2008 R2 server in Contoso. Read the documentation and then install and configure the

new server as per the instructions in the e-mail.

The main tasks for this exercise are as follows:

1. Read server installation instructions.2. Mount the Windows Server product DVD.3. Install Windows Server 2008 R2 as per instructions in the e-mail.4. Set the administrator password.

Task 1: Read server installation instructions View the contents of the e-mail message in the lab scenario to determine the required information

for the planned installation.

Task 2: Mount the Windows Server product DVD1. On your host computer, switch to Hyper-V Manager.2. In the Virtual Machineslist, right-click 6418C-NYC-BLANKand then click Settings.3. In the navigation pane, under IDE Controller 1, click DVD Drive.4. In the results pane, under Media, click Image fileand in the Image filebox, type C:\Program

Files\Microsoft Learning\6418\Drives\

WServer2008R2_Eval.iso, and then click OK.

5. In the Virtual Machineslist, right-click 6418C-NYC-BLANKand then click Snapshot.6. In the Virtual Machineslist, right-click 6418C-NYC-BLANKand then click Start.7. In the Virtual Machineslist, right-click 6418C-NYC-BLANKand then click Connect.

Task 3: Install Windows Server 2008 R2 as per instructions inthe e-mail1. Switch to the NYC-BLANK virtual machine.2. Install the operating system using the instructions provided in the e-mail from Ed Meadows.

Note:Setup proceeds; setup copies files, expands files, installs features and updates, and completes

installation. This phase takes around twenty minutes. Your instructor might continue with otheractivities during this phase.

Task 4: Set the administrator password Set the administrator password to Pa$$w0rd.

Note:You are logged on and the Server Core command prompt opens.

Results:After this exercise, you should have installed a new Server Core server.


11/137


Exercise 2: Configuring Server Core

Scenario

You have installed the new server and must now configure it. Read the e-mail to determine the required

configuration settings for the new server.

The main tasks for this exercise are as follows:1. Review the post-installation configuration options instructions.2. Configure network settings.3. Change the computer name.4. Add the computer to the Contoso.com domain.

Note:It is assumed that you are logged onto Server Core and the command prompt is open. If youinadvertently close the command prompt, press CTRL+ALT+END and click Start Task Manager. Onthe Applicationstab, click New Task. In the Create New Taskdialog box, in the Openbox, typecmd.exeand press ENTER. Close Task Manager.

Task 1: Review the post-installation configuration options instructions Refer to the Post-installation configuration options section of the e-mail from Ed Meadows for

additional guidance about configuring the server.

Task 2: Configure network settings Using sconfig, configure the network connection with the appropriate IPv4 address, subnet mask,

default gateway, and DNS server address:

IP address: 10.10.10.30 Subnet mask: 255.255.0.0 Default gateway: 10.10.10.1 Primary DNS server: 10.10.10.10

Task 3: Change the computer name1. Change the computer name to the required name using sconfig.

Computer name: NYC-SVR-CORE2. Restart the server computer.3. Log on using the following credentials:

User name: Administrator Password: Pa$$w0rd

Task 4: Add the computer to the Contoso.com domain1. Add the computer to the Contoso.com domain using sconfig.2. Use the following credentials:

User name: Contoso\Administrator Password: Pa$$w0rd

3. Restart the server computer.4. Log on using the following credentials:


12/137



Results:After this exercise, you should have configured the post-installation settings as per thedocumentation.


13/137


14/137


Lab C: Managing Roles and Features

Lab Setup

The virtual machines should still be running from the previous lab.

Lab Scenario

You have successfully installed and configured a new Server Core server computer. You must now deploy

the required roles to the server.


E-Mail thread of correspondence with Ed Meadows:

Charlotte Weiss

From: Ed Meadows [[email protected]]

Sent: 1 May 2010 17:00

To: [email protected]

Subject: New Server Installation

Charlotte,

Please use the following information to install and configure the new server:

Language: English

Time and currency format: English (United States)

Keyboard or input method: US

Product: Windows Server 2008 R2 Enterprise (Server Core Installation)

Administrator password: Pa$$w0rd

Installation options

Post-installation configuration options:


15/137


Server name: NYC-SVR-CORE

Domain name: Contoso.com

IP address: 10.10.10.30/16

Gateway: 10.10.10.1

DNS Server: 10.10.10.10

Remote Desktop enabled for any version of Remote Desktop

Allow MMC Remote Management

Enable Windows PowerShell

Allow Server Manager Remote Management

Remote administration options:

DNS

DHCP

Roles and features

Regards,

Ed


16/137


Exercise 1: Adding the Domain Name System and Dynamic HostConfiguration Protocol Server Roles

Scenario

Following installation of the first server, you must now install the required roles and features according to

the e-mail sent to you from Ed Meadows.The main tasks for this exercise are as follows:

1. Review the roles and features section in the e-mail.2. Install the DNS role using DISM.3. Install the DHCP role using Ocsetup.

Task 1: Determine the roles and features to be installed Refer to the e-mail from Ed Meadows for additional guidance about configuring roles and features.

Task 2: Install the Domain Name System role using Deployment Image Servicing andManagement

1. Switch to the NYC-BLANK server.2. Use dism.exeto install the DNS-Server-Core-Rolecomponent.

Task 3: Install the Dynamic Host Configuration Protocol role using Ocsetup1. Use ocsetup.exeto install the DHCPServerCorerole.2. Authorize the server by running the following command:

netsh dhcp add server nyc-svr-core.contoso.com 10.10.10.30

Results:After this exercise, you should have deployed the DNS and DHCP server roles to the ServerCore computer.


17/137


Exercise 2: Managing Server Core

Scenario


1. Verify the installed roles are running.2. Start DHCP Server.

Task 1: Verify the installed roles are running1. Switch to the NYC-DC1 domain controller.

It is assumed that Server Manager is running and connected remotely to NYC-SVR-CORE. If this is notthe case, repeat the following steps:1. Click Start, point to Administrative Tools, and then click Server Manager. In Server Manager, in thenavigation pane, right-click Server Manager (NYC-DC1)and then click Connect to AnotherComputer.2. In the Connect to Another Computerdialog box, in the Another computerbox, type NYC-SVR-COREand then click OK.

2. Use Server Manager to determine which roles are installed on NYC-SVR-CORE.3. Which roles are installed?

Task 2: Start Dynamic Host Configuration Protocol Server1. In the navigation pane, click DHCP Server.2. Attempt to start the DHCP Server service. Hint: You may need to modify the Startup Type settings.

Results:After this exercise, you should have verified both roles are installed and started.

To prepare for the next moduleWhen you finish the lab, revert the virtual machines back to their initial state. To do this, complete the

following steps:

1. On the host computer, start Hyper-V Manager.2. Right-click 6418C-NYC-DC1 in the Virtual Machineslist, and then click Revert.3. In the Revert Virtual Machinedialog box, click Revert.4. Repeat these steps for 6418C-NYC-BLANK.5. In the Virtual Machines pane, click 6418C-NYC-DC1, and then in the Actions pane, click Start.6. To connect to the virtual machine for the next modules lab, click 6418C-NYC-DC1, and then in the

Actions pane, click Connect.

Important:Start the 6418C-NYC-DC1 virtual machine first, and ensure that it is fully started beforestarting the other virtual machines.

7. Wait for 6418C-NYC-DC1 to start, and then start 6418C-NYC-SVR2. Connect to the virtual machine.


18/137


19/137



Branch office 1

Branch Office 2


20/137


Head Office


21/137


Exercise 1: Planning Volume Activation

Scenario

Study the supporting documentation and then consider the following additional information.

Branch Office 1This branch will contain twenty computers running Windows 7 and Windows Server 2008 R2. There is a

connection to the Internet.

Branch Office 2

This branch contains 45 computers which will be running Windows 7 and Windows Server 2008 R2; there

will be six servers. There is currently no Internet connectivity as this branch deals with highly sensitive

corporate data.

Head Office

The head offices in New York have around 2,000 computers which will be running Windows 7 and

Windows Server 2008 R2. There is Internet connectivity from all parts of the corporate network except for

the five computers in the isolated network.

Isolated Network

The five computers in the isolated network will run Windows 7. There is no permanent connection to the

Internet.


1. Review the supporting documentation.2. Answer the questions and complete the Contoso Volume Activation Plan document.

Task 1: Review the supporting documentation Read the Contoso documentation.

Task 2: Answer the questions and complete the Contoso Volume Activation Plandocument

Complete the Contoso Volume Activation Plan document.Contoso Volume Activation Plan

Document Reference Number:CW120510/1

Document Author

Date

Charlotte Weiss

12th May


Provide recommendations about how to handle volume activation for various locations within theContoso network.


Proposals

1. How do you propose to handle activations in Branch Office 1?

2. How do you propose to handle activations in Branch Office 2?

3. How do you propose to handle activations in the head office?


22/137


Contoso Volume Activation Plan

4. Are there any special considerations for the isolated network?

Results:After this exercise, you should have completed the Contoso Volume Activation Plan

document.


23/137

Lab Instructions: Implementing Deployment Technologies 1

Module 2

Lab Instructions: Implementing Deployment Technologies

Contents:Exercise 1:Creating an Answer File 3

Exercise 2:Using the Answer File 7


24/137

2 Lab Instructions: Implementing Deployment Technologies

Lab: Deploying Windows Server 2008 with an AnswerFile

Lab Setup



1. On the host computer, click Start, point to Administrative Tools, and then click Hyper-V Manager.2. In Hyper-V Manager, click 6418C-NYC-DC1, and in the Actions pane, click Start.3. In the Actions pane, click Connect. Wait until the virtual machine starts.4. Log on using the following credentials:


5. Repeat these steps for 6418C-NYC-SVR2.Lab Scenario

Contoso, Ltd wants to deploy branch office servers to various regional centers. They do not have the

budget to send experienced IT staff to each site, so they want to automate the installation. Yourecommend using an answer file to assist the automation. Contoso accepts your recommendation, and

tasks you with creating the necessary answer file.


25/137


Exercise 1: Creating an Answer File

Scenario

To assist with the process of creating the necessary answer file, Ed Meadows has sent you a document

with the appropriate configuration information.

Branch Office Server Configuration

Document Reference Number:EM010610/1

Document Author

Date

Ed Meadows

1stJune


To automate the deployment of branch office servers.


Deployment method: automated high-touch retail media deployments.

Configuration information Operating System Version: Windows Server 2008 R2 Enterprise Full or Server Core: Server Core Installation location: C:\Windows Disk partition size: 20 GB File system: NTFS Domain: Contoso.com User account to use for domain join operation: Administrator Enable Windows Firewall Use Dynamic Host Configuration Protocol to obtain IPv4 configuration


1. Read the Branch Office Server Configuration document.2. Create an answer file.3. Add required settings to answer file.4. Configure answer file.5. Verify and save answer file.6. Copy the answer file to removable media.

Task 1: Read the Branch Office Server Configuration document Read the Branch Office Server Configuration document.

Task 2: Create an answer file1. Switch to the NYC-SVR2 server.2. Open Windows System Image Manager.3. Create a new answer file.4. When prompted, select the installation image located in E:\labfiles\Mod02\install.wim.5. When prompted, select the Windows Server 2008 R2SERVERENTERPRISECOREoperating system.6. When prompted to create a catalog, click Yes.

Note:This operation might take 10-20 minutes.


26/137


Task 3: Add required settings to answer fileNote:Accuracy is important. Detailed steps are provided here that mirror those in the Lab AnswerKey.

1. In Windows System Image Manager, under Windows Image, expand Components.2. Right-click amd64_Microsoft-Windows-International-Core-WinPE_6.1.7600.16385_neutral , and

then click Add Setting to Pass 1 windows PE.

3. Right-click amd64_Microsoft-Windows-Setup_6.1.7600.16385_neutral , and then click AddSetting to Pass 1 windows PE.

4. Expand amd64_Microsoft-Windows-Setup_6.1.7600.16385_neutral, right-clickDiskConfigurationand then click Add Setting to Pass 1 windows PE.

5. Expand DiskConfiguration, right-click Diskand then click Add Setting to Pass 1 windows PE.6. Expand Disk, expand CreatePartions, right-click CreationPartition, and then click Add Setting to

Pass 1.

7. Expand ModifyPartions, right-click ModifyPartitionand then click Add Setting to Pass 1.8.

Under amd64_Microsoft-Windows-Setup_6.1.7600.16385_neutral, right-click ImageInstalland thenclick Add Setting to Pass 1 windows PE.

9. Under amd64_Microsoft-Windows-Setup_6.1.7600.16385_neutral, right-click UserDataand then clickAdd Setting to Pass 1 windows PE.

10. Under Components, right-click amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral ,and then click Add Setting toPass 4 specialize.

11. Expand amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral , right-click OOBE, andthen click Add Setting toPass 7 oobeSystem.

12. Under Components, expand amd64_Microsoft-Windows-UnattendedJoin_6.1.7600.16385_neutral, expand Identification, right-click Credentialsand then

click Add Setting to Pass 4 specialize.

Task 4: Configure answer file settings1. In Windows System Image Manager, under Answer File, under 1 windows PE, click

amd64_Microsoft-Windows-Internationl-Core-WinPE_neutral.

2. In the results pane, under Microsoft-Windows-International-Core-WinPE Properties, under Settings,configure the following settings:

a. In the InputLocalebox, type 0409:00000409.b. In the SystemLocalebox, type en-US.c. In the UILanguagebox, type en-US.d. In the UserLocalebox, type en-US.

3. Under Answer File, expand amd64_Microsoft-Windows-International-Core-WinPE_neutralandthen click SetupUILanguage.

4. In the results pane, under SetupUILanguage Properties, under Settings, in the UILanguagebox, typeen-US.

5. Under Answer File, click amd64_Microsoft-Windows-Setup_neutral, and then in the result pane,under Microsoft-Windows-Setup Properties, under Settings, configure the following settings:

a. In the EnableFirewalllist, click true.b. In the EnableNetworklist, click true.


27/137


6. Under Answer File, expand amd64_Microsoft-Windows-Setup_neutral, and then clickDiskConfiguration.

7. In the results pane, under DiskConfiguration Properties, under Settings, in the WillShowUIlist, clickOnError.

8. Under Answer File, under DiskConfiguration, click Disk.9. In the results pane, under Disk Properties, under Settings, configure the following settings:

a. In the DiskIDbox, type 0.b. In the WillWipeDisklist, click true.

10. Under Answer File, under DiskConfiguration, expand Disk, expand CreatePartitionsand then clickCreatePartition.

11. In the results pane, under CreateConfiguration Properties, under Settings, configure the followingsettings:

a. In the Order box, type 1.b. In the Sizebox, type 20000.c. In the Typelist, click Primary.

Note:If your host machine does not have 20GB of free disk space, modify the Size value accordingly.

12. Under Answer File, under DiskConfiguration, under Disk, expand ModifyPartitionsand then clickModifyPartition.

13. In the results pane, under ModifyConfiguration Properties, under Settings, configure the followingsettings:

a. In the Active list, click true.b. In the Extendlist, click false.c. In theFormatlist, click NTFS.d. In the Labelbox, type System.e.

In the Letterlist, click C.f. In the Orderbox, type 1.

g. In the PartitionIDbox, type 1.14. Under Answer File, under amd64_Microsoft-Windows-Setup_neutral, expand ImageInstall, and then

click OSImage.

15. In the results pane, under OSImage Properties, under Settings, in the WillShowUIlist, click OnError.16. Under Answer File, under OSImage, right-click InstallFromand then click InsertNew MetaData.17. In the results pane, under MetaData Properties, under Settings, configure the following settings:

a. In the Keybox, type/IMAGE/Name.b. In the Valuebox, type Windows Server 2008 R2 SERVERENTERPRISECORE.

18. Under Answer File, expand OSImage, and then click InstallTo.19. In the results pane, under InstallTo Properties, under Settings, configure the following settings:

a. In the DiskIDbox, type 0.b. In the PartitionIDbox, type 1.

20. Under Answer File, click UserData.21. In the results pane, under UserData Properties, under Settings, configure the following settings:

a. In the AcceptEULAlist, click true.b. In the FullNamebox, type Registered User.


28/137


c. In the Organizationbox, type Contoso.22. Under Answer File, expand UserData, and then click ProductKey.23. In the results pane, under ProductKey Properties, under Settings, in the WillShowUIlist, click

OnError.

Note:You will see an option to type a product key but we do not have one. The installation willcontinue anyway.

24. Under Answer File, under Components, expand 4 specialize, and then click amd64_Microsoft-Windows-Shell-Setup_neutral.

25. In the results pane, under Microsoft-Windows-Shell-Setup Properties, under Settings, in theComputerNamebox, type BRANCH-SVR1.

26. Under Answer File, under 4 specialize, under amd64_Microsoft-Windows-UnattendedJoin_neutral,click Identification.

27. In the results pane, under Identification Properties, under Settings, configure the following settings: In the JoinDomainbox, type Contoso.com.

28. Under Answer File, click Credentials.29. In the results pane, under Credentials Properties, under Settings, configure the following settings:

a. In the Domainbox, type Contoso.com.b. In the Passwordbox, type Pa$$w0rd.c. In the Usernamebox, type Administrator.

30. Under Answer File, under 7 oobeSystem, under amd64_Microsoft-Windows-Shell-Setup_neutral clickOOBE.

31. In the results pane, under OBBE Properties, under Settings, configure the following settings:a. In the HideEULAPagelist, click true.b. In the ProtectYourPCbox, type 3.

Task 5: Verify and save answer file1. When you have completed the configuration process, in Windows System Image Manager, click

Tools, and then click Validate Answer File.

Note:Some settings have not been modified and will not be saved. This is normal.

2. When you have completed the verification process, in Windows System Image Manager, click File,and then click Save Answer File.

3. In the navigation pane, click Desktop.4. In the File namebox, type Autounattend.xmland then click Save.

Task 6: Copy the answer file to removable media1. Close Windows System Image Manager.2. Click Start, click Computer, and then double-click Floppy Disk Drive (A:).3. Drag Autounattend.xmlfrom the Desktop to the open Windows Explorer window.

Results:After this exercise, you should have created and distributed an answer file.


29/137


Exercise 2: Using the Answer File

Scenario

You have sent the answer file to the branch office. A user there will launch the setup process on their

recently delivered server computer.


1. Configure the virtual machine.2. Verify that setup starts.3. Verify that setup was successful.

Task 1: Configure the virtual machineNote:You are now going to move the answer file between the virtual machines. This requires thatyou change the settings for the virtual machines so that the virtual floppy diskette is accessible from

the second virtual machine.

1. On the host computer, in the 6418C-NYC-SVR2 on localhost Virtual Machine Connection window,on the Mediamenu, point to Diskette Driveand then click Eject floppy.vfd.

Note:You have now ejected the floppy disk from the first virtual machine.

2. Switch to Hyper-V Manager.3. In the Virtual Machineslist, right click 6418C-NYC-BLANKand then click Settings.4. In the Settings for 6418C-NYC-BLANKdialog box, click Diskette Drive.5. In the results pane, click Virtual floppy disk (.vfd) file:.6. In the Virtual floppy disk (.vfd) file:box, type C:\Program Files

\Microsoft Learning\6418\Drives\floppy.vfdand then click OK.

Note: You have now inserted the floppy disk into the second virtual machine.

7. In Hyper-V Manager, click 6418C-NYC-BLANK, and in the Actions pane, click Start.8. In the Actions pane, click Connect.

Task 2: Verify that setup starts Does setup start?

Note: Let the installation proceed.

Task 3: Verify that setup was successful1. Logon with the following credentials:

Username: Administrator Password: Pa$$w0rd Domain: Contoso


30/137


2. At the command prompt, type hostname.3. What is the computer name?4. At the command prompt, type ipconfig /all.5. What is the IP address?6. From where was this configuration obtained?

Results:After this exercise, you should have deployed a branch server with an answer file.


following steps:

1. On the host computer, start Hyper-V Manager.2. Right-click 6418C-NYC-DC1 in the Virtual Machineslist, and then click Revert.3. In the Revert Virtual Machinedialog box, click Revert.4. Repeat these steps for 6418C-NYC-BLANKand 6418C-NYC-SVR2.5. In the Virtual Machines pane, click 6418C-NYC-DC1, and then in the Actions pane, click Start.6. To connect to the virtual machine for the next modules lab, click 6418C-NYC-DC1, and then in the





31/137

Lab Instructions: Using Microsoft Windows Deployment Services 1

Module 3

Lab Instructions: Using Microsoft Windows DeploymentServices

Contents:Exercise :Installing and Configuring Windows Deployment Services 3Exercise 2:Creating Operating System Images withWindows Deployment Services 5

Exercise 3:Using an Unattended File with Windows Deployment Services 7Exercise 4:Configuring Custom Computer Naming 8Exercise 5:Deploying Images with Windows Deployment Services 9


32/137


33/137


Exercise 1: Installing and Configuring Windows Deployment Services

Scenario

To assist with the process of configuring Windows Deployment Services, Ed Meadows has sent you a

document with the appropriate configuration information.

Branch Office Deployment Guide

Document Reference Number:EM310710/1

Document Author

Date

Ed Meadows

31stJuly


To configure Microsoft Windows Deployment Services to aid in the deployment of branch office servers.


Deployment method: automated standard image deployments.

Configuration information NYC-SVR2 is to be used to host Windows Deployment Services. It currently supports the Dynamic

Host Configuration Protocol (DHCP) role.

Configure Multicast transmission to use Auto-Cast. Configure automatic naming to identify branch servers. Place branch servers in the Research organization unit (OU); admin approval required. Operating System Version: the Windows Server 2008 R2 Enterprise operating system. Full or Server Core: Server Core. Use answer file for configuration. To domain-join branch servers, use the following credentials:

Username: Administrator Password: Pa$$w0rd Domain: Contoso.com

Questions

1. Does the fact that the NYC-SVR2 server is running both Windows Deployment Services andDHCP raise any issues?

2. How many installation images are required?3. What issues does placement of branch servers in the Research OU raise?


1. Read the supporting documentation.2. Answer the questions in the Branch Office Deployment Guide document.3. Install the Windows Deployment Services role.4. Configure Windows Deployment Services.

Task 1: Read the supporting documentation Read the supporting documentation.

Task 2: Answer the questions in the Branch Office Deployment Guide document Answer the questions in the document.


34/137

4 Lab Instructions: Using Microsoft Windows Deployment Services

Task 3: Install the Windows Deployment Services role1. Switch to the NYC-SVR2 computer.2. Open Server Manager.3. Install the Windows Deployment Services server role with both role services.4. Close Server Manager.

Task 4: Configure Windows Deployment Services1. Open Windows Deployment Services from Administrative Tools.2. Right-click NYC-SVR2.Contoso.com, and then click Configure Server.3. Use the following information to complete configuration:

a. On the Remote Installation Folder Locationpage, accept the defaults.b. Accept the System Volume Warningmessage.c. On the DHCP Option 60page, enable both Do not listen on port 67and ConfigureDHCP

option 60 to PXEClient.

d. On the PXE Server Initial Settingspage, select the Respond to all (known and unknown)client computers option.

e. When prompted, choose to not add images to the server.

Results:After this exercise, you should have installed and configured the Windows DeploymentServices role.


35/137


Exercise 2: Creating Operating System Images with Windows DeploymentServices

Scenario

Windows Deployment Services is installed and configured. You must now create various operating system

images to aid the deployment process.


1. Add a Windows Preinstallation Environment (Windows PE) boot image.2. Use WSDUtil to add a boot image.3. Create a capture image.4. Add an install image.

Task 1: Add a Windows Preinstallation Environment (Windows PE) boot image1. If necessary, open Windows Deployment Services snap-in.2. Add a new boot image using the following information to complete the process:

a. On the Image Filepage, use the following file name: C:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim.

b. Accept the defaults on the Image Metadatapage.c. Accept the defaults on the Summarypage.d. On the Task Progresspage, click Finish.

3. Minimize Windows Deployment Services. Task 2: Use WDSUtil to add a boot image

1. Open a Command Prompt and type the following command and then press ENTER.wdsutil /progress /add-image /imagefile:"E:\labfiles\mod02\boot.wim" /imagetype:boot

/name:"Microsoft Windows Setup (x64)"

2. Close the command prompt.3. Switch to Windows Deployment Services and verify the presence of the new boot image.

Question: How many boot images are listed?

Task 3: Create a Capture Image1. If necessary, open Windows Deployment Services snap-in.2. Add a new capture image using the following information to complete the process:

Note: This can take around ten minutes.

a. Source boot image: Microsoft Windows Setup (x64).b. Location and filename: E:\labfiles\mod03\capture_image.WIM.c. On the Task Progresspage, select the Add image to the Windows Deployment Server now

check box, and then click Finish.

d. Accept the defaults on the Image Filepage.e. Image name: Contoso Capture (x64).f. Image description: Contoso Capture (x64).


36/137


Task 4: Add an install image1. If necessary, open Windows Deployment Services snap-in.2. Add a new Image Group with the image group name of Windows Server 2008 R2.3. Add a new install image to this group using the following information to complete the process:

Note: This can take around twenty minutes.

a. On the Image Filepage, use the following file name: E:\labfiles\mod02\install.wim.

b. On the Available Imagespage, clear all checkboxes except WindowsServer 2008 R2SERVERENTERPRISECORE,and then click Next.

c. Accept the defaultson the Summarypage.d. Click Finishon the Task Progresspage.

4. Minimize Windows Deployment Services.

Results:After this exercise, you should have installed the necessary operating system images to begindeployment of branch servers.


37/137


Exercise 3: Using an Unattended File with Windows Deployment Services

Scenario

You have been provided with an answer file by a colleague. You must check its validity and then configure

Windows Deployment Services and the appropriate installation image to use the answer file.


1. Configure Windows Deployment Services Unattended file.2. Enable Client Unattend.

Task 1: Configure Windows Deployment Services Unattended file1. Open the E:\labfiles\Mod03\WDSClientUnattend.xmlfile for editing.2. Locate each of the following parts of the file and verify the indicated text.

Administrator

Contoso.com

Pa$$w0rd

Windows Server 2008 R2 SERVERENTERPRISECORE

Windows Server 2008 R2

3. On the Filemenu, click Save.4. Close Notepad.5. Copy WDSClientUnattend.xmlto C:\RemoteInstall\WdsClientUnattend\.6. In Windows Deployment Services, open the properties of NYC-SVR2.Contoso.com.7. On the Clienttab, enable unattended installationand for x64 architecture installations, browse and

select the C:\RemoteInstall\WdsClientUnattend

\WDSClientUnattend.xmlfile.

Task 2: Enable Client Unattend1. In Windows Deployment Services, open the properties of NYC-SVR2.Contoso.com and on the Boot

tab, for x64 architecture installations, select the Microsoft Windows Setup (x64)image as the

default boot image.

2. In the console, locate the Windows Server 2008 R2image group and then view the properties of theWindows Server 2008 R2 SERVERENTERPRISECOREimage.

3. Select Allow image to install in unattended modeand specify the file to use asE:\LabFiles\Mod03\WDSClientUnattend.xml.

Results:After this exercise, you should have enabled unattended installation.


38/137


Exercise 4: Configuring Custom Computer Naming

Scenario

In order to automate computer naming, you must configure the custom naming properties for Windows

Deployment Services as per the document Ed Meadows sent you. This also involves configuring

delegation on the AD DS organizational unit that will contain the computer accounts. Admin approval is

required, so you must also configure that.


1. Configure Automatic Naming.2. Configure Admin Approval.3. Configure AD DS permissions.

Task 1: Configure Automatic Naming1. In Windows Deployment Services, view the properties of NYC-SVR2.Contoso.com.2. On the AD DStab, use the following information to configure automatic naming:

a. In the Format box, type BRANCH-SVR-%02#.b. Under Computer Account Location, select the Research OUin the Contoso.com domain.

Task 2: Configure Admin Approval1. In Windows Deployment Services, view the properties of NYC-SVR2.Contoso.com.2. On the PXE Responsetab, select Require administrator approval for unknown computers. Also

change the PXE Response Delayto 3seconds.

3. Open a command prompt and type the following command to create a message for installers to viewwhile awaiting admin approval:

WDSUTIL /Set-Server /AutoAddPolicy /Message:The Contoso administrator is authorizingthis request. Please wait.

4. Close the command prompt. Task 3: Configure Active Directory Domain Services (AD DS) permissions

1. Switch to the NYC-DC1 computer and open Active Directory Users and Computers.2. On the Research organizational unit, use the Delegate Control wizard to delegate the NYC-SVR2

computer account the ability to create computer objects in the OU. Use the following information to

help:

a. Create a custom task to delegate.b. On the Active Directory Object Typepage, click Only the following objects in the folder,

select the Computer objectscheck box, select the Create selected objectsinthis foldercheck

box.

c. On the Permissionspage, in the Permissionslist, select the Full Controlcheck box.

Results:After this exercise, you should have configured automatic naming for Windows DeploymentServices deployments.


39/137


Exercise 5: Deploying Images with Windows Deployment Services

Scenario

You have provided instructions for a branch supervisor to initiate the installation process on the branch

office server computer. The installation will now take place.


1. Configure Windows Deployment Services Server for Multicast transmission.2. Configure the client for Pre-Boot Execution Environment (PXE) Booting.

Task 1: Configure Windows Deployment Services Server for Multicast transmission1. Switch to the NYC-SVR2 computer.2. Create a new multicast transmission using the following information to complete the process:

a. Transmission name: Windows Sever 2008 R2 Branch Serversb. Image group: Windows Server 2008 R2c. Image: Windows Server 2008 R2 SERVERENTERPRISECOREd. Multicast type: Auto-Cast

Task 2: Configure the client for Pre-Boot Execution Environment (PXE) Booting1. On the host computer, switch to Hyper-V Manager.2. In the Virtual Machines list, right click 6418C-NYC-BLANK, and then click Settings.3. In the Settings for 6418C-NYC-BLANKdialog box, click BIOS.4. In the results pane, click Legacy Network adapter.5. Use the arrows to move Legacy Network adapterto the top of the list and then click OK.6. In Hyper-V Manager, click 6418C-NYC-BLANK, and in the Actions pane, click Start.7. In the Actions pane, click Connect.8. When the computer reboots, note the PXE DHCP notice. When prompted, press F12 for Network

Boot.

Question: Do you see the admin approval message?9. Switch to the NYC-SVR2 computer.10. In Windows Deployment Services, click Pending Devices.11. Right-click the pending requestand click Approve.12. In the Pending Devicedialog box, click OK.13. Switch to the NYC-BLANK computer.

Question: Which image is the default?

Question: Does setup start?

14. Switch to NYC-DC1.15. In Active Directory Users and Computers, in the Research folder, click Refresh.

Question: Can you see a new computer object?

Question:What is it called?

Note:You can let the installation proceed if you wish, but this is not required.

Results:After this exercise, you should have started the automated deployment process for a newbranch server.


40/137



following steps:

1. On the host computer, start Hyper-V Manager.2. Right-click 6418C-NYC-DC1 in the Virtual Machineslist, and then click Revert.3. In the Revert Virtual Machinedialog box, click Revert.4. Repeat these steps for 6418C-NYC-BLANKand 6418C-NYC-SVR2.5. In the Virtual Machines pane, click 6418C-NYC-DC1, and then in the Actions pane, click Start.6. To connect to the virtual machine for the next modules lab, click 6418C-NYC-DC1, and then in the





41/137

Lab Instructions: Implementing the Microsoft Deployment Toolkit 1

Module 4

Lab Instructions: Implementing the Microsoft DeploymentToolkit

Contents:Exercise :Configuring the Microsoft Deployment Toolkit (MDT 2010) 3Exercise 2:Creating and Customizing a Task Sequence 4Exercise 3:Configuring the Deployment Share 6Exercise 4:Performing a Lite-Touch Deployment 7


42/137

2 Lab Instructions: Implementing the Microsoft Deployment Toolkit

Lab: Implementing the Microsoft Deployment Toolkit

Lab Setup



1. On the host computer, click Start, point to Administrative Tools, and then click Hyper-V Manager.2. In Hyper-V Manager click 6418C-NYC-DC1, and in the Actions pane, click Start.3. In the Actions pane, click Connect. Wait until the virtual machine starts.4. Log on using the following credentials:

a. User name: Administratorb. Password: Pa$$w0rdc. Domain: Contoso

5. Repeat these steps for 6418C-NYC-SVR2.Lab Scenario

Having completed the branch server deployments at the regional branch offices, Ed Meadows wants you

to take a look at creating a lite-touch deployment environment to enable on-going server deployments

within the head office. You recommend using a combination of MDT 2010 and Windows Deployment

Services. Ed accepts your suggestion, and you are now tasked with creating and configuring the required

environment to support these ad-hoc deployments.


43/137


Exercise 1: Configuring the Microsoft Deployment Toolkit (MDT 2010)

Scenario

MDT 2010 is already installed on NYC-SVR2. This server also has DHCP installed and configured. You must

now configure MDT 2010.


1. Create a Deployment Share in Deployment Workbench.2. Mount the Windows Server product DVD.3. Add an operating system in Deployment Workbench.

Task 1: Create a Deployment Share in Deployment Workbench1. On NYC-SVR2, open the Deployment Workbench.2. Create a new Deployment Share using the following information to complete the process:

a. In the New Deployment Share Wizard, on the Pathpage, accept the defaults.b. On the Sharepage, accept the defaults.c. Deployment share description: Contoso Deployment Share.d. Clear the Ask if an image should be capturedcheck box.e. On the Allow Admin Passwordpage, accept the defaults.f. On the Allow Product Keypage, accept the defaults.

Task 2: Mount the Windows Server product DVD1. On your host computer, in the 6418C-NYC-SVR2 on localhost Virtual Machine Connection

dialog box, on the Mediamenu, point to DVD Driveand then click Insert Disk.

2. In the Opendialog box, in the File namebox, type C:\Program Files\Microsoft Learning\6418\Drives\ WServer2008R2_Eval.isoand then click Open.

3. In the 6418C-NYC-SVR2 virtual machine, close the AutoPlaydialog box. Task 3: Add an operating system in Deployment Workbench

1. In the Deployment Workbench console tree, expand Deployment Shares, expand ContosoDeployment Share (C:\DeploymentShare), and then click Operating Systems.

2. Use the following information to import an operating system:

Note: This operation can take around fifteen minutes.

a. On the OS Typepage, click Full set of source files.b. On the Sourcepage, type D:\.c. Destination directory name:Windows Server 2008 R2 x64.

Note: In the Details pane of Deployment Workbench, multiple Windows Server 2008 R2 operatingsystems are listed.

Results:After this exercise, you should have added an operating system to MDT 2010.


44/137


Exercise 2: Creating and Customizing a Task Sequence

Scenario

You must now create a task sequence in MDT 2010 to deploy the Windows Server 2008 R2 operating

system.


1. Create a task sequence in Deployment Workbench.2. Customize a task sequence in Deployment Workbench.

Task 1: Create a task sequence in Deployment Workbench1. In the Deployment Workbench console tree, right-click Task Sequencesand then click New Task

Sequence.

2. Use the following information to complete the process of adding a new task sequence:a. Task sequence ID: 1b. Task sequence name:Deploy WS08 F&P Serverc. On the Select Templatepage, select Standard Client Task Sequenced. Operating System: Windows Server 2008 R2 SERVERENTERPRISE in Windows Server 2008 R2

x64 install.wim

e. Select Do not specify a product key at this timef. On the OS Settingspage:

i. Full Name: Authorized Userii. Organization: Contosoiii. Internet Explorer Home Page: contoso.comiv. Administrator Password: Pa$$w0rd

Task 2: Customize a task sequence in Deployment Workbench1. In Deployment Workbench select the Task Sequencesfolder.2. View the properties of Deploy WS08 F&P Server.3. In the Deploy WS08 F&P Server Propertiesdialog box, click the Task Sequencetab.4. In the Task Sequencelist, click Apply Network Settings.5. Click the New Itembutton.

Note:The New Item button is a yellow star on the Properties pane.

6. In the Network Settingsdialog box, in the Namebox, type LAN Connection.7. Click Use the following IP address.8. Click the New IP Addressbutton in the Network Settings section.

Note:The New IP Address button is a yellow star.

a. IP address: 10.10.10.30b. Subnet mask: 255.255.0.0

9. In the Gateway Settings section, click the New Gateway Settingsbutton.


45/137


Note:The New Gateway Address button is a yellow star.

10. The TCP/IP Gateway Addressdialog box appears. Gateway: 10.10.10.1

11. Click the DNStab.12. Select Use the following DNS Servers.

Note: The New DNS Server button is a yellow star.

a. DNS server: 10.10.10.10b. Register this connection's address in DNS

13. In the Deploy WS08 F&P Server Propertiesdialog box, click OK.

Results:After this exercise, you should have created a task sequence.


46/137


Exercise 3: Configuring the Deployment Share

Scenario

Having created the task sequence successfully, you must now configure the deployment share. You will

modify the driver settings for Windows Preinstallation Environment (Windows PE) x64 and then update

the deployment share.

The main task for this exercise is to configure the Deployment Share in Deployment Workbench.

Task 1: Configure the Deployment Share in Deployment Workbench1. Right-click Contoso Deployment Share (C:\DeploymentShare)and then click Properties.2. Clear the x86check box and then click the Windows PE x64 Componentstab.3. Under Driver Injection select the following check boxes and then click OK:

Include all video drivers in the selection profile Include all system-class drivers in the selection profile

4. Right-click Contoso Deployment Share (C:\DeploymentShare), and then click UpdateDeployment Share.

5. In the Update Deployment Share Wizard, on the Optionspage, click Next.6. On the Summarypage, click Next.

Note: This operation can take around 25 minutes. Please move on to Exercise 4 while this operationcompletes.

Results:After this exercise, you should have configured the deployment share.


47/137


Exercise 4: Performing a Lite-Touch Deployment

Scenario

Rather than distribute the Windows PE image on DVD or memory stick, you have elected to use Windows

Deployment Services to initiate the Lite-Touch deployment. Once Windows Deployment Services is

installed, you must add the Lite-touch Windows PE image you created earlier to the Boot Images folder inWindows Deployment Services. Then you will test the lite-touch deployment by connecting a new server

to Windows Deployment Services by using Pre-Boot Execution Environment (PXE) network startup.


1. Install the Windows Deployment Services role.2. Configure the Windows Deployment Services role.3. Add a Windows PE boot image.4. Configure the client for PXE Booting.5. Perform a Lite-Touch Installation.6. Validate Lite-Touch Deployment (optional).

Task 1: Install the Windows Deployment Services role1. Switch to the NYC-SVR2 computer.2. Open Server Manager.3. Install the Windows Deployment Services server role with both role services.4. Close Server Manager.

Task 2: Configure the Windows Deployment Services role1. Open Windows Deployment Services from Administrative Tools.2. Right-click NYC-SVR2.Contoso.com, and then click Configure Server.3. Use the following information to complete configuration:

On the Remote Installation Folder Locationpage, accept the defaults.

Accept the System Volume Warningmessage.On the DHCP Option 60page, enable both Do not listen on port 67and ConfigureDHCP

option 60 to PXEClient.

On the PXE Server Initial Settingspage, select the Respond to all client computers (known

and unknown) option.

When prompted, choose to not add images to the server.

4. Switch back to the Update Deployment Share Wizard.

Note: You must wait until the update is completed before moving to step 5.

5. On the Completionpage, click Finish.6. In Windows Explorer, navigate to C:\DeploymentShare\boot.7. Verify that LiteTouchPE_x64.wimis present.8. Close Windows Explorer.9. Close Deployment Workbench.

Task 3: Add a Windows Preinstallation Environment (Windows PE) boot image1. If necessary, open Windows Deployment Services snap-in.2. Add a new boot image using the following information to complete the process:


48/137


a. On the Image Filepage, use the following file nameC:\DeploymentShare\boot\LiteTouchPE_x64.wim.

b. Accept the defaults on the Image Metadatapage.c. Accept the defaults on the Summarypage.d. Click Finishon the Task Progresspage.

3. Close Windows Deployment Services. Task 4: Configure the client for Pre-Boot Execution Environment (PXE) Booting

1. On the host computer, switch to Hyper-V Manager.2. In the Virtual Machineslist, right click 6418C-NYC-BLANK, and then click Settings.3. In the Settings for 6418C-NYC-BLANKdialog box, click BIOS.4. In the results pane, click Legacy Network adapter.5. Use the arrows to move Legacy Network adapter to the top of the listand then click OK.6. In Hyper-V Manager, click 6418C-NYC-BLANK, and in the Actions pane, click Start.7. In the Actions pane, click Connect.8. When the computer reboots, note the PXE DHCP notice. When prompted, press F12 for Network

Boot. (Note: You need to press F12 quickly.)

Task 5: Perform a Lite-Touch Installation1. When the boot process is complete, the Welcome Windows Deployment window appears.2. Click Run the Deployment Wizard to install a new Operating System, and then use the following

information to launch the lite-touch installation process:

a. User Name: administratorb. Password: Pa$$w0rdc. Domain: contosod. Deploy WS08 F&P Servere. Computer name: NYC-SVR3f. Join a domaing. Domain: contoso

3. On the Language and other preference page, accept the defaults.4. On the Set the Time Zonepage, accept the defaults.5. On the Specify the BitLockerconfigurationpage, accept the defaults.6. On the Ready to begin page, click Begin.

Note: This operation can take around 40 minutes or more to complete. It is optional to allow theinstallation to complete.

Task 6: Validate Lite-Touch Deployment (optional)1. When installation is complete, the computer restarts and you are automatically logged on; the Lite-

touch installation proceeds after logon.

2. In the Deployment Summary window, click Finish.Question: In Initial Configuration Tasks, what is the IPv4 address?

Question: What is the computer name?

3. Click Start, and then click Internet Explorer.


49/137


4. In Set Up Windows Internet Explorer 8, click Ask me later.5. In Internet Explorer, on the toolbar, click the Homebutton.6. Verify that the Internet Explorer home page is set to Contoso.com.

Results:After this exercise, you should have deployed Windows Server 2008 R2.


following steps:

1. On the host computer, start Hyper-V Manager.2. Right-click 6418C-NYC-DC1 in the Virtual Machineslist, and then click Revert.3. In the Revert Virtual Machinedialog box, click Revert.4. Repeat these steps for 6418C-NYC-BLANKand 6418C-NYC-SVR2.5. In the Virtual Machines pane, click 6418C-LON-DC1, and then in the Actions pane, click Start.6. To connect to the virtual machine for the next modules lab, click 6418C-LON-DC1, and then in the


Important:Start the 6418C-LON-DC1 virtual machine first, and ensure that it is fully started beforestarting the other virtual machines.

7. Wait for 6418C-LON-DC1 to start, and then start 6418C-LON-SVR1. Connect to the virtual machine.


50/137

Lab Instructions: Migrating Active Directory Directory Service 1

Module 5

Lab Instructions: Migrating Active Directory DirectoryService

Contents:Exercise :Preparing the Existing Forest for the New Domain Controller 4Exercise 2:Deploying a Windows Server 2008 R2 Domain Controller 5Exercise 3:Removing Legacy Domain Controllers 6Exercise 4:Enabling New Windows Server 2008 R2 Domain Features 7


51/137

2 Lab Instructions: Migrating Active Directory Directory Service

Lab: Migrating Active Directory Directory Service

Lab Setup



1. On the host computer, click Start, point to Administrative Tools, and then click Hyper-V Manager.2. In Hyper-V Manager, click 6418C-LON-DC1, and then in the Actions pane, click Start.3. In the Actions pane, click Connect. Wait until the virtual machine starts.4. Log on using the following credentials:

User name: Administrator Password: Pa$$w0rd Domain: Adatum

5. Repeat these steps for 6418C-LON-SVR1.Lab Objectives

After completing this lab, you will be able to:

Prepare the existing forest for the new domain controller. Deploy a Windows Server 2008 R2 operating system domain controller in the domain. Remove legacy domain controllers. Enable new Windows Server 2008 R2 domain features.Lab Scenario

Contoso, Ltd. has a partner organization, A. Datum Corporation. This forest is running Windows Server

2003 Active Directory directory service. Your task is to upgrade this forest to Active Directory Domain


52/137


Services (AD DS) with a Windows Server 2008 R2 functional level. The new domain must have the Active

Directory Recycle Bin activated to minimize risks and SYSVOL must replicate using DFS-R.


53/137


Exercise 1: Preparing the Existing Forest for the New Domain Controller

Scenario

The administrator must prepare adatum.com to contain a Windows Server 2008 R2 domain controller.

The main task for this exercise is as follows:

Run the ADPREP command to prepare the existing forest. Task: Run the ADPREP command to prepare the existing forest

1. On the host computer, mount the C:\Program Files\MicrosoftLearning\6418\Drives\WServer2008R2_Eval.isofile to the 6418C-LON-DC1virtual machine.

2. On LON-DC1, open a command prompt and browse to the Supportfolder on drive D and then runadprep32 /forestprepto prepare the forest.

3. On LON-DC1, run adprep32 /domainprep /gpprepto prepare the domain.

Results:After this exercise, you should have prepared the A. Datum forest for the addition of aWindows Server 2008 R2 domain controller.


54/137


55/137


Exercise 3: Removing Legacy Domain Controllers

Scenario

After promoting LON-SVR1, it is important to demote LON-DC1 to raise the forest and domain functional

levels to Windows Server 2008 R2.


1. Migrate settings to the new domain controller.2. Remove the legacy domain controller.3. Change the domain and forest functional levels to support required features.

Task 1: Migrate settings to the new domain controller1. On LON-SVR1, open a command prompt and run Ntdsutil.exe.2. Use Ntdsutil to move all FSMO roles to LON-SVR1.If there is an error, wait for five minutes, and then

retry.

Task 2: Remove the legacy domain controller On LON-DC1, run dcpromo.exeto remove Active Directory directory service from LON-DC1. UsePa$$w0rdas the Administrator password.

Task 3: Change the domain and forest functional levels to support required features1. On LON-SVR1, start Active Directory Domains and Trusts.2. Raise the domain functional level to Windows Server 2008 R2.3. Raise the forest functional level to Windows Server 2008 R2.

Results:After this exercise, you should have removed the legacy domain controller from adatum.com

and elevated the forest functional level to Windows Server 2008 R2.


56/137


Exercise 4: Enabling New Windows Server 2008 R2 Domain Features

Scenario

Now that the forest is ready, we will enable the Active Directory Recycle Bin feature to comply with the

organization requirements.


1. Enable AD DS replication with DFSRMIG.2. Enable Active Directory Recycle Bin.

Task 1: Enable Active Directory Domain Service (AD DS) replication with DFSRMIG1. On LON-SVR1, start an elevated command prompt.2. Run dfsrmig /getGlobalStateto check the current state.3. Run dfsrmig /setGlobalState 1to prepare for the migration.4. Run dfsrmig /getMigrationStateto confirm the migration has been prepared.5. Run dfsrmig /setGlobalState 2to start the migration.6. Run dfsrmig /setGlobalState 3to finish the migration.7. Run dfsrmig /getGlobalStateto check the current state.

Task 2: Enable Active Directory Recycle Bin1. On LON-SVR1, start an elevated Microsoft Windows PowerShell prompt.2. Run the Enable-ADOptionalFeature cmdlet to enable the Active Directory recycle bin:

Enable-ADOptionalFeature Identity CN=Recycle Bin Feature,CN=OptionalFeatures,CN=Directory Service,CN=Windows

NT,CN=Services,CN=Configuration,DC=adatum,DC=com Scope ForestOrConfigurationSet

Target adatum.com

Results:In this exercise, you enabled SYSVOL DFS Replication and the Active Directory Recycle Bin.

Lab ShutdownAfter you complete the lab, you must shut down the virtual machines.


following steps:

1. On the host computer, start Hyper-V Manager.2. Right-click the virtual machine name in the Virtual Machineslist, and then click Revert.3. In the Revert Virtual Machinedialog box, click Revert.4. In the Virtual Machines pane, click 6418C-NYC-DC1, and then in the Actions pane, click Start.5. To connect to the virtual machine for the next modules lab, click 6418C-NYC-DC1, and then in the


Important:Start the NYC-DC1 virtual machine first, and ensure that it is fully started before startingthe other virtual machines.

6. Wait for NYC-DC1 to start, and then start 6418C-NYC-SVR1. Connect to the virtual machine.


57/137

Lab Instructions: Migrating File, Print and Web Services 1

Module 6

Lab Instructions: Migrating File, Print and Web Services

Contents:Lab A:Migrating Windows Server 2003 File and Print Services

Exercise 1:Installing the Appropriate Tools to Enable Migration ofFile and Print Services 3

Exercise 2:Enabling Windows Server Migration Tools 4

Exercise 3:Migrating File Services 5Exercise 4:Verifying the Successful Migration of File and Print Services 6

Lab B:Migrating a Web Application to Windows Server 2008 R2 andInternet Information Services (IIS) 7

Exercise 1:Installing the Web Server (IIS) Role with the Required Components 8

Exercise 2:Installing the Microsoft Web Deployment Tool 9

Exercise 3:Migrating Web Services to Windows Server 2008 R2 10

Exercise 4:Verifying the Successful Migration 11


58/137

2 Lab Instructions: Migrating File, Print and Web Services

Lab A: Migrating Windows Server 2003 File and PrintServices

Lab Setup



1. On the host computer, click Start, point to Administrative Tools, and then click Hyper-V Manager.2. In Hyper-V Manager, click 6418C-NYC-DC1, and then in the Actions pane, click Start.3. In the Actions pane, click Connect. Wait until the virtual machine starts.4. Log on using the following credentials:


5. Repeat these steps for 6418C-NYC-SVR1and 6418C-NYC-SVR2.Lab Scenario

Contoso, Ltd. is finishing its upgrade to the Windows Server 2008 R2 operating system environment.

Now that the operating systems are installed, the services on the old legacy servers must be migrated to

the new servers. The most important services for Contoso are the File and Print Services, so they decide to

start the migration with those two.


59/137


Exercise 1: Installing the Appropriate Tools to Enable Migration of File andPrint ServicesIn this exercise, the students will:

1. Install file and print server roles on Windows Server 2008 R2.2. Configure the Distributed File System (DFS) infrastructure to support the content migration.

Task 1: Install File and Print Server roles on Windows Server 2008 R21. On NYC-SVR2, open Server Manager and install the File Servicesand Print and Document Services

server roles with the following options:

Print and Document Services: Print Server File Services: File Server, Distributed File System Choose to create a DFS namespace later.

Task 2: Configure Distributed File System (DFS) to support migration1. On NYC-SVR1, open a command prompt and use DFSUtil.exeto find which namespaces are hosted

on NYC-SVR1.2. Use DFSUtil.exeto find which kind of namespaces are hosted and which servers host those

namespaces.

3. Use DFSUtil.exeto create a backup of the DFS configuration on NYC-SVR1.

Note:It is recommended to add a second namespace server to a single-server namespace to keep itspermissions. If that is not possible, the permissions should be noted as above.

Note:A full backup of the server is recommended, as well as a System State backup of a domaincontroller for a namespace integrated in Active Directory DomainServices (AD DS).

Results:After this exercise, you should have installed the File Services and Print Services roles on NYC-SVR2. Also, you have prepared NYC-SVR1 for migration.


60/137


Exercise 2: Enabling Windows Server Migration ToolsIn this exercise, the students will:

1. Install the Windows Server Migration Tools.2. Create a deployment package.3. Register Windows Server Migration Tools.

Task 1: Install the Windows Server Migration Tools On NYC-SVR2, use Server Manager to install the Windows Server Migration Tools Feature.

Task 2: Create a deployment package for NYC-SVR11. On NYC-SVR2, use SmigDeploy.exeto create a deployment package for NYC-SVR1. Store the

package in a folder called C:\Migration.

2. Copy the Migration folder to C:\drive on NYC-SVR1. Task 3: Register Windows Server Migration Tools on NYC-SVR1

On NYC-SVR1, use SmigDeploy.exeto install the Windows Server Migration Tools. After the tool isinstalled, close all open windows.

Results:After this exercise, you should have installed the Windows Server Migration Tools feature on

NYC-SVR2 and registered them on NYC-SVR1.


61/137


Exercise 3: Migrating File ServicesIn this exercise, the students will:

1. Export local users and groups.2. Import local users and groups.3. Migrate data.4. Rename the printer.

Task 1: Export local users and groups from NYC-SVR1 On NYC-SVR1, start the Windows Server Migration Tools and use the Export-SmigServerSetting

cmdlet to export the local users and groups to C:\Migration\UsersGroups.

Task 2: Import local users and groups to NYC-SVR21. On NYC-SVR2, copy the folder C:\Migrationfrom NYC-SVR1to C:\.2. Use the Import-SmigServerSettingcmdlet to import the local users and groups from NYC-SVR1.

Task 3: Migrate data from NYC-SVR1 to NYC-SVR21. On NYC-SVR2, use the Receive-SmigServerData cmdlet to prepare the server for data reception.2. On NYC-SVR1, use the Send-SmigServerData cmdlet to export data in C:\Filesto NYC-SVR2.3. On NYC-SVR2, share the C:\Filesfolder with Administrator full control and Everyone Read permission.4. On NYC-SVR1, open the Distributed File System console and add NYC-SVR2.Contoso.comas a new

root target.

Task 4: Rename NYC-SVR2 to NYC-SVR11. Rename NYC-SVR1to NYC-OLDand shut it down.2. Rename NYC-SVR2, to NYC-SVR1and restart the computer. Log back on as Administratorwith the

password of Pa$$w0rd.

Results:In this exercise, you migrated the File Server and Printer Server role settings to NYC-SVR2,

NYC-SVR1 was renamed to retire it in the future, and NYC-SVR2 was renamed to take its place.


62/137


Exercise 4: Verifying the Successful Migration of File and Print Services

Scenario

In this exercise, the students will verify that file and print services have been migrated successfully.

Task 1: Verify that file and print services have been successfully migrated1. On NYC-SVR2 (now NYC-SVR1), go to start, click run, and then type cmd.exe.2. Run net userto get a list of all local users.3. Run net localgroupto get a list of all local groups.4. Open DFS Management and verify that the \\contoso.com\sharedfiles namespace exists.5. Remove the \\NYC-SVR2 namespace server.6. Go to Start, Control Panel, and then click Printers.7. Verify that Printer1 exists and is shared.

Results:In this exercise, you validated the services have migrated successfully to the new server.

To prepare for Lab BWhen you finish the lab, revert the virtual machines back to their initial state. To do this, complete thefollowing steps:

1. On the host computer, start Hyper-V Manager.2. Right-click the virtual machine name in the Virtual Machineslist, and then click Revert.3. In the Revert Virtual Machinedialog box, click Revert.4. In the virtual machines pane, click 6418C-NYC-DC1, and then in the actions pane, click Start.5. To connect to the virtual machine for the next lab, click 6418C-NYC-DC1, and then in the Actions

pane, click Connect.

Important:Start the NYC-DC1 virtual machine first, and ensure that it is fully started before starting

the other virtual machines.

6. Wait for 6418C-NYC-DC1 to start, and then start 6418C-NYC-SVR2and 6418C-NYC-SVR1. Connectto the virtual machines.


63/137


Lab B: Migrating a Web Application to WindowsServer 2008 R2 and Internet Information Services (IIS)7.0

Lab Setup





5. Repeat these steps for 6418C-NYC-SVR1and 6418C-NYC-SVR2.Lab Scenario

Contoso, Ltd. is finishing its upgrade to a Windows Server 2008 R2 operating system environment. Nowthat the operating systems are installed, the Intranet Web site must be migrated from the older Windows

Server 2003 operating system server. To accomplish this, the administrator will use the Microsoft Web

Deployment Tool.


64/137


Exercise 1: Installing the Web Server (IIS) Role with the RequiredComponents

Scenario

In this exercise, the students will install the Web server (IIS) role on Windows Server 2008 R2.

Task: Install the Web Server (IIS) role1. On NYC-SVR2, install the Web Server (IIS) role.2. Install the IIS 6 Management Compatibility role service (including all sub-role services).

Note: In this case, it is not necessary to install Microsoft .NET Framework 1.1, but it might be a

requirement in a real environment. Other IIS components may be necessary also, depending on the

application.

A full backup of the destination server is recommended before installing IIS.

Results:After this exercise, you should have installed the Web Server (IIS) role on NYC-SVR2.


65/137


Exercise 2: Installing the Microsoft Web Deployment ToolIn this exercise, the students will:

1. Install the Microsoft Web Deployment Tool on both servers.2. Install the Microsoft Web Deployment Tool on NYC-SVR1 with Remote Service.

Task 1: Install Microsoft Web Deployment Tool on NYC-SVR2 On NYC-SVR2, install WebDeploy_x64_en-USfrom E:\Labfiles\Mod06in normal mode.

Task 2: Install Microsoft Web Deployment Tool on NYC-SVR1 with Remote Service1. On NYC-SVR1, install WebDeploy_x86_en-USfrom \\NYC-SVR2

\E$\Labfiles\Mod06 and select the Custom installation.

2. Install the Remote Agent Service.3. Start the MSDEPSVC service.

Results:After this exercise, you should have installed the Microsoft Web Deployment Tool on NYC-SVR2 and NYC-SVR1, and have enabled Remote Services on NYC-SVR1.


66/137


Exercise 3: Migrating Web Services to Windows Server 2008 R2In this exercise, the students will:

1. Run the msdeploycommand to do a pull migration of the Intranet Web site.2. Modify the Intranet DNS record.

Task 1: Run the ms ploycommand to do a pull migration of the Intranet Web site1. On NYC-SVR2 use msdeployto perform a pull migration of the Intranet Web site on NYC-SVR1. Use

the following command:

msdeploy -verb:sync -source:metakey=lm/w3svc/1,computername=NYC-SVR1 -

dest:metakey=lm/w3svc/1

2. Shut down NYC-SVR1.

Note:You could add whatifat the end of the command to see what would happen if the commandwas executed.

Task 2: Modify the Intranet DNS record On NYC-DC1 modify the DNS record for Intranetto point to nyc-svr2.contoso.com.

Results:In this exercise, you migrated the Intranet Web site to NYC-SVR2. You also modified the

Domain Name System (DNS) record that points to intranet.contoso.com.


67/137


Exercise 4: Verifying the Successful Migration

Scenario

In this exercise, the students will verify that the Intranet Web site has been migrated successfully.

Task: Verify that the Internet Web site has been migrated successfully On NYC-DC1 use Internet Explorer to connect to http://intranet.contoso.com.

Results:In this exercise, you checked if the Web site has migrated successfully to the new server.


following steps:

1. On the host computer, start Hyper-V Manager.2. Right-click the virtual machine name in the Virtual Machineslist, and then click Revert.3.

In the Revert Virtual Machinedialog box, click Revert.

4. Repeat steps 2 and 3 for every virtual machine used in this Lab.


68/137

Lab Instructions : Deploying Branch Office and Remote Access Services 1

Module 7

Lab Instructions: Deploying Branch Office and RemoteAccess Services

Contents:Lab A:Deploying a Read-Only Domain Controller to a Branch Office

Exercise 1:Enabling the Forest to Support Read-OnlyDomain Controller Deployment 3

Exercise 2:Deploying an RODC Role on Server Core 4

Exercise 3:Creating the Branch Office Site 5

Exercise 4:Securing the RODC 6

Lab B:Implementing BranchCache

Exercise 1:Configuring BranchCache on a Server 8

Exercise 2:Configuring BranchCache Distributed Cache Mode 9

Exercise 3:Verifying BranchCache Functionality 10


69/137

2 Lab Instructions: Deploying Branch Office and Remote Access Services

Lab A: Deploying a Read-Only Domain Controller to aBranch Office

Lab Setup





5. Repeat these steps for 6418C-NYC-RODC1.Lab Scenario

Contoso, Ltd. is planning to create new branch offices to support its regional sales effort. Security is a

concern and the wide area network (WAN) links fail sporadically.

To support the users authentication at the branch offices, Contoso plans to deploy RODCs. Your task is to

deploy the RODC at the Bellevue branch office, and then perform post-deployment configuration.


70/137

Lab Instructions : Deploying Branch Office and Remote Access Services 3

Exercise 1: Enabling the Forest to Support Read-Only Domain ControllerDeployment

Scenario

Before being able to deploy the RODC in the Bellevue office, the administrator must prepare the domain.

The main task for this exercise is to prepare the schema and forest to support RODCs.

Task: Prepare the schema and forest to support read-only domain controllers (RODCs)1. On NYC-DC1, mount the C:\Program Files\Microsoft Learning\6418

\Drives\WServer2008R2_Eval. isofile.

2. On NYC-DC1, run the following command in an elevated privileges command prompt:D:\support\adprep\adprep /rodcprep

Documents

6418cd 6418c Enu Labmanual