At some companies, an administrator might integrate Unified Access Gateway with the third-party OPSWAT MetaAccess application. 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 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.

To use OPSWAT integration, the following requirements must be met.

  • An administrator must configure the Endpoint Compliance Checks feature in Unified Access Gateway. Unified Access Gateway 3.8 or later is required. For information, see the Deploying and Configuring VMware Unified Access Gateway document.
  • You must install OPSWAT Mobile App on the client device. You can download OPSWAT Mobile App from the App Store.

Horizon Client generates a device ID that is unique to the client device. When you start Horizon Client, and OPSWAT Mobile App is installed, Horizon Client prompts you to share the device ID with OPWSAT Mobile App. To share the device ID, tap Share. If you tap Never ask again, Horizon Client does not share the device ID and you are not prompted again. To close the dialog box, tap Cancel.

If you tap Share, OPSWAT verifies the client device's security status and sends a compliance report to the MetaAccess server. If the client device is already registered with OPSWAT, it is enrolled successfully. If the device is not registered with OPSWAT, an error message appears and the device is not enrolled. To return to Horizon Client, tap Return.

You can configure device ID sharing by activating or deactivating a setting in Horizon Client. For more information, see Configure Device ID Sharing with OPSWAT.