I got a request to build Always-On with cluster and everything had to be pre-staged, creating the same in Azure we will see what all permission we need to have this built.
Created an Azure VM with the below configuration, I created nested virtualization and for that the requirement is to have a VM with “v3” size.
Thanks to the Azure Spot Instance it has now become very cheap to build and test VM in Azure.
You can add another SSD drive of P10 for the Hyper-V images. (Don’t forget to map the drive inside the VM too)
Once the VM is created, log in and configure the Hyper-V feature.
In such cases I usually make three copies of the Windows Server ISO, to start installing three nodes simultaneously.
Create 3 Hyper-V VMs using the 3 copies of ISO files. The only option that you have to keep in mind is that in Configure Networking choose “Microsoft Hyper-V Network Adapter – Virtual Switch”. Complete the installation of all three.
It took me 15 minutes to complete the installation on all the three servers.
Once that is done, you need to configure IP settings for the DC, below is what I have setup in my environment.
Now add AD domain services, DNS and DHCP role on the DC server.
Once installation is completed promote the server to a domain controller.
Provide a new forest name, (I have named mine “testing.ao”) and in the next tab provide a password everything else can be kept as default. It will reboot the server, once back up you need to configure DHCP and scope.
Goto DHCP from Tools, then IPv4 and Select New Scope. Provide a scope name and in the IP address range select the range of IPs for which you want dynamic IP allocation.
For the Default Gateway select the IP that was selected when configuring DC IPv4 setting.
Now add node1 and node2 to the domain. When adding to the domain it will ask for login, provide the credential which Administrator in DC.
Once it is done for both you will be able to see both the servers in “AD Users and Computers” at DC end.