The GUI sets the expiration to be at midnight (0h zero
hundred??:o)??) of the next day after the date of
expiration...
That is if you set for expiration at the end of 9/5/2004 it
will expire at 12:00AM 9/6/2004. The GUI actually says above the date listed
"Account expires" and then a radio box of "End of:". So at the end of 9/5/2004
it would expire, in actuality the date is 9/6/2004.
The fact that that bugged me and a friend of mine needed to
do that on member machines and the GUI no longer allows that in 2K made me
create the AccExp tool. Not only will it show you the date, but it will show you
the time as well. Note however it won't let you set a specific time, it will let
you just set the date. I set the expiration for 1AM, I hate doing things around
the noon and the midnight, everyone always gets confused. Or at least I do which
is enough, I have sway over the developer - he who must not be named.
:oP
joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jef Kazimer
Sent: Friday, August 06, 2004 11:19 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Account Expiration Date Mismatch?
It appears that ADUC displays the User Expiration date differently than a VBS script does. An in house coded application is being questioned because these values do not match.
ADUC says 8/8/2004
VBS says 8/9/2004
The script is simply:
Set objUser = GetObject _
(rs.fields("adspath"))
wscript.echo(objUser.AccountExpirationDate)
Does anyone know what the code is to return the same value as USers & Computers MMC?
I have a feeling it's an estimate based on the time offset, but I am unsure.
Jef
