Settings tab
On the global Settings tab of Applications, you can configure:
- whether managed applications should be fully implemented, partially implemented or disabled.
- additional settings for the behavior of applications and the Start Menu.
- the defaults that should be used for each new application.
Workspace Control managed applications can be implemented fully, partially or not at all. In a new environment, Applications is disabled: Windows Shell shortcut creation is set to Do not create shortcuts, so that users get the same Start Menu, Desktop and Quick Launch area in their Workspace Control session as they had outside of the Workspace Control session. With this setup, Workspace Control does not manage any of the user's applications. At this point, you can configure applications in the Console, but these are not made available to any users.
When you are ready to start managing users' applications through Workspace Control, you can enable Applications partially or fully:
- To give users Workspace Control-managed applications in addition to their existing, non-Workspace Control-managed applications, choose Windows Shell shortcut creation: Merge with unmanaged shortcuts.
- To give users only Workspace Control-managed applications, choose Windows Shell shortcut creation: Replace all unmanaged shortcuts. This eliminates non-Workspace Control managed applications from the Workspace Control session.
- Replace all unmanaged tiles on the start screen is applicable to user sessions running on Microsoft Windows 8.1 / 2012 R2 / 10.
- If Windows Shell shortcut creation is set to Replace all unmanaged shortcuts, this may lead to unpredictable results for global User Settings that preserve information in %desktop%, %startmenu% or %appdata%\Microsoft\Internet Explorer\QuickLaunch. This does not affect application-level User Settings for those folders.
- For users with a new profile or logging on to a system in a VDI environment that uses a non-persistent/pooled model), Workspace Control automatically creates a tile layout on the user's Start screen that is similar to the default Start screen created by Microsoft Windows 8.1 / 2012 R2 / 10. If you would like to place different default tiles on the user's Start screen, you can create the file DefaultTilelayout.xml (Windows 8.1 / 2012 R2) or DefaultTileLayout_Windows10.xml (Windows 10) and add it as a Custom Resource to Workspace Control, in the root (at Administration > Custom Resources).
The following settings determine the behavior of applications and the Start Menu:
Setting |
With this setting, Workspace Control will: |
---|---|
Autolaunch new applications on refresh if new application is configured to launch automatically |
If access to applications is based on location, and a user starts a Terminal Server session at a certain location, he will have access to the applications that have been configured for that particular location. If the user disconnects from this session and reconnects from a different location, Workspace Control will refresh the Workspace, to update this change. As a result, the user will then have access to the applications that have been configured for the new location. If these applications have been configured for AutoLaunch, selecting this option will automatically launch these applications on a refresh of the Workspace. |
Check actively for disabled applications in Workspace Control shell |
Check for disabled applications each time the user opens the Start Menu. Disabled applications are marked with a red cross. |
Disable Active Setup |
Active Setup compares registry keys at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\%APPNAME% and HKEY_CURRENT_USER\Software\Microsoft\Active Setup\Installed Components\%APPNAME%. If the HKEY_CURRENT_USER registry entries do not exist, or the version number of HKEY_CURRENT_USER is less than HKEY_LOCAL_MACHINE, then the specified application is executed by Active Setup for the current user. Disabling Active Setup may have a positive effect on login times, but certain features (for example Microsoft Internet Explorer and Windows Themes) depend on the actions it performs. A timeout period can be configured for Active Setup. For more details, see ActiveSetupTimeout. |
Disable autolaunch for managed applications |
This option prevents the automatic start of managed applications that have the application-level option Autolaunch at session start configured as Mandatory. Applications that have Autolaunch at session start configured as Voluntary are not affected. |
Select this option to disable Process interception for unmanaged shortcuts globally or for exception tabs. This overrules the application-level setting If managed shortcut was not used: Intercept new process and apply configuration. |
|
Do not show offline applications when computer is online |
Hides applications if the configured connection state does not match the computer's current connection state. If this option is not selected, users who try to start an "offline" application will be confronted with a message. |
Do not show online applications when computer is offline |
Hides applications if the configured connection state does not match the computer's connection state. By default, "online" applications are always shown in the user's Start Menu. When a user launches an application, the connection state of the computer is only checked against the required connection state of the application. This allows the user to change the connection state of the computer (by connecting to the corporate network), to gain access to the application without having to refresh the Start Menu. If this option is not selected, users who try to start an "online" application will be confronted with a message. |
Do not show Workspace Extensions when VDX / Workspace Extender not detected |
Hides applications configured to run as a Workspace Extension on computers on which the Workspace Extender has not been installed. |
Refresh start menu if new software is installed |
Enabling this option will refresh Workspace Control sessions that use the application shortcut mode Merge with unmanaged shortcuts whenever the content of the common Start menu changes due to an (un)install of a software package. As a result, the user's Start menu will reflect this change. After a software package installation has finished, it may take up to 5 seconds before the refresh is performed. This option is not available when Windows Shell shortcut creation is set to Do not create shortcuts or Replace all unmanaged shortcuts. |
Remove all empty menus |
Enabling this option will automatically hide any empty menus (both managed and unmanaged) from the user's Start Menu. |
Remove empty managed menus only |
Enabling this option will automatically remove all managed empty folders in the user's Start Menu. Managed folders are folders that were created on the Start Menu tab at Composition > Applications. |
When offline, start a specific application () instead of Workspace Control taskbar and When online, start a specific application () instead of Workspace Control taskbar |
Start a specific application if the connection state of a computer is "Offline", or if it is "Online". These two settings allow you, for example, to configure a laptop to connect to a published Ivanti Workspace Composer when online and to a local Ivanti Workspace Composer when offline. You can specify which application should start:
It is possible to configure an application timeout and configure the session's behavior if the application is terminated before the set timeout, or when the application exceeds the set timeout. By checking Launch before other actions the application will be run before other actions are performed, except for Automation Tasks and Execute Commands, if these have also been configured to 'run before other actions'. |
In a user session, if a user starts an application using Run as different user / Run as administrator, actions configured for the application (on the Configuration > Actions tab of the application) will not be applied. In this situation, only the settings related to the start of the application (configured on the Properties > Settings tab of the application) are applied:
- Parameters
- Startup style of application
- Process priority of application
- Disable file system redirector on 64-bit systems