Hi Lars  I hope that you have go a solution to your problem, but someone else might have the same problem, I will summit my solution to the problem that have just had.  We are in a process to rename all users logins i AD... And after a users login has been renamed in AD, the user could not login. With no error in the FMS errror log, or on our AD servers. The new users was created in Foglight correct, but when the user tried to login, but still got a login error.  I found a solution that is working for us. I found that when I enabled debugging on FMS, i got this error message in the error log:      Cannot insert duplicate key in object 'dbo.sec_user_alias'. The duplicate key value is (Michael Secher).  We are running the Foglight database on a Microsoft SQL server, so i looked in the table sec_user_alias, and found that even that I had deleted the old user in Foglight, the login name and user name was still in this table:  useralias    username             isdeleted str_xxx      Michael Secher     F  So I just update the username table with this:       UPDATE sec_user_alias      SET username = 'Michael Secher - old'      WHERE useralias = 'str_xxx'  and then I could login with the new user login, but all config and settings for that user is gone...  And as I have not talked with Quest/Dell about this, I don't know if this is allowed to do this, and I don't take any responsibility that it will work in your configuration.  Best Regards. Michael  Update: I found this: Knowledge Article 85132 - 'LDAP user unable to log in after LDAP name changed' - [URL]  Message was edited by: Michael Secher
Hi Guys  I have a problem regarding a user with acess to vFoglight through LDAP authentication. The user have been renamed in AD. (changed name) After the rename the user is not able to login.  In the audit trail the user is first authenticated OK, and then in the same second there is a Login FAILED.  I have tried to remove the user from vFoglight, wait for some time and then try to logon again.  I have checked on the AD Domain controller, and the user is authenticated OK  Is it a SQL issue ?  Any ideas ?
Renamed AD user not able to login