Quantcast
Channel: Azure Active Directory forum
Viewing all articles
Browse latest Browse all 16000

Azure AD Connect Health Agent Installation failure

$
0
0

I am attempting to deploy Azure AD Connect Health to monitor my ADFS implementation (Two federations servers and 2 proxies all running on Server 2012 in Azure IAAS). I was able to enable the service in the Azure portal with no trouble, but I cannot get the agents to install. Specifically, I am getting stuck at the authentication phase. Here are my steps:

1. Launch powershell and run Register-ADHealthAgent cmdlet
2. Dialog pops up and asks for email. I give it and click Continue.
3. I am asked MS Account vs. Work/School. I choose Work/School and am redirected to my STS login page
4. I enter my credentials and click Login.
5. It appears that the page simply reloads, and username and password boxes are blanked out. I know the credentials I entered are correct because if I intentionally enter incorrect credentials, I get an error message about bad credentials instead of the described behavior. When I eventually give up and close the dialog, the error message in powershell and in the log for the cmdlet just inidicates that I cancelled the authentication dialog and nothing about whatever the problem is.

I have confirmed (by launching IE separately) that I can browse to https://sts.blah.com/adfs/ls/idpinitiatedsignon.aspx and authenticate with my credentials successfully, so it's not a problem with the machine reaching ADFS. The user I'm using to login is a Global Admin on the tenant and has an AAD Premium license applied. The machine I'm attempting to register is one of my ADFS proxy servers. No outbound restrictions are in place, IE ESC is disabled, and there is no forward proxy configured. I have rebooted the server multiple times.

One additional piece of information that may be relevant: I originally installed the AD Health Agent while the server was still running only powershell 3. The installation completed successfully, but the register-adhealthagent cmdlet didn't exist. I then installed WMF 4 to get PS 4. I have since uninstalled and reinstalled the AD Health Agent as a troubleshooting step, but this behavior is still present. 


Viewing all articles
Browse latest Browse all 16000

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>