Yep and if you get the timeouts, adfind should tell you
that pretty clearly. You can then use the -t switch to modify the timeout value.
I often use -t 0 to disable the timeouts on really large (like get every user
object in the 200k user forest) queries.
If you are still getting other errors, add the -exterr
switch and post the info as that can help troubleshoot it.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Sent: Tuesday, September 12, 2006 9:45 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] dsget error The
query is probably timing out. Get
Joe’s ADfind and run something like this: Adfind
–default –f “(&(objectCategory=person)(objectClass=user))” displayName
samAccountName pwdLastSet You
can tag a –csv on there too Thanks, Brian
Desmond [EMAIL PROTECTED] c
- 312.731.3132 From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Clay, Justin (ITS) Any time I try to run a large query using dsquery and dsget
where I pipe it to a text file for output, I eventually get a “dsget failed:The
server is not operational.” error from dsget. I’ve searched the Internet for
this and seen posts from a couple of other people who have had this issue, with
no resolution. Am I doing something wrong? Am I stupid? (yes, I probably am)
Am I missing some limitation of stdout? Here’s the command I was using: “dsquery user -name * -limit 0 | dsget -display -samid
–pwdneverexpires” Thnx, JC
|
- RE: [ActiveDir] dsget error joe
- RE: [ActiveDir] dsget error joe