If you migrated from VMware vRealize Automation 7.x to VMware Identity Manager 3.3.4 or upgraded an NSX-T deployment to VMware Identity Manager 3.3.4, and your deployment includes external VMware Identity Manager Linux connectors, you can migrate your external Linux connectors to external VMware Identity Manager 3.3.4 Windows connectors.

To migrate, you download the migration package from My VMware to each external Linux connector instance, and run the generateClusterFile.sh migration script. The script saves the configuration information from the Linux connector to the cluster-hostname-conn-timestamp.enc configuration package file. You then copy each configuration package file to a separate Windows host, and install a new Windows connector instance using the configuration package file.

Perform this procedure for each external Linux connector instance that you want to migrate.


  • If you have configured any authentication methods on the external Linux connector in addition to password authentication, make a note of the authentication adapter configurations. During connector migration, only the Password authentication adapter is migrated. After you migrate to the new Windows connector, you must reconfigure the other authentication adapters.
  • Download the cluster-support.tgz cluster-migration package from the VMware Identity Manager 3.3.4 Download page on My VMware to the Linux connector virtual appliance. Save the file under the /root directory.
  • Prepare a Windows server for the new, external Windows connector. See System Requirements for VMware Identity Manager Connector (Windows) in Installing and Configuring VMware Identity Manager Connector 2018.8.1.0 (Windows).
  • Download the VMware Identity Manager Connector 3.3.4 (Windows) installer from the VMware Identity Manager 3.3.4 Download page on My VMware to the Windows server you prepared for the external Windows connector.


  1. Log in to the Linux connector virtual appliance as the root user.
  2. In the directory in which you saved the cluster-support.tgz file, run a command such as the following to uncompress the file.
    tar xvfz cluster-support.tgz
    The command extracts two files, one of which is the generateClusterFile.sh file.
  3. Run the generateClusterFile.sh script with the following command that also creates a password.
    ./generateClusterFile.sh password

    Replace password with a password of at least eight characters that includes at least one special character, upper case letter, and lower case letter. You need the password later to migrate the external Linux connector configuration to the corresponding external Windows connector.

    The command creates cluster-hostname-conn-timestamp.enc, an encrypted file that contains the external Linux connector configuration information.
  4. Copy the cluster-hostname-conn-timestamp.enc file from the Linux connector virtual appliance to the Windows server.
    Important: Use a secure method, such as Secure File Transfer Protocol (SFTP), to transfer the configuration file from one server to another as the file contains sensitive information.

    To ensure security, also delete the configuration file from both the old and new servers after migration is finished, and delete old deployments that are no longer needed. See Perform Migration-Related Steps When Configuring the External Windows-Based Connector.

  5. See Perform Migration-Related Steps When Configuring the External Windows-Based Connector for information on performing migration-related steps while installing and configuring the external Windows connector.