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 SP6 and lower

    • Updated:
    • 3 Apr 2014
    • Product/Version:
    • Endpoint Encryption 3.1 PolicyServer
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
Summary
Learn how to migrate a PolicyServer database SP6 and lower.
Details
Public
To more the PolicyServer database:
  1. Back up the current MobileArmorDB and MobileArmorLog databases.
    1. Go 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 click Tasks > Backup.
    4. Select Options tab and choose to overwrite all the existing backup sets.
    5. Select General tab and click the Add.
    6. Click the box next to the File Name field to choose a location and name to save the file.
    7. Specify the filename and the location in which to save the file.
    8. Click OK on each box to save the backup database.
    9. Do the above procedure to back up the MobileArmorLog database.
  2. Install the Endpoint Encryption database on the new SQL Server.
    Consider the following for the installation:
    • Make sure you have the PolicyServerDataBaseSetup.exe file to install the MobileArmorDB and MobileArmorLog databases on the new SQL instance.
    • The SQL Server Administrator Account (sa) must be used for initial installation.
    • The PolicyServerDataBaseSetup.exe file allows an administrator to create a unique SQL administrator account for the PolicyServer database(s) only.
    • The database may be installed on any distributed database or server cluster.
    • The database may be installed on the default or any named instance.
    • The database installation may run from any machine as long as the proper database is entered in the database location fields.
      The user logged in during the install must have rights to write to C:\Windows\System32 directory.
    • The database is approximately 12 MB in size but may grow significantly if logs are not cleared.
    • The database may 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 the PolicyServer database and the PolicyServer Log database.
    • The PolicyServer database stores all users, devices, and groups, and 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.
    • The Log 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. Double-click the PolicyServerDataBaseSetup.exe icon.
    2. Accept the License Agreement.
    3. Enter the IP Address or hostname of the Database Server.
    4. Enter a database administrator username with privileges to create and update databases in the Authorized Administrator UserID field.
    5. Enter the password of the database administrator in the Authorized Administrator Password field.
    6. Click Continue.
  4. Under New Version, click the Install button for MobileArmorDB.
  5. Enter a database administrator username (new or existing) with a minimum of read/write privileges in the New/Existing Database Administrator User ID field.
    If adding a new account, the purpose of the additional account is to enable the SQL administrator to manage the PolicyServer database without utilizing the SQL Administrator (SA) username and password.
  6. Enter the password for the new/existing database administrator shown in the New/Existing Database Administrator Password field.
  7. Re-enter the password of the new/existing database administrator in the Retype Password field.
  8. Click Continue.
    The initial database install screen redisplays and the Uninstall button is active for MobileArmorDB. This username and password were previously established on the PolicyServer Database Install window in the New/Existing Database Administrator UserID field.
  9. Install the MobileArmorLog Database.
  10. Restore the backups on the new SQL Instance.
    1. Open the Databases folder in the SQL Server Management Studio and locate the MobileArmorDB and MobileArmorLog database.
    2. Right-click MobileArmorDB database and click Tasks > Restore > Database.
    3. Select MobileArmorDB in the To database field.
    4. Select From Device to specify the source from where the backup sets will be restored.
    5. Click the box next to the From device field to locate the backup file to add.
    6. Click Add to specify the backup media and its location for the restore operation.
    7. Select the previously saved backup database file (Example: MobileArmorDB Backup).
    8. Click OK on each box to return to the main Restore Database box.
      The backup database should now be listed in the backup sets to restore box.
    9. Click the Options tab and select Overwrite the existing database.
    10. Elect to leave the database operational and click OK.
    11. Do the same procedure to restore the MobileArmorLog database.
  11. Remove Schema from MADB (this is whatever SQL User Account used for PolicyServer SQL Access to MobileArmorDB and MobileArmorLog) account:
    1. Click 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 Database.
    3. Expand Security and click on the Schemas folder.
    4. Locate the account where MADB is the Owner.
    5. Double-click the MADB name.
    6. Click Search on the Schema Properties box.
    7. Enter dbo and click the Check Names.
      The object name will change to [dbo] once it is found.
    8. Click OK.
  12. Remove the MADB account from Users in the restored MobileArmorDB and MobileArmorLog Database portion of the new SQL Server instance:
    1. Click 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 database.
    3. Expand Security and click the Users folder.
    4. Locate the MADB account.
    5. Right-click the MADB account and click Delete.
    6. Follow the procedure above to delete the MADB account from the MobileArmorLog database.
  13. Add the new MADB account that was created earlier and designate permissions of db_owner, db_datareader, and db_datawriter:
    1. Open the Databases folder in the SQL Server Management Studio and locate and expand the MobileArmorDB and MobileArmorLog database.
    2. Expand Security, right-click the Users folder, and click New User.
    3. Select a name for the new MADB account and assign the correct permissions.
    4. Click OK.
  14. Install the remaining Mobile Armor software package and PolicyServer.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Install; Upgrade; Migrate
Solution Id:
1059583
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.