Powershell command to query AD home Dir users

Make sure you're connecting to the right domain controller via the powershell command; it's possible that one or more of your DCs aren't synchronizing properly.

If you want to lock into a particular DC you can user the -Server parameter on the Get-ADUser cmdlet.  In those cases I usually focus in on the PDC Emulator for a variety of reasons.

Code would be something like below, combining with previous question:

$DC = (Get-ADDomain).PDCEmulator
$Props = `
@(
 "scriptpath"
 "homedrive"
 "homedirectory" 
 )

Get-ADUser -Filter * -Properties $Props -Server $DC| 
Export-Csv -NoTypeInformation -Path C:\temp\users.csv

Select allOpen in new window

only 2 DC's on domain both are on the same site. I have checked both DC's each chowing correct info on user.

Can you conjure up an example of the inconsistency?

Why do I need to change the command. Its inaccurate not incorrect data its bringing back.

Yes I can. in the output data the users it captures with home Directories is correct, however the data is incorrect as there are users are no of in AD that have home directories that are not showing up.

Are you always exporting to the same file name?  If it's locked, the export will fail and you will keep seeing the same data over and over.

No recreating every time. plus the data hasn't changed since starting today.

What happens if you just try to query one of the users that are missing?

OK. I ran the same command on teh other DC and it brought back the correct result. Yes both report same data.

You mean there are users you know have home directories that are not showing up in the report?  If so you should check a few of them manually through Active Directory Users & Computers.  Consider that there are other ways to map home folders like net use .../home.

It's very unlikely Get-ADUser is missing something that matches the query.

Let me know what you find.

I run the command on DC01 it brings back wrong results

I run on DC02 it brings back the right results.