|
I have an interesting observation about this one. If by
default your MaxPwd policy is set to 42 days, then you will get (using
the LDAP) 0 for LowPart and -8640 for High Part. If you change your
MaxPwd policy to something else (ex. 45 days), then you will get
-1956036608 for LowPart and -9053 for HighPart. But if you change your
policy back to 42 days, then you will get 178683904 for LowPart and -8449
for HighPart which is different from the original setting. Anyway, the
calculation is always right if you omit is Lowpart=0 part of the script and use
MaxPwdAge = ABS((objMaxPwd.HighPart * 2^32) +
objMaxPwd.LowPart)/(600000000 * 1440)
it should give you the right answer.
Regards
Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory [EMAIL PROTECTED], [EMAIL PROTECTED] http://ladava.com
|
Title: [ActiveDir] maxPwdAge property on AD2003
- [ActiveDir] maxPwdAge property on AD2003 Rich Milburn
- RE: [ActiveDir] maxPwdAge property on AD2003 Matjaž Ladava
- RE: [ActiveDir] maxPwdAge property on AD2003 Rich Milburn
