Set up Your Omnissa Access Environment for Horizon Integration - Access 2412 and later

After setting up your Horizon environment, you must set up your Omnissa Access environment before integrating the Horizon pods and pod federations with the Omnissa Access service.

Using valid certificates signed by a trusted Certificate Authority (CA) for the Horizon Connection Servers is strongly recommended. If you have not obtained CA-signed certificates and are using self-signed certificates temporarily for testing purposes, you must upload the root certificates to the Virtual App service trust store.

Prerequisites

• To integrate Horizon pods and pod federations, you must install the Virtual App service component of the Omnissa Access connector.
• To sync users and groups from Active Directory to Omnissa Access, you must install the Directory Sync service component of the Omnissa Access connector.

Procedure

1. Enable and configure the objectGuid attribute in the Omnissa Access admin console.

   1. In the Omnissa Access admin console, navigate to Settings > User Attributes. In the Custom Attributes section, create an attribute with the name objectGuid. Select Add Row. Select Save to complete the custom attribute creation.

   2. Navigate to Integrations > Directories. Expand the section labelled Mapped Attributes.

   3. In the Attribute Name in Workspace ONE Access column, find the objectGuid attribute. In the Attribute Name in Active Directory column, select objectGUID in the corresponding dropdown.

   4. Navigate to Settings > Login Preferences. Enable the toggle for orgUseObjectGuidForProfiles.

2. If the Horizon Connection Servers have self-signed certificates, upload the root certificates to the Virtual App service trust store.

   1. On the Windows server on which the Virtual App service is installed, run the Omnissa Access connector installer again.

   2. On the Welcome page, click Next.

   3. On the Program Maintenance page, select Add/Remove Services and click Next.

   4. Click Next until the Install Trusted Root Certificates page appears.

   5. On the Install Trusted Root Certificates page, click Browse and upload the certificate.

   6. Save your changes and close the installer.

   7. Restart the Virtual App Service.

3. Ensure that the distinguishedName attribute is mapped to the Active Directory attribute distinguishedName.

   1. Log in to the Omnissa Access console.

   2. Navigate to the Integrations > Directories page.

   3. Select the directory that contains the users and groups with Horizon entitlements.

   4. On the directory page, click Sync Settings, then select the Mapped Attributes tab.

   5. Verify that the objectGuid attribute is mapped to the Active Directory objectGUID attribute.

4. Sync all users and groups with global or local entitlements in Horizon from Active Directory to the Omnissa Access service.

   1. Review which users and groups are currently synced to Omnissa Access by going to the Accounts > Users and Accounts > User Groups pages.

   2. Select Integrations > Directories.

   3. Select the appropriate directory.

   4. Click Sync Settings.

   5. In the Users and Groups tabs, modify the settings if required, and click Save.

   6. On the directory page, click Sync > Sync with Safeguards or Sync > Sync without Safeguards to sync the directory.

      Sync safeguards limit the number of changes allowed during sync. For more information, see Directory Integration with Omnissa Access.

   Note: Users must have the userPrincipalName and distinguishedName attributes set. If the userPrincipalName or distinguishedName attribute is not set for a user, the user might not be able to run desktops and applications.

5. If applicable, establish a connection to multi-domains or trusted multi-forest domains in Active Directory. See Directory Integration with Omnissa Access for information.