Howto move the NetControl/GPOAdmin database to a new SQL Server or drive?
Please read Additional Information below for Disclaimer)
1. On the NetControl server, launch services.msc through Start|Run|Services.msc
2. Stop the Netpro NetControl Server service.
3. On the SQL server, launch the SQL Server Management Studio through Start|Programs|Microsoft SQL Server 2005|SQL Server Management Studio.
4. Connect to the DB Engine.
5. Right-Click on the NetControl database and Select Properties.
6. Click on Files and write down the database file locations.
7. Click Cancel.
8. Right-Click on the NetControl database and Select Tasks|Detach.
9. Check all 3 boxes and Click OK.
10. The database will now vanish from the list of databases.
11. Navigate Windows Explorer to the database file locations from step 6.
12. Move the files to the new location.
13. Launch on the new SQL server, or go back into the SQL Server Management Studio through Start|Programs|Microsoft SQL Server 2005|SQL Server Management Studio .
14. Connect to the DB Engine.
15. Right-Click on the Databases folder and Select Attach.
16. Click Add Button.
17. Click on the databases .mdf file in the location it was moved to.
18. Click OK.
19. Verify the .ldf location is correct.
20. Click OK
21. Close the Databases folder and expand the Security|Login folders.
22. Verify the account that NetControl is using for the database connection has DBO rights over the NetControl database.
23. Perform steps 3 through 22 for the GPOAdmin database.
24. On the NetControl Server, launch ConfigureDB.exe in C:\Program Files\NetPro\NetControl\ConfigureDB.exe
25. Browse to new SQL Server name. If the same SQL server, dont change the Server name.
26. Input the User Account
27. Click Use an existing database and select the NetControl database.
28. Click OK.
29. Click Yes to restart the service.
30. Launch the NetControl Console through Start|Programs|Netpro|NetControl|Console
31. Click on the GPOAdmin node.
32. Browse to new SQL Server name. If the same SQL server, dont change the Server name.
33. Verify the Database name is correct.
34. Verify the Connect to an existing database is checked.
35. Click the Apply button. If the Apply button is grayed out put a space at the end of the database name, then delete the space.
Quest does not provide support for problems that arise from improper modification of the SQL database. SQL Databases contain information critical to your applications. Make sure you back up the database before modifying it. For information on how to backup a SQL database please refer to Create a Full Database Backup (SQL Server)