As it is the first VM created it will be dynamically allocated x.x.x.4 and match the DNS Server address created above. If the plan is to create an AD then first VM created must be the AD server, thus it will be a DNS server. The first address it will use will be x.x.x.4, e.g. Download the Windows Azure PowerShell Management Tools.Īzure allocates Virtual Network addresses dynamically.When creating a VM always give the access account a complex password – it’s used to connect to the VM over the public internet.Always create VMs in their own Cloud Services and give the VM and Cloud Service the same name if possible.
Create a Virtual Network and configure a Subnet (these are the addresses your VMs will use to communicate internally and all allocated dynamically).Create a DNS server (accessed via the Networks tab).Set the Storage Group Replication Setting as Local Redundant – it’s cheaper and is good enough for test environments in my opinion.Create a Storage Account and allocate to the Affinity Group created above.Create an Affinity Group (accessed via the Settings tab).Below are a few getting started tips Before You Startīefore you get stuck into creating Azure Virtual Machines (VMs) consider doing the following: messing about with virtual servers that I will manage myself, including setting up an Active Directory (AD), SCCM, SCOM etc. I am a sysadmin and not a developer so my focus is on Infrastructure as a Service (IaaS), i.e. This means that I now an Azure subscription as well. Finally convinced my employer to replace my retired TechNet subscription with an MSDN subscription.
0 kommentar(er)
