How do I move the VigilEnt Policy Center (VPC) installation to a different server? (NETIQKB36852)

How do I move the VigilEnt Policy Center (VPC) installation to a different server?

Important: Before attempting this move, back up the VPC database (For versions 2.x and 3.1 the default name is: PentasafeVPC.  For version 4.0 the default name is: NetIQVPC) and back up your VigilEnt Policy Center directory structure.

To move VigilEnt Policy Center (VPC) to a different server, please follow the steps below:

1. Install VPC on the new server. The VPC application must be the same version as the VPC database. If you are currently running VPC 3.0 GA:
   1. VPC 3.0 comes packaged in an installation kit. Double-click the executable (.exe) file to extract the installation to the default directory (C:\Program Files\VPCSetup).
   2. Select the Install now  tab -OR- Browse to C:\Program Files\VPCSetup and double-click installVPC.exe.
      
      

2. Follow the defaults on the installation wizard pages until you get to the page asking for the database you want.  Choose Microsoft SQL instance.  The next page will show the name of the SQL database that will be created, by default it will be named PentasafeVPC.

   Important Note: You must change this database name from the one currently used or the install will replace it with a new, empty database (wiping out your data). This new database is only used to complete the VPC installation. It will eventually be discarded when the database path is mapped to the correct database name.

3. When prompted to enter the parameters of the SQL host and the port:
   1. Enter either the qualified name of the SQL server (if it is in DNS) or enter the IP address of the server. 
   2. Enter the port number of the SQL server.  The default is 1433. 
   3. Enter a SQL Server administrator?s username and password for accessing the SQL Server and click Next.  (The default administrator username (used to connect and create the database on the SQL Server) is SA.  If your Database Administrator cannot give you the SA password, you may need to have them type it in,  or have your Database Administrator create a user account that has the privileges to create databases on this SQL server. Then replace the default ?SA? (userid) with this new userid). 
    
4. Use the default VPC_user  when prompted for the VPC database user, or type in a new username and password.  VPC will use this account for all transactions.
   
   
5. Finish setup.
   
   
6. Test your setup:
   1. Open a browser to the VPC admin site (the default path is http:// localhost:8080/VpcAdmin).  
   2. Go to the Policy Center tab  and select View/Edit Policy.  There should be no policies under Draft, Review, Published or Archived, as VPC is now connected to the new database on the new server.
      
      
7. On the old VPC server, find the db.properties file in the default directory <InstallDir>\Server\shared\classes and copy it.  On the new VPC server, go to the default directory <InstallDir>\Server\shared\classes and paste the old db.properties file in that directory to overwrite the one there.
   
   
8. On the new VPC server stop and restart the VPC service.
   
   
9. Test your installation:
   1. Open a browser to the VPC admin site (the default path is http:// localhost:8080/VpcAdmin).
   2. Go to the Policy Center tab and select View/Edit Policy.  You should see all of your VPC data, since VPC is now connected to.
      the database currently in use.
      
      
10. When you are ready to remove VPC from the old server, go to Add or Remove Programs  in Control Panel and uninstall VPC. Choose Automatic from the uninstall wizard.  When asked, Do you want to perform a rollback? , choose No.

    Notes:

    • This uninstall does not remove the database. 
    • To remove the new database that was created during the (step 1) install, use the Microsoft SQL Server Enterprise Manager.

.

Formerly known as NETIQKB36852

If you are migrating both the VPC server and the database, it is extremely important that you mirror the exact install directory and path from the source VPC server onto the new target VPC server.