How to migrate vRanger configuration and license (4042855)

Before getting started, please note the following:

• It is not possible to upgrade from any version lower than 6.1 to any of the latest versions of vRanger.
• In order to recover, upgrade, or merge licenses, please contact Quest Licensing Assistance.
• It is recommended to install SQL Management Studio in order to perform the database backup and restore process.
• Please take note of the current location of the vRanger database. If SQL has been installed using the vRanger embedded installer, the instance name is called VRANGERPRO. In order to identify the name of the SQL instance name, open services.msc and find the SQL Server service. The name of the instance will be seen next to the SQL Server in parenthesis. As an example, SQL Server (VRANGERPRO) means there's an SQL instance called VRANGERPRO. 
• The migration needs to be performed using the same vRanger installer or higher. This procedure cannot be used to rollback the configuration to a previous version.

The vRanger configuration is stored in a SQL database, and it contains the job/task history, inventory connection details, repository configuration, and the job configuration. If the SQL database is installed locally in the vRanger application server, you can migrate the database using the following steps:

1. In order to backup the database, stop the Quest vRanger service.
2. Backup the current vRanger database:
   1. Start SQL Management Studio and connect to the VRANGERPRO SQL instance. 
   2. Click on the plus (+) sign next to Databases.
   3. Right-click on the vRangerPro DB, point to Tasks, and click on "Back Up...".
   4. In the backup wizard, you can change the location of the backup destination if you do not want to use the default path, then press "Ok".
3. Install vRanger in the new server which will install the application along with a SQL Express instance. Optionally, you can choose to install a new full SQL edition or you can restore the database in an external dedicated external server.
4. Stop the Quest vRanger Service in the new server.
5. Restore the database overwriting the newly created database using SQL Management Studio.
   1. Start SQL Management Studio and connect to the VRANGERPRO database.
   2. Right-click on vRangerPro DB, point to Tasks, point on Restore, and Click on Restore.
   3. Under "Source for restore" select the "From Device" radio button and press on the ellipsis "...".
   4. Select the file of the backup that was performed (it may have to be moved from the location where it was stored).
   5. On the left side, click on Options and place a check on "Overwrite the existing database" and click OK.
6. (OPTIONAL) If the vRanger version installed in the new server is higher than the previous server, run the vRanger installer and choose to modify the installation in order to upgrade the database configuration options to the same version of vRanger that is installed.  
7. Start Quest vRanger Service.
8. Update the password for the following objects:
   1. VMware vCenter / ESXi passwords.
   2. Hyper-V SCVMM / Failover Cluster / Host. 
   3. Physical machines.
   4. vRanger repositories.
9. Re-run any task to confirm the migration has been completed successfully.

In order to migrate the license, locate the vRangerLicense.ASC file in the vRanger installation directory (the default installation directory is "C:\Program Files\Quest\vRanger"). Copy this file to the new vRanger server and then apply it by following these steps:

1. Open the vRanger UI. 
2. Click on Tools > Options.
3. Click on Licensing > Product. 
4. Click on "Add New License" and choose the copied license file. 
5. Click on Licensing > Virtual Machine Hosts & Physical Machines to assign the license to the required hosts/machines.