Get-Aduser script only returning a small amount of results on .CSV file

Xiomara McClenton 21

I have the following script, however when I run it it only returns random amount of results ( 254 run again 518, then 1000+ results ) but I need it to return all users which is 5000+. What can I do to fix this ?

get-aduser -filter * -Searchbase "OU=my,OU=domain,OU=Users" -properties * |
Select-Object SamAccountName,description,@{N='serialNumber';E={$_.SerialNumber[0]}} |
Export-csv C:\Users\user1\Desktop\serial.csv

Accepted answer

Ian Xue 37,706 Reputation points Microsoft Vendor

2020-12-02T03:57:30.717+00:00

Hi,

Do you have multiple domain controllers? If yes, there could be replication delays across DCs. As powershell may query different DCs, you may get differnet results if the users are recently added.

Best Regards，
Ian

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Xiomara McClenton 21 Reputation points

2020-12-02T14:50:04.313+00:00

Thank you, yes we have several DC's, I am going to try to run the script from a different server this morning.

Rich Matheisen 46,896 Reputation points

2020-12-02T16:06:46.787+00:00

No need to run the script from another server . . . just use the -Server parameter.

In a multi-server domain where you might run a series of cmdlets it's a good idea to use the same DC for all of the cmdlets, especially if you're adding or modifying content. For example, adding an Exchange mailbox and, in the same script, adding the new mailbox to multiple distribution groups. You may be surprised to find the new mailbox was added to DC1 and the distribution group modified on DC2 -- which probably won't have received a replication from DC1 yet.

Xiomara McClenton 21 Reputation points

2020-12-02T19:45:26.413+00:00

Thank you, I was able to get the information i needed with your guidance.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

1 additional answer

Andreas Baumgarten 111.4K Reputation points MVP

2020-12-01T21:05:16.217+00:00

Without testing:

You didn't specified the -filter parameter with a value? If "no" I wouldn't use -filter in the query.
The -SearchBase parameter doesn't not follow the correct syntax. It should be "OU=<Whatever>,OU=<anotherOU,DC=<domainname>,DC=<domainsuffix>"
The parameter -properties doesn't have a value? I would use -properties * to get all properties of the user object

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten
Please sign in to rate this answer.

1 person found this answer helpful.
Rich Matheisen 46,896 Reputation points

2020-12-02T03:38:16.56+00:00

I'm pretty sure that if the Get-ADUser incorporates the -SearchBase parameter then the -Filter (or -LDAPFilter) parameter is mandatory. In the poster's example a "-Filter *" would be appropriate.

As for the -Properties parameter, he's only exporting three properties so that's all he needs to specify. Using "*" would work, too.

Xiomara McClenton 21 Reputation points

2020-12-02T14:49:14.513+00:00

Thank you i think when i removed some of my organization's information i removed the OU syntax
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Get-Aduser script only returning a small amount of results on .CSV file

1 additional answer

Your answer