Well, we have gone and bought some Azure time/space and as one of the Consultants said "It's like leaving some money behind the bar". If that's the case, I'll have a Guinness......
First of all getting access seemed a bit long winded - someone has to gain access to the account and then delegate some sort of server admin role so VMs can be created.
Deploying a VM is pretty easy - New > Virtual Machine > Quick Create (or From Gallery).
Once the VM created you click on the Connect icon down the bottom of the screen and a RDP shortcut is downloaded.
Double clicking on the shortcut, at work, produced the normal failure to connect due to Firewall rules.....
What we needed to do was:
1. Double click on the machine name.
2. In the new Window click on Endpoints links.
3. Change the *PUBLIC PORT to 3389 (same as the PRIVATE PORT).
4. Change the Firewall rules so that 3389 is open to (and from) the *MS Datacentres IP ranges that we use.
* By default MS Windows Azure assigns a port in the dynamic range (49152–65535) for Remote Desktop
* A list of IP ranges per Datacentre can be found here
No comments:
Post a Comment