Simple Desktop Delivery System
Updated: March 23, 2011
Applies To: Windows Server 2008 R2, Windows Server 2008 R2 with SP1
The simplest way to deliver applications from an RD Session Host server is to install the applications on a single server and then have people log into that server via Remote Desktop Connection. To support this model you need to deploy two RDS roles: an RD Session Host server and a RD Licensing Server. You will also need to install the applications on the RD Session Host server.
When you deploy a single server for full desktop connections, users can connect to the RD Session host by typing the server’s name into their Remote Desktop Connection client. Only users with the right to log onto the RD Session Host server and members of the Remote Desktop Users Group will be able to connect via RDP. For more information about the Remote Desktop Users Group, see Configuring the Remote Desktop Users Group.
By default, all users connecting to the full desktop will see the full set of applications installed on the RD Session Host server. They will have the permissions associated with their user accounts, so although they will be able to see (for example) the RDS tools they will not be able to reconfigure the server.
The main benefit to a single-server design for delivering full desktops is that it is a simple way to deliver desktop replacement. In a single server design, you will not need to consider the following:
Ensure that all servers are weighted appropriately for their hardware capabilities, as when deploying servers in a farm in order to load balance connections properly.
Publish applications as RemoteApp programs.
Create a solution for users to discover available applications.
Ensure all servers in the farm use the same certificates.
Implement Web-based single sign-on (SSO) to avoid multiple logons for users.
To determine whether single-server desktop delivery is right for you, consider the decisions in the following table:
Design Decision | Single-server Desktop Delivery | Other Solution | ||
---|---|---|---|---|
Will users run both locally installed applications and applications from an RD Session Host server? |
Users will run applications installed locally and applications from an RD Session Host server. |
RemoteApps will be used in the environment. |
||
Does the user require administrative rights on the machine |
In the RD Session Host server environment, that uses shared sessions; administrative rights cannot be granted to individual users. |
The user requires administrative rights on the machine. |
||
How many users will need access to the RD Session Host server? |
A single RD Session Host server will support all users |
Multiple RD Session Host servers are needed to support all the users. |
||
What is the impact if this single server fails? |
Users can continue working at essential parts of their jobs. |
If the server fails users will not be able to work.
|