Reseting age of password? Possible?

[BertieBigBollox]

At the moment, password policy is set to expire passwords after 90
days.

We use ghost to take an image of our PCs, which we then use to roll
out to other PCs. Trouble is because I first created the image 76 days
ago, its now popping up a message saying password is due to expire.

I've tried creating a new image but Windows seems to know the date
when this user was first created.

Any idea where windows stores this date? Is there any way to reset?

Of course, the one thing I could do is change the password, and then
change it back I guess. However, I'd have to fiddle with gpedit again
because we restrict on re-using passwords.

 

[Desk Rabbit]

At the moment, password policy is set to expire passwords after 90
days.

We use ghost to take an image of our PCs, which we then use to roll
out to other PCs. Trouble is because I first created the image 76 days
ago, its now popping up a message saying password is due to expire.

I've tried creating a new image but Windows seems to know the date
when this user was first created.

Any idea where windows stores this date? Is there any way to reset?

Of course, the one thing I could do is change the password, and then
change it back I guess. However, I'd have to fiddle with gpedit again
because we restrict on re-using passwords.

Domain or Workgroup?

 

[BertieBigBollox]

On 11/01/2011 11:02, (e-mail address removed) wrote:> At the moment, password policy is set to expire passwords after 90





Domain or Workgroup?

Standalone.

 

[Zaphod Beeblebrox]

message

At the moment, password policy is set to expire passwords after 90
days.

We use ghost to take an image of our PCs, which we then use to roll
out to other PCs. Trouble is because I first created the image 76
days
ago, its now popping up a message saying password is due to expire.

I've tried creating a new image but Windows seems to know the date
when this user was first created.

Any idea where windows stores this date? Is there any way to reset?

Of course, the one thing I could do is change the password, and then
change it back I guess. However, I'd have to fiddle with gpedit
again
because we restrict on re-using passwords.

Do you use sysprep before using ghost to take the image? If not, you
might give it a try - it resets a number of things so could take care
of the password date for you. Of course, it will likely reset some
other things you don't want it to which means having to set up a
runonce to fix things back... Or you could just live with having to
change the password, either way it is likely to involve pain.

--
Zaphod

Arthur Dent, speaking to Trillian about Zaphod:
"So, two heads is what does it for a girl?"
"...Anything else he's got two of?"

 

[Desk Rabbit]

On 11/01/2011 11:02, (e-mail address removed) wrote:> At the moment, password policy is set to expire passwords after 90





Domain or Workgroup?

Standalone.[/QUOTE]
Shame, with a domain it would be simplicity. Your only option appears to
be to create your image with the password policy set to not expire and
then have as part of your roll-out procedure a task to reset it.

 

[G. Morgan]

At the moment, password policy is set to expire passwords after 90
days.

We use ghost to take an image of our PCs, which we then use to roll
out to other PCs. Trouble is because I first created the image 76 days
ago, its now popping up a message saying password is due to expire.

I've tried creating a new image but Windows seems to know the date
when this user was first created.

Any idea where windows stores this date? Is there any way to reset?

Of course, the one thing I could do is change the password, and then
change it back I guess. However, I'd have to fiddle with gpedit again
because we restrict on re-using passwords.

Make an image on a machine logged in as Administrator, then set
the GP's. Then setup a new user and generic pass and tick "user
must change password on next login". Then disable the
Administrator account, shut down the machine, yank the drive and
Ghost it.

As far as an individual's work files are concerned, are they on a
network share?

 

[Desk Rabbit]

Maybe they dont wanna set up a server for a simple pc home office system?

^_^

Which is why I suggested a solution which doesn't require one.