B
bob
Hello,
I am in the process of writing utilities to allow for
password changes to be automated in my environment. In
the olde NT domain arch, we were using the
NetUserChangePassword API Call to make password changes,
that would also verify and validate the new password
against the Password Policies that were put in place.
We are in the process of migrating our domains over to
Active Directory. I am having Intermittent results with
this API call. Though I can use ADSI to make the password
change, we would like to use our old utility that makes
the API call until we have a chance to rewrite that tool.
Currently the API worked Once for a specific user, and
each try after that initial success returned
the "PasswordTooShort" error (Which can mean many things,
including Password Too Short, Too Long, . . .)
Barring the fact that it MAY be a Group Policy
effecting the call, I was wondering if anyone had similar
issues and or workarounds for the problem I am having.
The new code is being written in c#, not sure if there is
a comperable Call using DirectoryServices.dll in dotNet
that will also allow me to make checks against the Domain
Password Policies.
Any info on either would be GREATLY appreciated.
Thank you,
Bob
I am in the process of writing utilities to allow for
password changes to be automated in my environment. In
the olde NT domain arch, we were using the
NetUserChangePassword API Call to make password changes,
that would also verify and validate the new password
against the Password Policies that were put in place.
We are in the process of migrating our domains over to
Active Directory. I am having Intermittent results with
this API call. Though I can use ADSI to make the password
change, we would like to use our old utility that makes
the API call until we have a chance to rewrite that tool.
Currently the API worked Once for a specific user, and
each try after that initial success returned
the "PasswordTooShort" error (Which can mean many things,
including Password Too Short, Too Long, . . .)
Barring the fact that it MAY be a Group Policy
effecting the call, I was wondering if anyone had similar
issues and or workarounds for the problem I am having.
The new code is being written in c#, not sure if there is
a comperable Call using DirectoryServices.dll in dotNet
that will also allow me to make checks against the Domain
Password Policies.
Any info on either would be GREATLY appreciated.
Thank you,
Bob