AzureStack-QuickStart-Templ.../active-directory-new-domain...
Wei Luo 45a0601401 Update AD related templates to use Managed Disk for VMs. (#458)
* 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.
2019-12-03 11:23:06 -08:00
..
DSC Update AD related templates to use Managed Disk for VMs. (#458) 2019-12-03 11:23:06 -08:00
nestedtemplates Update AD related templates to use Managed Disk for VMs. (#458) 2019-12-03 11:23:06 -08:00
.gitignore Storage spaces direct template for Azure Stack (#358) 2018-07-17 12:32:44 -07:00
README.md Update AD related templates to use Managed Disk for VMs. (#458) 2019-12-03 11:23:06 -08:00
azuredeploy-unmanagedDisk.json Update AD related templates to use Managed Disk for VMs. (#458) 2019-12-03 11:23:06 -08:00
azuredeploy.json Update AD related templates to use Managed Disk for VMs. (#458) 2019-12-03 11:23:06 -08:00
azuredeploy.parameters.json Storage spaces direct template for Azure Stack (#358) 2018-07-17 12:32:44 -07:00
metadata.json Update AD related templates to use Managed Disk for VMs. (#458) 2019-12-03 11:23:06 -08:00

README.md

Create 2 new Windows VMs, create a new AD Forest, Domain and 2 DCs in an availability set

Description

This template will deploy 2 new VMs (along with a new VNet, Storage Account and Load Balancer) and create a new AD forest and domain, each VM will be created as a DC for the new domain and will be placed in an availability set. Each VM will also have an RDP endpoint added with a public load balanced IP address.

Click the button below to deploy

Change

2019-11

  • Rename original deployment to azuredeploy-unmanagedDisk.json.
  • Update deployment to use managed disk for VMs.
  • Update api version based on Azure Stack build 1908.
  • Update availability set to support VMs with managed disks.
  • Update DSC:

Notice

  • The disks of VM will be created during VM creation. Deployment will be failed if there is disk with same name.
  • Need Internet access to download dependencies if starting deployment from Github Uri.

Known Issues

  • This template is entirely serial due to some concurrency issues between the platform agent and the DSC extension which cause problems when multiple VM and\or extension resources are deployed concurrently, this will be fixed in the near future - fixed in managed disk deployment "azuredeploy.json" with changes 2019-11.

  • No deployment button for Azure Stack since Azure Stack portal Uri is customerized, not standard.

    • Workaround: customize the Uri as following format:

      https://YOUR_AZURE_STACK_TENANT_URI/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fwellsluo%2FAzureStack-QuickStart-Templates%2Fwellsluo-dev%2Factive-directory-new-domain-ha-2-dc%2Fazuredeploy.json
      

      Example:

      https://portal.local.azurestack.contoso.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fwellsluo%2FAzureStack-QuickStart-Templates%2Fmaster%2Factive-directory-new-domain-ha-2-dc%2Fazuredeploy.json