Settings

Enables the application.

Allows Workspace Control to preserve system capacity. E.g. if you specify that the user is allowed to start the application only once and the user tries to start a second instance, he will be prompted whether to return to the open application or to close the open application and start the application in a new window. The maximum # of instances that can be specified is 30, but setting the maximum # of instances to 0 allows an unlimited # of instances.

Specifies the startup style of the application.

Specifies the process priority of the application in the field. A high priority allows for a larger amount of processor capacity, but can result in system freezes. A low priority decreases the chance on system hiccups and freezes, but can make the application slow. When selecting this option, the option Only Workspace Control is allowed to launch this application on the tab Security > Authorized files is selected automatically, to ensure that the application cannot be started unmanaged with a different priority by using e.g. a command prompt or Windows Explorer.

Specifies the required connection state of the computer that grants access to the application. This is useful if Workspace Control is also used on laptops and the application should only be accessible when the laptop is connected to a network. By default, the applications stay visible in the Start Menu.

Hides the application in PowerHelp. The user will not see the availability of this application.

Disables notifications about already running instances of the applications or reaching the maximum number of allowed instances.

Excludes the application from the "New Applications" notification that is shown if a user logs on after new applications have been installed.

Limits the availability of the application to the selected shell.

Specifies the system tray behavior of the application.

Specifies the automatic launch of the application when the user logs on:

• Take no action: The application will not start automatically. The user can change this behavior on the Startup tab of the Workspace Preferences tool.
• Voluntary: Initially, this will start the application automatically, but the user can change this behavior on the Startup tab of the Workspace Preferences tool.
• Mandatory: This will always start the application automatically. The user cannot change this behavior.

When changing configuration to Voluntary, the application will not start automatically for users that previously logged on before this setting was changed. These users can still change Autolaunch behavior using the Workspace Preferences tool.

When configured as Mandatory, the Global Application Setting Disable autolaunch for managed applications can override this behavior.

The application launches automatically after all other logon actions are complete.

This option only applies when the Autolaunch at session start option is set to Voluntary or Mandatory. This option does not apply to user-installed applications.

Disallows the user to select the application to launch automatically.

This option is cleared and disabled when the Autolaunch at session start option is set to Voluntary or Mandatory.

Uses password verification before the user is allowed to launch the application. This is the standard Windows user password.

Excludes the application from CPU Optimization.

Excludes the application from Memory Optimization Limits. If the user reaches the maximum number of applications allowed to run on his desktop, Memory Optimization will allow the "excluded" application to be launched.

Excludes the application from Memory Optimization. This will disable the automatic release of reserved physical memory when the application is just launched and no longer uses it. It will also disable the automatic release of physical memory when the application has been inactive for a while.

Runs the application in a dedicated Virtual DOS Machine process. Use this setting for 16-bit applications only. It does not affect 32-bit applications.

Hides the application in the Start Menu and PowerHelp. The user will not be able to select the application for desktop placement, AutoStart or Quick Launch, but the application will still be able to run.

Only shows the application in the Start Menu of the user if the application`s command line is valid on the computer on which the user has logged on. The application will be hidden in the Start Menu if the application`s command line is not valid. This option also applies to Workspace Extensions.

For Microsoft App-V 5.x application that have Package delivery mode set to a value other than None (on the Properties > General tab), this option is grayed out.

Please note that if you want to make the application available through Instant Passthrough, it is recommendable only to use the setting Do not passthrough if application is available on local computer. The Instant Passthrough settings can be edited at Composition > Applications. Edit the application, go to the Publishing tab and then to the Citrix XenApp Published Application, Settings tab. Click the Settings button and go to the Behavior tab.

Only shows the application in the Start Menu of the user if a specified file (for example a script file) is present at the configured location. The application will be hidden if the file is not present.

The file's location can be on the local computer that user logs on to, or on a network share that can be reached from the user session.

Use of environment variables is permitted. Wildcards can only be used in the filename.

Allows you to integrate with application virtualization solutions other than Microsoft App-V (e.g. Thinstall, Citrix).

On a 64-bit system, starting an application is influenced by folder redirection. Disable this folder redirection to ensure that the application is started from its defined path.