34,333
edits
Changes
→Making RemoteApps Available to Users via TS Web Access
By default, RemoteApps are configured to be accessible via TS Web Access (for details on installing and configuring the TS Web Access service role refer read [[Configuring Windows Server 2008 TS Web Access]]. As outlined above this setting can be checked during the RemoteApp configuration process by verifying that the ''RemoteApp is available through TS Web Access'' box is set in the properties dialog. This setting can be modified at any time by right clicking on the RemoteApp in question on the TS RemoteApp Manager ''RemoteApp Programs'' list and selecting ''Properties''.
Assuming that the RemoteApps are configured for TS Web Access, simply open a browser windows and enter the URL of the TS Web Access page the format of is typically as follows (where ''serverIDserver'' is the name or IP address of the Terminal Server system):
http:''serverIDserver''/ts When a connection has been established the browser will prompt for the user's login and password credentials before displaying the TS Web Access page: [[Image:windows_server_2008_TS_Web_Access_page.jpg|Windows Server 2008 TS Web Access web page]] To launch an application the user simply clicks on the icon for the required application. First to appear will be the ''RemoteApp Starting'' dialog. This will be followed by a settinmgs dialog which allows the user to decide which resources on the local system (such as drives, devices, keyboard, mouse, printers, ports etc) should be made available to the application running on the remote system. this can be particularly useful, for example, if a user needs to print from the remote application onto a local printer, or save a file onto a local disk or USB drive: [[Image:windows_server_2008_remoteapp_local_recourse_access.jpg|Making local resources available to a remote application]] Once the connection is established the remote application will appear in a window on the local desktop just as a local running application would appear. == Making RemoteApps Available to Users via Windows Installer Packages == One alternative to providing RemoteApp access via TS 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, right click on the RemoteApp in question on the TS 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 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. 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 a .xls extention. When configured, file extension association 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 setting 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 ''\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''. As with TS Web Access, the user will be given the option to control which local resources such as devices and printers are to made accessible to the remote application. == Making RemoteApps Available to Users via .RDP Files ==
