A server runs Windows Server 2008 R2. The Remote Desktop Services server role is installed on the server.
You deploy a new application on the server.
The application creates files that have an extension of .xyz.
You need to ensure that users can launch the remote application from their computers by double- clicking a file that has the .xyz extension.
What should you do?
A.
Configure the Remote Desktop Connection Client on the users’ computers to point to the server.
B.
Configure the application as a published application by using a Remote Desktop Program file.
C.
Configure the application as a published application by using a Microsoft Windows Installer package file.
D.
Configure the application as a published application by using a Remote Desktop Web Access Web site.
Explanation:
Launching Apps from the Desktop
For users who want to double-click documents to launch the application, terminal services now provides the ability to “install” the remote application’s link to the desktop. This process effectively wraps the RemoteApp’s RDP file into a Windows Installer package—an MSI file—that is later installed to desktops in the environment.
At the same time, the installed MSI can modify the file extension associations on the desktop to reroute a double-clicked file to its associated RemoteApp on the terminal server. Figure 3 shows how the file extension associations have been modified on a client system after a Word RemoteApp is installed. Now, double-clicking any of the common Word file extensions will launch Word via the Remote Desktop Connection.
Figure 3 File extension associations that have been altered to launch the Remote Desktop Connection
To create a Windows Installer package out of an existing RemoteApp, first navigate to the TS RemoteApp Manager. Right-click the RemoteApp of interest and select Create Windows Installer Package. By default, all created Windows Installer packages are stored in the location C:Program FilesPackaged Programs, but this location can be changed from within the RemoteApp Wizard. Also configurable within the wizard are the name and port for the server that will host the RemoteApp, as well as server authentication, certificate settings, and TS Gateway settings.
Settings that relate to the application’s location after installation to a candidate desktop are shown in Figure 4. As you can see, it is possible to create a shortcut on the desktop as well as to a location within the Start menu folder. The most important checkbox on this screen is at the very bottom. It’s the checkbox for Take over client settings, and it re-associates any file extension associations for the RemoteApp from the local desktop to the terminal server. This checkbox must be selected if you want users to be able to double-click documents to launch their TS-hosted application. Click Next and Finish to complete the wizard.Please Note: -Since Windows2008R2 Terminal Services (TS) is now rebranded to Remote Desktop Services (RDS)-
Source: http://technet.microsoft.com/en-us/query/dd314392
