D
David Phelan
Hi, hope someone can help with this.
We are trying to do some cleanup in our active directory. We would like to
be able to automate the process as best we can. Mainly we are trying to
clean up old computer objects for PCs that we no longer have but are still
in our system.
I found a code snippet which goes through the computer list in AD and
generates a list of machines that have lastLogon dates older then 1 year
which works just fine. The problem is that there are some machines in the
list that we know are in daily use. Their logon dates are over a year old
but the machines are logged into every day. Other active machines in the
system have null login dates.
We checked a couple of the machines in question to make sure that machine
names hadn't been changed and that they had been rebooted and relogged on
to, but the lastlogon date does not change.
Anyone have any idea why this would be true or how to force the logon date
to update when the machine connects to the network?
Dave
We are trying to do some cleanup in our active directory. We would like to
be able to automate the process as best we can. Mainly we are trying to
clean up old computer objects for PCs that we no longer have but are still
in our system.
I found a code snippet which goes through the computer list in AD and
generates a list of machines that have lastLogon dates older then 1 year
which works just fine. The problem is that there are some machines in the
list that we know are in daily use. Their logon dates are over a year old
but the machines are logged into every day. Other active machines in the
system have null login dates.
We checked a couple of the machines in question to make sure that machine
names hadn't been changed and that they had been rebooted and relogged on
to, but the lastlogon date does not change.
Anyone have any idea why this would be true or how to force the logon date
to update when the machine connects to the network?
Dave