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. |
||
|---|---|---|
| .. | ||
| CreateADPDC.ps1.zip | ||
| Readme.md | ||
| adVmTemplate.json | ||
| azuredeploy.json | ||
| azuredeploy.parameters.json | ||
| deployPrimaryAD.json | ||
| metadata.json | ||
| nic.json | ||
| vnet-with-dns-server.json | ||
Readme.md
Create a AD domain controller server non-HA with PowerShell DSC Extension
This template will create a AD domain controller Server using the PowerShell DSC Extension; it creates the following resources:
- A Virtual Network
- One Storage Account
- One external load balancer
- One A1 size VM configured as Domain Controller for a new forest with a single domain
The external load balancer creates an RDP NAT rule to allow connectivity to the AD VM created.
Notes
For VM with managed disk deployment template, refer to "active-directory-new-domain".- The images used to create this deployment are
- AD - Latest Windows Server 2012 R2 Image
- The VM size, storage type on which the VM is created , subnet and IP address can be updated before deployment.
- All the resources will be deployed in the same location as the resource group.
- The image configuration is defined in variables - details below - but the scripts that configure this deployment have only been tested with version mentioned above and may not work on other images.
Deploying from Portal
- Login into Azurestack portal
- Click "New" -> "Custom" -> "Template deployment"
- Copy conent in azuredeploy.json, Click "Edit Template" and paste content, then Click "Save"
- Fill the parameters
- Click "Create new" to create new Resource Group
- Click "Create"
Deploying from PowerShell
Download azuredeploy.json and azuredeploy.parameters.json to local machine
Modify parameter value in azuredeploy.parameters.json as needed
Allow cookies in IE: Open IE at c:\Program Files\Internet Explorer\iexplore.exe -> Internet Options -> Privacy -> Advanced -> Click OK -> Click OK again
Launch a PowerShell console
Change working folder to the folder containing this template
# Add specific Azure Stack Environment
$AadTenantId = <Tenant Id> #GUID Specific to the AAD Tenant
Add-AzureRmEnvironment -Name 'Azure Stack' `
<EFBFBD><EFBFBD><EFBFBD> -ActiveDirectoryEndpoint ("https://login.windows.net/$AadTenantId/") `
<EFBFBD><EFBFBD><EFBFBD> -ActiveDirectoryServiceEndpointResourceId "https://azurestack.local-api/" `
<EFBFBD><EFBFBD><EFBFBD> -ResourceManagerEndpoint ("https://api.azurestack.local/") `
<EFBFBD><EFBFBD><EFBFBD> -GalleryEndpoint ("https://gallery.azurestack.local/") `
<EFBFBD><EFBFBD><EFBFBD> -GraphEndpoint "https://graph.windows.net/"
# Get Azure Stack Environment Information
$env = Get-AzureRmEnvironment 'Azure Stack'
# Authenticate to AAD with Azure Stack Environment
Add-AzureRmAccount -Environment $env -Verbose
# Get Azure Stack Environment Subscription
$SubName = <Subscription Name> # The sbuscription name is the offer name by default
Get-AzureRmSubscription -SubscriptionName $SubName | Select-AzureRmSubscription
#Resource group name. Please make sure the resource group does not exist
$resourceGroupName = "adResourceGroup"
$deploymentName = "adDeployment"
$location = "Local"
New-AzurermResourceGroup -Name $resourceGroupName -Location $location
#Start new Deployment
New-AzurermResourceGroupDeployment -Name $deploymentName -ResourceGroupName $resourceGroupName `
<EFBFBD><EFBFBD><EFBFBD> -TemplateParameterFile .\azuredeploy.parameters.json -TemplateFile .\azuredeploy.json