Introducing RemoteApp and Desktop Connections

  • Comments 19

Since the debut of RemoteApp in Windows Server 2008, Windows users have been able to enjoy remote applications with the same look and feel as local applications. RemoteApp and Desktop Connections is a new feature in Windows 7 and Windows Server 2008 R2 that builds on this by bringing RemoteApp programs to the Start menu, giving them the same launch experience as local applications.

RemoteApp and Desktop Connections works with a new feature of Remote Desktop Web Access (RD Web Access)--the RemoteApp and Desktop Connection feed. Instead of presenting RemoteApp programs in the form of a web page, this feed presents them in a software-parsable XML document.

With RemoteApp and Desktop Connections, the user subscribes to a feed of RemoteApp programs by supplying the client software with its URL. After the user has subscribed to the feed (that is, created a “connection”), his work is done. From then on, the RemoteApp and Desktop Connections client software will make sure that the resources in this connection are placed in the user’s Start menu.

The RemoteApp and Desktop Connections feature offers several benefits:

  • RemoteApp programs launch from the Start menu just like any other application.
  • Published Remote Desktop connections are included alongside RemoteApp programs on the Start menu.
  • Changes to the published connection (such as newly published RemoteApp programs) are automatically reflected on the user’s Start menu, without any effort on the user’s part.
  • RemoteApp programs can be easily launched with Windows Search.
  • Users only have to log on once, to create the connection. From that point on, updates happen with no prompt for user credentials.
  • RemoteApp and Desktop Connections does not require domain membership for client computers.
  • RemoteApp and Desktop Connections benefits from new features in Windows Server 2008 R2, such as Personal Desktop assignment or per-user application filtering.
  • RemoteApp and Desktop Connections is built on standard technologies such as XML and HTTPS, making it possible for developers to build solutions around it. It also offers APIs that allow the client software to support other types of resources, in addition to RemoteApp programs and Remote Desktop connections.

Getting started

Setting up a new connection is simple. Just follow these steps:

1. Open RemoteApp and Desktop Connections in Control Panel, either by opening Control Panel, or by using Windows Search.


2. Click Set up a new connection with RemoteApp and Desktop Connections. This will start the new connection wizard.


3. Enter the URL of the connection. This URL will generally be of the form:


Here, “<servername>” is the host name of the RD Web Access server. The wizard should look like this:


Note: RemoteApp and Desktop Connections uses HTTPS to connect to the server. In order to connect properly, the client operating system must trust the SSL certificate of the RD Web Access server. Also, the server name in the URL must match the one in the server’s SSL certificate.

4. Click Next.


5. Click Next. The RemoteApp and Desktop Connections client software will now contact the RD Web Access server to set up the connection. You will be prompted to authenticate to the web server.


6. Enter your credentials. Now the RemoteApp and Desktop Connections client software will finish setting up the connection.


In a moment, the process will complete, and you will see a wizard page that summarizes the results.


7. Click Finish.

Now the RemoteApp and Desktop Connections Control Panel will show your newly created connection:


You can return to this summary page anytime you need to manage your connections.

The Start menu will now contain the RemoteApp programs from the new connection:


You can also access these programs by using Windows Search:


Coming soon

In future posts, we will discuss:

· How administrators can help users set up RemoteApp and Desktop Connections without entering a URL

· How to set up RemoteApp and Desktop Connections automatically on managed computers, by using Group Policy Objects and a script

· How developers can build onto RemoteApp and Desktop Connections to make it even more powerful

Leave a Comment
  • Please add 8 and 2 and type the answer here:
  • Post
  • PingBack from

  • How do you change the name od the remote desktop connection? default is "Remote Desktop Services Default Connection". In you screenshot it is "Contoso applications".

    Where is the point i can configure this.

    Thanks for the info.

  • Is it possible to configure the compression algorithm used for the transmission of the GUI of the application. Let say I am using Paint with remoteApp, how can I tweak remoteApp setting so that a 24 bit image will not be degraded by the compression algorithm.


  • RDP does not use lossy compression.

    Rob [MSFT]

  • When RDWA pointing to ‘One or more RemoteApp sources”, then the setting are coming from %Windir%\Web\RDWeb\App_Data\RDWebAccess.config file on RDWA server machine at ‘WorkspaceSettings’ element.

    When RDWA pointing to “An RD Connection Broker server”, you need to go to Connection Broker machine, and in “Remote desktop connection manager” modify the connection settings.

    You can verify the RDWA source in ‘Configuration’ tab

  • I need to configure Remote App as an activeX control in my own container in C#. I found Microsoft RDP Client Control (c:\windows\system32\mstscax.dll). Using Windows Forms ActiveX Control Importer aximp.exe generated MSTSCLib.dll and AxMSTSCLib.dll out of mstscax.dll. When we are trying to use component like follows in code.

    private AxMsRdpClient myAxMsRdpClient;

    myAxMsRdpClient = new AxMsRdpClient();

    ((ISupportInitialize) (myAxMsRdpClient)).BeginInit();

    int nColorDepth = myAxMsRdpClient.ColorDepth;

    int nCipherStrength = myAxMsRdpClient.CipherStrength;

    It is throwing exception "System.Windows.Forms.AxHost+InvalidActiveXStateException".

    Am I missing any further initialization? Kindly help.

  • I want to provide a access to application published in RemoteApp multiple times, but keeping remote login  id common for all users. How will it be configured?

    Workaround is- Publish multiple copies of that application and give access of all to that user id.

    After login by same id by each user, they will see all those applications with diff names say "app", "copy of app" etc. And each one of them has to use and bind to the application icons.

    Need to validate this with expert opinions.

  • Is the article on "How to set up RemoteApp and Desktop Connections automatically on managed computers, by using Group Policy Objects and a script" available?  If so, please link to it.

  • You can use the script here to install a connection from the command-line:

    To install a connection through GPO, have this script run as a user login script.

  • what is url and what I have to type and I can t to set up it

  • To Jochen

    Change all Page Titles by editing the %WinDir%\Web\RDWeb\App_Data\RDWebAccess.Config file line:

    <WorkspaceSettings Name="YOUR TEXT HERE" ID="servername.domain.suffix" Description="" />

  • HI!,

    I have configured a remote desktop and remote applications.

    I would like to know is it possible to access remote applications within the remote desktop?

    Gateway - RDGW01 -

    web server - RDWEB01 -

    connection broker - RDCB01 -

    Directory server - RDAD01 -

    remote desktop - RDSH01 -

    remote application - RDAPP01 -

    on central gateway I did nating to access using public IP.

    so when I connect to Remote desktop & tried to configure remote app using control panel using internal IP - it failed with certificate failed.



  • Nice! Thank you. That makes life a lot easier.

  • using remoteapp test file *.rdp to test remoteapp servers, return "the remote computer does not support remoteapp remote service" .

    why has this error, thanks for the info.

  • Is there a method of organising the Start Menu - Desktop connections folder. If you start publishing many applications it can get very busy (we are 25+) which makes it difficult for users.

    If you could publish the folder to the Start Menu top instead of two levels down (Programs->Remote App->Contoso->Apps that would make usability a lot better too.

Page 1 of 2 (19 items) 12

Introducing RemoteApp and Desktop Connections