Prerequisites for Installing the Omnissa Access Connector

Before you install the Omnissa Access connector, complete the prerequisites that apply to your installation scenario.

• Make sure that you read the Release Notes and check compatibility in the Product Interoperability Matrix.

• Verify that your Windows server meets the requirements listed in Omnissa Access Connector Systems Requirements.

• If you are installing the Kerberos Auth service or the Virtual App service:

  • Join the Windows server to the Active Directory domain.

  • Perform the connector installation as a domain user that is also part of the administrator group on the Windows server on which you are installing the connector.

  • The account used to install the connector must have "Log on as a service" rights on the connector server.

  • During installation, specify the domain user account to use to run the Kerberos Auth service and the Virtual App service. Make sure that the account is part of the Domain Admins group in Active Directory. After the installation is completed, the account can be removed from the Domain Admins group.

    Important:

    • If you plan to integrate Citrix applications and desktops with Omnissa Access, the domain user account that you use to run the Virtual App service must also be a Citrix server Read Only administrator who is able to load the Citrix PSSnapin.

    • The Kerberos Auth service supports only the following special characters in the domain user account password:

      ! ( & % @ / = ? * , . #

      If the password contains any other special characters, Kerberos Auth service installation fails.

• (Kerberos Auth service and Virtual App service only) For the installer to be able to browse to and validate domains and users during installation:

  • The Windows server must be domain joined.
  • NetBIOS over TCP/IP must be enabled.
  • Broadcast traffic should be enabled on the network.

• If you plan to configure proxy server settings, you need the proxy server host name or IP address, port, and, if the proxy server requires authentication, a user name and password. Only HTTP proxies are supported; HTTPS proxies are not supported.

  If you plan to specify non-proxy hosts, hosts that should be reached directly without going through the proxy server, you need the hosts' host name or IP address, and port.

• If you plan to configure a syslog server, you need the syslog server's fully-qualified domain name or IP address, and port. You can configure multiple syslog servers.

  You can set up any of the standard syslog servers available. The connector must be able to reach the syslog server on the configured port, for example, 514 (UDP).

• A trusted SSL certificate is required for the Kerberos Auth service only. The certificate can be uploaded during installation or later. See Uploading an SSL Certificate for the Kerberos Auth Service for requirements.

• If you plan to install the connector in FIPS mode, see Omnissa Access Connector and FIPS Mode (Omnissa Access FedRAMP Only) for additional requirements and prerequisites.