Moving Verify Privilege Vault to Another Machine
If you are moving/migrating Verify Privilege Vault to a new machine and have installed IIS and .NET Framework as described in the Installation Guide on the new machine, you do not need to run the installer; you just need to follow the steps below:
-
If you use the "Force HTTPS/SSL" option, disable it by clicking Configuration from the Administration menu, and then click the Security tab, and Edit. You can re-enable the "Force HTTPS/SSL" option after you set up and install an SSL certificate on the new machine.
If you are also moving the SQL Server database, be sure to create a new backup of the database, as this setting is written to it. To move the database, follow the steps in Moving the Microsoft SQL Server Database to Another Machine. -
If you have configured encryption of your key using DPAPI, you will also need to turn this off before continuing with Step 3. To do so, click Configuration from the Administration menu, then click the Security tab. Click Decrypt Key to not use DPAPI and enter your Verify Privilege Vault account password.
-
Copy the folder that holds your Verify Privilege Vault instance to the new computer.
-
Shut down the old web site and recycle its application pool as it is running background threads that are accessing the database.
-
Set up the new folder in Internet Information Server (IIS) as a virtual directory/application under the Default Web Site or as a separate Website. For detailed instructions, refer to Advanced (Manual) Installation in the Installation Guide.
-
If your database server and credentials have not changed, skip this step. If they have changed, follow the steps below:
- Delete the database.config file from the secretserver folder (on the ASP.NET/IIS machine).
- Restart your new Verify Privilege Vault website, so it is running.
- Browse to your Verify Privilege Vault URL \ dbconnectionreset.aspx
http:\\secretserverurl\dbconnectionreset.aspxand you will be prompted to enter your new database connection details. - Enter your new SQL Server and the account information.
- Click Next and the site will connect to the new database. Your site is now pointing the new database.
-
Activate the licenses for the new server by going to the Licenses page.
-
If you are using certs, remember to set them on your new IIS, and then browse to Verify Privilege Vault over HTTPS and re-enable force HTTPS if this was set on the original machine.
-
Re-enable DPAPI if this was disabled in the earlier step.
If you are moving Verify Privilege Vault web application from Windows Server 2008 to 2012 AND your Verify Privilege Vault is below version 8.5, make sure that:
- .Net extensions 3.5 and ASP.Net 3.5 when adding the IIS role on the new server.
- Change the Verify Privilege Vault application pool to 2.0 and recycle the application pool after running the installer.