Partager via

Overview of TS RemoteApp

  • Article

Applies To: Windows Server 2008

What is TS RemoteApp?

TS RemoteApp enables you to make programs that are accessed remotely through Terminal Services appear as if they are running on the end user's local computer. These programs are referred to as RemoteApp programs. Instead of being presented to the user in the desktop of the remote terminal server, the RemoteApp program is integrated with the client's desktop. The RemoteApp program runs in its own resizable window, can be dragged between multiple monitors, and has its own entry in the taskbar. If a user is running more than one RemoteApp program on the same terminal server, the RemoteApp programs will share the same Terminal Services session.

Users can access RemoteApp programs several ways. They can:

  1. Access a link to the program on a Web site by using Terminal Services Web Access (TS Web Access).

  2. Double-click a Remote Desktop Protocol (.rdp) file that has been created and distributed by their administrator.

  3. Double-click a program icon on their desktop or Start menu that has been created and distributed by their administrator with a Windows Installer (.msi) package.

  4. Double-click a file where the file name extension is associated with a RemoteApp program. This can be configured by their administrator with a Windows Installer package.

The .rdp files and Windows Installer packages contain the settings that are needed to run RemoteApp programs. After opening a RemoteApp program on their local computer, the user can interact with the program that is running on the terminal server as if it were running locally.

Why use TS RemoteApp?

TS RemoteApp can reduce complexity and reduce administrative overhead in many situations, including the following:

  • Branch offices, where there may be limited local IT support and limited network bandwidth.

  • Situations where users need to access programs remotely.

  • Deployment of line-of-business (LOB) programs, especially custom LOB programs.

  • Environments, such as "hot desk" or "hoteling" workspaces, where users do not have assigned computers.

  • Deployment of multiple versions of a program, particularly if installing multiple versions locally would cause conflicts.

Additional references