What should you do to ensure that new RemoteApp programs published on Server1 are automatically added to the Start menu?

Your network contains an Active Directory domain named contoso.com.
The domain contains a server named Server1 and a client computer named Computer1.
Server1 runs Windows Server 2008 R2. Computer1 runs Windows 7.
Server1 has the Remote Desktop Session Host (RD Session Host) role service and the Remote Desktop Web Access (RD Web Access) role service installed.
You need to ensure that new RemoteApp programs published on Server1 are automatically added to the Start menu on Computer1.

What should you do?

A.
From RemoteApp and Desktop Connections on Server1, set up a new connection.

B.
From RemoteApp and Desktop Connections on Computer1, set up a new connection.

C.
From RemoteApp Manager on Server1, create an .rdp file. Deploy the .rdp file to Computer1.

D.
From RemoteApp Manager on Server1, create a Windows Installer package. Deploy the package to Computer1.

Explanation:
RemoteApp and Desktop Connection

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.

Source: http://technet.microsoft.com/en-us/library/dd560650(WS.10).aspx

Step-by-Step Client configuration of a RemoteApp and Desktop Connection web feed via the control panel.

The first step is to open the RemoteApp and Desktop Connection Applet:

Click on the link to “Set up a new connection …”

Specify the URL for the web feed:

Click Next and confirm your selection:

You receive confirmation that the connection was successfully added:

And you can then see the connection in the applet:

If you click on the Properties button, you can see the connection’s details and you also have an “Update Now” button that you can use to manually update the list of RemoteApps and Desktops:

Source: http://blogs.technet.com/b/askperf/archive/2009/10/14/windows-7-windows-server-2008-r2-remoteapp-and-desktop-connection.aspx