45a0601401
* Add quick deployment template for singlae ADDS DC. * Correct API verion error. * Remove AvailabilitySet.SKU property. * Set availabilityset fault domain to 2, update domain to 5. * update the VM managed disk storage account type. * Test managed disk in template * Update availability set sku to Aligned as managed. * update availabilitySets API version to 2017-12-01 to support sku "Aligned". * Update VM size to Standard_DS2_v2. * Test managed disk in VM. * Modify managed disk properties. * "storageAccountType": "StandardSSD_LRS" * test VM API version * correct VM API version to 2017-12-01 * update the API version for all components. * Update Readme.md. Singale DC deployment is successful. * Update vnet DNS to AD DC IP. * Wellsluo dev (#2) * Start to update ad domain HA templates to Managed Disk. Update api version. * Update the VM disk to managed disk. Remove creation the storage account. * update templates link * update templates link with correct _artifactsLocation uri * change data disk size to 20GB. * update 2nd DC dependson. * Change BDC name to adBDC02 since AzS report error when creating disk with name adBDC. * Update VirtualNetwork in vnet.json API version to 2017-10-01. * Remove chagne of adBDC name. * Update metadata.json with latest info. * update metadata.json with updated information. * Update apiVersion to 2017-10-01. * update apiVersion to 2017-10-01. * Update apiVersion to 2017-10-01. * update apiVersion to 2017-12-01. * Update to use managed disk when deploying VM. * Update the VM naming convention. * Update the DSC file to add the DSN forwarder to AzureStack virtual DNS, in order to resolve external DNS names, like site in Internet. Get the xDnsServer DSC module from https://github.com/PowerShell/xDnsServer, latest released version 1.13.0.0. * Update the "Known issue" part. Add issue of external FQDN name resolving. * Correct the error to compose the vmName. * Update change and known issue. * For VM with managed disk deployment template, refer to "active-directory-new-domain". * Update readme.md with changes. Rename original template file to azuredeploy-unmanagedDisk.json * Update deployment Uri to master branch. |
||
|---|---|---|
| .. | ||
| DSC | ||
| nestedtemplates | ||
| README.md | ||
| azuredeploy.json | ||
| azuredeploy.parameters.json | ||
| metadata.json | ||
README.md
Create a new Windows VM and create a new AD Forest, Domain and DC
Description
This template will deploy a new VM (along with a new VNet and Load Balancer) and will configure it as a Domain Controller and create a new forest and domain.
Last update on 2019/11/08.
Components
- 1 Virtual Machine as Active Directory Domain Service domain controller.
- Default VM size: Standard_DS2_v2
- OS: Windows Server 2019 Datacenter
- 1 Nic with static virtual network IP Address: 10.0.0.4
- 1 OS disk and 1 Data disk - Managed Disks.
- 1 Public Load Balancer.
- 1 Public IP address (VIP).
- 1 Virtual Network.
- IP Range: 10.0.0.0/16
- 1 subnet: 10.0.0.0/24
- DNS: 10.0.0.4
- 1 Availability Set for virtual machine.
Deployment
Click the button below to deploy
Known issue
- No external FQDN resolving since the DNS server is currently pointed to the DNS Server in Domain Controller. Workaround: manually add DNS forwarder in DNS Server management console, point to a DNS which can resolve external FQDN, Azure DNS is an option: 168.63.129.16.