I have problem when creating VM from a custom created image in gallery. Image is a domain controller. Stuck on Running (Provisioning). I captured the image after sysprep etc.
But when I create VM from an image which is a none domain controller(stand alone) image, it works fine.
Is it because the server is a domain controller? And when you create VM from an image, the Azure ask you to write the administrator username name and password, it is not possible to fill a domain user like "domain\user"
Any idea?
There was an issue for a while where running sysprep /shutdown on Azure causes this behaviour - could it be down to how/when the images were created? -
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown?forum=WAVirtualMachinesforWindows
....If you capture a VM that has been started after sysprep has been run, the guest OS is not in the correct state. The capture operation will succeed, but VMs created from the image will fail to provision successfully, and will ultimately show status Provisioning timed out.
The issue had since been resolved, but it may explain the difference if one image was created at that time once the other hadn't.
To answer your second question - you can't create a new VM AND set it to join a domain at at the same time from the portal but you CAN do that in powershell - Add-AzureProvisioningConfig
which you would use with New-AzureVMConfig
to create a configuration you would feed into New-AzureVM
has switches to provide domain information - name, user and password.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With