The newest member in the A-Team, Ahmed Moseb, along with Yash, helps us with a neat customization that can be done in Remote Desktop Services (RDS) in Windows Server 2012.
In Windows Server 2012, you can either publish the RemoteApps on the Remote Desktop Session Host server (RDSH) or you can publish the full blown desktop. Which means, when you publish an application in the RDSH server, the icon changes from what is shown in screenshot 1 to screenshot 2:
Screenshot 1: No RemoteApp published
Screenshot 2: RemoteApps published.
If you need to give the option of both the clients, then they need to perform the following steps for customizing it and publishing the Remote Desktop as well as RemoteApp icons:
1. Click on Publish RemoteApp programs under the Collection Name.
2. Select Remote Desktop Connection under the RemoteApp programs.
3. Publish the Remote desktop Connection application to the RDWeb.
4. The application is published to the RDweb.
5. Edit the Remote Desktop Connection Program properties.
6. Click on Parameters and select the Always use the following command-line parameters. Type the following in the text box: /v: <FQDN of the RDSH server>.
7. You will find the icon now on the RDWeb Page and you can connect to the Session Host server from the RDweb.
In this way, you give access to the full desktop with the Remote Desktop Connection (RDC) available, as well as the RemoteApps published on the same server.
Hope this helps. Happy Reading!
Doesn't this result in mstsc being launched from the RD Session Host itself in stead launched from the client?
There is a workaround (not sure if this is 100% supported) for this allowing both Remote Apps & Full Desktop by modifying the registry.
When you perform the above mentioned steps, it does the same change to the registry as mentioned in the link provided by you. The registry key change from 0 to 1 from the registry hive might not be supported as it may break the environment unknowingly, but the steps above are completely supported.
But you are correct in your opinion that the RDP will launch from the RD Session Host itself.
Hope this helps.
Perhaps this is what they meant when they referred to "Nested RDP connections" when discussing RDP8.
I did wonder what they were talking about (I have always been able to initiat an RDP connection to a *different* server from an existing RDP session)
It also works if you use the FQDN of the RD Connection Broker, with the added benefit of load balancing across all your RD Session Hosts.
Thanks for your awesome articles!
It also works if you use the FQDN of the RD Connection Broker, with the added benefit of load balancing across all your RD Session Hosts. Thanks for your awesome articles!
Is is possible to point to an app on that server as well? Would be great for compatibility.
Seriously? I have some users who need the session host as their full workspace and some that need just one app. The RD session within a session is clunky and changes the way they work. What a bad design.
Please note, this is not the best solution. Even if you use the FQDN of the Broker the subsequent RDP session will not be load balanced. In order to display the RemoteDesktops option at the same time as the RemoteApps you can use an unsupported registry
switch HKLM\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ Terminal Server\ CentralPublishedResources\ PublishedFarms\ \ RemoteDesktops\
ShowInPortal REG_DWORD 0x00000001