Enjoy Sharing

Setting Up An EMS Lab in ARM (Azure Resource Manager) Step-By-Step – Part 2

Quick links to the other parts of the post:-

 

Now that we’ve got the fundamentals out of the way it is time to create some virtual machines. At the very least, we need a domain controller, a server for AD Connect and a server for SCCM.

Click on Virtual machines and then click Add.

image

 

Select Windows Server > Windows Server 2012 R2 Datacenter, then click Create.

image

 

Enter the details for the virtual machine as below. Change as required. Because I have multiple lab environments, I like to label my VMs with a prefix of “Labxx-“ where xx can be an incremental number to mark the set of VMs in the same environment.

  • Name: Lab02-DC01
  • Username: <username>
  • Password: <password>
  • Subscription: <subscription>
  • Resource group: <The resource group that was created in Part 1>
  • Location: <Location>

image

 

Choose a size of the virtual machine, then click Select. I would suggest a F1S Standard VM for a domain controller. If you don’t see it, click View All at the top right corner of the blade to display all VM sizes.

image

 

Configure the settings of the virtual machine as below:-

  • Disk type: Standard
  • Storage account: stwklab02
  • Virtual network: VNET-Lab02
  • Subnet: Subnet-01 (10.1.0.0/24)
  • Public IP address: (new) Lab02-DC01
  • Network security group: NSG-Lab02
  • Extensions: None
  • Diagnostics: Enabled
  • Diagnostics storage account: stwklab02
  • Availability set: None

image

 

Click OK.

image

 

Wait a few minutes for the virtual machine to be provisioned. Once the virtual machines has been created, it is time to add a data disk to be used for data. I normally use my data disks for program files and databases. If you want, you can choose to add more than one data disks especially for the SCCM server. The number of data disks you can add to a virtual machine depends on the virtual machine size you picked.

image

 

Repeat creating all virtual machines with the details below:-

Name

Size

Virtual Network

Subnet

Public IP

Network Security Group

Lab02-DC01

F1S

VNET-Lab02

Subnet-01

<New>

NSG-Lab02

Lab02-ADC01

F1S

VNET-Lab02

Subnet-01

<New>

NSG-Lab02

Lab02-CM01

DS2_V2

VNET-Lab02

Subnet-01

<New>

NSG-Lab02

 

Now that my virtual machines are all created, it is time to set up my domain environment. I will not walk through this step-by-step here as this is not what this post is about. What I do want to mention is that all virtual machines in Azure IaaS has a dynamic IP address by default. However, a static IP address is always recommended for a domain controller.

To set static IP address for your domain controller, click on Lab02-DC01 virtual machine which will be your domain controller, then click Network interfaces.

image_thumb1

 

You should only have one network interface on that virtual machine. Click IP addresses, change the Assignment to Static and then click Save. A reboot of the virtual machine may be required. As a best practice, always restart a virtual machine in the ARM console.

image_thumb3

 

Another thing you want to do for a domain controller is to set its DNS to point to its own IP address. Click DNS servers, click Custom DNS then enter the private IP address of the domain controller virtual machine. Click Save.

In fact do this for all the virtual machines in this lab to point to the domain controller IP address for DNS.

image_thumb[3]

In the next part, we will be looking at setting up the integration between the on-premises AD with Azure AD, domain purchase and verification.

 

 

 

Enjoy!!!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s