An RDS host is a server computer that hosts applications and desktop sessions for remote access. An RDS host can be a virtual machine or a physical server.
In View, an RDS host is a server that has the Microsoft Remote Desktop Services role, the Microsoft Remote Desktop Session Host service, and View Agent installed. Remote Desktop Services was previously known as Terminal Services. The Remote Desktop Session Host service allows a server to host applications and remote desktop sessions. With View Agent installed on an RDS host, users can connect to applications and desktop sessions by using the display protocol PCoIP. PCoIP provides an optimized user experience for the delivery of remote content, including images, audio and video.
The performance of an RDS host depends on many factors. For information on how to tune the performance of different versions of Windows Server, see http://msdn.microsoft.com/library/windows/hardware/gg463392.aspx.
View supports at most one desktop session and one application session per user on an RDS host.
When users submit print jobs concurrently from RDS desktops or applications that are hosted on the same RDS host, the ThinPrint server on the RDS host processes the print requests serially rather than in parallel. This can cause a delay for some users. Note that the print server does not wait for a print job to complete before processing the next one. Print jobs that are sent to different printers will print in parallel.
If a user launches an application and also an RDS desktop, and both are hosted on the same RDS host, they share the same user profile. If the user launches an application from the desktop, conflicts may result if both applications try to access or modify the same parts of the user profile, and one of the applications may fail to run properly.
The process of setting up applications or RDS desktops for remote access involves the following tasks:
- Set up RDS hosts.
- Create a farm. See Creating Farms.
- Create an application pool or an RDS desktop pool. See Creating Application Pools or Creating RDS Desktop Pools.
- Entitle users and groups. See Entitling Users and Groups.
- (Optional) Enable time zone redirection for RDS desktop and application sessions. See Enable Time Zone Redirection for RDS Desktop and Application Sessions.
Because the procedure described in http://support.microsoft.com/kb/179221 affects both desktop and application sessions, it is recommended that you do not create RDS desktop pools and application pools on the same farm if you plan to follow the procedure in the Microsoft KB article, so that desktop sessions are not affected.
If you plan to create application pools, you must install the applications on the RDS hosts. If you want View to automatically display the list of installed applications, you must install the applications so that they are available to all users from the Start menu. You can install an application at any time before you create the application pool. If you plan to manually specify an application, you can install the application at any time, either before or after creating an application pool.
When you create an application pool, View automatically displays the applications that are available to all users rather than individual users from the Start menu on all of the RDS hosts in a farm. You can choose any applications from that list. In addition, you can manually specify an application that is not available to all users from the Start menu. There is no limit on the number of applications that you can install on an RDS host.