This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 42%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
not sure if this the right forum...
We have an existing server running Azure AD Connect that we are looking to migrate to a new server
The existing server is running version 1.6...(so no longer supported) and the new server has the latest version
The new server is currently in staging mode. I had some issues with the install (proxy issues) and the wizard didnt complete so i had to re-install which worked fine.
We are getting this showing in the health portal tho for the new server. Is this because the server is still in staging mode?
Verify the health service is running on the servers and if so, restart regardless.
Give it a day or two to update after that in the portal
Thanks for the response. Server has been rebooted multiple times and still the same condition exists in the Azure portal. The server is still in staging mode
i did re-install the health components and it the powershell reports no errors
Is the AADConnect health service running on that server?
How about testing?
Test-AzureADConnectHealthConnectivity -Role Sync
[https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-health-agent-install#install-the-agent
the service is running. I did have issues the first time round install the Azure Sync app because of the proxy which caused the wizard to fail. Once i corrected the proxy and did the re-install the wizard completed. Is there any harm in deleting the server from the Azure health portal where the alert is generated?
if i run that command i get this...
You can delete the agent, yes. Sure seems like the proxy isnt set correctly however. or a network issue :(