How do I connect to the VigilEnt Security Manager database after it has been moved from one machine (NETIQKB36614)

goal
How do I connect to the VigilEnt Security Manager database after it has been moved from one machine to another?

fact
VigilEnt Security Manager 4.1

fix

To connect to the VSM database after it has been moved:

1. In the script below, replace qabox24 with the correct server name of the machine where the database is installed.  Please note: This script may have errors on the first run through. If there are errors the first time, run it again. It should have no errors on the second run.
   
2. If you still have errors on the second run with VigilEnt User, run the following command: exec sp_revokedbaccess VigilEnt_Users  and  run the script twice again.
   
3. After editing the script as noted above, copy and paste it into SQL Query Analyzer and execute.
   
   DECLARE @Box VARCHAR(50)
   SET @Box = 'qabox24\VigilEnt_Users'

USE VigilEnt
exec sp_revokedbaccess vigilentservice
exec sp_revokedbaccess VSMConsole
exec sp_revokedbaccess @Box
exec sp_grantdbaccess vigilentservice
exec sp_grantdbaccess VSMConsole
exec sp_grantdbaccess @Box, 'vigilent_users'
exec sp_addrolemember @rolename = 'VigilEntUserAccess', @membername = 'VigilEntService'
exec sp_addrolemember @rolename = 'VigilEntUserAccess', @membername = 'VSMConsole'
exec sp_defaultdb VSMConsole, VigilEnt
exec sp_defaultdb VigilEntService, VigilEnt
exec sp_defaultdb @Box, VigilEnt

Formerly known as NETIQKB36614