locked
How to create RDP for remoteapp? RRS feed

  • Question

  • It seems that the GUI is missing an option to generate a RDP file to distribute to end users.

    how can i generate a RDP for remoteapps in windows server 2012 and specify terminal services gateway name, internal server name, etc?

    thank you.

    Wednesday, September 5, 2012 9:50 PM

Answers

  • Hi,

    Thanks for your post.

    In Server 2012, we've expanded upon this feature: you can now configure RemoteApp and Desktop Connections on end-user machines via GP, which also enables file type associations to be installed with the connection. I expect you'll see more details on this in a future blog post on the RDS blog.

    Remote Desktop Services Blog

    http://blogs.msdn.com/b/rds/

    Best Regards,

    Aiden


    Aiden Cao

    TechNet Community Support

    Friday, September 7, 2012 7:27 AM

All replies

  • from my understanding there's no more rdp or msi option for remoteapp. You have to use remoteapp feeds.
    Thursday, September 6, 2012 9:59 AM
  • thanks for your response.

    i'm looking in to using remoteapp feeds on alternate ports for small business environments that only have a single public IP and HTTPS is used for exchange web services and small business server's remote web workplace/remote web app functionality.

    Interestingly, i found that even when doing a clean install of 2012, if you use the same internal server name and the app installs to the same path, old RDP files created in 2008 R2 work to connect to the remoteapp on 2012.

    So it seems you could create a RDP file manually, i'm just unsure how you'd get the "signature" section of it which is a long string of random characters when viewing the rdp file in notepad.

    • Proposed as answer by Ryan Grisham Thursday, October 4, 2012 8:30 PM
    • Unproposed as answer by Ryan Grisham Thursday, October 4, 2012 8:30 PM
    Thursday, September 6, 2012 11:52 AM
  • Hi,

    Thanks for your post.

    In Server 2012, we've expanded upon this feature: you can now configure RemoteApp and Desktop Connections on end-user machines via GP, which also enables file type associations to be installed with the connection. I expect you'll see more details on this in a future blog post on the RDS blog.

    Remote Desktop Services Blog

    http://blogs.msdn.com/b/rds/

    Best Regards,

    Aiden


    Aiden Cao

    TechNet Community Support

    Friday, September 7, 2012 7:27 AM
  • I have found a way to get the actual rdp file. First you have to configure the feed in Control Panel\All Control Panel Items\RemoteApp and Desktop Connections.

    which by default is https://SERVERNAME/rdweb/feed/webfeed.aspx

    once you do that it pulls all the published apps in and stores the actual rdp file here: %appdata%\Microsoft\Workspaces\, there will be a GUID folder in there and a resource folder under that that contains the rdp files.

    alternatively, you can get that location from the shortcut it creates in the start menu. (in the target field)

    once you have that rdp file you can distribute it and even make changes to it using notepad. its just a text file with all the settings in it.

    Thursday, October 4, 2012 8:39 PM
  • hi Ryan,

    if i want to configure the feed it says it can't due to problems with the certificate

    any idea?

    thx

    marc

    Tuesday, October 23, 2012 12:01 PM
  • hi Ryan,

    if i want to configure the feed it says it can't due to problems with the certificate

    any idea?

    thx

    marc

    I had to go to https://servername/rdweb and then install the certificate to the trusted root certification authorities, then I was able to publish the feed on my laptop and grab the .rdp file. 

    Thanks for the post guys!  Very helpful. 

    Is there anything else you have to do to the .rdp file when you open it in Notepad to get it to work correctly on Mac?

    Thanks.

    • Proposed as answer by yt7ju Wednesday, May 14, 2014 9:36 PM
    • Unproposed as answer by yt7ju Wednesday, May 14, 2014 9:36 PM
    Wednesday, November 14, 2012 2:28 AM
  • hi localitpro,

    thx for the trick

    it worked flawlessly

    cu

    marc

    Wednesday, November 14, 2012 1:26 PM
  • I have found a way to get the actual rdp file. First you have to configure the feed in Control Panel\All Control Panel Items\RemoteApp and Desktop Connections.

    which by default is https://SERVERNAME/rdweb/feed/webfeed.aspx

    once you do that it pulls all the published apps in and stores the actual rdp file here: %appdata%\Microsoft\Workspaces\, there will be a GUID folder in there and a resource folder under that that contains the rdp files.

    alternatively, you can get that location from the shortcut it creates in the start menu. (in the target field)

    once you have that rdp file you can distribute it and even make changes to it using notepad. its just a text file with all the settings in it.


    Thank you, sir! This worked brilliantly.

    - Frode Henriksen

    • Proposed as answer by Jos Lieben Saturday, March 16, 2019 8:20 AM
    • Unproposed as answer by Jos Lieben Saturday, March 16, 2019 8:20 AM
    Tuesday, April 9, 2013 10:47 AM
  • I just don't understand why Microsoft makes it so difficult - it was a bit troublesome to do this in 2008 and would love a simplier way to create .msi and .rdp files. But here they have just made it even worse! We don't have MS-servers connected to eachother and each one is independent (not member of domain or anything like that). The server I want to run RDP on doesn't even have a website, so I had to activate that, generate certificate and https and follow instructions here to get a work-around.

    In a big environment, with houndres of servers, this is maybe a better way. But please don't forget that not everyone has 100% MS environment and automated everything (it makes it expensive when something goes wrong and you have to be a MS-specialist to figure it out).

    Also, going into control panel and remote app gives "an error occured" when I try to use the tool and instructions above to publish the apps. It does ask for username and password, but after that it stops with the error message. The event-log doesn't reveal anything.

    I guess it's going back to 2008...

    • Edited by Megda Tuesday, July 1, 2014 2:49 AM
    Tuesday, July 1, 2014 1:55 AM
  • Actually this is fairly simple on Server 2012 R2. Im sure you can do this on Server 2012 as well. Once you have the program on your remoteapps. You can log into your https://test.hnnnd.local/rdweb site. Obviously you will have to put your own server name for your rdweb site. 

    Once there you can log in and see all the programs that you have allowed to be in remoteapp. Click on the icon of the program that you want and you will get either an option to open/save an RDP file. Or it will auto-run the program. Since the save file is exactly what you want that part is straight forward.

    Now if you get it to auto run, then you need to disable two add-in from your internet options. 

    >> Internet Options >> Programs tab >> Manage Add-Ons >> Show ( All add-ons) >> *Disable* MsRdpClientShell Class >> *Disable* Microsoft RDP Client Control

    Restart Internet explorer, go back to your rdweb site. Log in, click the icon and now you should have the options to open / save your .rdp file. 

    Don't worry, took me a long time to figure out too. Mine kept auto-loading. 


    Tuesday, December 23, 2014 5:55 PM
  • Actually its even easier than that!

      Open an alternate web browser (anything other than Internet Explorer) to https://yourtswebserver/rdweb 

      Log in as a user that you want an app for.

      click on the app to run and it will by DEFAULT download an .rdp file for you! works great but I DO miss the old admin console for remote app that would do this and make a pretty msi for you.... 

    Thursday, January 22, 2015 12:02 PM
  • If you already have an .rdp file, say from an old remote app and you've moved it to a new RDS server, you simply can open the file in the text editor of your choice and simply change the name of the server.

    Thank you for your post which led me to this discovery!

    Tuesday, June 2, 2015 6:53 PM
  • Aiden,

    This is exactly where I find myself. Apparently not understanding the change in architecture from 2008 to 2012 R2.  I am attempting to migrate T.S. Application access from a 2008 R2 Server to 2012 R2, and clearly not getting the steps.  For minimizing the shock to the end user community, I was hoping to mimic the architecture as closely as possible.  They are all using .rdp files to access the old Server.  Is there an article or paper that you can point me to that would spell out the steps that I should follow to setup the new T.S. Server (now, I guess, referred to as Remote Desktop Services Server)?

    Thanx for any help that can be offered!

    G

    Wednesday, March 30, 2016 6:55 PM
  • Yeah, I was just coming back here to say that i had plowed ahead and discovered exactly that!  I was concerned because the average end user does not like change and we had deployed before by simply handing out .rdp files.  Once I got everything Published and opened a browser to the Server I discovered the downloaded .rdp files, so there should be less complaining when I have to direct users to the new Server.  Just give tehm their new .rdp files and they'll never konw the difference!

    Thanx

    G

    Wednesday, March 30, 2016 8:13 PM
  • Ryan's suggestion does work, however, I am finding is that users who use the file are bypassing the credentials assigned for explicit access to the RemoteApp. As such, it appears anyone using that shortcut (i.e. copied or emailed from another user), has access to the App, if they also have access to the Collection.

    This stinks because it is(was) easy to govern company wide RemoteApp access by allowing Domain Users to the Collection, and then giving the proper Security Groups access to only the RemoteApps they used. Now I'm going to have to lock down Collection access as well unless there is another workaround.

    Monday, December 19, 2016 8:17 PM
  • or just use Edge
    Thursday, March 22, 2018 10:01 AM
  • Hello, if you are still alive and can see this, can you please update this link to wherever this particular blog you mention has been moved?
    Thursday, February 13, 2020 11:39 PM