This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Password Policy Manager

We have installed the Password Policy Manager on one DC in our organization for testing the Dictionary Rule.  We only want to use that option in the Policy Rules and only to look at the Dictionary after it looks against our AD policies.  The problem I am having is, if I put a password in the dictionary I want to test it will take the password.  I choose a password I know will get past our AD rules but we want it to be stopped when it hits the dictionary.  But, its not.

 

For the Password Policy Manger to work do we need it installed on all DCs?  The reason I ask is because we have 6 more DCs that do not have the Policy Manager installed on. 

 

Thank you,

Wade

Parents
  • Unfortunately, I cannot comment on all your questions for complexity of subject cannot fit in the “narrow” format of the forum and recommend you to engage PSO.
    Password Manager got major features:
    (a) Forgot Password via Secured Q/A Authentication (Server side)
    (b) Change Password via current AD password Authentication (Server side)
    (c) Unlock via Secured Q/A Authentication (Server side)
    (d) (ex-GINA) Windows logon screen button to (a) (PC client side, deployed via AD GPO)
    (e) Reset Cashed Password Credentials (PC client side, deployed via AD GPO)
    (f) Password Granular Complexity Policy (segregation per OU, AD\group) (AD side – GPO, msi installed on all DCs)
    (g) Notifications (email: enroll, password will expire in X days etc…)
    (h) Reporting / Audit (SSRS)
    (i) Custom scripting on top of Password manager Engine
Reply
  • Unfortunately, I cannot comment on all your questions for complexity of subject cannot fit in the “narrow” format of the forum and recommend you to engage PSO.
    Password Manager got major features:
    (a) Forgot Password via Secured Q/A Authentication (Server side)
    (b) Change Password via current AD password Authentication (Server side)
    (c) Unlock via Secured Q/A Authentication (Server side)
    (d) (ex-GINA) Windows logon screen button to (a) (PC client side, deployed via AD GPO)
    (e) Reset Cashed Password Credentials (PC client side, deployed via AD GPO)
    (f) Password Granular Complexity Policy (segregation per OU, AD\group) (AD side – GPO, msi installed on all DCs)
    (g) Notifications (email: enroll, password will expire in X days etc…)
    (h) Reporting / Audit (SSRS)
    (i) Custom scripting on top of Password manager Engine
Children
No Data