In an on-premises Omnissa Access service installation, if you change the fully-qualified domain name (FQDN) of the Omnissa Access service, you must also update the FQDN entry in the Directory Sync, User Auth, Kerberos Auth, and Virtual App services' application.properties files if you deployed these services before the FQDN change.
One of the scenarios in which you typically change the Omnissa Access service FQDN is when you place the Omnissa Access service virtual appliances behind a load balancer.
Procedure
-
Log in to the Omnissa Access connector server.
-
For each enterprise service (Directory Sync service, User Auth service, Kerberos Auth service, or Virtual App service) that is installed on the server, edit the
INSTALL_DIR\Workspace ONE Access\enterpriseService\conf\application.propertiesfile and make the following changes:-
If you are editing the Directory Sync service
application.propertiesfile, update the Omnissa Access service FQDN in the following entry:eds.SAAS.endpoint=WorkspaceONEAccessServiceURLFor example:
eds.SAAS.endpoint=https://mysva.example.com -
If you are editing the User Auth service
application.propertiesfile, update the Omnissa Access service FQDN in the following entry:eas.SAAS.endpoint=WorkspaceONEAccessServiceURLFor example:
eas.SAAS.endpoint=https://mysva.example.com -
If you are editing the Kerberos Auth service
application.propertiesfile, update the Omnissa Access service FQDN in the following entry:eks.SAAS.endpoint=WorkspaceONEAccessServiceURLFor example:
eks.SAAS.endpoint=https://mysva.example.com -
If you are editing the Virtual App service
application.propertiesfile, update the Omnissa Access service FQDN in the following entry:eis.SAAS.endpoint=WorkspaceONEAccessServiceURLFor example:
eis.SAAS.endpoint=https://mysva.example.com
-
-
Restart the Directory Sync, User Auth, Kerberos Auth, and Virtual App services.
Was this page helpful?