Hi Karlo88,
Thanks for posting here.
If you have created the machine and it says Running ( provisioning) for a very long time.
I suggest you the following options.
The two most common cases for this are:
1. To resolve this issue: Remove this VHD as an image and instead add it back as a Disk with an Operating System. You can then boot the disk, run "sysprep /generalize" and then capture the VHD as an image.
2. The second case is if there is an unattend.xml file located on the uploaded VM in one of the directories listed in Implicit Answer File Search Oder in the following article:http://technet.microsoft.com/en-us/library/cc749415.asp. To resolve this issue
you can remove the VHD as an image, add it back as a disk without an operating system, and then attach the disk to a running VM to remove the unattend.xml files. Once the files have been removed the VHD can be readded as an image and it should work correctly.
This is due to the fact taht when an image is deployed the unattend.xml file must come from the ISO image that is attached to the Virtual Machine by Windows Azure as part of VM provisioning from an image.
An unattend.xml on the VHD itself, maybe in %windir%\Panther\Unattend.xml, that could be conflicting with the one on the provisioning ISO.
When the VM is provisioned, an ISO is attached with an unattend.xml that drives sysprep to do things like set the computer name and enable RDP.
And If you cant access the server :
All virtual machines that you create in Azure can automatically communicate using a private network channel with other virtual machines in the same cloud service or virtual network. However, computers on the Internet or other virtual networks require endpoints
to direct the inbound network traffic to a virtual machine.
Refer the link :
https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-set-up-endpoints/
Hope this helps you.
