After the Omnissa Access instance is deployed, you use the Setup wizard to set passwords and configure the external database properties.
Make sure that you run the Setup wizard using the fully qualified host name. Do not enter the IP address as the name.
Prerequisites
-
The Omnissa Access machine is powered on.
-
The database created in Microsoft SQL server as the external database server. See Create the Omnissa Access Service Database.
For information about specific versions that Omnissa Access supports, see the Omnissa Product Interoperability Matrix.
-
In the Microsoft SQL server, make sure that the database user is granted the db_owner role. Members of the db_owner database role can perform all configuration and maintenance activities on the database. See Change Database-Level Roles in Omnissa Access Service.
-
To enable encryption, the Microsoft SQL server must be configured with a TLS certificate. Make sure that you can access the certificate to upload to the Omnissa Access service.
Procedure
-
Go to the Omnissa Access URL that was displayed when you finished the installation. Enter the fully qualified domain name (FQDN). For example,
https://WS1AccessHostnameFQDN.example.com. -
Accept the certificate, if prompted.
You can update the certificate after the initial set up.
-
In the Get Started page, click Continue.
-
In the Set Passwords page, set passwords for the following administrator accounts, which are used to manage the appliance, then click Continue.
Account Appliance Administrator Set the password for the admin user. You cannot change the admin user name. The admin user account is used to manage the appliance settings. To create a strong password, the passwords must be 8 or more characters long and contain at least one of each of the following.
- Uppercase characters A-Z (Latin alphabet)
- Lowercase characters a-z (Latin alphabet)
- Numeric digits 0-9
- Special characters (!, $, #, %, and so on.)Appliance Root Set the root user password. The root user has full rights to the appliance.
To create strong passwords for the root user and remote user (sshuser), the passwords must be 14 or more characters long and contain at least one of each of the following.
- Uppercase characters A-Z (Latin alphabet)
- Lowercase characters a-z (Latin alphabet)
- Numeric digits 0-9
- Special characters (!, $, #, %, and so on.)Remote User Set the sshuser password. This password is used to log in remotely to the appliance with an SSH connection. -
Set up the external database. In the Database Connection Setup page, select External Database as the database type.
Note Using the internal database in Omnissa Access is not supported in User Acceptance Test (UAT) or production environments.
Important: You select the database type to use when you first deploy the Omnissa Access appliance. You cannot change the database type.
To use the external database, configure the following.
-
For Database Type, select External Database.
-
Configure the following external database settings.
Option Description Authentication Type To use a Microsoft SQL database for the Omnissa Access server, you must create a new database in the Microsoft SQL server. During setup, you select an authentication type for the database.
SQL Server Authentication. See Configure Microsoft SQL Database Using Local SQL Server Authentication Mode for Omnissa Access
- Windows Authentication. See Configure the Microsoft SQL Database with Windows Authentication Mode for Omnissa AccessDomain Name When you select Windows Authentication, enter the domain name. JDBC Server Address Enter database server IP:Port or FQDN:Port. The default port is 1433. Enter as <hostname_or_IP_address:port#>Database Username Enter the CREATE LOGIN user name that you configured when you created the database. See Configure Microsoft SQL Database Using Local SQL Server Authentication Mode for Omnissa Access. Database Password Enter the CREATE LOGIN user password that you configured when you created the database. Database Name This is the CREATE DATABASE name you entered when you set up the data base. For example, saasdb.Encrypt Connection To set up an encrypted connection between Omnissa Access and the Microsoft SQL Server, select Encrypt Connection.
The Encrypt Connection option is not supported when the Microsoft SQL Server is configured in Windows Authentication mode.
Microsoft SQL servers must be configured with a TLS certificate to use the Encrypt Connection feature with Omnissa Access. See Microsoft SQL server documentation to configure the TLS certificate.
Note: An encrypted connection to the database increases the security of data transmitted across networks. However, enabling encryption can slow the performance on the SQL Server.SQL Server Always on To enable SQL Server Always On capability, select SQL Server Always On.
-
-
If you did not upload the root CA signed certificate, click Upload to upload the certificate now. Make sure that the file includes the entire certificate chain in the correct order, primary certificate first, then your intermediate certificate, and then the ROOT certificate. The entire certificate is everything between and including the lines -----BEGIN CERTIFICATE----- and -----END CERTIFICATE---- must be included.
-
Click SAVE.
When you click SAVE, the connection is tested to verify access to the database.
Results
The connection to the database is configured and the database is initialized. When the process is complete, the Setup is complete page appears.
What to do next
To set up a directory, you must first install one or more instances of the Workspace ONE connector. See the corresponding version of the Installing Omnissa Access Connector guide. Before setting up the directory, review Directory Integration with Omnissa Access for requirements and limitations.
Was this page helpful?