Video Screencast Help

Endpoint Encryption 8.2- User lock

Created: 29 Jan 2013 • Updated: 20 Sep 2013 | 6 comments
LukasM's picture
This issue has been solved. See solution.

I was installing the console with my domain user. After I change my password like every month, my user is locked... We belive that, this process came from the database server.

Any ideas why this happend? What should I do if I have to change my password every month?

Thx!

Comments 6 CommentsJump to latest comment

Ashish-Sharma's picture

HI,

Check this artical may be help

 

Lockout Assistance Request with Symantec Endpoint Encryption

Article:TECH187471  |  Created: 2012-04-26  |  Updated: 2012-04-27  |  Article URL http://www.symantec.com/docs/TECH187471
 

 

Thanks In Advance

Ashish Sharma

 

 

LukasM's picture

Thx for the answer, but my domain user is locked because I used for the installation of the management console and I had change the password for security reasons. 

SMLatCST's picture

Did you use your own creds in the SEEMS Config Manager as the account to be used to access the database/AD/or client check-in?

Only in the Config Manager are account details kept, the console is just a MMC and so uses the currently logged in user's creds.

SMLatCST's picture

Oh yeah, it's worth mentioning that if you did configure your own account as the account clients use to check-in with the SEE Server, then you're in a bit of a pickle.

The account used by clients to check-in with the server is included in the client install package, and cannot be changed by policy, but instead requires a reinstall/upgrade of the Framework client on all your existing endpoints:

http://www.symantec.com/docs/TECH122714

SOLUTION
LukasM's picture

Ok, so how do I change the IIS account on my server? Can I do it with the configuration manager?

SMLatCST's picture

Yup, you'll have to log into the server and open up the SEEMS Configuration Manager.  From here you can change the credentials used for the client check-in via IIS.

Once done, you'll then need to create/export a new framework client package that also uses these new details, and push it out onto your existing SEE clients to get them to swap over to using the new account.  

Don't forget to use the reinstall=all reinstallmode=vomus switches when updating the clients!