You manage a server that runs Windows Server 2008 R2 with the Remote Desktop Services and
Application Server roles. Your company uses a custom Line-of-Business (LOB) application that
generates document files with the “.lob” custom filename extension. The files can be opened only by
the LOB client application, which resides on the Remote Desktop Session Host (RD Session Host)
server. The
application is accessible as a RemoteApp application. Users logging in to a Remote Desktop session
on the RD Session Host server are able to double-click a .lob file and open the LOB application
automatically. You need to enable users to open the RemoteApp application by double-clicking a
.lob file on their client computer. What should you do?

A.
Install a custom administrative (ADM) template on the client computers and refresh Group Policy.

B.
Deploy a Windows Installer (MSI) package for the RemoteApp application to the client computers.

C.
Distribute the URL for the RemoteApp application to the users.

D.
Copy a Remote Desktop Protocol (RDP) package for the RemoteApp application to the client
computers.

Explanation:
At this point you should see the program you chose to deploy as a RemoteApp in the RemoteApp
Programs list at the bottom of the RemoteApp Manager. The next step is to create an .rdp or .msi
file to run the RemoteApp on your client. The .rdp file will be able to open your RemoteApp when
users double-click on it, but it will not associate a file extension with the RemoteApp. To make the
file association you need to create an .msi file for your RemoteApp. When you run the .msi file on a
compatible client it will setup the file association and create icons (which you can configure).
http://www.enterprisenetworkingplanet.com/windows/article.php/3777631/Configure-MicrosoftsRemoteApp-for-Terminal-Services.htm