Logo

Maarten Balliauw {blog}

ASP.NET, ASP.NET MVC, Windows Azure, PHP, ...

About the author

Maarten Balliauw is currently employed as .NET Technical Consultant at RealDolmen. His interests are mainly web applications developed in ASP.NET (C#) or PHP and the Windows Azure cloud platform.
More about me More about me
Send mail E-mail me


ASP.NET MVC Quickly Subscribe to my RSS feed Follow me on Twitter! View Maarten Balliauw's profile on LinkedIn
View Maarten Balliauw's MVP profile

Search

Latest Twitter

    Follow me on Twitter...

    Archive

    Disclaimer

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

    © Copyright Maarten Balliauw 2012


    Windows Azure Remote Desktop Access

    The latest relase of the WIndows Azure platform, portal and tools (check here) includes support for one of the features announced at PDC last month: remote desktop access to your role instances. This feature is pretty easy to use and currently allows you to deploy a preconfigured VM with IIS where you can play with the OS. No real application needed!

    Here’s how:

    1. Create a new Cloud Service and add one Web Role. This should be the result:

      image
    2. Once that is done, right click the Cloud Service and select “Publish…”
    3. In the publish dialog, click “Confiure Remote Desktop connections…”
    4. Create (or select) a certificate, make sure you also export the private key for it.
    5. Enter some credentials and set te expiration date for the account to some far future.
    6. Here’s an example of how that can look like:

      image
    7. Don’t publish yet!
    8. Navigate to http://windows.azure.com and create a new Hosted Service. In this hosted service, upload the certificate you just created:

      image
    9. Once that is done, switch back to Visual Studio, hit the Publish button and sit back while your deployment is being executed.
    10. At a given moment, you will see that deployment is ready.
    11. Switch back to your browser, click your instance and select “Connect” in the toolbar:

      image
    12. Enter your credentials, prefixed with \. E.g. “\maarten”. This is done to strip off the Windows domain from the credentials entered.
    13. RDP happyness!

      image

    Categories: Azure | General | ICT | Scalability | Webfarm

    Comments (6) -

    Sergey United States |

    Monday, February 21, 2011 11:21 PM

    Sergey

    Hi,

    After step 9 publish fails with "The HTTP request was forbidden with client authentication scheme 'Anonymous'.", though I carefully followed instructions on creating and uploading certificates.

    I would appreciate any help.

    Thanks,
    Sergey.

    maartenba Belgium |

    Wednesday, February 23, 2011 8:53 AM

    maartenba

    Have you posted this on the MSDN forums? Should work smoothly...

    chad caldwell United States |

    Thursday, February 24, 2011 9:43 PM

    chad caldwell

    Where is the cert stored on the hard drive when created inside visual studio?

    maartenba Belgium |

    Friday, February 25, 2011 11:07 AM

    maartenba

    In your local cert store (try running certmgr.msc)

    charlie Australia |

    Tuesday, March 15, 2011 4:42 AM

    charlie

    Problem "The HTTP request was forbidden with client authentication scheme 'Anonymous' has been discussed and solved at:
    social.msdn.microsoft.com/.../

    charlie Australia |

    Tuesday, March 15, 2011 4:48 AM

    charlie

    It needs to upload two certificates. One to the service to allow RDP authentication and one to the Management Certificates section of the Azure Portal to allow Service Management API authentication

    Pingbacks and trackbacks (2)+

    Comments are closed