Process interception for unmanaged shortcuts

Workspace Control can intercept processes that are started through unmanaged shortcuts, and treat them as if they were a managed application. Process interception for unmanaged shortcuts detects the start of a process, and checks whether a managed application is available to the user that also uses the same process. If such a match is found, all the settings and configurations for the managed application are applied before the process is allowed to continue.

For example, in a session where Microsoft Word is available as a managed application, a user finds and double-clicks an unmanaged shortcut to Microsoft Word. This launches winword.exe, which Workspace Control intercepts. Workspace Control first checks that Microsoft Word is allowed to start, based on date and time restrictions, maximum number of instances, licensing etc. If so, Workspace Control applies the settings and actions configured for Microsoft Word, such as User Settings, Drive and Port Mappings and Environment Variables. As a result, Microsoft Word starts up, and it has all its familiar Workspace Control configurations for the managed application Microsoft Word.

Configuration

On the Settings tab at Composition > Applications, the option Disable process interception for unmanaged shortcuts determines whether Workspace Control will intercept any processes at all. This option can be set for the global Workspace Model and for Workspace exceptions.

To start using process interception, clear the global option Disable process interception for unmanaged shortcuts, then configure individual managed applications to intercept their processes if started unmanaged. This is determined by the option If managed shortcut was not used (on the application's Properties > Shortcuts tab, under Automatic shortcuts):

• Ignore: Take no additional action. The process will start without any configuration by Workspace Control.
• Intercept new process and apply configuration: Intercept the process and apply the configuration defined for the managed application.

If a process is intercepted that matches several available managed applications, Workspace Control applies the settings and configurations of the first managed application it finds. This may occur if multiple configurations of the same managed application exist.

If a user starts several processes that are intercepted, they are processed one at a time.

A process started from an unmanaged shortcut will continue without any Workspace Control configurations in the following situations:

• if there is no managed application available in the user session for the same process.
• if the managed application is not configured to intercept.
• if process interception for managed shortcuts is disabled.

Process interception for Citrix published applications

To use Process interception for Citrix published applications, set the option Run Workspace Composer to Automatic for servers running XenApp (at Administration > Agents). If an unmanaged Citrix published application is started on these servers, it will always be launched by the Workspace Composer. If there is a managed application that uses the same process and that is configured with If managed shortcut was not used: Intercept new process and apply configuration, it will be intercepted.

Process interception for Microsoft TS Remote published applications

To use Process interception for Microsoft TS Remote published applications, on servers hosting the applications:

• Make sure that the Workspace Composer (pfwsmgr.exe) is started when users log on (for example using the Microsoft Group Policy 'Custom user interface').
• Set the Workspace Control registry value XenDesktop7Intercept.

If there is a managed application that uses the same process and that is configured with If managed shortcut was not used: Intercept new process and apply configuration, it will be intercepted.
With this feature you can, for example, implement Workspace Control in an existing environment, without republishing existing TS Remote published applications.