The Settings tab of a managed application is used to configure the following options:
Check this setting to enable the Workspace Control configuration for the managed application.
Uncheck this setting to disable the Workspace Control configuration for the application. When the application is started, it is treated as an unmanaged application.
The Application is enabled setting can be also configured by right-clicking on the application and then selecting Quick Edit > Enable/Disable > Enable or Disable.
Disabling applications via the command line
To disable a managed application in Workspace Control using the command line, Building Blocks are required to do so. This mechanism can be used to update applications using a script and to disable the application before starting the update and enabling it after the update is complete.
Steps to follow:
Export the Workspace Control application as single Building Block (e.g. Internet Explorer.xml on C:\)
Rename the Building Block to Enable_Internet Explorer.xml
Make a copy of the Building Block (application) needed to update and rename the file to Disable_Internet Explorer.xml
Edit the Building Block Disable_Internet Explorer.xml and change <enabled>yes</enabled> to <enabled>no</enabled>
Before starting the update, execute C:\progra~1\respow~1\pwrtech.exe /add C:\Disable_Internet Explorer.xml
Perform the update
After the update is complete, execute C:\Program Files\Workspace Control\pwrtech.exe /add C:\Enable_Internet Explorer.xml
Make sure that the Update agent cache on change option is set to Immediately: Administration> Agents > Settings tab.
Configure this setting to specify the maximum number of instances of the managed application that can be simultaneously opened during a Workspace Control session. This can be used to allow Workspace Control to preserve system capacity.
Value: 0 to 30.
Configuring this setting to zero (0), allows an unlimited number of application instances to be opened simultaneously.
Example: Specify to users that they are allowed to start an application only once and when users try to start a second application instance, they are prompted to return to the already opened application window or to close the opened application and start the application in a new window.
Configure this setting to specify if the managed application starts in either Normal, Minimized or Maximized window style.
Configure this setting to specify the process priority of the managed application. A High priority allocates for a larger amount of processor capacity to the application, but can result in system freezes. A Low priority decreases the chance of system hiccups and freezes, but can make the application run slowly.
When configuring this setting to any option besides Normal, the Only Workspace Control is allowed to launch this application option found under the Security > Authorized Files tab is checked automatically. This occurs to ensure that the application cannot be started unmanaged with a different priority by using, for example, a command prompt or Windows Explorer.
If the application is set back to Normal from a different value, the Only Workspace Control is allowed to launch this application option remains checked. However, it is now possible to uncheck it if desired.
Configure this setting to specify the required Workspace Control connection state of the machine that grants access to the managed application. This is useful when Workspace Control is used on laptops and the application must be accessible only when the laptop is connected to a network.
Select Online connection to specify that the managed application can be started only if the machine is connection to a network.
Select Offline connection to specify that the application can be started only if the machine is not connected to a network.
By default, even if the connection state does not match the configured setting, applications remain visible in the user's Start Menu.
Default: Both online and offline connections
Check this setting to make the managed application unavailable in the user's PowerHelp.
Check this setting to disable notifications about already running instances of managed applications or about reaching the maximum number of simultaneous instances. For more details, see Maximum instances.
Check this setting to exclude the managed application from the New Applications notification shown when users start a Workspace Control session after new applications were installed.
Configure this setting to specify the shell where the managed application is available. For more details, see Shell.
Select Workspace Control Shell to make the application available only when using the Workspace Control Shell.
Select Microsoft Windows Shell to make the application available only when using the Windows Shell.
Default: Both Workspace Control and Windows Shell
Check this setting to hide the application from showing in the Windows system tray when using the Workspace Control Shell.
This setting is unavailable when using only the Microsoft Windows Shell.
Configure this setting to determine the automatic launch of the managed application upon user logon:
Take no action
The application does not start automatically. Users can change this behavior on the Startup tab of the Workspace Preferences tool.
Initially, this starts the application automatically, but users can change this behavior on the Startup tab of the Workspace Preferences tool.
This always starts the application automatically. Users cannot change this behavior.
When changing configuration to Voluntary, the application does 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 Disable autolaunch for managed applications global application setting can override this behavior. This setting is found under Composition > Applications > Settings tab.
Default: Take no action
Check this setting to configure the managed application to start automatically only after all other logon actions are complete.
This setting only applies when the Autolaunch at session start option is set to either Voluntary or Mandatory. This setting does not apply to User Installed Applications.
Check this setting to disallow users from configuring the application to start automatically.
This setting is unchecked and unavailable when the Autolaunch at session start option is set to either Voluntary or Mandatory.
Check this setting to allow the start of the managed application only after users provide their Windows password.
Check this setting to exclude the managed application from CPU optimization.
Check this setting to exclude the managed application from memory optimization limits. If users reach the maximum number of applications allowed to run on their desktop, memory optimization allows the application to be launched.
Check this setting to exclude the managed application from memory optimization. It disables the automatic release of reserved physical memory when the application is just started and no longer uses it. The setting also disables the automatic release of physical memory when the application has been inactive for a while.
Check this setting to configure the managed application to run in its own dedicated Virtual DOS Machine.
This setting applies only to 16-bit applications. It does not affect 32-bit applications.
Check this setting to make the managed application unavailable in the user's Start Menu and PowerHelp. Users cannot create a shortcut to the application on their desktop, assign the application to AutoStart, or pin the application to the Windows taskbar. However, users can still run the application.
Check this setting to show the managed application in the user's Start Menu only if the application’s command line is valid on the computer where the user logs on. The application is unavailable in the user's Start Menu if the application’s command line is invalid.
This setting also applies to Workspace Extensions.
For Microsoft App-V 5.x applications that have the Package delivery mode option (on the Properties > General tab) set to a value other than None, 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.
Configure this setting to only show the managed application in the user's Start Menu if the specified file (for example, a script file) is present at the provided location. The application is hidden if the specified file is not present.
The file's location can be on the local computer that user logs onto, or on a network drive that can be reached from the user session.
Use of environment variables is permitted. Wildcards can only be used in the filename.
Check this setting to allow the managed application to integrate with application virtualization solutions besides Microsoft App-V.
Check this setting to disable folder redirection from influencing the start of the managed application on Windows 64-bit systems. This ensures that the application is started from its defined file path.