Test Lab Guide: Base Configuration in

Azure

Microsoft Corporation

Abstract
This Microsoft Test Lab Guide (TLG) provides you with step-by-step instructions to create the
Base Configuration test lab in a Microsoft Azure Virtual Network, using computers running
Windows Server 2012 R2. With the resulting test lab, you can experiment with the new
environment of Azure, use it as a basis for application development, or build test labs based on
other TLGs or one of your own design.
Copyright Information
This document is provided for informational purposes only and Microsoft makes no warranties,
either express or implied, in this document. Information in this document, including URL and
other Internet Web site references, is subject to change without notice. The entire risk of the
use or the results from the use of this document remains with the user. Unless otherwise noted,
the example companies, organizations, products, domain names, e-mail addresses, logos,
people, places, and events depicted herein are fictitious, and no association with any real
company, organization, product, domain name, e-mail address, logo, person, place, or event is
intended or should be inferred. Complying with all applicable copyright laws is the responsibility
of the user. Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any
means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose,
without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you
any license to these patents, trademarks, copyrights, or other intellectual property.

© 2014 Microsoft Corporation. All rights reserved.

Date of last update: 9/15/2014

Microsoft, Windows, Active Directory, Internet Explorer, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.

All other trademarks are property of their respective owners.

Contents
Introduction ..................................................................................................................................... 5
In this guide .................................................................................................................................. 5
Test lab overview ......................................................................................................................... 5
User account control ................................................................................................................ 7

Ongoing costs of test lab virtual machines in Azure ....................................................................... 8

Step 1: Create the Azure Virtual Network ....................................................................................... 8

Create a virtual network named TestLab ..................................................................................... 8
Create a new cloud service for the TestLab virtual network ....................................................... 8
Create a new storage account ..................................................................................................... 9

Step 2: Configure DC1 ..................................................................................................................... 9

Create an Azure Virtual Machine for DC1 .................................................................................... 9
Add a data disk ........................................................................................................................... 10
Configure DC1 as a domain controller and DNS server ............................................................. 11
Create a user account in Active Directory ................................................................................. 11

Step 3: Configure APP1 .................................................................................................................. 12

Create an Azure Virtual Machine for APP1 ................................................................................ 13
Join APP1 to the CORP domain .................................................................................................. 14
Install the Web Server (IIS) role on APP1 ................................................................................... 14
Create a shared folder on APP1 ................................................................................................. 14

Step 4: Configure CLIENT1 ............................................................................................................. 15

Create an Azure Virtual Machine for CLIENT1 ........................................................................... 15
Join CLIENT1 to the CORP domain ............................................................................................. 16
Test access to intranet resources from the Corpnet subnet ..................................................... 17

Additional Resources ..................................................................................................................... 17

Appendix........................................................................................................................................ 18
Set UAC behavior of the elevation prompt for administrators.................................................. 18
Starting the test lab virtual machines after being shut down ................................................... 18
Introduction
Test Lab Guides (TLGs) allow you to get hands-on experience with new products and technologies using
a pre-defined and tested methodology that results in a working configuration. When you use a TLG to
create a test lab, instructions tell you what servers to create, how to configure the operating systems
and platform services, and how to install and configure any additional products or technologies. A TLG
experience enables you to perform all of the configuration steps on both the front-end and back-end
that go into a single- or multi-product or technology solution.

The purpose of this TLG is to enable you to create the Windows Server 2012 R2 Base Configuration test
lab as a set of virtual machines in a cloud-only Azure Virtual Network. A cloud-only Azure Virtual
Network does not have a connection back to your organization network.

In this guide
This document contains instructions for setting up the Windows Server 2012 R2 Base Configuration test
lab by deploying three server computers running Windows Server 2012 R2 as Azure virtual machines.
The resulting configuration simulates a private intranet that is connected to the Internet.

Important
The following instructions are for configuring the Windows Server 2012 R2 Base Configuration in
Azure test lab. Individual computers are needed to separate the services provided on the
network and to clearly show the desired functionality. This configuration is neither designed to
reflect best practices nor does it reflect a desired or recommended configuration for a
production network. The configuration, including IP addresses and all other configuration
parameters, is designed only to work on this test lab network.

Test lab overview

The Windows Server 2012 R2 Base Configuration in Azure test lab consists of the following:

 One Azure virtual machine running Windows Server 2012 R2 named DC1 that is configured as an
intranet domain controller and Domain Name System (DNS) server.

 One Azure virtual machine running Windows Server 2012 R2 named APP1 that is configured as a
general application and web server.

 One Azure virtual machine running Windows Server 2012 R2 named CLIENT1 that will act as an
intranet client.

The Windows Server 2012 R2 Base Configuration in Azure test lab consists of the Corpnet subnet in a
cloud-only Azure Virtual Network named TestLab that simulates a simplified intranet, as shown in Figure
1.

5
Figure 1 Windows Server 2012 R2 Base Configuration in Azure

This configuration allows DC1, APP1, CLIENT1, and additional Corpnet subnet computers to be:

 Connected to the Internet to install updates, access Internet resources in real time, and participate
in public cloud technologies such as Microsoft Office 365 and other Azure services.
 Remotely managed using Remote Desktop Connections by your computer that is connected to the
Internet or your organization network.

For a short video that describes the configuration of this test lab, see the Base Configuration in Azure
Test Lab Guide Overview.

Key differences from the Test Lab Guide: Windows Server 2012 R2 Base Configuration—which
configures DC1, APP1, and CLIENT1 on an isolated subnet—are the following:

 DC1 is no longer a DHCP server. It obtains its IPv4 address allocation from Azure through DHCP.
6
 APP1 is now a DHCP client like DC1, rather than statically configured.
 To provide name resolution for Internet resources, the DNS Server service on DC1 forwards DNS
queries to the addresses of Internet DNS servers.
 Because Azure does not currently offer a Windows 8.1 or Windows 8 virtual machine image,
CLIENT1 runs Windows Server 2012 R2.
 Operating system configuration procedures are done almost exclusively through Windows
PowerShell.

There are four steps to setting up the Corpnet subnet of the Windows Server 2012 R2 Base
Configuration test lab in Azure.

1. Create the Azure Virtual Network.

2. Configure DC1.
3. Configure APP1.
4. Configure CLIENT1.

Note
You must be logged on as a member of the Domain Admins group or a member of the
Administrators group on each computer to complete the tasks described in this guide. If you cannot
complete a task while you are logged on with an account that is a member of the Administrators
group, try performing the task while you are logged on with an account that is a member of the
Domain Admins group.

Important: The instructions for configuring the computers of the Corpnet subnet of the Base
Configuration test lab are designed to be as simple as possible and require as few computers as
possible. In some cases, servers provide multiple roles that would normally be placed on different
servers. This configuration is neither designed to reflect best practices nor does it reflect a desired or
recommended configuration for a production network.

If you do not already have an Azure account, you can sign up for a free trial at Try Azure. If you have an
MSDN Subscription, see Microsoft Azure Special Pricing: MSDN, MPN, and Bizspark Benefits.

User account control

When you configure Windows Server 2012 R2, you are required to click Continue or Yes in the User
Account Control (UAC) dialog box for some tasks. Several of the configuration tasks require UAC
approval. When you are prompted, always click Continue or Yes to authorize these changes.
Alternatively, see the Appendix of this guide for instructions about how to set the UAC behavior of the
elevation prompt for administrators.

7
Ongoing costs of test lab virtual machines in Azure
Virtual machines in Azure incur an ongoing monetary cost when they are running. This cost is billed
against your free trial, MSDN subscription, or paid subscription. For more information about the costs of
running Azure virtual machines, see Virtual Machines Pricing Details and Azure Pricing Calculator.

To minimize the cost of running the test lab virtual machines, you can do one of the following:

 Create the test lab and perform your needed testing and demonstration as quickly as possible.
When complete, delete the test lab virtual machines from the Virtual Machines page of the Azure
Management Portal.
 Shut down your test lab virtual machines into a deallocated state from the Virtual Machines page of
the Azure Management Portal. However, you should start your virtual machines in a specific order.
For more information, see Starting the test lab virtual machines after being shut down.

Step 1: Create the Azure Virtual Network

First, you create the TestLab Azure Virtual Network that will host the Corpnet subnet of the base
configuration. Then, you create an Azure cloud service. The cloud service acts as a security boundary
and logical container for the virtual machines placed in the virtual network. It also provides a way for
you to remotely connect to and manage the virtual machines on the Corpnet subnet. Lastly, you
configure a storage account that will contain the disks for your virtual machines and extra data disks.

Create a virtual network named TestLab

1. In the task bar of the Azure Management Portal, click NEW > NETWORK SERVICES > VIRTUAL
NETWORK > CUSTOM CREATE.
2. On the Virtual Network Details page, type TestLab or the name of your choice in NAME.
3. In LOCATION, select the appropriate region.
4. Click the Next arrow.
5. On the DNS Servers and VPN Connectivity page, in DNS servers, type DC1 in Select or enter name,
type [Link] in IP address, and then click the Next arrow.
6. On the Virtual Network Address Spaces page, in Subnets, click Subnet-1 and replace the name with
Corpnet.
7. In the CIDR (ADDRESS COUNT) column for the Corpnet subnet, click /24 (256).
8. Click the Complete icon. Wait until the virtual network is created before continuing.

Create a new cloud service for the TestLab virtual network

1. In the task bar of the Azure Management Portal, click NEW > COMPUTE > CLOUD SERVICE > QUICK
CREATE.
2. In URL, type a unique name. For example, you could name it TestLab-UniqueSequence, in which
UniqueSequence is an abbreviation of your organization. For example, if your organization is named
Tailspin Toys, you could name the cloud service TestLab-Tailspin. Ensure that there is a green
checkmark next to the name. This indicates that the name is unique. If you see a red exclamation
and the message "The specified URL is already in use", you must choose another name.
3. In REGION OR AFFINITY GROUP, select the same region as your TestLab virtual network.
8
4. Click the CREATE CLOUD SERVICE complete icon. Wait until the cloud service is created before
continuing.

Create a new storage account

1. In the task bar of the Azure Management Portal, click NEW > DATA SERVICES > STORAGE > QUICK
CREATE.
2. In URL, type a unique name. For example, you could name it testlabUniqueSequence, in which
UniqueSequence is an abbreviation of your organization. For example, if your organization is named
Tailspin Toys, you could name the cloud service testlabtailspin. Ensure that there is a green
checkmark next to the name. This indicates that the name is unique. If you see a red exclamation
and the message "The specified URL is already in use", you must choose another name.
3. In REGION OR AFFINITY GROUP, select the same region as your TestLab virtual network.
4. Click the CREATE STORAGE ACCOUNT complete icon. Wait until the storage account is created
before continuing.

Step 2: Configure DC1

DC1 provides the following services:

 A domain controller for the [Link] Active Directory Domain Services (AD DS) domain.
 A DNS server for the virtual machines of the TestLab virtual network.

DC1 configuration consists of the following:

 Create an Azure Virtual Machine for DC1.

 Add a data disk.
 Configure DC1 as a domain controller and DNS server.
 Create a user account in Active Directory.

Create an Azure Virtual Machine for DC1

1. In the task bar of the Azure Management Portal, click NEW > COMPUTE > VIRTUAL MACHINE >
FROM GALLERY.
2. On the Choose an Image page, click Windows Server 2012 R2 Datacenter, and then click the Next
arrow.
3. On the Virtual machine configuration page:
 In VIRTUAL MACHINE NAME, type DC1.
 In SIZE, select A2.
 In NEW USER NAME, type the name of a local administrator account. You will use this
account when initially connecting and as an alternate set of credentials when DC1 becomes
a domain controller. Choose a name that is not easy to guess.
 In NEW PASSWORD and CONFIRM, type a strong password for the local administrator
account.
 Record the local administrator account name and password in a secured location.
4. Click the Next arrow.
5. On the second Virtual machine configuration page:
9
  In CLOUD SERVICE, select the cloud service that you created in "Step 1: Create the Azure
Virtual Network."
 In REGION/AFFINITY GROUP/VIRTUAL NETWORK, select TestLab.
 In STORAGE ACCOUNT, select the storage account that you created in "Step 1: Create the
Azure Virtual Network."
 In ENDPOINTS, in the PowerShell row, delete the default port number in the PUBLIC PORT
column.
6. Click the Next arrow.
7. On the third Virtual machine configuration page, click the Complete icon. Wait until Azure creates
the virtual machine.
8. On the virtual machines page of the Azure Management Portal, click Running in the STATUS column
for the DC1 virtual machine.
9. On the command bar, click Attach, and then select Attach Empty Disk. The Attach Empty Disk
dialog box appears. The Storage Location and File Name boxes contain automatically generated
names that do not need to be altered.
10. In the Size box, type 20.
11. Leave the Host Cache Preference set to the default value of NONE.
12. Click the Complete icon to attach the empty data disk. Wait until the status is Running before
continuing (a few minutes).
13. In the task bar, click CONNECT.
14. When prompted to open [Link], click Open.
15. When prompted with a Remote Desktop Connection message box, click Connect.
16. When prompted for credentials, use the following:
 Name: DC1\[Local administrator account name] (from step 3)
 Password: [Local administrator account password] (from step 3)
17. When prompted with a Remote Desktop Connection message box referring to certificates, click Yes.

Add a data disk

Add an extra data disk as a new volume with the drive letter F:.

1. In the left pane of Server Manager, click File and Storage Services, and then click Disks.
2. In the contents pane, in the DISKS group, click disk 2 (with the Partition set to Unknown).
3. Click Tasks, and then click New Volume.
4. On the Before you begin page of the New Volume Wizard, click Next.
5. On the Select the server and disk, click Disk 2, and then click Next. When prompted, click OK.
6. On the Specify the size of the volume page, click Next.
7. On the Assign to a drive letter or folder page, click Next.
8. On the Select file system settings page, click Next.
9. On the Confirm selections page, click Create.
10. When complete, click Close.

10
Configure DC1 as a domain controller and DNS server
To configure DC1 as a domain controller and DNS server for the [Link] domain, run the
following commands at a Windows PowerShell command prompt:

Windows PowerShell commands

Note that you will be prompted to supply a Directory Services Restore Mode (DSRM) password and
to restart DC1.

Install-WindowsFeature AD-Domain-Services -IncludeManagementTools

Install-ADDSForest -DomainName [Link] -DatabasePath "F:\NTDS" -SysvolPath "F:\SYSVOL" -LogPath "F:\Logs"

After DC1 restarts, reconnect to the DC1 virtual machine.

1. On the virtual machines page of the Azure Management Portal, click Running in the STATUS column
for the DC1 virtual machine.
2. In the task bar, click CONNECT.
3. When prompted to open [Link], click Open.
4. When prompted with a Remote Desktop Connection message box, click Connect.
5. When prompted for credentials, use the following:
 Name: CORP\[Local administrator account name] (from step 3 of the "Create an Azure
Virtual Machine for DC1" procedure)
 Password: [Local administrator account password] (from step 3 of the "Create an Azure
Virtual Machine for DC1" procedure)
6. When prompted by a Remote Desktop Connection message box referring to certificates, click Yes.

Create a user account in Active Directory

To create a user account in Active Directory that will be used when logging in to CORP domain member
computers, run the following commands at an administrator-level Windows PowerShell command
prompt:

Windows PowerShell commands

11
 Note that the first command results in a prompt to supply the User1 account password. Because this
account will be used for remote desktop connections for all CORP domain member computers,
choose a strong password.

New-ADUser -SamAccountName User1 -AccountPassword (read-host "Set user password" -assecurestring) -name "User1" -
enabled $true -PasswordNeverExpires $true -ChangePasswordAtLogon $false
Add-ADPrincipalGroupMembership -Identity "CN=User1,CN=Users,DC=corp,DC=contoso,DC=com" -MemberOf
"CN=Enterprise Admins,CN=Users,DC=corp,DC=contoso,DC=com","CN=Domain
Admins,CN=Users,DC=corp,DC=contoso,DC=com"

Record the User1 account password in a secured location.

Reconnect to the DC1 virtual machine using the CORP\User1 account.

1. Close the Remote Desktop Connection window for DC1.

2. On the virtual machines page of the Azure Management Portal, click Running in the STATUS column
for the DC1 virtual machine.
3. In the task bar, click CONNECT.
4. When prompted to open [Link], click Open.
5. When prompted with a Remote Desktop Connection message box, click Connect.
6. When prompted for credentials, use the following:
 Name: CORP\User1
 Password: [User1 account password]
7. When prompted by a Remote Desktop Connection message box referring to certificates, click Yes.
From the Windows PowerShell command prompt, run the following commands to allow traffic for the
Ping tool:

Windows PowerShell commands

Set-NetFirewallRule -DisplayName "File and Printer Sharing (Echo Request - ICMPv4-In)" -enabled True

Step 3: Configure APP1

APP1 provides web and file sharing services. APP1 configuration consists of the following:

 Create an Azure Virtual Machine for APP1.

 Join APP1 to the CORP domain.
 Install the Web Server (IIS) role on APP1.
12
 Create a shared folder on APP1.

Create an Azure Virtual Machine for APP1

1. In the task bar of the Azure Management Portal, click NEW > COMPUTE > VIRTUAL MACHINE >
FROM GALLERY.
2. On the Choose an Image page, click Windows Server 2012 R2 Datacenter, and then click the Next
arrow.
3. On the Virtual machine configuration page:
 In VIRTUAL MACHINE NAME, type APP1.
 In SIZE, select A2.
 In NEW USER NAME, type the name of a local administrator account. You will use this
account when initially connecting and as an alternate set of credentials once APP1 has
joined the CORP domain. Choose a name that is not easy to guess.
 In NEW PASSWORD and CONFIRM, type a strong password for the local administrator
account.
 Record the local administrator account name and password in a secured location.
4. Click the Next arrow.
5. On the second Virtual machine configuration page:
 In CLOUD SERVICE, select the cloud service that you created in "Step 1: Create the Azure
Virtual Network."
 In STORAGE ACCOUNT, select the storage account that you created in "Step 1: Create the
Azure Virtual Network."
 In ENDPOINTS, in the PowerShell row, delete the default port number in the PUBLIC PORT
column.
6. Next arrow.
7. On the third Virtual machine configuration page, click the complete icon.
8. Wait until Azure creates the virtual machine.
9. On the virtual machines page of the Azure Management Portal, click Running in the STATUS column
for the APP1 virtual machine.
10. In the task bar, click CONNECT.
11. When prompted to open [Link], click Open.
12. When prompted with a Remote Desktop Connection message box, click Connect.
13. When prompted for credentials, use the following:
 Name: APP1\[Local administrator account name] (from step 3)
 Password: [Local administrator account password] (from step 3)
14. When prompted with a Remote Desktop Connection message box referring to certificates, click Yes.
To check name resolution and network communication between APP1 and DC1, run the ping
[Link] command at the Windows PowerShell command prompt and verify that there
are four replies.

13
Join APP1 to the CORP domain
To join APP1 to the CORP domain, run the following commands at the Windows PowerShell command
prompt:

Windows PowerShell commands

Add-Computer -DomainName [Link]

Restart-Computer

Note that you must supply your CORP\User1 domain account credentials after entering the Add-
Computer command.

Reconnect to the APP1 virtual machine.

1. After APP1 restarts, on the virtual machines page of the Azure Management Portal, click Running in
the STATUS column for the APP1 virtual machine.
2. In the task bar, click CONNECT.
3. When prompted to open [Link], click Open.
4. When prompted with a Remote Desktop Connection message box, click Connect.
5. When prompted for credentials, use the following:
 Name: CORP\User1
 Password: [User1 account password]
6. When prompted by a Remote Desktop Connection message box referring to certificates, click Yes.

Install the Web Server (IIS) role on APP1

On APP1, open an administrator-level Windows PowerShell command prompt. To install the Web Server
(IIS) role and make APP1 a web server, run the following command:

Windows PowerShell command

Install-WindowsFeature Web-WebServer -IncludeManagementTools

Create a shared folder on APP1

To create a shared folder and a text file within the folder on APP1, run the following commands:
14
 Windows PowerShell commands

New-Item -path c:\files -type directory

Write-Output "This is a shared file." | out-file c:\files\[Link]
New-SmbShare -name files -path c:\files -changeaccess CORP\User1

Note that the “Create an Azure Virtual Machine for APP1” and “Join APP1 to the CORP domain”
procedures in this section can also be used to add more Windows Server R2 2012-based computers to
the Corpnet subnet.

Step 4: Configure CLIENT1

CLIENT1 configuration consists of the following:

 Create an Azure Virtual Machine for CLIENT1.

 Join CLIENT1 to the CORP domain.
 Test access to intranet resources on the Corpnet subnet.

Create an Azure Virtual Machine for CLIENT1

1. In the task bar of the Azure Management Portal, click NEW > COMPUTE > VIRTUAL MACHINE >
FROM GALLERY.
2. On the Choose an Image page, click Windows Server 2012 R2 Datacenter, and then click the Next
arrow. If you are using Azure through your MSDN subscription, you can click the Windows 8.1
Enterprise (x64) image.
3. On the Virtual machine configuration page:
 In VIRTUAL MACHINE NAME, type CLIENT1.
 In SIZE, select A2.
 In NEW USER NAME, type the name of a local administrator account. You will use this
account when initially connecting and as an alternate set of credentials once CLIENT1 has
joined the CORP domain. Choose a name that is not easy to guess.
 In NEW PASSWORD and CONFIRM, type a strong password for the local administrator
account.
 Record the local administrator account name and password in a secured location.
4. Click the Next arrow.
5. On the second Virtual machine configuration page:
 In CLOUD SERVICE, select the cloud service that you created in "Step 1: Create the Azure
Virtual Network."

15
  In STORAGE ACCOUNT, select the storage account that you created in "Step 1: Create the
Azure Virtual Network."
 In ENDPOINTS, in the PowerShell row, delete the default port number in the PUBLIC PORT
column.
6. Click the Next arrow.
7. On the third Virtual machine configuration page, click the Complete icon.
8. Wait until Azure creates the virtual machine.
9. On the virtual machines page of the Azure Management Portal, click Running in the STATUS column
for the CLIENT1 virtual machine.
10. In the task bar, click CONNECT.
11. When prompted to open [Link], click Open.
12. When prompted with a Remote Desktop Connection message box, click Connect.
13. When prompted for credentials, use the following:
 Name: CLIENT1\[Local administrator account name] (from step 3)
 Password: [Local administrator account password] (from step 3)
14. When prompted with a Remote Desktop Connection message box referring to certificates, click Yes.
To check name resolution and network communication between CLIENT1 and DC1, run the ping
[Link] command at a Windows PowerShell command prompt and verify that there are
four replies.

Join CLIENT1 to the CORP domain

To join CLIENT1 to the [Link] domain, run the following commands:

Windows PowerShell commands

Add-Computer -DomainName [Link]

Restart-Computer

Note that you must supply the CORP\User1 domain account credentials after entering the Add-
Computer command.

Reconnect to the CLIENT1 virtual machine.

16
1. After CLIENT1 restarts, on the virtual machines page of the Azure Management Portal, click Running
in the STATUS column for the CLIENT1 virtual machine.
2. In the task bar, click CONNECT.
3. When prompted to open [Link], click Open.
4. When prompted with a Remote Desktop Connection message box, click Connect.
5. When prompted for credentials, use the following:
 Name: CORP\User1
 Password: [User1 account password]
6. When prompted by a Remote Desktop Connection message box referring to certificates, click Yes.

Test access to intranet resources from the Corpnet subnet

Verify that you can access web and file share resources on APP1 from CLIENT1.

1. From the desktop, open Server Manager.

2. In the tree pane, click Local Server.
3. In Properties for CLIENT1, click On next to IE Enhanced Security Configuration.
4. In Internet Explorer Enhanced Security Configuration, click Off for Administrators and Users, and
then click OK.
5. From the Start screen, click the Internet Explorer icon.
6. In the Address bar, type [Link] and then press ENTER. You should see
the default IIS 8 web page for APP1.
7. From the Start screen or the desktop taskbar, click the File Explorer icon.
8. In the address bar, type \\app1\Files, and then press ENTER.
9. You should see a folder window with the contents of the Files shared folder.
10. In the Files shared folder window, double-click the [Link] file. You should see the contents of
the [Link] file.
11. Close the [Link] - Notepad and the Files shared folder windows.

Note that the “Create an Azure Virtual Machine for CLIENT1” and “Join CLIENT1 to the CORP domain”
procedures in this section can also be used to add more client computers to the Corpnet subnet.

Your base configuration in Azure is now ready for experimentation and additional Azure TLGs. For more
information, see Azure Test Lab.

Additional Resources
For more information about Azure infrastructure services, see Infrastructure Services | Azure.

To provide the authors of this guide with feedback or suggestions for improvement, send an email
message to tlgfb@[Link].

We strongly encourage you to develop and publish your own TLG content, either in the TechNet Wiki
(example: Test Lab Guide: Demonstrate Remote Access VPNs) or in your own publishing forum
17
(example: Test Lab Guide (Part 1) - Demonstrate TMG PPTP, L2TP/IPsec and SSTP Remote Access VPN
Server). See Creating and Publishing Test Lab Guide Content for information about the types of content
you can create and links to templates, guidance, and examples.

For a list of additional Microsoft TLGs, see Test Lab Guides in the TechNet Wiki.

Appendix
This appendix describes how to change the default User Account Control (UAC) behavior and starting
the test lab virtual machines after being shut down.

Set UAC behavior of the elevation prompt for administrators

By default, UAC is enabled in Windows Server 2012 R2 and Windows 8.1. This service will prompt for
permission to continue during several of the configuration tasks described in this guide. In all cases, you
can click Continue in the UAC dialog box to grant this permission, or you can use the following
procedure to change the UAC behavior of the elevation prompt for administrators.

To set UAC behavior of the elevation prompt for administrators

1. From the Start screen, type [Link], and press ENTER.

2. In the console tree, open Local Policies, and then click Security Options.

3. In the contents pane, double-click User Account Control: Behavior of the elevation prompt
for administrators in Admin Approval Mode.

4. Select Elevate without prompting in the list, and then click OK.

1. 6. Close the Local Security Policy window.

Starting the test lab virtual machines after being shut down
To ensure that your virtual machines work properly when starting all of them from the Stopped
(Deallocated) state, start them in the following order:

1. DC1
2. APP1
3. CLIENT1
To start a virtual machine from the Virtual Machines page of the Azure Management Portal, click
Stopped next to the virtual machine name, and then click Start in the task bar.

18