Best way to run AD queries

i trying run query on ad list of users properties returned, make sure account enabled, , if office either x or y.

not hard @ write up, best way go (using quest). should use included qad switches of -includedproperties , -ldapfilter?

my understanding command process on domain controller, using cpu time instead of workstation.

or should use where-object , select-object cmdlets filter every user get-qaduser return?

my understanding of filtering , sorting take place locally on workstation , reduce overhead on domain controller , network traffic. however, wont increase network traffic pulling 10-13k users opposed 2-3k?

what industry standard way going forward if going create more , more of these type of queries?

ive written query both ways , seems piping where-object , select-object faster. trying via cmdlet returns 20 records every 30 seconds, roughly.

i suggest going www.powergui.org forums if want subject matter expert input on quest cmdlets.  yes, generally, using built-in filters perform better, versus where-object or select-object, doesn't mean noticeable...

this wouldn't have industry standard.  built-in cmdlet filtering typically requires less overall resource usage, "good idea", if will...

Windows Server  >  Windows PowerShell