S
SLDavis
I noticed that when the "User Must Change Password at Next
Logon" is checked on a user's account, you do not get a
date/time for these accounts in the PSWDLastSetTime field
when running a report using DumpACL. When it is not
checked, there is a date/time in the field. At my
company , we used to leave this field unchecked due to
synchronization problems between Novell and NT. We expire
all accounts that have not been accessed within a six
month time period. I have a job that looks at the last
login field to determine if it is six months old.
However, if this field is zeroes, then I look at this
PSWDLastSetTime field to see if that date is six months
old. This gave me a way to figure out if the accounts that
had never been accessed were six months old. However,
since we are now only a Windows 2000 shop, we have started
checking this at account creation. Needless to say this
is causing me problems with the accounts that have never
been accessed in determining if they are six months old.
Is there a way to force a date in this password time field
during the creation of the account and still have
the "User Must Change Password At Next Logon" checked?
Your help will most definitely be appreciated.
Logon" is checked on a user's account, you do not get a
date/time for these accounts in the PSWDLastSetTime field
when running a report using DumpACL. When it is not
checked, there is a date/time in the field. At my
company , we used to leave this field unchecked due to
synchronization problems between Novell and NT. We expire
all accounts that have not been accessed within a six
month time period. I have a job that looks at the last
login field to determine if it is six months old.
However, if this field is zeroes, then I look at this
PSWDLastSetTime field to see if that date is six months
old. This gave me a way to figure out if the accounts that
had never been accessed were six months old. However,
since we are now only a Windows 2000 shop, we have started
checking this at account creation. Needless to say this
is causing me problems with the accounts that have never
been accessed in determining if they are six months old.
Is there a way to force a date in this password time field
during the creation of the account and still have
the "User Must Change Password At Next Logon" checked?
Your help will most definitely be appreciated.