Azure AD Connect Upgrade

[dapaulio]

Hi

 

I noticed after a user reported that they couldn't log on to O365 that it is reporting that my directory sync is out of date on my server and hasn't synced for more than 3 days. If I perform a manual full import within Synchronization Service manager, the end user can log back in but led me to investigate and address the out of date directory sync.

 

We currently have AD Directory Sync for O365 installed and it looks as though someone has attempted to upgrade to AD Connect, failed and given up. I have Azure AD Connect shortcut on my server's desktop however when I run it it comes up with an error on load "Invalid Class". if I run the Synchronization Service Manager it reports the AD Sync Service is not running. I can start it but it seems to crash and stop the service periodically which I assume is linked to the failed attempt to upgrade to AD connect.

 

Looking at video tutorials of the AD connect upgrade seems straight forward so cannot understand how the techy has managed to partially screw it up

 

Do I just reinstall the service from scratch? how does that affect my users already who use O365?

I would be grateful for any advice/help anyone can give.

 

Regards

[Matt_Renato]

First of all I would download the latest version of Azure AD Connect here and attempt the upgrade again to see if resolves the issue. If that doesn't work I'd remove all version of AD Sync and Azure AD Connect, reboot the server and try and install Azure AD Connect again. The only issue your users will have is that password synchronization won't be working until you get everything back up and running, so if they change their AD password it won't be reflected in O365.

[pow]

Simple server reboot sorted this issue for me!

[dapaulio]

Simple server reboot sorted this issue for me!

 

Tried that I hoped it was all I needed to do as I am not familiar with how azure works tbh so I was hoping not to have to work it out either.

[dapaulio]

First of all I would download the latest version of Azure AD Connect here and attempt the upgrade again to see if resolves the issue. If that doesn't work I'd remove all version of AD Sync and Azure AD Connect, reboot the server and try and install Azure AD Connect again. The only issue your users will have is that password synchronization won't be working until you get everything back up and running, so if they change their AD password it won't be reflected in O365.

 

Thanks I will give it a go when I have a bit of quiet time

[pow]

I've noticed that the Azure AD Sync and 2008 R2 doesn't play ball nicely, whereas another school where I have a 2012 R2 sync controller it's all fine... did you have lots of custom joiners and filters in DirSync?

[dapaulio]

I've noticed that the Azure AD Sync and 2008 R2 doesn't play ball nicely, whereas another school where I have a 2012 R2 sync controller it's all fine... did you have lots of custom joiners and filters in DirSync?

 

Tbh I am really not sure. This is the first time I have actually touched ad connect so I'm just getting my head around it. It is installed on a 2008r2 dc.

[dapaulio]

OK

exported the settings from sync services

Have tried to remove AD connect but get the same error invalid class. it looks as though the upgrade in the first place has properly screwed something up to the point I cant reinstall or remove AD connect on this server.

I can repair the installation but it crashes with the error invalid class.

 

Any thoughts?

[Matt_Renato]

Is there anything in Event Viewer which provides more details of exactly what is happening?

[dapaulio]

Is there anything in Event Viewer which provides more details of exactly what is happening?

 

funny enough no.

 

as far as the server is concerned it is uninstalled or repaired successfully

Windows Installer reconfigured the product. Product Name: Microsoft Azure AD Connect. Product Version: 1.1.180.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.[/Quote]

 

I have just tried installing it on another DC (2012R2) and just dealing with a proxy issue error now.

Scheduler::SchedulerThreadMain : An error occured and scheduler run failed to perform all operation.

System.Management.Automation.CmdletInvocationException: Microsoft.IdentityModel.Clients.ActiveDirectory.AdalServiceException: user_realm_discovery_failed: User realm discovery failed ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.

at System.Net.HttpWebRequest.GetResponse()

 

I have configured the web proxy in machine.config as it was on my 2008 r2 dc previously but no luck

[Matt_Renato]

If you check the connectivity section on this page does your machine.config match the example?

[dapaulio]

If you check the connectivity section on this page does your machine.config match the example?

 

yeah it matches but I have just read something in that same link about specifying Authticating service account in a custom setup. which I don't recall doing so going to try that

[dapaulio]

never managed to fix the original problem but have managed to get it running on my 2012r2. All synced up with no errors. I suspect something has happened in the past that has properly screwed up the installation.

 

ADConnect is definitely uninstalled off my 2008r2 server but running the MSI thinks its still installed and crashes when trying to repair it.

 

The proxy error I had happened to be fixed by copying the proxy setting that was edited in machine.config also into web.config and rebooting the server.

 

       
           	    usesystemdefault="true"
           proxyaddress="http://proxy:port"
           bypassonlocal="true"
           />
       
   

[dapaulio]

this link was very helpful to read

https://blog.kloud.com.au/2016/05/24/configuring-proxy-for-azure-ad-connect-v1-1-105-0-and-above/

kudos to the contributor

[Matt_Renato]

Glad to hear you've got it sorted. The new version updates itself unless you configure it not to, so you shouldn't have to worry about updates going forward.