Azure Ad Connect fails

[Sheridan]

I'm trying to install Azure AD connect on our first 2019 server but simply get stuck when trying to authenticate

 

'Unable to validate credentials due to an unexpected error. Restart Azue AD Connect with the /InteractiveAuth option to further diagnose this issue. (The remote server returned an error: (407) Proxy Authentication Required).

The proxy is set correctly and internet access works ok, so I'm not sure why its thinking authentication is required (its a smoothwall and ad authentication is used)

 

I'm wondering if its a 2019 issue or a AD connect issue?

Edited September 27, 2019 by Sheridan

[3s-gtech]

Have a look at https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-connectivity (you may have already)

 

I suspect you have the proxy set via winhttp/netsh but it's not using that.

[sister_annex]

IIRC correctly you have to specify the proxy settings in the .NET config files or AADConnect doesn't listen (even with netsh)

 

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-connectivity

[Sheridan]

Proxy is set by GPO (and visible in IE) but it seems to be ignoring that! I had a look at the .net config - and edited the machine.config file which broke it even tough I added the proxy settings exactly as mentioned in that thread! I had to manually copy the machine.config file from a working server again.

 

I'm going to try Server 2016 and see if that works.

[sister_annex]

feel free to PM your machine.config over and i'll take a look, it's most likely a formatting Error

[Sheridan]

feel free to PM your machine.config over and i'll take a look, it's most likely a formatting Error

 

Cheers for that - but I've done the same process on a 2016 server and its working OK now - same login, same settings. Odd,unless there is something afoot with my 2019 server!

[Chuckster]

@Sheridan, did you ever resolve this? I've just encountered it on 2019 so am now in the midst of setting it up 2016.

[Sheridan]

@Sheridan, did you ever resolve this? I've just encountered it on 2019 so am now in the midst of setting it up 2016.

 

No, I simply installed in on 2016 server and left it on there. Never could find a reason why 2019 didn't work