Endpoint Encryption

We accidently deployed SEE onto some SED drives and SEE throws the exception "unable to update settngs".

While we are troubleshooting this, clients are getting a prompt that the machine will be locked in N days because it cannot communicate with the server.

I have tried extending the ContactDueDateTime and NoContactDaysMax in the registry but it doesn't seem to take effect and clients are still getting a warning?

Perhaps the install is corrupted but shouldn't changing these keys allow us to extend the dead line?

Did the drives encrypt already? If not, it may be easier to re-install. Had the same issue but drives were not yet encrypted so I re-created the installer and updated the policy to "Do not enforce a monimum contact period with the SEE Management Server"

They encrypted already...  Trying to somehow force an extension of the time while we figure this out.

Methinks you want this:

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

and the "--extend-client-monitor" switch.

Thank you, that is a great suggestion but we are on 8.2.1 which does not have that command line.

Similar sort of thing then, open up the SEE Client Administrator console on the client machine, log in as a client administrator, and hit the extend due date button.

This remained largely unchanged since SEE6

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

Unfortunately that doesn't work.. in that it allows it to be clicked but has no effect.

We are pretty sure the DB files on c:\ must be corrupt...

In that case, I think your last option is to use the clientadmin account at preboot to unlock the machine when it locks out.