Views:
  1. The Authentication Method of the user is Domain.

    • Check the diagnostic monitor logs on the Policy Server if there are any errors or warnings which are related to "LDAP".
    • When you get an LDAP unknown error, use the AD Process Tool to view the logs.
    • When changing the user who is logged in to preboot as the enterprise Administrator or Authenticator on the policy server MMC and login MMC, you can see if there are errors in the diagnostic monitor logs.

      • If no logs are created, use the diagnostic monitor tool to check the connection between PS and the agent.
  2. The Authentication Method of the user is Fixed Password.

    • Check the diagnostic monitor logs on the Policy Server if there are messages under restful API:

      Restful - http://{policy server address}:{port}/TMEEService/device/{device id}?action=authenticate

      For example: AuthenticateUserOnDeviceFailed: Invalid user name or password

      Restful API message

    • If no logs are created, use the diagnostic monitor tool to check the connection between PS and the agent.
  1. Click Synchronize policies to create logs in the diagnostic monitor logs.
  2. Check the network icon, it should display as blue.

    Synchronize policies

Check the enterprise log events for the following:

On the PolicyServer MMC, navigate to Console Root > QA1 > QA Group1 - Group > Log Events to view the following:

    • FDE agent log shows the message "Device synchronized".
    • FDE agent log shows the message "Unsuccessful logon using fixed password".
    • Policy Server agent shows the message "User unable to log on using LDAP Authentication Failed".

      PolicyServer MMC

  • In diagnostic monitor logs, you will see these similar logs:

    • LogonUser() with domain qatd1.com, user tmeeuser1: Invalid UserName Password:1326
    • Change the user who is logged in to preboot as the enterprise Administrator or Authenticator on the policy server MMC and login MMC, to verify the password.

      diagnostic monitor logs

  • Verify that the Num Lock and Caps Lock are working as expected in preboot.
  • Verify that the keyboard layout is working as expected in preboot.

    • Check the language display on the upper right corner.
    • Check the language code in the preboot log: preboot\var\log\keyboard-setup.log

When the user and device are not in the same group, it displays "User 'tmeeuser1' and device '{device id}' do not share a group:

  1. Log in to the Policy Server with enterprise Administrator/Authenticator credentials.
  2. Check if the user and device are in the same group.

user and device are not in the same group

To resolve the issue:

  1. Check if the network is available between PS and LDAP.
  2. Install ldp.exe and verify the connection.

Policy Server is not connecting to LDAP

The issue often occurs in Windows 2008 or in newer versions.

Diagnostics Monitor logs show the following message:

Failed to connect to an IPC Port: The system cannot find the file specified.

endpoint and LDAP issue

The Account Lockout Policy Settings can be configured in the following location in the Group Policy Management Console:

Computer Configuration\Windows Settings\Security Settings\Account Policies\Account Lockout Policy

Unlock the domain user and try to log in again.

Account Lockout Policy 1

Account Lockout Policy 2