I want aunch a VM instance on Windows Azure Virtual Machines to take a look at the Visual Studio 2013 preview. Seems simple enough, right? Just log in to the Azure portal and spin up a new VM from the gallery from an image configured with VS 2013. Then, just step through the Wizard and connect with RDP.
Give the machine a name, select instance size (small, in my case), and specify a username and password and we should be good to go.
Well, yes, and no.
Okay, the instance launches and appears to be running. As far as I know I am being charged for this resource now.
Cool. My instance seems to have a public IP address and I should be able to connect to it via RDP, login using the username and password I specified and party on. Just like Amazon EC2 and Rackspace.
But no! There is a problem.
Try and connect using RDP to actually use the instance and there is an error.
So, what is going on here?
Right now I haven’t the slightest idea. Maybe it is something simple or obvious. Maybe they didn’t enable RDP on the image. Maybe I am doing something stupid. Maybe I need to open a port or set a security group or something. But … at this point I don’t care. I don’t have the time or patience to troubleshoot it.
I’m going to spin up a Windows Sever 2012 instance on Amazon EC2, install the VS 2013 preview myself and take it from there. At least I know I will have no problem connecting to the instance. Amazon IaaS is much more straightforward to use.