Error: 'User not authenticated' when logging into the VigilEnt Security Manager console. (NETIQKB35946)

fact
VigilEnt Security Manager 4.1

symptom
Error: 'User not authenticated' when logging into the VigilEnt Security Manager console.

symptom
VigilEnt Security Manager is set up using Active Directory as an external authentication source and is mapped to the samAccountName.  The actual source shows successful verification.

cause
The cause of the above error is due to the Microsoft Active Directory Migration tool.  The tool migrates user accounts into Active Directory and the results of the migration causes the user logon name (pre-Windows 2000) to be in upper case.  The logon accounts in VigilEnt Security Manager (VSM) were in lower case, thus creating a mismatch. These accounts were not created in AD using capital letters. It seems that, when using the Microsoft Active directory migration tool, it automatically switches accounts to upper case.  Therefore, any account created prior to the migration could not connect.  All those created after the migration were created with lower case and could connect without a problem. 

fix

This issue can be resolved by changing the case of the User logon name (pre-Windows 2000) to match the logon name in VSM.  This can be done by following the steps below:

1. Launch Active Directory Users and Computers while logged in as an administrator.
   
2. Browse to the container where the VigilEnt Security Manager user accounts reside.
   
3. Right click the user account(s) in question and select Properties.
   
4. Click the Account tab.
   
5. In the User logon name (pre-Windows 2000) field, type in the correct case for the user account name to match the VSM account case.
   
6. Click OK.

Formerly known as NETIQKB35946