Mapping Your Deployment Goals to a Remote Desktop Session Host Design
In this article
Updated: March 23, 2011
Applies To: Windows Server 2008 R2, Windows Server 2008 R2 with SP1
Now that you have identified the goals for your RD Session Host deployment, you can map those to a design as in the following table.
Simple Desktop Delivery System
Users will run applications both locally and from an RD Session Host server.
A single RD Session Host server can support all the users.
You do not expect additional RD Session Host servers in the future.
High availability is not an issue.
No need for:
Administrative permissions on the desktop
Users to install applications to the desktop
Publish applications as RemoteApp programs.
Single Remote Desktop Session Host Server for Desktop Delivery Design
Simple RemoteApp Delivery System
RemoteApp programs display correctly.
A single RD Session Host server can support all the users.
You do not expect additional RD Session Host servers in the future.
High availability is not an issue.
No need for:
Administrative permissions on the desktop
Users to install applications to the desktop
Single RD Session Host Server for RemoteApp Delivery Design
Highly available RemoteApp or desktop delivery system
High availability is an issue.
You expect additional RD Session Host servers in the future.
Ability to add capacity.
No need for:
Administrative permissions on the desktop
Users to install applications to the desktop
Remote Desktop Session Host Farm Design
Before you select an RD Session Host design, you must understand how each deployment works. You should also be sure to review component requirements and configuration details. The following deployment methods are discussed in this guide: