Most of the recipes in this chapter are focused on full desktop sessions provided by RDSH servers because this is the most common scenario that I find RDS used for in the field. One additional piece I would like to take a quick look into is RemoteApp publishing. This is the ability to publish individual applications out to remote users from an RDSH server, rather than a full desktop session. It provides a seamless window for the application, allowing the RemoteApp to look and feel like any other program on the user's computer. Let's set up a sample application and test using it from a client computer. For the sake of simplicity in demonstrating this capability, we will use WordPad as our application to publish and launch.
Our work to publish WordPad as a RemoteApp will be performed from our Server 2016 RDSH called RDS1. We will also use a client computer in order to test accessing this application once we are finished publishing it.
To publish WordPad as a RemoteApp, follow these steps:
https://RDS1/RDweb
.
If you do not have a need for users to receive access to a full desktop when they log in to the RDS environment, you have the option of publishing individual applications instead. This can be useful for restricting the resources that employees have access to, or perhaps for someone such as a vendor or a temporary assignment that only needs access to certain programs and data. While this was a very simple demonstration using the WordPad program baked into Windows, you can use this same process with other applications you have installed onto your RDSH servers yourself.
3.146.176.172