none
Providing alias for Remote Desktop Web Apps

    Question

  • I've set up a RemoteApp server and it works fine and is accessible from both intranet and extranet. However, the address on the intranet is https://servername/rdweb and the address from the internet is https://apps.domain.com/rdweb. I would like to be able to provide a shorter name so the /rdweb doesn't have to be appended. Is there some way to create an alias so for instance on the intranet all I would have to type is https://webapps? It would be great to have an alias setup for access from the internet also so I don't have to remember to add the /rdweb to the url.

    And I know I can just type it in once and then bookmark it, but this is actually for a customer who likes things as simple as possible.


    Jonathan

    Friday, March 29, 2013 3:05 PM

All replies

  • Hi,

    In IIS Manager on your RDWeb server, please select Default Web Site in the left pane.  In the middle pane double-click HTTP Redirect.  Select Redirect requests to this destination and enter the following:

    https://yourserver.yourdomain.com/rdweb

    Select Only redirect requests to content in this directory (not subdirectories)

    Set Status Code to Permanent (301)

    After making the above change please test that you are seeing the desired behavior.

    For more details,refer to here:http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/17576677-f3ca-4f4e-8d41-5f0f3a91231d

    regards,

    Clarence


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    Tuesday, April 02, 2013 7:19 AM
    Moderator
  • A note if doing as above. You may have to add the shortname as a Subject Alternative Name in your rdweb certificate.

    http://blogs.technet.com/b/isablog/archive/2011/10/09/how-to-generate-a-certificate-with-subject-alternative-names-san.aspx

    If not, people that are browsing https://webapps will get a certificate error. If just typing in the name (eg. http), it will work perfectly.


    MCT | MCSE: Private Cloud/Server, Desktop Infrastructure

    Tuesday, April 02, 2013 7:46 AM
  • A note if doing as above. You may have to add the shortname as a Subject Alternative Name in your rdweb certificate.

    http://blogs.technet.com/b/isablog/archive/2011/10/09/how-to-generate-a-certificate-with-subject-alternative-names-san.aspx

    If not, people that are browsing https://webapps will get a certificate error. If just typing in the name (eg. http), it will work perfectly.


    MCT | MCSE: Private Cloud/Server, Desktop Infrastructure

    Thanks much for the help. Your ideas jogged my memory of how I set up redirection on a sharepoint server. It wasn't working quite right and for other reasons with the server I opened a support call to MS. As part of fixing the problem they corrected my redirection and it wasn't to use the standard method as you outlined in your other post, but rather to set up certain bindings.

    So doing this one that same way (as well as adding a zone in internal DNS) now has allowed me to have users just type in https://apps.domain.com from within or without and get to the rdweb server without having to add the /rdweb as part of the url. I'm not sure I can have users type http rather than https like they're able to do with the sharepoint site because with sharepoint there is both a port 80 site and a port 443 site in IIS, whereas with the rdweb site, I'm just using the default web site with both 80 and 443 bindings.

    As for adding the shortname to the certficate, I'm not sure I can do that since I elected to use a wildcard certificate the client already had rather than create a self-signed one. As it is, entering http://apps.domain.com doesn't work, only https works.


    Jonathan

    Tuesday, April 02, 2013 2:37 PM