How to upload existing on-premises Hyper-V domain controllers to Azure by using Azure PowerShell
This article describes how to upload existing on-premises Hyper-V domain controllers to Microsoft Azure by using Azure PowerShell.
Original product version: Cloud Services (Web roles/Worker roles)
Original KB number: 2904015
On-premises domain controllers that are moved to Azure must have the following components:
- System Volume (SYSVOL) shared directory
- Active Directory Domain Services (AD DS) database
- AD DS log files that are located on one or more drives that do not share the same hard disk as the operating system.
Including these components on different volumes that use the same disk as the operating system is not valid. Such a configuration could result in Jet database inconsistencies because the operating system disk in Azure had Writeback cached enabled.
For more information, refer Safely virtualizing Active Directory Domain Services (AD DS) to deploy Windows Server Active Directory on Azure Virtual Machines.
Prepare the on-premises domain controllers
To prepare the on-premises domain controllers to be uploaded or moved into Azure Infrastructure as a Service (IaaS), follow these steps:
Create a Storage account.
Create an Azure virtual network that has a site-to-site virtual private network (VPN) connection to your on-premises network.
- Create a subnet within the Azure virtual network.
- Define an on-premises domain name system (DNS) server on the Azure virtual network. This is the server that the virtual machines that are running in Azure will use to locate the on-premises domain controllers.
Create an Azure virtual machine.
- If you are uploading the only domain controller in your forest, go step 5.
- If you are uploading an additional domain controller for an existing domain, you should define an on-premises DNS server for the Azure virtual network to make sure that the domain controller locates other domain controllers when it comes online in Azure.
Run the following command:
diskpart san policy=onlineall
If the StopReplicationOnAutoRecovery value exists in the registry of the domain controller, make sure that it is set to zero (0) in case the Distributed File System Replication (DFSR) Automatic Recovery process has to occur.
For information about the StopReplicationOnAutoRecovery registry value, read DFSR event ID 2213 in Windows Server 2008 R2 or Windows Server 2012
Before you restart the computer, set the IP and DNS settings to Automatic (Dynamic).
Prepare the host
To prepare the host that will upload the virtual machines, follow these steps:
Download and install the latest Azure PowerShell version that is listed on the Azure download webpage.
Open an elevated Azure PowerShell Command Prompt window, and then run the
This command starts a browser instance and connects to
https://windows.azure.com/download/publishprofile.aspxWhen you are signed in to your Azure Account, you are prompted to save the management certificate (contains management credentials for your Azure account) in a
Import the downloaded
.publishsettingsfile by running the following command:
Import-AzurePublishSettingsFile <path to folder that contains .publishsettings file>
Upload on-premises VHDs
Upload your on-premises virtual hard disks into your Azure Storage account, and then create the domain controller in an Azure virtual machine. To do this, follow these steps by using the commands as shown:
Start Azure PowerShell, and then retrieve your subscription name by running the
$subscriptionName = 'MY SUBSCRIPTION'
Retrieve your storage account name by running the
$storageAccountName = 'MY_STORAGE_ACCOUNT'
Specify the storage account location to store the newly created virtual hard disks.
Set-AzureSubscription -SubscriptionName $subscriptionName -CurrentStorageAccount $storageAccountName
Select the correct subscription (multiple subscriptions are supported).
Select-AzureSubscription -SubscriptionName $subscriptionName
Retrieve the Azure location and Affinity group name in which the storage account is running by using the Get-AzureAffinityGroup command.
$location = 'Azure_Location' $affinity = 'AFFINITY_GROUP_NAME'
Specify the virtual machine size as either Small, Medium, Large, or ExtraLarge.
$instanceSize = 'Medium'
Specify a cloud service name. Run the
Test-AzureName -Service 'CLOUD_SERVICE_NAME'command to see whether the name is already being used. A return of false indicates that you can use the name.
$serviceName = 'CLOUD_SERVICE_NAME'
Specify the virtual network and the subnet in which your virtual machine will run. Run the Get-AzureVNetSite command to return the virtual network name in the "name" value and the list of available subnets in the "subnet" value.
$vnet = 'VIRTUAL_NETWORK_NAME' $subnet = 'SUBNET_NAME_IN_YOUR_AZURE_NETWORK'
Enter the server name.
$vmname1 = 'MY_VM_NAME'
Enter the path of the virtual hard disks that are to be uploaded.
$sourceosvhd = 'C:\MyVHDsDC1OSDisk.vhd' $sourcedatavhd = 'C:\MyVHDsDC1DataDisk.vhd'
Provide the target upload location to upload the virtual hard disks.
$destosvhd = 'https://' + $storageAccountName + '.blob.core.windows.net/uploads/DC1OSDisk.vhd' $destdatavhd = 'https://' + $storageAccountName + '.blob.core.windows.net/uploads/DC1DataDisk.vhd' Add-AzureVhd -LocalFilePath $sourceosvhd -Destination $destosvhd Add-AzureVhd -LocalFilePath $sourcedatavhd -Destination $destdatavhd Add-AzureDisk -OS Windows -MediaLocation $destosvhd -DiskName 'DC1OSDisk' Add-AzureDisk -MediaLocation $destdatavhd -DiskName 'DC1DataDisk' $migratedVM = New-AzureVMConfig -Name $vmname1 -DiskName 'DC1OSDisk' -InstanceSize $instanceSize | Add-AzureDataDisk -Import -DiskName 'DCDataDisk' -LUN 0 | Add-AzureEndpoint -Name 'Remote Desktop' -LocalPort 3389 -Protocol tcp Set-AzureSubnet -SubnetNames $subnet -VM $migratedVM New-AzureVM -ServiceName $serviceName -Location $location -VMs $migratedVM -VNetName $vnet -AffinityGroup $affinity
Start the virtual machine, move the system-managed page file to the Temporary volume, and then restart the virtual machine.
Contact us for help
If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure community support.