RemoteApp and Desktop Connection
Updated: July 20, 2009
Applies To: Windows Server 2008 R2
In Windows Server 2008, Terminal Services introduced RemoteApp programs, which are programs that are accessed remotely through Remote Desktop Services and appear as if they are running on the end user's local computer. In Windows Server 2008 R2, Remote Desktop Services provides administrators the ability to group and personalize RemoteApp programs as well as virtual desktops and make them available to end users on the Start menu of a computer that is running Windows® 7. This new feature is called RemoteApp and Desktop Connection.
RemoteApp and Desktop Connection provides a personalized view of RemoteApp programs, session-based desktops, and virtual desktops to users. When a user starts a RemoteApp program or a session-based desktop, a Remote Desktop Services session is started on the Remote Desktop Session Host (RD Session Host) server that hosts the remote desktop or RemoteApp program. If a user connects to a virtual desktop, a remote desktop connection is made to a virtual machine that is running on a Remote Desktop Virtualization Host (RD Virtualization Host) server. To configure which RemoteApp programs, session-based desktops, and virtual desktops are available through RemoteApp and Desktop Connection, you must add the Remote Desktop Connection Broker (RD Connection Broker) role service on a computer that is running Windows Server 2008 R2, and then use Remote Desktop Connection Manager.
In Windows 7 and Windows Server 2008 R2, you configure RemoteApp and Desktop Connection by using Control Panel. After RemoteApp and Desktop Connection is configured, RemoteApp programs, session-based desktops, and virtual desktops that are part of this connection are available to users on the Start menu of their computer. Any changes that are made to RemoteApp and Desktop Connection, such as adding or removing RemoteApp programs or virtual desktops, are automatically updated on the client and on the Start menu.
Users can use the new RemoteApp and Desktop Connection notification area icon to:
Identify when they are connected to RemoteApp and Desktop Connection.
Disconnect from RemoteApp and Desktop Connection if the connection is no longer needed.
Administrators can create a client configuration file (.wcx) and distribute it to users within their organization so that the user can automatically configure RemoteApp and Desktop Connection. Administrators can also write and distribute a script to run the client configuration file silently so that RemoteApp and Desktop Connection is set up automatically when the user logs on to their account on a Windows 7 computer.
RemoteApp and Desktop Connection will be of interest to organizations that are interested in assigning programs or virtual desktops to users and providing a seamless user experience that is tightly integrated into the Windows 7 client experience.
You must have Remote Desktop Web Access (RD Web Access) deployed within your organization to provide RemoteApp and Desktop Connection to the Start menu on a Windows 7 computer.
RemoteApp and Desktop Connection is available in the following editions of Windows Server 2008 R2:
Windows Server 2008 R2 Standard
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 Datacenter
RemoteApp and Desktop Connection is not available in the following editions of Windows Server 2008 R2:
Windows Web Server 2008 R2
Windows Server 2008 R2 for Itanium-Based Systems