If your existing VMware Identity Manager™ service is on-premises on a Windows system, to upgrade to 20.01, you must install the product, now named VMware Workspace ONE® Access™, on a Linux system. To facilitate the process, migrate the VMware Identity Manager configuration from Windows to the new Workspace ONE Access installation on Linux.

Starting with version, the Workspace ONE Access service is available on-premises solely on Linux.

To upgrade VMware Identity Manager 19.03 for Linux to Workspace ONE Access, do not perform the migration procedures. Perform the upgrade procedures. See Upgrading to VMware Workspace ONE Access

Important Migration Facts and Considerations

  • The connector version you use with the Workspace ONE Access 20.01 service can vary. When appropriate, migrate your connector instances to the Workspace ONE Access 20.01 connector, which is available solely for Windows systems. See Migrating to Workspace ONE Access 20.01 Connectors.

    However, if you are using Virtual Apps or plan to use Virtual Apps in the future, do not migrate to 20.01 connector instances.

    Important: Citrix, Horizon Connection Server, and ThinApp integrations are not available with the Workspace ONE Access 20.01 connector.
    • To use ThinApp packaged applications, use the VMware Identity Manager connector (Linux) version 2018.8.1.0.
    • To use other Virtual Apps, such Horizon desktops and applications or Citrix published resources, use the VMware Identity Manager connector (Windows) version 19.03.
  • As a best practice, use different IP addresses and fully qualified domain names (FQDN) for the new Linux nodes than you used for your Windows nodes.
  • If your deployment includes a single node without a load balancer and is integrated with Horizon, the migration changes the fully qualified domain name (FQDN) of the Workspace ONE Access service. After the migration to the Linux system, update the Horizon Connection Server with the new FQDN.
  • If the deployment consists of a Workspace ONE Access cluster, perform the migration on the primary node. During post migration, clone the migrated primary node to create the additional nodes of the cluster.
  • As a best practice, preserve the Windows IP addresses until you finish the migration. Using additional IP addresses for your Linux deployment might affect network ranges. Be prepared to update network ranges and to update load balancers accordingly. See VMware Workspace ONE Access Administration.
  • When you export the VMware Identity Manager Configuration, Elasticsearch data (sync-log history and audit events) is not included.
  • If syslog servers are enabled in your Windows deployment, the migration enables the syslog servers in your Linux deployment, too, with no further configuration necessary.
  • If your Windows deployment used an HTTP proxy server, after the migration to the Linux system, you can use the YaST utility to enable the proxy settings. See Workspace ONE Access 20.01 Post-Migration Configuration