Changes

Jump to: navigation, search

Configuring RemoteApps on Windows Server 2008 R2

25 bytes added, 19:07, 1 April 2011
m
Making RemoteApps Available to Users via Windows Installer Packages
One alternative to providing RemoteApp program access via RD Web Access is to create a Windows Installer package which can be used to install the RemoteApp launcher on any client systems which need access. To create a Windows Installer for a RemoteApp program, right click on the RemoteApp program in question on the RemoteApp Manager RemoteApp Programs list and select ''Create Windows Installer Package'' from the menu. When the RemoteApp Wizard welcome screen appears click on Next to proceed to the package setting screen. On this screen, set the target directory where the RemoteApp program launcher is to be installed in the client system. Also on this screen are settings for controlling which server and Remote Desktop Protocol (RDP) port the client system will be directed to in order to launch the RemoteApp. The final setting allows access to the RemoteApp to be protected through the use of certificates.
<google>WIN28BOX</google>
The Next button proceeds to the Configuration screen where settings such as controlling whether the application is listed in the Start menu and Desktop of the client user's desktop after installation. The final option is related to file extension associations. As examples of file extension associations, a Word document has a .doc file extension and an Excel file an .xls extension. When configured, file extension associations ensure that when a user double clicks, for example, on a .doc file, Word is started with the selected file opened and ready for editing. The ''Take over file extensions'' option associates appropriate file extensions with the RemoteApp, such that the RemoteApp is started when a corresponding local file is selected by a user.
Once the settings are complete, proceed to the confirmation screen, review the settings summary and click on Finish to complete the Windows Installer Package creation. Once completed the .msc package can be found in the location specified during the configuration process (by default this is ''C:\Program Files\Packaged Programs''). This file should be copied to any client systems where access to the RemoteApp is required and executed to install the application. Once installed, the RemoteApp can be found in the ''Start -> All Programs -> Remote Programs'' and on the Desktop if the corresponding option was selected during the installer configuration process.
As with RD Web Access, the user will be given the option to control which local resources such as devices and printers are to be made accessible to the remote application and must login in as a user that has either administrative or remote desktop privileges on the RD Session Host.
== Making RemoteApps Available to Users via .RDP Files ==

Navigation menu