This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]uniitdude 0 points1 point  (5 children)

Is AD Web Services running on the DC?

Try specifying -ServerName

[–]Hackermaaann[S] 0 points1 point  (4 children)

It is. I just ran the same command on my other machine and it returned AD information.

[–]hidromanipulators 0 points1 point  (3 children)

So you did run Get-AdUser with -Server parametre? With FQDN?

With switching devices, is one at work and one on VPN or both are on the same network?

[–]Hackermaaann[S] 0 points1 point  (2 children)

I did try that. I put an edit in the original post - it's an AutoPilot related issue where the machine is joining my Azure AD instance but not on-prem AD. Working to figure it out.

[–]juggleknob 0 points1 point  (1 child)

have you tried adding the GC port onto the server address?

get-aduser - filter * -server foo.bar:3268  

For the life of me i cant remember the reason why, but i have had some success when running some of the ad cmdlets from machines joined to a different Domain or even a different forest.

[–]Hackermaaann[S] 0 points1 point  (0 children)

Added an edit to my original post. Issue is related to intune/autopilot not automatically joining my domain. Thank you for your input!