If the Policy Server becomes corrupted or inaccessible, it is recommended to perform a clean uninstall (except for the database as it will be needed). Do the following:

1. Re-run the PolicyServer Installer.
2. Connect it to the same SQL Server using the appropriate credentials and click Continue.

   

   ^{Click the image to enlarge.}

   The Database Logon screen will appear.

3. Provide the Primary Database logon credentials and click Continue.
    

   This is different from the SQL Database logon credentials.

    

   

   ^{Click the image to enlarge.}

4. Wait until the installation is finished. Once finished, verify on the PolicyServer if all the Policies have been restored.

   

   ^{Click the image to enlarge.}

If the user forgot the Primary Database username or if it is unavailable, the following additional steps can be performed:

1. On the SQL Server, right-click MobileArmorDB > New Query
2. Run the following command and click the !Execute button:
   sp_change_users_login 'report'
    

   Take note of the username (e.g. SQLEXPRESS).

    
3. Type the following command and click the !Execute button:
   sp_change_users_login 'auto_fix','',NULL, ''
    

   The Username from the result of the sp_change_users_login 'report' query should be used as the Username.

    
4. Create your password, making sure that it follows the requirements below:
   • Does Not contain all or part of the user's account name
   • Contains at least six characters in length
   • Contain characters from three of the following four categories:
     • English uppercase characters (A through Z)
     • English lowercase characters (a through z)
     • Base 10 digits (0 through 9)
     • Non-alphanumeric characters (e.g., !, $, #, %)
5. Redo Steps 1 to 4 for MobileArmorLog.