Omnissa Access On Premises Release Notes

Omnissa Access 26.10

Omnissa Access 26.10 is the latest Omnissa Access release based on the new deployment architecture that was introduced in version 26.07. It is delivered as a set of containerized microservices that run on a Control Plane — an automated platform that installs, runs, scales, and monitors the services that make up Omnissa Access.

This release also includes a new version of the Omnissa Access connector, version 26.10.

Omnissa Access 26.10 continues to include Hub Services, a service co-located with Omnissa Access that lets you design and set up how employees use the Workspace ONE® Intelligent Hub app to access, discover, and connect with corporate resources, teams, and workflows within a company. Users use the Workspace ONE Intelligent Hub app on devices or the Hub portal in a web browser to access the employee engagement features.

Omnissa Identity Service on premises is also included with Omnissa Access 26.10.

IMPORTANT: Upgrade to Omnissa Access 26.10 is available from version 26.07 only.

What's New

Omnissa Access 26.10 includes the following new features and updates.

• Deployment on Nutanix Prism hypervisor: Omnissa Access 26.10 supports deployment on the Nutanix hypervisor in addition to VMware ESXi. On Nutanix, you provide your own AlmaLinux 9.6 virtual machines and run the Omnissa configuration scripts to prepare the machines for Omnissa Access deployment. See Preparing Nutanix Virtual Machines for Omnissa Access Installation.

• New sizing options: A new Extra Small deployment size is now available for smaller deployments. See Phase 1 - Preparing Virtual Machines for Omnissa Access Installation.

• Vertical scaling: You can scale up a single-tenant deployment to the next larger size, for example, from Small to Medium. Scaling down and multi-tenant deployments are not supported. See NextGen Access Vertical Scaling.

• Deployment types: For new deployments, you can now specify a deployment type — Production, UAT, or Development. The Production type requires NFS storage configuration for disaster recovery.

• Outbound proxy configuration: You can configure Omnissa Access to send outbound traffic through an authenticated or unauthenticated proxy server, using the wso access proxy command. You can also specify hosts that bypass the proxy. See CLI Commands.

• Custom root CA certificates: You can now add custom root or intermediate CA certificates to the Omnissa Access service truststore using the wso access add-custom-ca command. Omnissa Access can then establish secure connections to servers whose certificate chain includes any of these certificates. See CLI Commands.

• Support for PostgreSQL Point-in-Time Recovery (PITR): Omnissa Access 26.10 supports PITR, which lets you roll back the database to a specific point in time.

• Access Deployment Wizard 26.10: The new version of the wizard further streamlines the deployment process and supports both new deployments and upgrades. See Deploying Omnissa Access Using the Access Wizard and Upgrading Omnissa Access Using the Access Wizard.

• Upgrade from version 26.07: You can upgrade Omnissa Access 26.07 to version 26.10 using the Access Deployment Wizard, which is the recommended method, or a manual process. See Upgrade.

• Omnissa Access Connector 26.10: A new version of the connector, containing security-related updates and other product fixes, is available with this release. See the Omnissa Access Connector Release Notes.

• New macOS Platform SSO features: Omnissa Access 26.10 supports the following new features for Platform SSO.

  • macOS login using Secure Enclave-based tokens
  • macOS MFA through Access conditional policies
  • Platform SSO Registration during macOS Setup Assistant (ADE)

  Note: The Omnissa Access service must be publicly reachable over the Internet. Platform SSO is not available for environments that do not have connectivity to the Internet.

  For information about configuring Platform SSO with Omnissa Access, see Configuring Apple macOS Platform Single Sign-On (Platform SSO) with Omnissa Access.

• Choice of Authentication extended to first-factor (primary authentication): Omnissa Access supports OR logic at the first-factor (primary authentication) step in access policy rules, extending the existing Choice of Authentication capability that was previously available only for second-factor authentication.

  With this enhancement, administrators can configure access policies where users are presented with a selection of first-factor authentication methods rather than being forced through a sequential fallback chain. This enables scenarios such as:

  • (Authenticator App OR Omnissa Pass) — first-factor choice to support phased user migration between authentication methods
  • (Password OR Kerberos) AND (RADIUS OR RSA) — mixed first-factor choice combined with second-factor step-up choice

  For information about configuring this feature, see Set Up Choice of Authentication Access Policy Rules.

Deprecated Features

Omnissa Access 26.07 and later versions do not include the built-in Key Distribution Center (KDC) used with the Mobile SSO (for iOS) authentication method. Omnissa recommends using the Mobile SSO (for Apple) authentication method instead.

Before You Begin

Compatibility

• Hypervisor: Tested on

  • VMware ESXi 9.x and 8.x
  • Nutanix Prism Central pc.7.3.0.6, Nutanix Cluster Check (NCC) 5.2.0, and Life Cycle Manager (LCM) 3.3

• Operating System: All virtual machines run AlmaLinux 9.6.

• Databases: PostgreSQL (included with Omnissa Access asset bundle)

• Omnissa Access Connector: Omnissa Access Connector 26.10 is compatible with Omnissa Access 26.10.

  See Omnissa Access Connector Release Notes for details about the connector.

• Windows Server (for Connector): See Omnissa Access Connector Release Notes.

• Directory Server (for Connector): See Omnissa Access Connector Release Notes.

• Web Browsers: The latest versions of Mozilla Firefox, Google Chrome, Safari, and Microsoft Edge

• Federal Information Processing Standards (FIPS): FIPS is supported with Omnissa Access FedRAMP only. Use a FedRAMP environment with the Omnissa Access connector installed in FIPS mode.

For the latest compatibility information, see the Omnissa Product Interoperability Matrix.

System Requirements

Omnissa Access 26.07 and later versions, including 26.10, have significantly higher infrastructure and resource requirements than previous appliance-based versions. Review the system requirements and sizing information in Installing Omnissa Access before planning your deployment.

Installation

You can download Omnissa Access 26.10 from Omnissa Customer Connect. Download the following files:

• Omnissa Access asset bundle: Access-asset-bundle-26.10.0.0-601-34434e1.zip
• OS security upgrade package (for upgrade): security-rpms-with-portable-script.tar.gz
• Omnissa Access Deployment Wizard: access-wizard-26.10.zip
• OVA (for deployment on VMware ESXi): alma-minimal-9.6-20261104-063239-minimal.ova
• Configuration scripts (for deployment on Nutanix Prism): external-os-portable-scripts.tar.gz

Note: SHA-256 checksum files to verify file integrity are also available on the download page.

For detailed step-by-step instructions on deploying Omnissa Access, see the Installing Omnissa Access guide.

Upgrade

• Upgrade to Omnissa Access 26.10 is supported from version 26.07 only.

  The following upgrade methods are available:

  • (Recommended) Access Deployment Wizard: Use the wizard to upgrade both the Access asset bundle and the OS security package. See Option 1 - Upgrading Omnissa Access Using the Access Wizard.
  • Manual upgrade: Run the upgrade commands from the bootstrap node. See Option 2 - Upgrading Omnissa Access Control Plane Deployments.

  Before you upgrade, verify that your existing deployment is healthy, and plan an appropriate maintenance window. For more information, see Upgrading Omnissa Access.

• Upgrade from previous appliance-based versions (24.12.x and earlier) is not supported.

  Customers running 24.12.x should deploy a new 26.10 environment and migrate from the legacy deployment to the new solution. Due to architectural changes introduced with the new microservices-based platform, a fresh installation is required. Omnissa recommends performing a side-by-side migration.

For Omnissa Access Connector, see the Omnissa Access Connector Release Notes for supported upgrade paths and procedures.

Known Issues

This release has the following known issue:

Omnissa Access might become unavailable after an Infrastructure/Platform node goes down in a high-availability deployment

When an Infrastructure/Platform node in an Omnissa Access deployment is powered off or becomes unavailable, Access services become unhealthy and users cannot log in.

After the node comes back online, even though health checks report a healthy status, you might still experience issues such as the following:

• Users cannot log in.
• Local administrator login works intermittently.
• Configured policy rules show as undefined in the console.

Workaround:

1. Power on the Infrastructure/Platform node.

2. Log in to the Bootstrap node and go to the cluster working directory, for example, /opt/wss/<cluster_name>.

3. Unseal the cluster:

   sudo wso cp unseal

4. Check the cluster health and service readiness:

   sudo wso healthcheck

   sudo wso access check-service-readiness

5. If you still experience issues, redeploy the following services from the Bootstrap node:

   sudo wso services deploy -s authcontrol

   sudo wso services deploy -s federation

   sudo wso services deploy -s saas

For more information, see Cluster Reboot or Planned Maintenance of Omnissa Access Cluster in Installing and Configuring Omnissa Access.

Documentation

• Omnissa Access documentation
• Omnissa Workspace ONE® Hub Services documentation

Localized Content

See KB article 6000664: Announcing Omnissa Localization Support for information about localized content.

Support Contact Information

Contact Support at Omnissa Customer Connect when you need help with your Omnissa Access deployment. See How to file a Support Request in Customer Connect and via Cloud Services Portal.