OPSWAT Integration for Horizon Windows Client

At some companies, an administrator might integrate Omnissa Unified Access Gateway with the third-party My OPSWAT Central Management. This integration, which is typically used on unmanaged devices in corporate bring-your-own-device (BYOD) environments, activates organizations to define device acceptance policies for Omnissa Horizon Client devices.

For example, an administrator might define a device acceptance policy that requires client devices to be password protected or have a minimum operating system version. Client devices that comply with the device acceptance policy can access remote desktops and published applications through Unified Access Gateway. Unified Access Gateway denies access to remote resources from client devices that do not comply with the device acceptance policy.

Horizon Client obtains and uses the OPSWAT_DeviceID to check the endpoint compliance. The Unified Access Gateway administrator generates this ID in My OPSWAT Central Management in Settings > Integrations > Device Identity, and selects the checkbox for Enable client certificate installation.

Normally, applications downloaded from Unified Access Gateway are run on the client in the context of the user. This behavior can be changed by setting a flag on Unified Access Gateway as documented below. The default flag is RUN_AS_USER.

The following flags are available for Horizon Windows Client devices and take effect for processes with the exe suffix:

• MONITOR_PROCESS: Monitors processes that are specified with this flag. Disconnects from server with an alert when the OPSWAT agent has stopped running, ends the old process and launches a new process.
• REUSE: Checks whether current existing OPSWAT agent is reusable and reuses a previously launched process. If not reusable, ends and relaunches the process.

For more information, see the Deploying and Configuring Unified Access Gateway document.