Endpoint Encryption

This is happening on both Win7Pro and XP Pro machines.  the user has registered with the encryption program and logged into it successfully for a few months.  Soon after changing their Active Directory password, SEE does not update the password, and it is also removing the user from the list of registered users.  When the user logs into windows, they are prompt to "register now" most of the time..Everything will work fine until they change their password again and then the same thing happens all over..    Any thoughts?  The computers are checking in with the management server. 

Few things to check,

a) Under the SEEMS Configuration wizard, check if when was the last time ADSync happened.

b) What version of SEE you have

c) Did this happened even after user changing their password and rebooting the client machine ?

SEE usually understand the change in the password from ADSync and it updates the client DB.

We have SEE 8.2.1, management agent 7.1, and endpoint protection 12.1.1101.401.  Our AD policy is to change pwd every 90 days.  Once the user changes their windows/AD password, they disappear from the registered users(not sure at what point).  If they log off and log back on they are prompt to register even though they were registered before the password change.    If they reboot they are no longer registered with SEE and cannot get on the PC.  They have even tried to lock the computer and unlock it after changing pwd  and SEE is not prompting saying the password was updated..  The computers are checking in the the SEE management server successfully on a regular basis... ??

1. When you created the framework and full disk client package, did you set the password policy to 90 days ?

2. SEE password update happens on the background, it will not promt you this update.

3. Are these affected clients geographically seprated ? even time zone ?

4. Are the users able to open the client user console and are able to login to it ?

5. If they are able to login, what shows under 'registered user' ?

Please perform repair on one of the client to see the affect, perform the below command from the command promt. Try to run the command prompt under elevated mode.

msiexec /fvamus 'path of the framework.msi file'

msiexec /fvamus 'path of the full disk.msi file'