Cause

When you try to connect to the MMC, you cannot connect to the server and the Health Monitor displays error 401.1. This issue occurs because the IIS requires integrated windows authentication.

Solution

1. Uninstall PolicyServer by opening PolicyServerInstaller.exe. Agree to the EULA and click Uninstall.
2. When the uninstallation is complete, click Install.
3. Select Use a Domain Account.
4. Specify the User Name, Password, and Domain for the user, and then click Continue. This user must either be a local admin on the machine or has the "Log on as a Service" rights.
5. Enter your database information and click Continue.
6. When the installation is complete, close the PolicyServerInstaller.exe.
7. Click Start > Run > inetmgr.
8. Expand Web Sites, and then right-click Default Web Site and choose Properties.
9. Click the Directory Security tab and choose Edit for Authentication and Access Control.
10. Tick the Enable anonymous access check box.
11. Click Browse and search for the user you are running the PolicyServer as, and then click OK.
12. Type the password, and then re-enter the password to confirm.
13. Click OK.
14. Do any of the following:
    • Reboot the server by right-clicking the server name in IIS and select All Tasks > Restart IIS.
    • Run the command "iisreset [computername] /restart".
15. Log into the MMC after the restart.

To resolve the issue, check the HKEY_CURRENT_USER\Software\Policies\Microsoft\MMC and HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\MMC registry keys to view the restrictions. Delete the whole MMC branch if you find them.

Cause

The Application Event Log Viewer keeps generating a warning error message. The messages are caused by the error logs generated on the PolicyServer. This issue happens when a client attempts to reconnect after its session key has expired, but can also be displayed when a device which is not in the database is trying to connect.

Solution

To resolve the issue, change the value of HKEY_LOCAL_MACHINE\SOFTWARE\Mobile Armor\Diagnostics\PolicyServer.DBAppDomain registry key from "EventLogLevel" to "FatalException". This will decrease the number of events logged by Windows.

Cause

The error happens when you use the External Directory Browser on a machine that has Microsoft .Net 2.0 only. This problem occurs because of the updates made to Microsoft .Net 2.0 that are included in SP1.

Solution

Install Microsoft .NET Framework 2.0 SP1 from the prerequisites folder or from Microsoft.

Cause

When upgrading from a previous version to SP6, the legal notice may become corrupted causing an incorrect display in the PolicyServer.

Solution

Re-import the legal notice file to the PolicyServer.

Cause

The error appears when you import users from Active Directory.

Solution

Importing the specified number of users would exceed your license count. Please contact Endpoint Encryption Sales to purchase additional licenses.

Cause

The error appears when you try to log into MMC. This is caused by McAffee Webroot anti-virus firewall which is blocking the communication to the server.

Solution

To log on with no issue, configure the Accessed Firewall settings and list http://saas.mobilearmor.com as an approved website.