February 2011 Entries
How to enable and connect to RDP on a Windows Azure Web Role Instance?

We all know there have been some updates to Windows Azure, and one of the biggest I would say is the capability of being able to remote into the “OS level” of the image running a role.  And I am not talking about VM Role, I am talking about a Web Role for example.

As developers we use Visual Studio, and when we are getting ready to deploy a project, we have the option of enabling this.

Here is how:

1.  We publish our Project


2. On the Deployment dialog, provide all the details for your account, and before clicking OK, click on Configure Remote Desktop connections.


3.  Enable connections and the rest of the configuration.  Now, here is where there is an extra set of steps.  The first thing to know: The certificate used here is different from the other certs you have in place.  I created a new one, the went into certmgr.msc, then to Personal, then I selected the cert I just created.  Did a right-click, then All Tasks > Export.  Because what is needed is a pfx package, make sure when exporting you select to export the private key.


4. Click OK, on the Remote Desktop Configuration screen, now before you click OK on the Deployment, you will need to visit the Azure Portal.
And perform the following:

  • Go to your hosted services. image
  • Then with the service available, select the Certificates folder location.
  • Then, select Add Certificate from the toolbar (more like Azure Portal Ribbon)
  • Provide the details to upload the recently create pfx file.
  • That will create the Certificate.

Click OK on the deployment dialog, this kick off the deployment process.



5. Now, we need to go to the Windows Azure Portal.  Here we will select the Web Role deployed and Configure RDP.




6. Time to test.  Click on the Instance (not the role), this will make the Remote Access Connect Button available.  A file will start the process to be downloaded too



7. You will then be prompted for the credentials you configured.


8.  Validate connectivity …


9. Open IIS Manager …


From here on, this is a way to manage and work with your Instance.
Posted On Sunday, February 27, 2011 10:07 AM | Comments (0)
And just like that, there went February

The best intentions were having me at perhaps posting more than twice a month, and here we are and … well it has been busy.

There has been a lot of SharePoint 2010 already in this first number of weeks of the year, a good amount of TFS 2010, but even better working quite actively on two topics that I enjoy quite a bit … Windows Azure and Application Lifecycle Management.  And there is more to come around those two.

Through the influencers program with Geekswithblogs and I got access to a hosted TFS solution that I am currently testing and will be posting my findings and documenting a good amount of information on that process.

Another great resource has been, and there will be more details on this too.  Pretty exciting stuff!

That is what is going on and what will be coming on here shortly.

Posted On Saturday, February 26, 2011 10:33 PM | Comments (0)
Adventures in Lab Management Configuration: Part 3 of 3

This is long overdue.  But here it is.

In the previous two sections I have discussed on how I got a CMMI v4.2 to take on the same fields as v5 and therefore be able to communicate with MTM and Lab Manager.  And that was quite a success. Yet when I opened up Lab Management while it was fully aware of the VMs being there, it refused to let me enroll them into an environment.  It kept stating there was no suitable host to deploy the VM to, error TF259115.

This was an indication something was not matching the expected network configuration between TFS and Hyper-V/SCVMM.

So, here are a couple of things that took place:

  1. Verified the network segment specified for network isolation matched what was configured physically for either DHCP or manually assigned IP addressing for the guest VMs
  2. Made sure TFS was fully aware of the configuration settings for the network location name.  For that I issued:  tfsconfig lab /settings /networklocation:”<name of the network location configured in SCVMM”

On that last item, that was key to making sure Lab Management communicated with the VMs and for it to allow enrollment into the new Virtual Environment.

Posted On Tuesday, February 15, 2011 7:56 AM | Comments (0)
Disclaimer: The views expressed on this blog are my own and do not necessarily reflect the views of my employer.

Creative Commons License

Check out my profile!

INETA Community Speakers Program

Follow enriquelima on Twitter
Locations of visitors to this page