Discussion:
DSQUERY COMPUTER and STALEPWD VS INACTIVE parameters
(too old to reply)
FB
2008-06-28 19:06:01 UTC
Permalink
DSQUERY COMPUTER and STALEPWD VS INACTIVE parameters


I´m testing the command to del a lot of computer accounts via Script

When i use the -stalepwd OR -inactive parameters, it returns very different
results than using BOTH parameters.

In the command:
dsquery computer -inactive 4 -stalepwd 30

The parameters are "ORed" ou "ANDed"?

-inactive 4 (weeks) is the same as -stalepwd (days)? So, the results have to
be the same. Bu it does not the same, really true, the results are very
different.

I don´t have ANY parameter blocking computer account password changes, but
sometimes a PC used in day-to-day operations is shown as a "old" PC account
on the AD

Why?

There is a secure way to delete old PCs withou the risk to delete "newest"
PC accounts?
Al Dunbar
2008-06-29 15:27:24 UTC
Permalink
Post by FB
DSQUERY COMPUTER and STALEPWD VS INACTIVE parameters
IŽm testing the command to del a lot of computer accounts via Script
When i use the -stalepwd OR -inactive parameters, it returns very different
results than using BOTH parameters.
dsquery computer -inactive 4 -stalepwd 30
The parameters are "ORed" ou "ANDed"?
My guess would be ANDed, because it would appear more logical that all of
the filters would apply to each item.
Post by FB
-inactive 4 (weeks) is the same as -stalepwd (days)? So, the results have to
be the same. Bu it does not the same, really true, the results are very
different.
Can you share some specific examples?
Post by FB
I donŽt have ANY parameter blocking computer account password changes, but
sometimes a PC used in day-to-day operations is shown as a "old" PC account
on the AD
Shown as "old" in what sense?
Post by FB
Why?
There is a secure way to delete old PCs withou the risk to delete "newest"
PC accounts?
You could consider looking at the creation date, but I'm not sure if that
can be done with dsquery or dsget.

/Al

Loading...