70-410R2 Full Lab PDF
70-410R2 Full Lab PDF
L1-1
10. In the Windows Setup Wizard, on the Windows Server 2012 R2 page, verify the following settings,
and then click Next.
o
15. On the Where do you want to install Windows? page, verify that Drive 0 Unallocated Space has
enough space for the Windows Server 2012 R2 operating system, and then click Next.
Note: Depending on the speed of the equipment, the installation takes approximately 20
minutes. The virtual machine will restart several times during this process.
16. On the Settings page, in both the Password and Reenter password boxes, enter the password
Pa$$w0rd, and then click Finish.
4. In the Ethernet Properties dialog box, click Internet Protocol Version 4 (TCP/IPv4), and then click
Properties.
5. In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click Use the following IP
address, enter the following IP address information, and then click OK:
o
IP address: 172.16.0.101
Username: Administrator
Password: Pa$$w0rd
L1-3
Results: After completing this exercise, you should have deployed Windows Server 2012 R2 on LON-SVR3.
You also should have configured LON-SVR3, including name change, date and time, networking.
4. In the Date and Time dialog box, click Change time zone. Set the time zone to the same time zone
that your classroom uses, and then click OK.
5. In the Date and Time dialog box, click Change Date and Time, and verify that the date and time
match those in your location. To dismiss the dialog boxes, click OK two times.
6. In the Command Prompt window, type 15, and then press Enter to exit Server Configuration.
5. On the Network Adapter Settings page, type 1, and then press Enter. This sets the Network Adapter
Address.
6. To select static IP address configuration, type S, and then press Enter.
7. At the Enter static IP address: prompt, type 172.16.0.111, and then press Enter.
8. At the Enter subnet mask prompt, Type 255.255.0.0, and then press Enter.
9. At the Enter default gateway prompt, type 172.16.0.1, and then press Enter.
10. On the Network Adapter Settings page, type 2, and then press Enter.
This configures the DNS server address.
11. At the Enter new preferred DNS server prompt, type 172.16.0.10, and then press Enter.
12. In the Network Settings dialog box, click OK.
13. Press Enter to not configure an alternate DNS server address.
14. Type 4, and then press Enter to return to the main menu.
15. Type 15, and then press Enter to exit sconfig.cmd.
16. At the command prompt, type ping lon-dc1.adatum.com to verify connectivity to the domain
controller from LON-CORE.
10. Sign in to server LON-CORE with the Adatum\Administrator account and the password Pa$$w0rd.
Results: After completing this exercise, you should have configured a Windows Server 2012 R2 Server
Core deployment and verified the servers name.
L1-5
5. Use the arrow to add LON-CORE and LON-SVR3 to the server group. Click OK to close the Create
Server Group dialog box.
6. In the Server Manager console, click LAB-1. Press and hold the Ctrl key, and then select both
LON-CORE and LON-SVR3.
7. Scroll down, and under the Performance section, select both LON-CORE and LON-SVR3.
8. Right-click LON-CORE, and then click Start Performance Counters.
14. On the Select installation type page, click Role-based or feature-based installation. Click Next.
15. On the Select destination server page, verify that LON-SVR3.Adatum.com is selected, and then
click Next.
16. On the Server Roles page, click Next.
17. On the Select features page, click Windows Server Backup, and then click Next.
18. On the Confirm installation selections page, select the Restart the destination server
automatically if required check box, and then click Install.
3. Sign in to LON-DC1 with the Adatum\Administrator account and the password Pa$$w0rd.
4. In Server Manager, click LAB-1.
5. Right-click LON-CORE, and then click Computer Management.
6. In the Computer Management console, expand Services and Applications, and then click Services.
7. Right-click the World Wide Web Publishing service, and then click Properties. Verify that the
Startup type is set to Automatic.
8. In the World Wide Web Publishing Service dialog box, on the Log On tab, verify that the service is
configured to use the Local System account.
9. On the Recovery tab, configure the following settings, and then click the Restart Computer Options
button:
o
10. In the Restart Computer Options dialog box, in the Restart Computer After box, type 2, and then
click OK.
11. Click OK to close the World Wide Web Publishing Services Properties dialog box.
12. Close the Computer Management console.
Results: After completing this exercise, you should have created a server group, deployed roles and
features, and configured the properties of a service.
4. At the command prompt, type the following, and then press Enter:
Import-Module ServerManager
L1-7
5. To review the roles and features installed on LON-CORE, at the command prompt, type the following,
and then press Enter:
Get-WindowsFeature
6. To review the running services on LON-CORE, at the command prompt, type the following, and then
press Enter:
Get-service | where-object {$_.status -eq "Running"}
7. To view a list of processes on LON-CORE, at the command prompt, type the following, and then press
Enter:
Get-process
8. To review the IP addresses assigned to the server, at the command prompt, type the following, and
then press Enter:
Get-NetIPAddress | Format-table
9. To review the most recent 10 items in the security log, at the command prompt, type the following,
and then press Enter:
Get-EventLog Security -Newest 10
3. To deploy the XPS Viewer feature on LON-SVR3, type the following command, and then press Enter:
Install-WindowsFeature XPS-Viewer -ComputerName LON-SVR3
4. To verify that the XPS Viewer feature has now been deployed on LON-SVR3, type the following
command and then press Enter:
Get-WindowsFeature -ComputerName LON-SVR3
5. In the Server Manager console, from the Tools drop-down menu, click Windows PowerShell ISE.
6. In the Windows PowerShell ISE window, in the Untitled1.ps1 script pane, type the following, pressing
Enter after each line:
Import-Module ServerManager
Install-WindowsFeature WINS -ComputerName LON-SVR3
Install-WindowsFeature WINS -ComputerName LON-CORE
Results: After completing this exercise, you should have used Windows PowerShell to perform a remote
installation of features on multiple servers.
L2-9
2.
3.
In the Add Servers dialog box, in the Name (CN) box, type LON-SVR1, and then click Find Now.
4.
Under Name, click LON-SVR1, and then click the arrow to add the server to the Selected column.
5.
6.
In Server Manager, in the Servers pane, right-click LON-SVR1, and then select Add Roles and
Features.
7.
8.
On the Select installation type page, ensure that Role-based or feature-based installation is
selected, and then click Next.
9.
On the Select destination server page, ensure that Select a server from the server pool is
selected.
10. Under Server Pool, verify that LON-SVR1.Adatum.com is highlighted, and then click Next.
11. On the Select server roles page, select the Active Directory Domain Services check box, click Add
Features, and then click Next.
12. On the Select features page, click Next.
13. On the Active Directory Domain Services page, click Next.
14. On the Confirm installation selections page, select the Restart the destination server
automatically if required check box, and then click Install.
Installation will take several minutes.
15. When the installation completes, click Close to close the Add Roles and Features Wizard.
On LON-DC1, in Server Manager, on the command bar, click the Notifications iconit looks like a
flag.
2.
3.
In the Active Directory Domain Services Configuration Wizard, on the Deployment Configuration
page, ensure that Add a domain controller to an existing domain is selected, and then, beside the
Domain line, click Select.
4.
In the Windows Security dialog box, in the Username box type Administrator, in the Password
box type Pa$$w0rd and then click OK.
5.
In the Select a domain from the forest dialog box, click adatum.com, and then click OK.
6.
Beside the Supply the credentials to perform this operation line, click Change.
7.
In the Windows Security dialog box, in the Username box, type Adatum\Administrator, in the
Password box, type Pa$$w0rd, and then click OK.
8.
9.
On the Domain Controller Options page, ensure that Domain Name System (DNS) server is
selected, and then deselect Global Catalog (GC).
Note: You would usually also want to enable the global catalog, but for the purpose of this
lab, this is done in the next lab task.
10. In the Type the Directory Services Restore Mode (DSRM) password section, type Pa$$w0rd in
both text boxes, and then click Next.
11. On the DNS Options page, click Next.
12. On the Additional Options page, Click Next.
13. On the Paths page, accept the default folders, and then click Next.
14. On the Review Options page, click View Script, examine the Windows PowerShell script that the
wizard generates.
15. Close the Notepad window.
16. On the Review Options page, click Next.
17. On the Prerequisites Check page, read any warning messages, and then click Install.
18. When the task completes successfully, click Close.
19. Wait for LON-SVR1 to restart.
2.
In Server Manager, click Tools, and then click Active Directory Sites and Services.
3.
When Active Directory Sites and Services opens, expand Sites, expand Default-First-Site-Name,
expand Servers, and then expand LON-SVR1.
4.
In the left column, right-click NTDS Settings, and then click Properties.
5.
In the NTDS Settings Properties dialog box, select Global Catalog (GC), and then click OK.
6.
Results: After completing this exercise, you will have explored Server Manager and promoted a member
server to be a domain controller.
L2-11
1.
On LON-DC1, in the lower-left corner of the screen, click the Start button.
2.
On the Start screen, type CMD, right click Command Prompt and then click Run as administrator.
3.
At a command prompt, type the following, pressing Enter after each line:
Ntdsutil
Activate instance ntds
Ifm
Create sysvol full c:\ifm
4.
Wait for the IFM command to complete and then close the command prompt.
2.
3.
4.
5.
6.
7.
In the toolbar, click Manage, and then click Add Roles and Features.
8.
9.
On the Select installation type page, ensure that Role-based or feature-based installation is
selected, and then click Next.
10. On the Select destination server page, verify that LON-SVR2.Adatum.com is highlighted, and then
click Next.
11. On the Select server roles page, click Active Directory Domain Services.
12. In the Add Roles and Features Wizard, click Add Features, and then click Next.
13. On the Select Features page, click Next.
14. On the Active Directory Domain Services page, click Next.
15. On the Confirm installation selections page, click Restart the destination server automatically if
required. Click Yes at the message box.
16. Click Install.
17. After the installation completes, click Close.
Note: If you see a message stating that a delegation for the DNS server cannot be created,
click OK.
On LON-SVR2, At the command prompt, type the following command, and then press Enter:
Robocopy k: c:\ifm /copyall /s
2.
3.
4.
5.
On the Deployment Configuration page, ensure that Add a domain controller to an existing
domain is selected, and confirm that adatum.com is the target domain. Click Next.
6.
On the Domain Controller Options page, ensure that both Domain Name System (DNS) server
and Global Catalog (GC) are selected. For the DSRM password, type Pa$$w0rd in both boxes, and
then click Next.
7.
8.
On the Additional Options page, select Install from media, in the Install from media path box,
type C:\ifm, and then click verify.
9.
Results: After completing this exercise, you will have installed an additional domain controller for the
branch office by using IFM.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L3-13
Switch to LON-DC1.
2.
In Server Manager, click Tools, and then click Active Directory Users and Computers.
3.
4.
5.
In the New Object Organizational Unit dialog box, in Name, type Branch Office 1, and then
click OK.
6.
7.
In the New Object Group dialog box, in Group name, type Branch 1 Help Desk, and then
click OK.
8.
Repeat steps 6 and 7 using Branch 1 Administrators as the new group name.
9.
Repeat steps 6 and 7 using Branch 1 Users as the new group name.
20. When the computer has restarted, sign in as Adatum\Administrator with the password Pa$$w0rd.
21. Switch to LON-DC1.
22. If necessary, switch to Active Directory Users and Computers.
23. In the navigation pane, right-click Branch Office 1, click Delegate Control, and then click Next.
28. On the Completing the Delegation of Control Wizard page, click Finish.
29. In the navigation pane, right-click Branch Office 1, click Delegate Control, and then click Next.
30. On the Users or Groups page, click Add.
31. In the Select Users, Computers, or Groups dialog box, in Enter the object names to select
(examples), type Branch 1 Administrators, and then click OK.
32. On the Users or Groups page, click Next.
33. On the Tasks to Delegate page, click Create a custom task to delegate, and then click Next.
34. On the Active Directory Object Type page, select Only the following objects in the folder, select
the following check boxes, and then click Next:
o
Computer objects
35. On the Permissions page, select both General and Full Control, and then click Next.
36. On the Completing the Delegation of Control Wizard page, click Finish.
X Task 2: Delegate a user administrator for the Branch Office Help Desk
1.
On LON-DC1, in the navigation pane, right-click Branch Office 1, click Delegate Control, and then
click Next.
2.
3.
In the Select Users, Computers, or Groups dialog box, in Enter the object names to select
(examples), type Branch 1 Help Desk, and then click OK.
4.
5.
On the Tasks to Delegate page, in the Delegate the following common tasks list, select the
following check boxes, and then click Next:
6.
L3-15
1.
2.
In the details pane, right-click Holly Dickson, and then click Add to a group.
3.
In the Select Groups dialog box, in Enter the object names to select (examples), type Branch 1
Administrators, and then click OK.
4.
5.
In the details pane, right-click Branch 1 Administrators, and then click Add to a group.
6.
In the Select Groups dialog box, in Enter the object names to select (examples), type Server
Operators, and then click OK.
7.
8.
On your host computer, in the 20410C-LON-DC1 window, on the Action menu, click
Ctrl+Alt+Delete.
9.
12. In the User Account Control dialog box, in User name, type Holly. In Password, type Pa$$w0rd,
and then click Yes.
13. In Server Manager, click Tools, and then click Active Directory Users and Computers.
14. In Active Directory Users and Computers, expand Adatum.com.
15. In the navigation pane, click Sales.
16. In the details pane, right-click Aaren Ekelund, and then click Delete.
17. Click Yes to confirm.
18. Click OK to acknowledge that you do not have permissions to perform this task.
19. In the navigation pane, click Branch Office 1.
20. In the details pane, right-click Ed Meadows, and then click Delete.
21. Click Yes to confirm.
You are successful because you have the required permissions.
On LON-DC1, in the details pane, right-click Bart Duncan, and then click Add to a group.
2.
In the Select Groups dialog box, in Enter the object names to select (examples), type Branch 1
Help Desk, and then click OK.
3.
4.
5.
6.
On the desktop, click Server Manager. In the User Account Control dialog box, in User name, type
Adatum\Administrator.
7.
Note: To modify the Server Operators membership list, you must have permissions beyond
those available to the Branch 1 Administrators group.
8.
9.
You can sign in locally at a domain controller because Bart belongs indirectly to the Server Operators
domain local group.
18. On the desktop, click Server Manager.
19. In the User Account Control dialog box, in User name, type Bart. In Password, type Pa$$w0rd,
and then click Yes.
20. In Server Manager, click Tools.
21. Click Active Directory Users and Computers.
22. In Active Directory Users and Computers, expand Adatum.com.
23. In the navigation pane, click Branch Office 1.
24. In the details pane, right-click Connie Vrettos, and then click Delete.
25. Click Yes to confirm.
You are unsuccessful because Bart lacks the required permissions.
26. Click OK.
27. Right-click Connie Vrettos, and then click Reset Password.
28. In the Reset Password dialog box, in New password and Confirm password, type Pa$$w0rd, and
then click OK.
29. Click OK to confirm the successful password reset.
30. On your host computer, in the 20410C-LON-DC1 window, on the Action menu, click
Ctrl+Alt+Delete.
31. On LON-DC1, click Sign out.
32. Sign in to LON-DC1 as Adatum\Administrator with the password Pa$$w0rd.
Results: After completing this exercise, you will have successfully created an OU, and delegated
administration of it to the appropriate group.
L3-17
2.
3.
4.
5.
6.
In the branch1-userdata Properties dialog box, on the Sharing tab, click Advanced Sharing.
7.
8.
In the Permissions for branch1-userdata dialog box, for the Full Control permission select the
Allow check box, and then click OK.
9.
In the Advanced Sharing dialog box, click OK, and then in the branch1-userdata Properties dialog
box, click Close.
10. In Server Manager, click Tools, and then click Active Directory Users and Computers, and then
expand Adatum.com.
11. Right-click Branch Office1, point to New, and then click User.
12. In the New Object User dialog box, in Full name, type _Branch_template.
13. In User logon name, type _Branch_template, and then click Next.
14. In Password and Confirm password, type Pa$$w0rd.
15. Select the Account is disabled check box, and then click Next.
16. Click Finish.
On LON-DC1, from within the Branch Office 1 OU, right-click _Branch_template, and then click
Properties.
2.
In the _Branch_template Properties dialog box, on the Address tab, in City, type Slough.
3.
4.
In the Select Groups dialog box, in Enter the object names to select (examples), type Branch 1
Users, and then click OK.
5.
6.
7.
X Task 3: Create a new user for the branch office, based on the template
1.
2.
In the Copy Object User dialog box, in First name, type Ed.
3.
4.
5.
6.
Clear the User must change password at next logon check box.
7.
Clear the Account is disabled check box, and then click Next.
8.
Click Finish.
9.
10. In the Ed Meadows Properties dialog box, on the Address tab, notice that the City is already
configured.
11. Click the Profile tab.
Notice that the home folder location is already configured.
12. Click the Member Of tab.
Notice that Ed belongs to the Branch 1 Users group. Click OK.
13. On your host computer, in the 20410C-LON-DC1 window, on the Action menu, click
Ctrl+Alt+Delete.
14. On LON-DC1, click Sign out.
Switch to LON-CL1.
2.
On your host computer, in the 20410C-LON-CL1 window, on the menu, click Ctrl+Alt+Delete.
3.
4.
5.
On the Start screen, type File Explorer and then press Enter.
6.
7.
8.
9.
On your host computer, in the 20410C-LON-CL1 window, on the Action menu, click
Ctrl+Alt+Delete.
2.
3.
In the User Account Control dialog box, in User name, type Holly.
4.
5.
In Server Manager, click Tools, and then click Active Directory Users and Computers.
6.
7.
8.
In the details pane, right-click LON-CL1, and then click Reset Account.
9.
In the Active Directory Domain Services dialog box, click Yes, and then click OK.
L3-19
Switch to LON-CL1.
2.
A message appears stating that The trust relationship between this workstation and the primary
domain failed.
3.
Click OK.
On LON-CL1 click the back arrow and switch to Adatum\Administrator with the password
Pa$$w0rd.
2.
On the Start screen, right-click the display, click All apps, and in the Apps list, click Control Panel.
3.
In Control Panel, in the View by list, click Large icons, and then click System.
4.
5.
In System Properties, click the Computer Name tab, and then click Network ID.
6.
On the Select the option that describes your network page, click Next.
7.
8.
On the You will need the following information page, click Next.
9.
On the Type your user name, password, and domain name for your domain account page, in
Password, type Pa$$w0rd. Leave the other boxes completed, and then click Next.
10. In the User Account and Domain Information dialog box, click Yes.
11. On the Do you want to enable a domain user account on this computer? page, click Do not add
a domain user account, and then click Next.
12. Click Finish, and then click OK.
13. In the Microsoft Windows dialog box, click Restart Now.
14. Sign in as Adatum\Ed with the password Pa$$w0rd.
You are successful because the computer had been successfully rejoined.
Results: After completing this exercise, you will have successfully reset a trust relationship.
2.
In the Virtual Machines list, right-click 20410C-LON-CL1, and then click Revert.
3.
4.
L4-21
2.
At the Windows PowerShell prompt, type the following command, and then press Enter:
New-ADOrganizationalUnit LondonBranch
3.
4.
5.
6.
When prompted for the desired password, type Pa$$w0rd, and then press Enter.
7.
When prompted to repeat the password, type Pa$$w0rd, and then press Enter.
8.
At the Windows PowerShell prompt, type Enable-ADAccount Ty, and then press Enter.
9.
10. Verify that the sign-in is successful and then sign out of LON-CL1.
To create a new global security group for users in the London branch office, on LON-DC1, at the
Windows PowerShell prompt, type the following command, and then press Enter:
New-ADGroup LondonBranchUsers -Path "ou=LondonBranch,dc=adatum,dc=com" -GroupScope
Global -GroupCategory Security
2.
To add Ty as a member of LondonBranchUsers, type the following command, and then press Enter:
Add-ADGroupMember LondonBranchUsers -Members Ty
3.
To confirm that Ty has been added as a member of LondonBranchUsers, type the following
command, and then press Enter:
Get-ADGroupMember LondonBranchUsers
Results: After completing this exercise, you will have created user accounts and groups by using Windows
PowerShell.
2.
In File Explorer, expand drive E:, expand Labfiles, and then click Mod04.
3.
4.
In Windows PowerShell Integrated Scripting Environment (ISE), read the comments at the top of the
script, and then identify the requirements for the header in the .csv file.
5.
6.
7.
In the How do you want to open this type of file (.csv)? message, click Notepad.
8.
9.
2.
3.
4.
5.
6.
2.
At the Windows PowerShell prompt, type cd E:\Labfiles\Mod04, and then press Enter.
3.
4.
5.
6.
Results: After completing this exercise, you will have used Windows PowerShell to create user accounts in
bulk.
L4-23
2.
To create a query for user accounts in the LondonBranch OU, at the Windows PowerShell Prompt,
type the following command, and then press Enter:
Get-ADUser -Filter * -SearchBase "ou=LondonBranch,dc=adatum,dc=com" | Format-Wide
DistinguishedName
3.
Verify that only users from the LondonBranch organizational unit (OU) are listed.
4.
To modify the previous command to force all user to change their password the next time they sign
in, at the Windows PowerShell prompt, type the following command, and then press Enter:
Get-ADUser -Filter * -SearchBase "ou=LondonBranch,dc=adatum,dc=com" | Set-ADUser
-ChangePasswordAtLogon $true
5.
On LON-DC1, in Server Manager, click Tools, and then click Active Directory Administrative
Center.
2.
In Active Directory Administrative Center, in the navigation pane, expand Adatum (local) and
double-click LondonBranch.
3.
Click the Type column header to sort based on the object type.
4.
Select all user accounts, right-click the user accounts, and then click Properties.
5.
In the Multiple Users pane, under Organization, select the Address check box.
6.
7.
8.
In the Country/Region box, click United Kingdom, and then click OK.
9.
Results: After completing this exercise, you will have modified user accounts in bulk.
When you finish the lab, revert all virtual machines back to their initial state by performing the following
steps:
1.
2.
In the Virtual Machines list, right-click 20410C-LON-CL1, and then click Revert.
3.
4.
L5-25
How many bits are required to support 100 hosts on the client subnet?
Answer: Seven bits are required to support 100 hosts on the client subnet (27-2=126, 26-2=62).
2.
How many bits are required to support 10 hosts on the server subnet?
Answer: Four bits are required to support 10 hosts on the server subnet (24-2=14, 23-2=6).
3.
How many bits are required to support 40 hosts on the future expansion subnet?
Answer: Six bits are required to support 40 hosts on the future expansion subnet (26-2=62, 25-2=30).
4.
5.
Which feature allows a single network to be divided into subnets of varying sizes?
Answer: Variable length subnet masking allows you to define different subnet masks when
subnetting. Therefore, variable length subnet masking allows you to have subnets of varying sizes.
6.
How many host bits will you use for each subnet? Use the simplest allocation possible, which is one
large subnet and two equal-sized smaller subnets.
Answer: The client subnet is 7 host bits. This allocation can accommodate up to 126 hosts and uses
half of the allocated address pool.
The server and future expansion subnets are 6-host bits. This can accommodate up to 62 hosts on
each subnet and uses the other half of the address pool.
Given the number of host bits allocated, what is the subnet mask that you will use for the client
subnet? Calculate the subnet mask in binary and decimal.
x
The client subnet is using 7 bits for the host ID. Therefore, you can use 25 bits for the subnet
mask.
Binary
Decimal
11111111.11111111.11111111.10000000
255.255.255.128
2.
Given the number of host bits allocated, what is the subnet mask that you can use for the server
subnet? Calculate the subnet mask in binary and decimal.
x
3.
Binary
Decimal
11111111.11111111.11111111.11000000
255.255.255.192
Given the number of host bits allocated, what is the subnet mask that you can use for the future
expansion subnet? Calculate the subnet mask in binary and decimal.
x
4.
The server subnet is using 6 bits for the host ID. Therefore, you can use 26 bits for the subnet
mask.
The future expansion subnet is using 6 bits for the host ID. Therefore, you can use 26 bits for the
subnet mask.
Binary
Decimal
11111111.11111111.11111111.11000000
255.255.255.192
For the client subnet, define the network ID, first available host, last available host, and broadcast
address. Assume that the client subnet is the first subnet allocated from the available address pool.
Calculate the binary and decimal versions of each address.
In the following table, the bits in bold are part of the network ID.
5.
Description
Binary
Decimal
Network ID
11000000.10101000.1100010.00000000
192.168.98.0
First host
11000000.10101000.1100010.00000001
192.168.98.1
Last host
11000000.10101000.1100010.01111110
192.168.98.126
Broadcast
11000000.10101000.1100010.01111111
192.168.98.127
For the server subnet, define the network ID, first available host, last available host, and broadcast
address. Assume that the server subnet is the second subnet allocated from the available address
pool. Calculate the binary and decimal versions of each address.
In the following table, the bits in bold are part of the network ID.
Description
Binary
Decimal
Network ID
11000000.10101000.1100010.10000000
192.168.98.128
First host
11000000.10101000.1100010.10000001
192.168.98.129
Last host
11000000.10101000.1100010.10111110
192.168.98.190
Broadcast
11000000.10101000.1100010.10111111
192.168.98.191
6.
Description
Binary
Decimal
Network ID
11000000.10101000.1100010.11000000
192.168.98.192
First host
11000000.10101000.1100010.11000001
192.168.98.193
Last host
11000000.10101000.1100010.11111110
192.168.98.254
Broadcast
11000000.10101000.1100010.11111111
192.168.98.255
Results: After completing this exercise, you should have identified the subnets required to meet the
requirements of the lab scenario.
2.
At the Windows PowerShell prompt, type the following cmdlet, and then press Enter:
Test-NetConnection LON-DC1
3.
Verify that you receive a reply that contains PingSucceded:True from LON-DC1.
4.
5.
Note: This script creates the problem that you will troubleshoot and repair in the next task.
6.
L5-27
For the future allocation subnet, define the network ID, first available host, last available host, and
broadcast address. Assume that the future allocation subnet is the third subnet allocated from the
available address pool. Calculate the binary and decimal versions of each address.
In the following table, the bits in bold are part of the network ID.
On LON-SVR2, at the Windows PowerShell prompt, type the following, and then press Enter:
Test-NetConnection LON-DC1
2.
Verify that you receive a reply that contains PingSucceded:False from LON-DC1.
3.
At the Windows PowerShell Prompt, type the following, and then press Enter:
Test-NetConnection TraceRoute
LON-DC1
Notice that the host is unable to find the default gateway, and that the following warning message
appears: Name resolution of lon-dc1 failed Status: HostNotFound.
4.
At the Windows PowerShell Prompt, type the following, and then press Enter:
Get-NetRoute
Notice that the default route and the default gateway information is missing in the routing table.
Note: You should not be able to locate DestinationPrefix 0.0.0.0/0 and NextHop 10.10.0.1.
5.
At the Windows PowerShell Prompt, type the following, and then press Enter:
Test-NetConnection 10.10.0.1
6.
Notice that the default gateway is responding by verifying that you receive a reply that contains
PingSucceded:True from 10.10.0.1.
7.
At the Windows PowerShell Prompt, type the following, and then press Enter:
New-NetRoute InterfaceAlias Ethernet DestinationPrefix 0.0.0.0/0 NextHop
10.10.0.1
Note: The New-NetRoute cmdlet will create the default route and the default gateway
information that was missing.
8.
At the Windows PowerShell Prompt, type the following, and then press Enter:
Get-NetRoute
9.
Notice that the default route and the default gateway information is present in the routing table by
locating DestinationPrefix 0.0.0.0/0 and NextHop 10.10.0.1.
10. At the Windows PowerShell prompt, type the following, and then press Enter:
Test-NetConnection LON-DC1
11. Verify that you receive a reply that contains PingSucceded:True from LON-DC1.
Results: After completing this lab, you should have resolved an IPv4 connectivity problem.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L6-29
2.
3.
4.
5.
6.
On the Select server roles page, select the DHCP Server check box.
7.
In the Add Roles and Features Wizard, click Add Features, and then click Next.
8.
9.
11. On the Installation progress page, wait until the Installation succeeded on lon-svr1.adatum.com
message appears, and then click Close.
In the Server Manager Dashboard, click Tools, and then click DHCP.
2.
In the DHCP console, expand and then right-click lon-svr1.adatum.com, and then click Authorize.
3.
Notice that the icons next to IPv4 IPv6 changes color from red to green, which means that the DHCP
server has been authorized in Active Directory Domain Services (AD DS).
4.
In the DHCP console, in the navigation pane, click lon-svr1.adatum.com, expand and right-click
IPv4, and then click New Scope.
5.
6.
On the Scope Name page, in the Name box, type Branch Office, and then click Next.
7.
On the IP Address Range page, complete the page using the following information, and then click
Next:
8.
Length: 16
On the Add Exclusions and Delay page, complete the page using the following information:
x
9.
12. On the Router (Default Gateway) page, in the IP address box, type 172.16.0.1, click Add, and then
click Next.
13. On the Domain Name and DNS Servers page, click Next.
14. On the WINS Servers page, click Next.
15. On the Activate Scope page, click Next.
16. On the Completing the New Scope Wizard page, click Finish.
X Task 3: Configure the client to use DHCP, and then test the configuration
1.
2.
On the Start page, type Control Panel, and then press Enter.
3.
In Control Panel, under Network and Internet, click View Network Status and Tasks.
4.
In the Network and Sharing Center window, click Change adapter settings.
5.
In the Network Connections window, right-click Ethernet, and then click Properties.
6.
In the Ethernet Properties window, click Internet Protocol Version 4 (TCP/IPv4), and then click
Properties.
7.
In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, select the Obtain an IP
address automatically radio button, select the Obtain DNS server address automatically radio
button, click OK, and then click Close.
8.
9.
In the Command Prompt window, at the command prompt, type the following, and then press Enter:
ipconfig /renew
10. To test the configuration and verify that LON-CL1 has received an IP address from the DHCP scope, at
a command prompt, type the following, and then press Enter:
ipconfig /all
Note: This command returns information such as IP address, subnet mask, and DHCP
enabled status, which should be Yes.
In the Command Prompt window, at a command prompt, type the following, and then press Enter:
ipconfig /all
2.
3.
Switch to LON-SVR1.
4.
In the Server Manager dashboard, click Tools, and then click DHCP.
5.
In the DHCP console, expand lon-svr1.adatum.com, expand IPv4, expand Scope [172.16.0.0]
Branch Office, select and then right-click Reservations, and then click New Reservation.
6.
In the MAC address field, type the physical address you wrote down in step 2.
L6-31
7.
Switch to LON-CL1.
8.
In the Command Prompt window, at a command prompt, type the following, and then press Enter:
ipconfig /release
Results: After completing this exercise, you should have implemented DHCP, configured DHCP scope and
options, and configured a DHCP reservation.
If you are going to complete the optional lab, revert the 20410C-LON-CL1 and 20410C-LON-SVR1 virtual
machines by performing the following steps:
1.
2.
In the Virtual Machines list, right-click 20410C-LON-CL1, and then click Revert.
3.
4.
5.
Start 20410C-LON-SVR1.
2.
In Server Manager, click Tools, and then click Routing and Remote Access.
3.
Add the DHCP relay agent to the router by performing the following steps:
a.
In the navigation pane, expand LON-RTR (local), expand IPv4, right-click General, and then
click New Routing Protocol.
b.
In the Routing protocols list, click DHCP Relay Agent, and then click OK.
In the navigation pane, right-click DHCP Relay Agent, and then click New Interface.
2.
In the New Interface for DHCP Relay Agent dialog box, click Ethernet 2, and then click OK.
3.
In the DHCP Relay Agent Properties Ethernet 2 Properties dialog box, click OK.
4.
5.
In the DHCP Relay Agent Properties dialog box, in the Server address box, type 172.16.0.11, click
Add, and then click OK.
6.
2.
In the Desktop, right-click the PowerShell icon and select Run as administrator.
3.
At a Windows PowerShell command prompt, type the following, pressing Enter after each line:
Add-WindowsFeature
-IncludeManagementTools dhcp
LON-SVR1
172.16.0.11
4.
5.
On the Start screen, type Control Panel, and then press Enter.
6.
Under Network and Internet, click View network status and tasks.
7.
In the Network and Sharing Center window, click Change Adapter Settings, right-click Ethernet,
and then click Properties.
8.
In the Ethernet Properties window, click Internet Protocol Version 4 (TCP/IPv4) and then click
Properties.
9.
In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click Obtain an IP address
automatically, click Obtain DNS server address automatically, click OK, and then click Close.
L6-33
10. Right-click the Start button and then click Command Prompt.
11. In the Command Prompt window, at a command prompt, type the following, and then press Enter:
ipconfig /renew
12. Verify that IP address and DNS server settings on LON-CL2 are obtained from DHCP Server scope
Branch Office 2, installed on LON-SVR1.
Results: After completing this exercise, you should have implemented a DHCP relay agent.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L7-35
On LON-SVR1, in the Server Manager console, click Add roles and features.
2.
3.
4.
On the Select destination server page, ensure that LON-SVR1.Adatum.com is selected, and then
click Next.
5.
On the Select server roles page, select Active Directory Domain Services.
6.
When Add Roles and Features Wizard appears, click Add Features, and then click Next.
7.
8.
9.
10. On the Installation progress page, when the Installation succeeded message appears, click Close.
11. In the Server Manager console, on the navigation page, click AD DS.
12. On the title bar where Configuration required for Active Directory Domain Services at
LON-SVR1 is visible, click More.
13. On the All Server Task Details and Notifications page, click Promote this server to a domain
controller.
14. In the Active Directory Domain Services Configuration Wizard, on the Deployment Configuration
page, ensure that Add a domain controller to an existing domain is selected, and then click Next.
15. On the Domain Controller Options page, deselect the Domain Name System (DNS) server check
box, and leave the Global Catalog (GC) check box selected.
16. Type Pa$$w0rd in both text fields, and then click Next.
17. On the Additional Options page, click Next.
18. On the Paths page, click Next.
19. On the Review Options page, click Next.
20. On the Prerequisites Check page, click Install.
21. On the Youre about to be signed out blue bar, click Close.
On the LON-DC1 virtual machine, in the Server Manager console, click Tools, and then click DNS.
2.
Expand LON-DC1, right-click Forward Lookup Zones, and then select New Zone.
3.
In the New Zone Wizard, on the Welcome to the New Zone Wizard page, click Next.
4.
On the Zone Type page, deselect the Store the zone in Active Directory check box, and then click
Next.
5.
On the Zone Name page, type Contoso.com, and then click Next.
6.
7.
8.
9.
Expand Forward Lookup Zones, and then select and right-click contoso.com zone and click New
Host (A or AAAA)
10. In the New Host window, in the Name textbox type www.
11. In the IP address box type 172.16.0.100.
12. Click Add Host.
13. Click OK and then click Done.
14. Leave DNS Manager console open.
1.
On LON-DC1, in the DNS Manager console, click and then right-click LON-DC1, and then click
Properties.
2.
In the LON-DC1 Properties dialog box, click the Root hints tab. Ensure that root hints servers
display.
3.
Click the Forwarders tab. Ensure that the list displays no entries, and that the Use root hints if no
forwarders are available option is selected.
4.
Click Cancel.
5.
6.
7.
In Windows PowerShell, type the following cmdlets, pressing Enter after each, and observe the output
returned:
Get-DnsServerRootHint
Get-DnsServerForwarder
Note that both cmdlets are the respective Windows PowerShell equivalents of the DNS Console
actions performed in steps 2 and 3 above.
X Task 4: Add the DNS server role for the branch office on the domain controller
1.
On LON-SVR1, in the Server Manager console, click Add roles and features.
2.
3.
L7-37
4.
On the Select destination server page, ensure that LON-SVR1.Adatum.com is selected, and then
click Next.
5.
6.
When the Add Roles and Features Wizard appears, click Add Features, and then click Next.
7.
8.
9.
10. On the Installation progress page, when the Installation succeeded message appears, click Close.
2.
3.
In the DNS Manager console, expand LON-SVR1, and then expand Forward Lookup Zones.
This container is probably empty.
4.
Switch back to Server Manager, click Tools, and then click Active Directory Sites and Services.
5.
In the Active Directory Sites and Services console, expand Sites, expand Default-First-Site-Name,
expand Servers, expand LON-DC1, and then click NTDS Settings.
6.
In the right pane, right-click the LON-SVR1 replication connection, and select Replicate Now.
Note: If you receive an error message, proceed to the next step, and then retry this step
after 3-4 minutes. If this retry fails, wait a few more minutes, and then try again.
7.
In the navigation pane, expand LON-SVR1, and then click NTDS Settings.
8.
In the right pane, right-click the LON-DC1 replication connection, click Replicate Now, and then
click OK.
9.
Switch back to the DNS Manager console, right-click Forward Lookup Zones, and then click
Refresh.
10. Ensure that both the _msdcs.Adatum.com and Adatum.com containers display.
11. Close DNS Manager.
2.
In Windows PowerShell, type the following cmdlet, and then press Enter:
Get-DnsClient
3.
Note the entries labeled Ethernet in the InterfaceAlias column. In the Interface Index column, note
the Interface Index number that is in the same row as Ethernet and IPv4. Write this number here:
____________
4.
In Windows PowerShell, type the following cmdlet, where X is the specific Interface Index number you
wrote down in the last step, and then press Enter:
Set-DnsClientServerAddress InterfaceIndex X ServerAddress 0.0.0.0
5.
7.
At the nslookup > prompt, type the following and then press Enter:
www.contoso.com
You should see the following reply: *** Unknown cant find www.contoso.com. No response
from server.
8.
At the Windows PowerShell prompt, type the following cmdlet, and then press Enter:
Set-DnsServerForwarder IPAddress '172.16.0.10' PassThru
2.
At the Windows PowerShell prompt, type the following cmdlet, and then press Enter:
Restart-Computer
2.
3.
Ensure that you receive an IP address for this host as a non-authoritative answer.
4.
Results: After completing this exercise, you should have installed and configured DNS on 20410CLON-SVR1.
2.
On the Start screen, type Control Panel, and then press Enter.
3.
L7-39
4.
5.
6.
In the Ethernet Properties dialog box, click Internet Protocol Version 4 (TCP/Ipv4), and then click
Properties.
7.
In the preferred DNS server box, overwrite the IP address for preferred DNS server with
172.16.0.11, click OK, and then click Close.
X Task 2: Create several host records for web apps in the Adatum.com domain
1.
On LON-DC1, in the Server Manager console, click Tools, and then click DNS.
2.
In the DNS Manager console, expand LON-DC1, expand Forward Lookup Zones, and then click
Adatum.com.
3.
4.
Name: www
IP address: 172.16.0.200
5.
6.
7.
Name: ftp
IP address: 172.16.0.201
On LON-SVR1, in the Server Manager console, click Tools, and then click DNS.
2.
In the DNS Manager console, expand LON-SVR1, expand Forward Lookup Zones, and then click
Adatum.com.
3.
Ensure that both www and ftp resource records display. It might take several minutes for the records
to display.
Note: If the www and ftp resource records do not display within several minutes,
right-click Adatum.com, and then click Refresh.
X Task 4: Use the ping command to locate new records from LON-CL1
1.
On LON-CL1, on the taskbar, right-click the Windows icon, and then click Run.
2.
In the Run pop-up window, in the Open text box, type cmd, and then press Enter.
3.
In the Command Prompt window, at a command prompt, type ping www.adatum.com, and then
press Enter.
4.
6.
Ensure that name resolves to 172.16.0.201. (You will not receive replies.)
7.
Results: After completing this exercise, you should have configured DNS records.
2.
Ping does not work. Ensure that the name resolves to the IP address 172.16.0.100.
3.
2.
In the DNS Manager console, expand LON-DC1, expand Forward Lookup Zones, and then click
contoso.com.
3.
4.
5.
6.
In the Command Prompt window, at a command prompt, type the following, and then press Enter:
ping www.contoso.com
Note that ping does not work, and that the old IP address (which is 172.16.0.100) is still displayed.
1.
Switch to LON-SVR1.
2.
In the Server Manager console, click Tools, and then click DNS.
3.
Click LON-SVR1, click the View menu, and then click Advanced.
4.
Expand LON-SVR1, expand the Cached Lookups node, expand .(root), expand com, and then click
contoso.
5.
In the right pane, examine the cached content and note that the www record has the IP address:
172.16.0.100.
6.
Switch to LON-CL1.
7.
In the Command Prompt window, at a command prompt, type ipconfig /displaydns, and then press
Enter.
8.
Look for cached entries and notice that www.contoso.com is resolving to 172.16.0.100.
2.
At the Windows PowerShell prompt, type Clear-DNSServerCache, and then press Enter.
3.
4.
Switch to LON-CL1.
5.
In a Command Prompt window, at a command prompt, type ping www.contoso.com, and then
press Enter.
The result still returns the old IP address.
L7-41
6.
In the Command Prompt window, at a command prompt, type ipconfig /flushdns, and then press
Enter.
7.
In the Command Prompt window, type ping www.contoso.com, and then press Enter.
Ping now should work on address 172.16.0.10.
Results: After completing this exercise, you should have examined the DNS server cache.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L8-43
2.
At the Windows PowerShell prompt, type ping lon-dc1, and then press Enter.
Notice that there are four replies from 172.16.0.10.
3.
4.
2.
In the Properties window, next to the Ethernet section, click 172.16.0.10, IPv6 enabled.
3.
In the Network Connections window, right-click Ethernet, and then click Properties.
4.
In the Ethernet Properties dialog box, clear the Internet Protocol Version 6 (TCP/IPv6) check box,
and then click OK.
5.
6.
In Server Manager, verify that Ethernet lists only 172.16.0.10. You may need to refresh the view.
LON-DC1 is now an IPv4-only host.
2.
In the Local Server Properties dialog box, next to Ethernet, click 10.10.0.11, IPv6 enabled.
3.
In the Network Connections window, right-click Ethernet, and then click Properties.
4.
In the Ethernet Properties dialog box, clear the Internet Protocol Version 4 (TCP/IPv4) check box,
and then click OK.
5.
6.
In Server Manager, verify that Ethernet now lists only IPv6 enabled. You may need to refresh the
view.
LON-SVR2 is now an IPv6-only host.
2.
Configure a network address that will be used on the IPv6 network. At the Windows PowerShell
prompt, type the following cmdlet, and then press Enter:
New-NetRoute -InterfaceAlias " Ethernet 2" -DestinationPrefix 2001:db8:0:1::/64
-Publish Yes
3.
Allow clients to obtain the IPv6 network address automatically from LON-RTR. At the Windows
PowerShell prompt, type the following cmdlet, and then press Enter:
Set-NetIPInterface -InterfaceAlias "Ethernet 2" -AddressFamily IPv6 -Advertising
Enabled
4.
Notice that Ethernet 2 now has an IPv6 address on the 2001:db8:0:1::/64 network. This address is used
for communication on the IPv6-only network.
2.
At the Windows PowerShell prompt, type ipconfig, and then press Enter.
Notice that the Ethernet now has an IPv6 address on the 2001:db8:0:1::/64 network. The network
address was obtained from the router through stateless configuration.
Results: After completing the exercise, you will have configured an IPv6only network.
2.
In DNS Manager, expand LON-DC1, expand Forward Lookup Zones, and then click Adatum.com.
3.
4.
5.
In the IP address box, type 172.16.0.1, and then click Add Host. ISATAP clients resolve this host
name to find the ISATAP router.
6.
7.
8.
L8-45
On LON-RTR, configure the IP address of the Ethernet adapter as the ISATAP router. At the Windows
PowerShell prompt, type the following cmdlet, and then press Enter:
Set-NetIsatapConfiguration -Router 172.16.0.1
2.
3.
Record the InterfaceIndex of the ISATAP interface that has an IPv6 address that includes 172.16.0.1.
Interface index:
4.
5.
Verify that Forwarding is enabled for the interface and that Advertising is disabled.
6.
The ISATAP interface for an ISATAP router must have forwarding enabled and advertising enabled.
Type the following command, and then press Enter:
Set-NetIPInterface -InterfaceIndex IndexYouRecorded -Advertising Enabled
7.
Create a new IPv6 network that will be used for the ISATAP network. Type the following command,
and then press Enter:
New-NetRoute -InterfaceIndex IndexYouRecorded -DestinationPrefix 2001:db8:0:2::/64
-Publish Yes
8.
View the IP address configuration for the ISATAP interface. Type the following command, and then
press Enter:
Get-NetIPAddress -InterfaceIndex IndexYouRecorded
9.
On LON-DC1, at the Windows PowerShell prompt, type the following command, and then press
Enter.
dnscmd /config /globalqueryblocklist wpad
2.
At the Windows PowerShell prompt, type Restart-Service DNS -Verbose, and then press Enter.
3.
On LON-DC1, at the Windows PowerShell prompt, type the following command, and then press
Enter:
Set-NetIsatapConfiguration -State Enabled
2.
3.
Verify that the Tunnel adapter for ISATAP has an IPv6 address on the 2001:db8:0:2/64 network.
Notice that this address includes the IPv4 address of LON-DC1.
On LON-SVR2, at the Windows PowerShell prompt, type the following command, and then press
Enter:
ping 2001:db8:0:2:0:5efe:172.16.0.10
2.
3.
In the Local Server Properties dialog box, next to Ethernet, click IPv6 enabled.
4.
In the Network Connections window, right-click Ethernet, and then click Properties.
5.
In the Ethernet Properties dialog box, click Internet Protocol Version 6 (TCP/IPv6), and then click
Properties.
6.
In the Internet Protocol Version 6 (TCP/IPv6) Properties dialog box, click Use the following DNS
server addresses.
7.
In the Preferred DNS server box, type 2001:db8:0:2:0:5efe:172.16.0.10, and then click OK.
8.
9.
10. At the Windows PowerShell prompt, type ping LON-DC1, and then press Enter.
Notice that four replies are received from LON-DC1.
Note: A ping from LON-DC1 to LON-SVR2 does not respond because the firewall
configuration on LON-SVR2 blocks ping requests.
Results: After completing this exercise, you will have configured an ISATAP router on LON-RTR to allow
communication between an IPv6only network and an IPv4only network.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L9-47
Sign in to LON-SVR1 with the username Adatum\Administrator and the password Pa$$w0rd.
2.
In Server Manager, click the Tools menu, and then click Computer Management.
3.
In the Computer Management console, under the Storage node, click Disk Management.
4.
5.
6.
In the Initialize Disk dialog box, select the Disk 2 check box, click GPT (GUID Partition Table), and
then click OK.
In the Computer Management console, in Disk Management, right-click the black marked box right
of Disk 2, and then click New Simple Volume.
2.
In the New Simple Volume Wizard, on Welcome to the New Simple Volume Wizard page, click
Next.
3.
On the Specify Volume Size page, in the Simple volume size MB field, type 4000, and then click
Next.
4.
On Assign Drive Letter or Path page, ensure that the Assign the following drive letter check box
is selected, and that F is selected in from the drop-down menu, and then click Next.
5.
On the Format Partition page, from the File system drop-down menu, click NTFS, in the Volume
label text box, type Volume1, and then click Next.
6.
7.
In the Disk Management window, right-click the black box right of Disk 2, and then click New Simple
Volume.
8.
In the New Simple Volume Wizard, on Welcome to the New Simple Volume Wizard page, click
Next.
9.
On the Specify Volume Size page, in the Simple volume size in MB field, type 5000, and then click
Next.
10. On the Assign Drive Letter or Path page, ensure that the Assign the following drive letter check
box is selected, verify that G is listed as the drive letter, and then click Next.
11. On the Format Partition page, from the File system drop-down menu, click ReFS, in the Volume
label text box, type Volume2, and then click Next.
12. On the Completing the New Simple Volume Wizard page, click Finish.
On the taskbar, open a File Explorer window, expand This PC, and then click Volume1 (F:).
2.
In File Explorer, click Volume2 (G:), right-click Volume2 (G:), point to New, and then click Folder.
3.
In the New folder field, type Folder1, and then press Enter.
Results: After you complete this lab, you should have initialized a new disk, created two simple volumes,
and then formatted them. You should also have verified that the drive letters you assigned are available in
File Explorer.
2.
3.
In the Shrink F: window, in the Enter the amount of space to shrink in MB field, type 1000, and
then click Shrink.
On LON-SVR1, in Disk Management, in the middle-pane, right-click Volume2 (G:), and then click
Extend Volume.
2.
In Extend Volume Wizard, on the Welcome to the Extended Volume Wizard page, click Next.
3.
On the Select Disks page, in the Select the amount of space in MB field, type 1000, and then click
Next.
4.
5.
In a File Explorer window, click Volume2 (G:), and verify that Folder1 is available on the volume.
Results: After this lab, you should have made one volume smaller, and extended another.
2.
In Server Manager, in the left pane, click File and Storage Services, and then in the Servers pane,
click Storage Pools.
3.
In the STORAGE POOLS pane, click TASKS, and then in the TASKS drop-down menu, click New
Storage Pool.
4.
In the New Storage Pool Wizard window, on the Before you begin page, click Next.
5.
On the Specify a storage pool name and subsystem page, in the Name box, type StoragePool1,
and then click Next.
6.
L9-49
On the Select physical disks for the storage pool page, click the following physical disks, and then
click Next:
o
PhysicalDisk3
PhysicalDisk4
PhysicalDisk5
PhysicalDisk6
PhysicalDisk7
7.
8.
On the View results page, wait until the task completes, and then click Close.
2.
In the VIRTUAL DISKS pane, click TASKS, and then from the TASKS drop-down menu, click New
Virtual Disk.
3.
In the New Virtual Disk Wizard window, on the Before you begin page, click Next.
4.
On the Select the storage pool page, click StoragePool1, and then click Next.
5.
On the Specify the virtual disk name page, in the Name box, type Mirrored Disk, and then click
Next.
6.
On the Select the storage layout page, in the Layout list, click Mirror, and then click Next.
7.
On the Configure the resiliency settings page, click Three-way mirror, and then click Next.
8.
On the Specify the provisioning type page, click Thin, and then click Next.
9.
On the Specify the size of the virtual disk page, in the Specify Size box, type 10, and then click
Next.
14. On the Select the server and disk page, in the Disk pane, click the Mirrored Disk virtual disk, and
then click Next.
15. On the Specify the size of the volume page, click Next to confirm the default selection.
16. On the Assign to a drive letter or folder page, in the Drive letter drop-down menu, ensure that H
is selected, and then click Next.
17. On the Select file system settings page, in the File system drop-down menu, click ReFS, in the
Volume label box, type Mirrored Volume, and then click Next.
18. On the Confirm selections page, click Create.
19. On the Completion page, wait until the creation completes, and then click Close.
X Task 3: Copy a file to the volume, and verify that it is visible in File Explorer
1.
Click to the Start screen, type command prompt, and then press Enter.
2.
In the Command Prompt window, at the command prompt, type the following command, and then
press Enter:
Copy C:\windows\system32\write.exe H:\
3.
4.
5.
6.
7.
2.
In Settings for 20410C-LON-SVR1, in the Hardware pane, click Hard Drive that begins with
20410C-LON-SVR1-Disk5.
3.
In the Hard Drive pane, click Remove, and then click OK. Click Continue.
Switch to LON-SVR1.
2.
3.
4.
5.
6.
In Server Manager, in the STORAGE POOLS pane, on the menu bar, click the Refresh Storage
Pools button.
Notice the warning that displays next to Mirrored Disk.
7.
In the VIRTUAL DISK pane, right-click Mirrored Disk, and then click Properties.
8.
In the Mirrored Disk Properties dialog box, in the left pane, click Health.
Notice that the Health Status indicates a Warning. The Operational Status should indicate Incomplete,
Unknown or Degraded.
9.
X Task 6: Add a new disk to the storage pool and remove a broken disk
1.
Switch to LON-SVR1.
2.
In Server Manager, in the STORAGE POOLS pane, on the menu bar, click the Refresh Storage
Pools button.
3.
In the STORAGE POOLS pane, right-click StoragePool1, and then click Add Physical Disk.
4.
In the Add Physical Disk window, click PhysicalDisk8 (LON-SVR1), and then click OK.
5.
L9-51
6.
7.
Note the FriendlyName for the disk that shows an OperationalStatus of Lost Communication.
8.
Type $Disk = Get-PhysicalDisk FriendlyName diskname and press ENTER. Replace diskname with
the name of the disk you noted in Step 7.
9.
11. If you get a warning that the disk cannot be removed, wait five minutes and then run the last
command again. It can take some time for the mirrored disk to be resynchronized after a disk has
been removed and another disk added. If you still cannot remove the disk after five minutes, restart
LON-SVR1, sign in as Adatum\Administrator using the password Pa$$w0rd, and repeat steps 5-10.
12. In Server Manager, in the STORAGE POOLS pane, on the menu bar, click the Refresh Storage
Pools button to see the warnings disappear.
Results: After completing this lab, you should have created a storage pool and added five disks to it. Then
you should have created a three-way mirrored, thinly provisioned virtual disk from the storage pool. You
should have also copied a file to the new volume and verified that it is accessible. Next, after removing a
physical drive, you should have verified that the virtual disk was still available and could be accessed.
Finally, you should have added another physical disk to the storage pool.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L10-53
2.
In File Explorer, in the navigation pane, expand This PC, and then click Allfiles (E:).
3.
On the menu toolbar, click Home, click New folder, type Data, and then press Enter.
4.
5.
On the menu toolbar, click Home, click New folder, type Development, and then press Enter.
6.
Marketing
Research
Sales
In File Explorer, navigate to drive E, right-click the Data folder, and then click Properties.
2.
In the Data Properties dialog box, click Security, and then click Advanced.
3.
In the Advanced Security Settings for Data dialog box, click Disable Inheritance.
4.
In the Block Inheritance dialog box, click Convert inherited permissions into explicit permissions
on this object.
5.
Click OK to close the Advanced Security Settings for Data dialog box.
6.
7.
8.
9.
In the Development Properties dialog box, click Security, and then click Advanced.
10. In the Advanced Security Settings for Development dialog box, click Disable Inheritance.
11. In the Block Inheritance dialog box, click Convert inherited permissions into explicit permissions
on this object.
12. Remove the two permissions entries for Users (LON-SVR1\Users), and then click OK.
13. On the Security tab, click Edit.
14. In the Permissions for Development dialog box, click Add.
15. Type Development, click Check names, and then click OK.
16. In the Permissions for Development dialog box, under Allow, select Modify permission.
17. Click OK to close the Permissions for Development dialog box.
18. Click OK to close the Development Properties dialog box.
19. Repeat steps 8 through 18 for the Marketing, Research, and Sales folders, assigning Modify
permissions to the Marketing, Research, and Sales groups for their respective folders.
In File Explorer, navigate to drive E, right-click the Data folder, and then click Properties.
2.
In the Data Properties dialog box, click the Sharing tab, and then click Advanced Sharing.
3.
In the Advanced Sharing dialog box, select Share this folder, and then click Permissions.
4.
5.
Type Authenticated Users, click Check names, and then click OK.
6.
In the Permissions for Data dialog box, click Authenticated Users, and then under Allow, select
Change permission.
7.
8.
9.
3.
4.
In File Explorer, in the address bar, type \\LON-SVR1\Data, and then press Enter.
5.
Note: Bernard can still see the other folders, even though he does not have access to their
contents.
7.
Switch to LON-SVR1.
2.
3.
In Server Manager, in the navigation pane, click File and Storage Services.
4.
In the File and Storage Services window, in the navigation pane, click Shares.
5.
6.
In the Data Properties dialog box, click Settings, and then select Enable access-based
enumeration.
7.
8.
L10-55
2.
3.
4.
In File Explorer, in the address bar, type \\LON-SVR1\Data, and then press Enter.
Note: Bernard can now view only the Development folder, the folder for which he has been
assigned permissions.
5.
Switch to LON-SVR1.
2.
3.
In File Explorer, navigate to drive E, right-click the Data folder, and then click Properties.
4.
In the Data Properties dialog box, click the Sharing tab, click Advanced Sharing, and then click
Caching.
5.
In the Offline Settings dialog box, click No files or programs from the shared folder are
available offline, and then click OK.
6.
7.
Results: After completing this exercise, you will have created a new shared folder for use by multiple
departments.
On LON-SVR1.
2.
3.
Navigate to drive E, right-click Allfiles (E:), and then click Configure Shadow Copies.
4.
In the Shadow Copies dialog box, click drive E, and then click Enable.
5.
6.
7.
8.
In drive E:\ dialog box, change Schedule Task to Daily, change Start time to 12:00 AM and then click
Advanced.
9.
In the Advanced Schedule Options dialog box, select Repeat task, and then set the frequency to
every 1 hours.
10. Select Time, and change the time value to 11:59 PM.
11. Click OK twice.
12. Click OK to close the Settings dialog box.
13. Leave the drive Shadow Copies dialog box open.
2.
Navigate to E:\Data\Development.
3.
On the menu toolbar, click Home, click New item, and then click Text Document.
4.
5.
Switch back to the Shadow Copies dialog box; it should still be opened on the Shadow Copies tab.
6.
2.
3.
In File Explorer, right-click the Development folder, and then click Properties.
4.
In the Development Properties dialog box, click the Previous Versions tab.
5.
Click the most recent folder version for Development, and then click Open.
6.
Confirm that Report.txt is in the folder, right-click Report.txt, and then click Copy.
7.
8.
In the other File Explorer window, right-click the Development folder, and then click Paste.
9.
Results: After completing this exercise, you will have enabled shadow copies on the file server.
2.
At the command prompt type the following command and press Enter:
Add-WindowsFeature FS-SyncShareService
Note that the name of the feature is case-sensitive.
L10-57
On LON-SVR1, in the Windows PowerShell command window type the following command and press
Enter:
New-SyncShare Corp path C:\CorpData User Adatum\Domain Users
2.
If required, on the taskbar, click the Server Manager icon to open Server Manager.
3.
4.
Click Work Folders and ensure the Corp sync share exists.
On LON-DC1, in Server Manager, click Tools and click Group Policy Management.
2.
3.
Right-click Adatum.com and click Create a GPO in this domain, and Link it here.
4.
In the New GPO dialog box, in Name, type Work Folders, and then click OK.
5.
6.
7.
8.
9.
2.
3.
4.
5.
6.
7.
8.
9.
10. In the Work Folders folder, right-click an empty space, point to New, and then click Text Document.
11. Name the new text document TestFile2, and then press Enter.
12. Switch to LON-SVR1 and click File Explorer.
13. Navigate to C:\CorpData\Administrator. Ensure the new text file named TestFile2 exists.
14. Close all open Windows.
Results: After completing this exercise, you will have installed the Work Folders role service, created a
sync share, and created a Group Policy Object to deliver the settings to the users automatically. You will
have also tested the settings.
2.
3.
4.
5.
On the Select destination server page, click the server on which you want to install the Print and
Document Services, and then click Next.
The default server is the local server.
6.
On the Select Server Roles page, select Print and Document Services.
7.
8.
9.
10. On the Print and Document Services page, review the Notes for the administrator, and then click
Next.
11. On the Select Role Services page, click Next until the Confirm Installation Selections page
displays.
12. Click Install to install the required role services.
13. Click Close.
On LON-SVR1, in the Server Manager, click Tools, and then click Print Management.
2.
Expand Printer Servers, expand LON-SVR1, right-click Printers, and then click Add Printer.
The Network Printer Installation Wizard starts.
3.
On the Network Printer Installation Wizard page, click Add a TCP/IP or Web Services Printer by
IP address or hostname, and then click Next.
4.
5.
In Host name or IP address, type 172.16.0.200, clear Auto detect the printer driver to use, and
then click Next.
6.
Under Device Type, click Generic Network Card, and then click Next.
7.
8.
Click Microsoft as the Manufacturer, under Printers, click Microsoft XPS Class Driver, and then click
Next.
9.
L10-59
Change the Printer Name to Branch Office Printer, and then click Next.
10. Click Next two times to accept the default printer name and share name, and to install the printer.
11. Click Finish to close the Network Printer Installation Wizard.
12. In the Print Management console, right-click the Branch Office Printer, and then click Enable
Branch Office Direct Printing.
13. In the Print Management console, right-click the Branch Office Printer, and then select Properties.
14. Click the Sharing tab, select List in the directory, and then click OK.
In the Print Management console, under LON-SVR1, right-click Ports, and then click Add Port.
2.
In the Printer Ports dialog box, click Standard TCP/IP Port, and then click New Port.
3.
4.
5.
6.
Click Finish to close the Add Standard TCP/IP Printer Port Wizard.
7.
8.
In the Print Management console, click Printers, right-click Branch Office Printer, and then click
Properties.
9.
In the Branch Office Printer Properties dialog page, click the Ports tab, select Enable printer
pooling, and then click the 172.16.0.201 port to select it as the second port.
10. Click OK to close the Branch Office Printer Properties dialog box.
11. Close the Print Management Console.
On LON-CL1, in the lower-left corner of the screen, right-click the Start button, and click Control
Panel.
2.
3.
In the Add a device dialog box, click Branch Office Printer on LON-SVR1, and then click Next. The
device installs automatically.
Results: After completing this exercise, you will have installed the Print and Document Services server role
and installed a printer with printer pooling.
2.
In the Virtual Machines list, right-click 20410C-LON-SVR1, and then click Revert.
3.
4.
L11-61
X Task 1: View the location of administrative templates in a Group Policy Object (GPO)
1.
2.
In Server Manager, click Tools, and then click Group Policy Management.
3.
In the Group Policy Management Console (GPMC), expand Forest: Adatum.com, expand Domains,
expand Adatum.com, and then expand the Group Policy Objects folder.
4.
Right-click the Default Domain Policy, and then click Edit. This opens the Group Policy
Management Editor window.
5.
In the Group Policy Management Editor window, expand the Default Domain Policy, under User
Configuration, expand Policies, and then click Administrative Templates.
6.
Point to the Administrative Templates folder, and note that the location is Administrative
Templates: Policy definitions (.admx files) retrieved from the local computer.
7.
2.
In the File Explorer window, expand Local Disk (C:), expand Windows, expand SYSVOL, expand
sysvol, expand Adatum.com, and then double-click Policies.
3.
In the details pane, right-click a blank area, click New, and then click Folder.
4.
2.
Note: Hint: To select all the content, click in the details pane, and then press CTRL+A.
3.
4.
Expand Local Disk (C:), expand Windows, expand SYSVOL, expand sysvol, expand Adatum.com,
expand Policies, and then open the PolicyDefinitions folder.
5.
In the GPMC, right-click the Default Domain Policy, and then click Edit.
2.
In the Group Policy Management Editor window, expand Polices, point to the Administrative
Templates folder and read the local information text, which reads: Administrative Templates: Policy
definitions (ADMX files) retrieved from the Central Store.
3.
Results: After completing this exercise, you should have configured a Central Store.
In the GPMC, right-click the Starter GPOs folder, and then click New.
2.
In the New Starter GPO dialog box, in the Name field, type Internet Explorer Restrictions, in the
Comment field, type This GPO disables the General page in Internet Options, and then click OK.
1.
In the GPMC, under the Starter GPOs folder, right-click the Internet Explorer Restrictions GPO, and
then click Edit.
2.
In the Group Policy Management Editor window, expand User Configuration, Administrative
Templates, and then click All Settings.
3.
4.
In the Filter Options dialog box, select the Enable Keyword Filters check box.
5.
6.
Beside Within, deselect the Help Text and the Comment checkboxes.
7.
Beside the Filter for word(s) field, click the drop-down list box, click Exact, and then click OK.
8.
Double-click the Disable the General page setting, click Enabled, and then click OK.
9.
X Task 3: Create an Internet Explorer Restrictions GPO from the Internet Explorer
Restrictions starter GPO
1.
In the GPMC, right-click the Adatum.com domain, and then click Create a GPO in this domain, and
Link it here.
2.
In the New GPO dialog box, in the Name field, type IE Restrictions.
3.
Under Source Starter GPO, click the drop-down box, select Internet Explorer Restrictions, and then
click OK.
2.
Point the mouse at the lower-right edge of the screen and click the Search charm when it appears.
3.
4.
L11-63
5.
6.
In the Network and Internet dialog box, click Change your homepage.
7.
Read the message box that appears informing you that this feature has been disabled, and then
click OK.
8.
In the Control Panel, click Internet Options. Notice that in the Internet Properties dialog box the
General tab does not display.
9.
X Task 5: Use security filtering to exempt the IT Department from the Internet Explorer
Restrictions policy
1.
Switch to LON-DC1.
2.
In the GPMC, expand the Group Policy Objects folder, and then in the left pane, click the
IE Restrictions policy.
3.
4.
5.
6.
In the Select Users, Computers, Service Accounts, or Groups window, in the Enter the object names
to select (examples) box, type IT, and then click OK.
7.
In the IE Restrictions Security Settings dialog box, click the IT (Adatum\IT) group, next to the
Apply group policy permission, select the Deny check box, and then click OK.
8.
2.
Switch to LON-CL1.
3.
Point the mouse at the lower-right edge of the screen and click the Search charm when it appears.
4.
5.
6.
7.
In the Network and Internet dialog box, click Change your homepage. The Internet Properties
dialog box opens to the General tab, and all settings are available.
8.
2.
Point the mouse at the lower-right edge of the screen and click the Search charm when it appears.
3.
4.
5.
6.
In the Network and Internet dialog box, click Change your homepage. A message box appears
informing you that this feature has been disabled.
7.
8.
Click Internet Options. In the Internet Properties dialog box, notice that the General tab does not
display.
9.
Results: After completing this lab, you should have created a GPO.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L12-65
On LON-DC1, in Server Manager, click Tools, and then click Active Directory Users and Computers.
2.
In Active Directory Users and Computers, in the navigation pane, right-click Adatum.com, click New,
and then click Organizational Unit.
3.
In the New Object - Organizational Unit window, in the Name box, type Member Servers OU, and
then click OK.
4.
In Active Directory Users and Computers, in the navigation pane, click Computers container.
5.
Press and hold the CTRL key. In the details pane, click both LON-SVR1 and LON-SVR2, right-click the
selection, and then click Move.
6.
In the Move window, click Member Servers OU, and then click OK.
On LON-DC1, in Active Directory Users and Computers, in the navigation pane, right-click the
Member Servers OU, click New, and then click Group.
2.
In the New Object Group window, in Group Name, type Server Administrators, and then click OK.
X Task 3: Create a Member Server Security Settings Group Policy Object (GPO) and link
it to the Member Servers OU
1.
On LON-DC1, in the Server Manager window, click Tools, and then click Group Policy
Management.
2.
In the Group Policy Management Console, expand Forests: Adatum.com, expand Domains, expand
Adatum.com, right-click Group Policy Objects, and then click New.
3.
In the New GPO window, in Name, type Member Server Security Settings, and then click OK.
4.
In the Group Policy Management Console, right-click Member Servers OU, and then click Link an
Existing GPO.
5.
In the Select GPO window, in the Group Policy Objects window, click Member Server Security
Settings, and then click OK.
2.
If necessary, click the Group Policy Objects container, right-click Default Domain Policy, and then
click Edit.
3.
4.
5.
In the Add Group dialog box, in Group name, type Administrators, and then click OK.
6.
In the Administrators Properties dialog box, next to Members of this group, click Add.
7.
In the Add Member dialog box type Adatum\Server Administrators, and then click OK.
8.
9.
In the Add Member dialog box type Adatum\Domain Admins, and then click OK twice.
X Task 5: Verify that Computer Administrators has been added to the local
Administrators group
1.
Switch to LON-SVR1.
2.
3.
At the Windows PowerShell prompt, type the following command, and then press Enter:
Gpupdate /force
4.
In the Server Manager window, click Tools, and then click Computer Management.
5.
In the Computer Management console, expand Local Users and Groups, click Groups, and then in
the right-hand pane, double-click Administrators.
6.
Confirm that the Administrators group contains both ADATUM\Domain Admins and
ADATUM\Server Administrators as members. Click Cancel.
7.
X Task 6: Modify the Member Server Security Settings GPO to remove Users from
Allow Log On Locally
1.
On LON-DC1, in the Group Policy Management Console, click Group Policy Objects.
2.
In the right-hand pane, right-click Member Server Security Settings, and then click Edit.
3.
4.
In the right-hand pane, right-click Allow log on locally, and then click Properties.
5.
In the Allow log on locally Properties dialog box, select the Define these policy settings check
box, and then click Add User or Group.
6.
In the Add User or Group window, type Domain Admins, and then click OK.
7.
8.
In the Add User or Group window, type Administrators, and then click OK twice.
X Task 7: Modify the Member Server Security Settings GPO to enable User Account
Control: Admin Approval Mode for the Built-in Administrator account
1.
2.
In the right-hand pane, right-click User Account Control: Admin Approval Mode for the Built-in
Administrator account, and then click Properties.
L12-67
3.
In the User Account Control: Admin Approval Mode for the Built-in Administrator account
Properties dialog box, select the Define this policy settings check box, ensure that Enabled is
selected, and then click OK.
4.
Switch to LON-SVR1.
2.
3.
At the Windows PowerShell prompt, type the following command, and then press Enter:
Gpupdate /force
4.
5.
6.
To prepare for the next exercise, sign out of LON-SVR1, and sign back in to LON-SVR1 as
Adatum\Administrator with the password Pa$$w0rd.
Results: After completing this exercise, you should have used Group Policy to secure Member servers.
Switch to LON-DC1.
2.
3.
4.
In the right-hand pane, right-click Member Server Security Settings, and then click Edit.
5.
6.
7.
In the right-hand pane, right-click Audit object access, and then click Properties.
8.
In the Audit object access Properties dialog box, select the Define these policy settings check
box, select both the Success and Failure check boxes, and then click OK.
9.
Switch to LON-SVR1.
2.
3.
In File Explorer, in the navigation pane, double-click Local Disk (C), and then click Home.
4.
5.
In the Computer window, right-click the Marketing folder, click Share with, and then click Specific
people.
6.
In the File Sharing window, type Adam, and then click Add.
7.
Change the Permission Level to Read/Write, click Share, and then click Done.
1.
On LON-SVR1, in the Local Disk (C:) window, right-click the Marketing folder, and then click
Properties.
2.
In the Marketing Properties window, click the Security tab, and then click Advanced.
3.
In the Advanced Security Settings for Marketing window, click the Auditing tab, click Continue, and
then click Add.
4.
5.
In the Select User, Computer, Service Account or Group window, in Enter the object name to select,
type Domain Users, and then click OK.
6.
In the Auditing Entry for Marketing window, from the Type drop-down menu, select All.
7.
In the Auditing Entry for Marketing window, under the Permission list, select the Write check box,
and then click OK three times.
8.
9.
At the Windows PowerShell prompt, type the following command, and then press Enter:
gpupdate /force
2.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
3.
4.
Open the Command Prompt window, and at the command prompt, type the following command,
and then press Enter:
gpupdate /force
5.
6.
Sign out from LON-CL1, and then sign in again as Adatum\Adam with the password Pa$$w0rd.
7.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
8.
9.
In the Marketing window, click Home, click New item, click Text Document, in File name, type
Employees, and then press Enter.
X Task 5: View the results in the security log on the domain controller
1.
Switch to LON-SVR1.
2.
In the Server Manager window, click Tools, and then click Event Viewer.
3.
In the Event Viewer window, expand Windows Logs, and then click Security.
4.
Results: After completing this exercise, you should have enabled file system access auditing.
2.
3.
In the Server Manager window, click Tools, and then click Group Policy Management.
4.
5.
6.
In the right-hand pane, right-click Default Domain Policy, and then click Edit.
7.
8.
9.
In the right-hand pane, right-click Audit account logon events, and then click Properties.
L12-69
10. In the Audit account logon events Properties dialog box, select the Define these policy settings
check box, select both the Success and Failure check boxes, and then click OK.
11. Point to the lower-right corner of the screen, and then click the Search charm when it appears.
12. In the Search box type cmd, and then press Enter.
13. At the command prompt, type the following command, and then press Enter:
gpupdate /force
2.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
3.
4.
At the command prompt, type the following command, and then press Enter:
gpupdate /force
5.
Close the Command Prompt window, and sign out from LON-CL1.
Note: This password is intentionally incorrect to generate a security log entry that shows
that that an unsuccessful sign in attempt has been made.
On LON-DC1, in Server Manager, click Tools, and then click Event Viewer.
2.
In the Event Viewer window, expand Windows Logs, and then click Security.
3.
Review the event logs for following message: Event ID 4771 Kerberos pre-authentication failed.
Account Information: Security ID: ADATUM\Adam.
Note: This password is correct, and you should be able to sign in successfully as Adam.
2.
Switch to LON-DC1.
2.
In the Server Manager window, click Tools, and then click Event Viewer.
3.
In the Event Viewer window, expand Windows Logs, and then click Security.
4.
Review the event logs for the following message: Event ID 4624 An account was successfully
logged on. New Logon: Security ID: ADATUM\Adam.
Results: After completing this exercise, you should have enabled domain logon auditing.
To prepare for the next lab, leave the virtual machines running.
L12-71
Switch to LON-DC1.
2.
In Server Manager, click Tools, and then click Active Directory Users and Computers.
3.
In Active Directory Users and Computers, in the navigation pane, right-click Adatum.com, click New,
and then click Organizational Unit.
4.
In the New Object - Organizational Unit window, type Client Computers OU, and then click OK.
On LON-DC1, in Active Directory Users and Computers, in the navigation pane, click Computers
container.
2.
3.
In the Move window, click Client Computers OU, and then click OK.
X Task 3: Create a Software Control GPO and link it to the Client Computers OU
1.
On LON-DC1, in Server Manager, click Tools, and then click Group Policy Management.
2.
3.
4.
In New GPO window, in the Name text box type Software Control GPO, and then click OK.
5.
In the right-hand pane, right-click Software Control GPO, and then click Edit.
6.
7.
Under AppLocker, right-click Executable Rules, and then click Create Default Rules.
8.
Repeat the previous step for Windows Installer Rules, Script Rules, and Packaged app Rules.
9.
In the navigation pane, click AppLocker, and then in the right-hand pane, click Configure rule
enforcement.
10. In the AppLocker Properties dialog box, under Executable rules, select the Configured check box,
and then from the drop-down menu, select Audit only.
11. Repeat the previous step for Windows Installer Rules, Script Rules, and Packaged app Rules, and then
click OK.
12. In the Group Policy Management Editor window, go to Computer Configuration/Policies
/Windows Settings/Security Settings.
13. Click System Services, and then double-click Application Identity.
14. In the Application Identity Properties dialog box, click Define this policy setting.
15. Under Select service startup mode, click Automatic, and then click OK.
16. Close the Group Policy Management Editor window.
17. In the Group Policy Management Console, right-click Client Computers OU, and then click Link an
Existing GPO.
18. In the Select GPO window, in the Group Policy Objects list, click Software Control GPO, and then
click OK.
Switch to LON-CL1.
2.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
3.
4.
In the Command Prompt window, type following command, and then press Enter:
gpupdate /force
5.
6.
Point to the lower-right corner of the screen, and then click the Settings charm when it appears.
7.
2.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
3.
4.
At the command prompt, type following command, and then press Enter:
gpresult /R
Review the result of the command and ensure that Software Control GPO is displayed under
Computer Settings, Applied Group Policy Objects.
5.
If Software Control GPO is not displayed, restart LON-CL1 and repeat steps 1 through 4.
6.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
7.
8.
At the command prompt, type the following command, and then press Enter:
C:\CustomApp\app1.bat
On LON-CL1, point to the lower-right corner of the screen, and then click the Search charm when it
appears.
2.
3.
In the Event Viewer window, expand Application and Services Logs, expand Microsoft, expand
Windows, and then expand AppLocker.
4.
L12-73
Click MSI and Scripts and review event log 8005 that contains the following text:
%OSDRIVE%\CUSTOMAPP\APP1.BAT was allowed to run.
Note: If no events are displayed, ensure that the Application Identity service has started,
and try again.
X Task 7: Create a rule that allows software to run from a specific location
1.
On LON-DC1, in Server Manager, click Tools, and then click Group Policy Management.
2.
In the Group Policy Management Console, expand the Group Policy Objects node, right-click
Software Control GPO, and click Edit.
3.
4.
5.
6.
7.
8.
On the Path page, in Path, type the path %OSDRIVE%\CustomApp\app1.bat, and then click Next.
9.
10. On the Name and Description page, in Name, type Custom App Rule, and then click Create.
In the Software control GPO window, in the navigation pane, click AppLocker, and then in the righthand pane, click Configure rule enforcement.
2.
In AppLocker Properties dialog box, under Executable rules, select the Configured check box, and
then from drop-down menu, click Enforce rules.
3.
Repeat the previous step for Windows Installer Rules, Script Rules, and Packaged app Rules, and then
click OK.
4.
Switch to LON-CL1.
2.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
3.
4.
In the Command Prompt window, type the following command, and then press Enter:
gpupdate /force
5.
6.
Point to the lower-right corner of the screen, and then click the Settings charm when it appears.
7.
8.
9.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
10. In the Search box type cmd, and then press Enter.
11. In the Command Prompt window, type following command, and then press Enter:
C:\customapp\app1.bat
1.
2.
3.
In the Computer window, double-click Local Disk (C:), double-click the CustomApp folder, rightclick app1.bat, and then click Copy.
4.
In the CustomApp window, on the navigation pane, right-click the Documents folder, and then
click Paste.
5.
In the Command Prompt window, type C:\Users\Tony\Documents\app1.bat, and then press Enter.
6.
Verify that apps cannot be run from the Documents folder, and that the following message is
displayed: This program is blocked by Group Policy. For more information, contact your system
administrator.
7.
Results: After completing this exercise, you should have configured AppLocker policies for all users
whose computer accounts are located in the Client Computers OU. The policies you configured should
allow these users to run apps that are located in the folders C:\Windows and C:\Program Files, and run the
custom-developed app app1.bat in the C:\CustomApp folder.
Switch to LON-DC1.
2.
In the Server Manager window, click Tools, and then click Active Directory Users and Computers.
3.
In Active Directory Users and Computers, in the navigation pane, right-click the Member Servers OU,
click New, and then click Group.
4.
In the New Object Group window, in Group Name, type Application Servers, and then click OK.
In Active Directory Users and Computers, in the navigation pane, click the Member Servers OU, in
the details pane right-click Application Servers group, and then click Properties.
2.
In the Application Server Properties dialog box, click the Members tab, and then click Add.
3.
In Select Users, Computers, Service Accounts or Groups, click Object Types, click Computers, and
then click OK.
4.
In the Enter the object names to select box type LON-SVR1, and then click OK.
5.
L12-75
1.
On LON-DC1, in Server Manager, click Tools, and then click Group Policy Management.
2.
In the Group Policy Management Console, expand Forests: Adatum.com, expand Domains, expand
Adatum.com, right-click Group Policy Objects, and then click New.
3.
In the New GPO window, in Name, type Application Servers GPO, and then click OK.
4.
In the Group Policy Management Console, right-click Application Servers GPO, and then click Edit.
5.
6.
7.
8.
9.
In the New Inbound Rule Wizard, on the Rule Type page, click Custom, and then click Next.
16. On the Name page, in the Name box type Application Server Department Firewall Rule, and then
click Finish.
17. Close the Group Policy Management Editor window.
On LON-DC1, in the Group Policy Management Console, right-click Member Servers OU, and then
click Link an Existing GPO.
2.
In the Select GPO window, in the Group Policy objects list, click Application Servers GPO, and then
click OK.
X Task 5: Use security filtering to limit the Application Server GPO to members of
Application Server group
1.
On LON-DC1, in the Group Policy Management Console, click Member Servers OU.
2.
Expand the Member Servers OU, and then click the Application Servers GPO link.
3.
4.
In the right-hand pane, under Security Filtering, click Authenticated Users, and then click Remove.
5.
6.
7.
In the Select User, Computer, or Group dialog box, type Application Servers, and then click OK.
2.
Point to the lower-right corner of the screen, and then click the Search charm when it appears.
3.
4.
In the Command Prompt window, type following command, and then press Enter:
gpupdate /force
5.
6.
Restart LON-SVR1, and then sign back in as Adatum\Administrator with the password of
Pa$$w0rd.
Switch to LON-SVR1.
2.
In Server Manager, click Tools, and then click Windows Firewall with Advanced Security.
3.
In the Windows Firewall with Advanced Security window, click Inbound rules.
4.
In the right-hand pane, verify that the Application Server Department Firewall Rule that you
created earlier using Group Policy is configured.
5.
Verify that you cannot edit the Application Server Department Firewall Rule, because it is
configured through Group Policy.
Results: After completing this exercise, you should have used Group Policy to configure Windows Firewall
with Advanced Security to create rules for app servers.
When you finish the lab, revert the virtual machines to their initial state by performing the following steps:
1.
2.
In the Virtual Machines list, right-click 20410C-LON-DC1, and then click Revert.
3.
4.
L13-77
2.
In the Properties pane, click the IPv4 address assigned by DHCP, IPv6 enabled link.
3.
In the Network Connections dialog box, right-click the network object, and then click Properties.
4.
In the Properties dialog box, click Internet Protocol Version 4 (TCP/IPv4), and then click
Properties.
5.
In the Properties dialog box, on the General tab, click Use the following IP address, and then
configure the following:
6.
IP Address: 172.16.0.31
On the General tab, click Use the following DNS server addresses, and then configure the
following:
o
7.
8.
9.
10. In the Server Manager console, from the Manage menu, click Add Roles and Features.
11. In the Add Roles and Features Wizard, on the Before you begin page, click Next.
12. On the Select installation type page, click Role-based or feature-based installation, and then
click Next.
13. On the Select destination server page, ensure that LON-HOST1 is selected, and then click Next.
14. On the Select server roles page, select Hyper-V.
15. In the Add Roles and Features Wizard, click Add Features.
16. On the Select server roles page, click Next.
17. On the Select features page, click Next.
18. On the Hyper-V page, click Next.
19. On the Virtual Switches page, verify that no selections have been made, and then click Next.
20. On the Virtual Machine Migration page, click Next.
21. On the Default Stores page, review the location of the Default Stores, and then click Next.
22. On the Confirm installation selections page, click Restart the destination server automatically if
required.
23. In the Add Roles and Features Wizard, review the message regarding automatic restarts, and then
click Yes.
24. On the Confirm Installation Selections page, click Install.
After a few minutes, the server restarts automatically. Ensure that you restart the machine from the
boot menu as 20410C-LON-HOST1. The computer will restart several times.
Sign in to LON-HOST1 using the account Administrator with the password Pa$$word.
2.
When the installation of the Hyper-V tools completes, click Close to close the Add Roles and
Features Wizard.
3.
In the Server Manager console, click the Tools menu, and then click Hyper-V Manager.
4.
5.
In the Hyper-V Manager console, in the Actions pane, with LON-HOST1 selected, click Hyper-V
Settings.
6.
In the Hyper-V Settings for LON-HOST1 dialog box, click the Keyboard item. Verify that the
Keyboard is set to the Use on the virtual machine option.
7.
In the Hyper-V Settings for LON-HOST1 dialog box, click the Virtual Hard Disks item.
8.
Verify that the location of the default folder to store Virtual Hard Disk files is
C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks, and then click OK.
Results: After completing this exercise, you should have installed the Hyper-V role onto a physical server.
2.
3.
In the Virtual Switch Manager for LON-HOST1 dialog box, click New virtual network switch.
Ensure that External is selected, and then click Create Virtual Switch.
4.
In the Virtual Switch Properties area, enter the following information, and then click OK:
5.
External Network: Mapped to the host computers physical network adapter. (This varies
depending on the host computer.)
In the Apply Networking Changes dialog box, review the warning, and then click Yes.
In Server Manager, on the Tools menu, open Hyper-V Manager, and then click LON-HOST1.
2.
3.
4.
Under Create virtual switch, click Private, and then click Create Virtual Switch.
5.
In the Virtual Switch Manager dialog box, in the Virtual Switch Properties section, configure the
following settings, and then click OK:
o
L13-79
1.
In Server Manager, on the Tools menu, open Hyper-V Manager, and then click LON-HOST1.
2.
3.
4.
Under Create virtual switch, click Internal and then click Create Virtual Switch.
5.
In the Virtual Switch Manager dialog box, in the Virtual Switch Properties section, configure the
following settings, and then click OK:
o
In Server Manager, on the Tools menu, open Hyper-V Manager, and then click LON-HOST1.
2.
3.
4.
On MAC Address Range settings, configure the following values, and then click OK:
5.
Minimum: 00-15-5D-0F-AB-A0
Maximum: 00-15-5D-0F-AB-EF
Results: After completing this exercise, you should have configured virtual switch options on a physicallydeployed Windows Server 2012 server running the Hyper-V role.
2.
Expand This PC, expand drive E, expand Program Files, expand Microsoft Learning, and then
expand Base.
Note: The drive letter may depend upon the number of drives on the physical host
machine.
3.
In the Base folder, verify that the Base14A-WS12R2.vhd hard disk image file is present.
4.
Click the Home tab, and then click the New Folder icon twice to create two new folders. Right-click
each folder and rename the folders to the following names:
o
LON-GUEST1
LON-GUEST2
5.
6.
In the Server Manager console, click Tools, and then click Hyper-V Manager.
7.
In the Hyper-V Manager console, in the Actions pane, click New, and then click Hard Disk.
8.
In the New Virtual Hard Disk Wizard, on the Before You Begin page, click Next.
9.
On the Choose Disk Format page, click VHD, and then click Next.
10. On the Choose Disk Type page, click Differencing, and then click Next.
11. On the Specify Name and Location page, specify the following details, and then click Next:
o
Name: LON-GUEST1.vhd
12. On the Configure Disk page, type the location: E:\Program Files\Microsoft Learning\Base
\Base14A-WS12R2.vhd, and then click Finish.
13. On the desktop, on the taskbar, click the Windows PowerShell icon.
14. At the Windows PowerShell prompt, type the following command to create a new differencing virtual
hard disk to be used with LON-GUEST2, and then press Enter:
New-VHD "E:\Program Files\Microsoft Learning\Base\LON-GUEST2\LON-GUEST2.vhd"
-ParentPath "E:\Program Files\Microsoft Learning\Base\ Base14A-WS12R2.vhd"
17. In the Open dialog box, browse to E:\Program Files\Microsoft Learning\Base\LON-GUEST2\, click
LON-GUEST2.vhd, and then click Open.
18. In the Virtual Hard Disk Properties dialog box, verify that LON-GUEST2.vhd is configured as a
differencing virtual hard disk with E:\Program Files\Microsoft Learning\Base
\Base14A-WS12R2.vhd as a parent, and then click Close.
In Server Manager, on the Tools menu, open Hyper-V Manager, and then click LON-HOST1.
2.
In the Hyper-V Manager console, in the Actions pane, click New, and then click Virtual Machine.
3.
In the New Virtual Machine Wizard, on the Before You Begin page, click Next.
4.
On the Specify Name and Location page, click Store the virtual machine in a different location,
enter the following values, and then click Next:
o
Name: LON-GUEST1
5.
On the Specify Generation page, select Generation 1 and then click Next.
6.
On the Assign Memory page, enter a value of 1024 MB, select the Use Dynamic Memory for this
virtual machine option, and then click Next.
L13-81
7.
On the Configure Networking page, for the connection, click Private Network, and then click
Next.
8.
On the Connect Virtual Hard Disk page, click Use an existing virtual hard disk. Click Browse,
browse to E:\Program Files\Microsoft Learning\Base\LON-GUEST1\lon-guest1.vhd, click Open,
and then click Finish.
9.
10. At the Windows PowerShell prompt, type the following command to create a new virtual machine
named LON-GUEST2, and then press Enter:
New-VM -Name LON-GUEST2 -MemoryStartupBytes 1024MB -VHDPath "E:\Program
Files\Microsoft Learning\Base\LON-GUEST2\LON-GUEST2.vhd" -SwitchName "Private
Network"
14. In the Settings for LON-GUEST2 on LON-HOST1 dialog box, click Automatic Start Action, and set
the Automatic Start Action to Nothing.
15. In the Settings for LON-GUEST2 on LON-HOST1 dialog box, click Automatic Stop Action, and set
the Automatic Stop Action to Shut down the guest operating system.
16. Click OK to close the Settings for LON-GUEST2 on LON-HOST1 dialog box.
2.
At the Windows PowerShell prompt, enter the following commands to enable resource metering on
the virtual machines, pressing Enter at the end of each line:
Enable-VMResourceMetering LON-GUEST1
Enable-VMResourceMetering LON-GUEST2
Results: After completing this exercise, you should have deployed two separate virtual machines using a
sysprepped virtual hard disk file as a parent disk for two differencing virtual hard disks.
2.
3.
4.
In the LON-GUEST1 on LON-HOST1 - Virtual Machine Connection window, perform the following
steps:
o
On the Settings page, click Next to accept the Region and Language settings.
On the Settings page, type the password Pa$$w0rd twice, and then click Finish.
5.
In the LON-GUEST1 on LON-HOST1 - Virtual Machine Connection window, from the Action menu,
click CTRL+Alt+Delete.
6.
Sign in to the virtual machine using the account Administrator and the password Pa$$w0rd.
7.
On the virtual machine, in the Server Manager console, click Local Server, and then click the
randomly assigned name next to the computer name.
8.
In the System Properties dialog box, on the Computer Name tab, click Change.
9.
In the Computer Name field, type LON-GUEST1, and then click OK.
1.
Sign in to the LON-GUEST1 virtual machine using the Administrator account and the password
Pa$$w0rd
2.
In the Server Manager console, click the Local Server node, and verify that the name of the computer
is set to LON-GUEST1.
3.
In the Virtual Machine Connection window, from the Action menu, click Checkpoint.
4.
In the Checkpoint Name dialog box, type the name Before Change, and then click Yes.
In the Server Manager console, click Local Server, and then next to Computer name, click
LON-GUEST1.
2.
In the System Properties dialog box, on the Computer Name tab, click Change.
3.
In the Computer Name field, type LON-Computer1, and then click OK.
4.
5.
6.
7.
Sign back in to the LON-GUEST1 virtual machine using the Administrator account and the password
Pa$$w0rd.
8.
In the Server Manager console, click Local Server, and verify that the server name is set to
LON-Computer1.
In the Virtual Machine Connection window, from the Action menu, click Revert.
2.
3.
In the Server Manager console, in the Local Server node, in the Virtual Machines list, verify that the
Computer Name is now set to LON-GUEST1.
L13-83
1.
2.
To retrieve resource metering information, at the Windows PowerShell prompt, enter the following
command, and then press Enter:
Measure-VM LON-GUEST1
Note the average CPU, average random access memory (RAM), and total disk usage figures.
3.
Results: After completing this exercise, you should have used virtual machine checkpoints to recover from
a virtual machine misconfiguration.
After you finish the lab, restart the computer in Windows Server 2012 by performing the following steps:
1.
2.
At the Windows PowerShell command prompt, type the following command, and then press Enter:
Shutdown /r /t 5
3.