7.1

e Select the script action.
f Click OK.
g Congure the Input Parameters that are included in the script action. To preserve the existing
relationship, bind the parameter to the other property.
h Click OK.
User Migration Batch Files Are Ineffective
After upgrading VMware vRealize ™ Automation from 6.2.x to 7.x, the administrator is unable to migrate
users with the provided utilities.
Problem
The migrate-identity-stores.bat or reassign-tenant-administrators.bat les do not migrate users after
upgrade.
Cause
This can happen when you install vRealize Automation in a non-default location.
Solution
1 Open a command prompt on the machine where you installed VMware vCenter Single Sign-On.
2 Change directories to the migration tool root\bin subfolder that is created when you open
vra_sso_migration.zip.
3 Open setenv.bat and change the drive leer in the VC_INSTALL_HOME variable to the drive leer
where you installed vRealize Automation: SET VC_INSTALL_HOME=Non-Default Drive
Leer:\Program Files\VMware.
4 Save your changes and close setenv.bat.
The batch les work as expected.
PostgreSQL External Database Merge Is Unsuccessful
The external PostgreSQL database merge with the embedded PostgreSQL database does not succeed.
Problem
If the external PostgreSQL database version is later than the embedded PostgreSQL database version, the
merge does not succeed.
Solution
1 Log in to the host for the PostgreSQL external database.
2 Run the psql --version command.
Note the PostgreSQL version for the external database.
3 Log in to the host for the PostgreSQL embedded database.
4 Run the psql --version command.
Note the PostgreSQL version for the embedded database.
If the external PostgreSQL version is later than the embedded PostgreSQL version, contact support for
assistance to merge your external PostgreSQL database.
Upgrading from vRealize Automation 6.2.x to 7.1
VMware, Inc. 47