The Hosted Application Manager module is used to publish remote desktop and web-based applications to Hosted Application modules on the currently selected dashboard and manage launch permissions for those applications.

This module functions outside the realm of the normal permissions hierarchy. It can be viewed by any user with membership in Site Administrators, Security Administrators, or Dashboard Management site-level roles with no regard to permissions assigned to the tab on which the module is placed. For more information on the roles referenced in this section please see the role based security topic. Administrative users can configure additional module settings by clicking the button.

All administrative users have the ability to create, edit, delete, and manage launch permissions for hosted applications.

Adding New Hosted Applications

To add a new hosted application administrative users click either the button which will open the hosted application editor where they will be presented with the new hosted application editor template.

Editing Existing Hosted Applications

To edit an existing hosted application administrative users click the button which will open the hosted application editor where they will be presented with the edit hosted application template.

Hosted Application Attributes

•Application Name: This is the name of the hosted application for admin purposes. It must be unique within the dashboard in which it is defined.

•Type: This is the type of application that will be presented. Valid choices are TerminalServer, Citrix, and URL.

•Locked: If an application is locked it can only be used by members of the Site Administrators or Security Administrators roles.

•Icon URL: Optional. If specified this is the URL of the application icon displayed to the end-users. It is recommended that the image be square 32x32 pixels.

•Icon Name: This is the name of the application as it will appear to the user.

•Icon Group: This is the (optional) name of the group that will contain the application (and other applications in the same group) when displayed to the end-user.

•Description: Optional description that will be visible in the form of a tool tip in most modern browsers.

•Content: For URL type applications this is the fully-qualified URL to the resource that will be displayed to the user. HTTPS is not required but is recommended. If the application type is TerminalServer then this is the content of a .RDP file that will be presented to the user and downloaded to start the remote application session. If the application is Citrix this is the content of an .ICA file that will be presented to the user and downloaded to start the remote application session.

When writing content for Remote Desktop and Citrix hosted applications you can specify any of the following case-sensitive tokens as placeholders for authentication details:

•#WINDOWSDOMAIN# can be used as a place holder for the Hosting Domain from the account profile.

•#WINDOWSUSERNAME# can be used as a place holder for the Hosting User Name from the account profile.

•For security reasons the password can NOT be injected into the content.

Sign RDP Applications

Clicking the Sign RDP Applications will ensure that all .RDP files delivered to clients are signed with the same certificate used to secure the pasPortal web application and related services. This prevents and warning that may appear in browsers or in environments that prohibit download of unsigned content. This only needs to be performed if the value of the content attribute is updated or if the system certificate is updated.

Send comments on this topic.