This content has been marked as final. Show 5 replies
Sorry no great words of wisdom here.
But I also suffered the same problems you mention.
In the end, I turned off the sync, so our encryption passwords are not necessarily our Windows passwords.
Looking fwd to hearing other peoples replies.
the local password is updated immediately, it's the remote db which is updated on sync. The most common cause of this behavior is incompatible templates - Windows accepts a password which is not valid for EEPC. You should make sure your EEPC password rules, including history, are more lenient than windows, or better still, turn them off altogether.
If Windows accepts a pwd which is unacceptable to EEPC, it will fail the change and default to 12345.
Thanks for your response. I'm interested in viewing the current password templates to see exactly how they are setup. Once again, excuse my lack of some basic aspects of EEPC, but where/how can I access the current password rules for EEPC to view them?
its in the user properties pages - password templates and rules etc.
Thanks for the heads up SB. The configurations seem pretty straight forward. At the current time, complexity is not being enforced with any policies aside from a minimum 8 character password. Right now, password change is set to force a change if it is '12345'. Password length in the properties is set to 8 chars min and none of the restrictions are enabled. There are no SB policies currently set so as far as the policies go, they appear to be pretty lenient.
Thanks for all your aid with this. Appreciate you really being helpful in laying out possible causes