Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Moving a PolicyServer database

    • Updated:
    • 10 May 2016
    • Product/Version:
    • Endpoint Encryption 3.1 PolicyServer
    • Endpoint Encryption 5.0
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 8 32-bit
    • Windows 8 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
Summary

Learn how to move a PolicyServer database 3.1 and higher.

Details
Public

To move a PolicyServer database:

  1. Back up the current MobileArmorDB and MobileArmorLog databases.
    1. Navigate to Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.
    2. Open the Databases folder in SQL Server Management Studio and locate the MobileArmorDB and MobileArmorLog database.
    3. Right-click MobileArmorDB and select Tasks.
    4. Click Backup. The backup database box displays.
    5. Select Options tab and choose to overwrite all existing backup sets.
    6. Select General tab and click Add.
    7. Click the box next to the File Name field to choose a location and name to save the file.
    8. Click OK on each box to save the backup database.
    9. Repeat steps C to H for MobileArmorLog database.
  2. Install the Full Disk Encryption database on the new SQL Server using the PolicyServerInstaller .exe file. Below are the things to consider when installing the PolicyServer database:
    • The SQL Server Administrator Account (sa) must be used for initial installation.
    • The PolicyServerInstaller .exe file allows an administrator to create a unique SQL administrator account for the PolicyServer database(s) only.
    • The database can be installed on any distributed database or server cluster.
    • The database can be installed on the default or any named instance.
    • The database installation can be ran from any machine as long as the proper database is entered in the database location fields. The user logged in during the installation must have the right to write on the C:\Windows\System32 directory.
    • The database size is approximately 12 MB but may grow significantly if logs are not cleared.
    • The database can be queried but sensitive fields such as passwords and encryption keys are stored in an encrypted state.
    • The PolicyServer database module allows the installation of both PolicyServer database and PolicyServer Log database.
      • The PolicyServer database stores all users, devices, and groups. This is the staging table for logs.
      • The PolicyServer Log database provides a repository for transactions such as user authentication and user/group/device management, etc. This database is used for long-term storage and is managed by the administrator who has the capability to search the stored data for trends such as security violations.
  3. Install the PolicyServer database.
    1. Run the PolicyServerInstaller.exe file.
    2. Click Accept on the Legal Notice screen.
    3. Click Install.
    4. Select Use the built-in Local System account (recommended).
    5. Click Continue.
    6. Enter the database Server location (localhost, host name, or IP Address), SQL Administrator User Name (sa), and the sa Password.
    7. Click Continue.
    8. Enter the SQL service account User Name for the account to be created.
    9. Enter and re-type the password.
    10. Click Continue, and then click Finished.
  4. Stop the Windows Service PolicyServerWindowsService.
  5. Restore the backup created on the new SQL Server Instance.
    1. Open the Databases folder in the SQL Server Management Studio and locate the MobileArmorDB and MobileArmorLog databases.
    2. Right-click the MobileArmorDB database and select Tasks.
    3. Click Restore database.
    4. On the To database field, select MobileArmorDB.
    5. Select From Device to specify the source from where the backup sets will be restored.
    6. Click the box next to the From device field to locate the backup file.
    7. Click Add to specify the backup media and its location for the restore operation.
    8. Select the previously saved backup database file and click OK.
    9. Click the Options tab and select Overwrite the existing database.
    10. Click OK.
    11. Repeat steps B to J for the MobileArmorLog database.
  6. Remove Schema from the MADB account or the SQL User Account used for PolicyServer SQL Access to MobileArmorDB abd MobileArmorLog.
    1. Navigate to Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.
    2. Open the databases folder in the SQL Server Management Studio and locate and expand the MobileArmorDB and the MobileArmorLog databases.
    3. Select Security and click the Schemas folder.
    4. Double-click the MADB name.
    5. Click Search on the Schema Properties box.
    6. Enter dbo and click Check Names.
    7. Click OK.
  7. Remove the MADB account from Users in the restored MobileArmorDB and MobileArmorLog database portion of the new SQL Server instance.
    1. Go to Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.
    2. Open the Databases folder in the SQL Server Management Studio and expand the MobileArmorDB and the MobileArmorLog databases.
    3. Select Security and click the Users folder.
    4. Right-click the MADB account and click Delete.
    5. Follow steps A to D to delete the MADB account from the MobileArmorLog database.
  8. Add the new MADB account and designate permissions of db_owner, db_datareader, and db_datawriter.
    1. Open the Databases folder in the SQL Server Management Studio and expand the MobileArmorDB and MobileArmorLog databases.
    2. Select Security.
    3. Right-click the Users folder and click New User.
    4. Select a name for the new MADB account and assign the correct permissions.
    5. Click OK.
  9. Install the remaining Endpoint Encryption software package and PolicyServer by running the PolicyServerInstaller.exe file on the new SQL Server.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Install; Upgrade; Migrate
Solution Id:
1059582
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.