Azure AD Connect configuration hang...

%3CLINGO-SUB%20id%3D%22lingo-sub-1428429%22%20slang%3D%22en-US%22%3EAzure%20AD%20Connect%20configuration%20hang...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1428429%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20case%20it%20helps%20anyone%20out%20who%20sees%20a%20similar%20problem%2C%20we%20recently%20transitioned%20our%20company's%20domain%20from%20federated%20(through%20ADFS)%20to%20a%20managed%20domain%20using%20Pass-Through%20Authentication.%3C%2FP%3E%3CP%3EWhen%20running%20the%20Azure%20AD%20Connect%20configuration%20(version%26nbsp%3B%3CSPAN%3E1.5.30.0)%20the%20application%20crashed%20at%20the%20point%20where%20AD%20enterprise%20admin%20credentials%20were%20being%20entered.%20No%20information%20in%20the%20event%20viewer%20or%20AAD%20Connect%20logfiles%20-%20just%20a%20hang%20of%20AzureADConnect.exe%2C%20which%20needed%20to%20be%20killed%20and%20restarted.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAfter%20some%20digging%20with%20process%20monitor%2C%20it%20transpired%20that%20Trend%20Micro%20AMSP%20(Anti%20Malware%20Solution%20Platform)%20was%20blocking%20AzureADConnect.exe's%20attempt%20to%20write%20to%20MSOCredProv.txt%20within%20the%20profile%20of%20the%20user%20running%20the%20AAD%20Connect%20wizard.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESomewhat%20unhelpfully%2C%20the%20AV%20product%20wasn't%20giving%20any%20notification%20or%20other%20indication%20that%20it%20was%20doing%20this.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAnyway%2C%20whitelisting%20AzureADConnect.exe%20in%20the%20AV%20software%20allowed%20the%20configuration%20wizard%20to%20run%20through%20and%20complete%20the%20transition%20to%20a%20managed%20domain.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20don't%20*think*%20I've%20read%20anywhere%20that%20AzureADConnect.exe%20should%20be%20excluded%20from%20any%20AV%20scanning%2C%20but%20if%20you're%20seeing%20any%20strange%20behaviours%20-%20that%20might%20help%20you.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAll%20the%20best%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMatt%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1428429%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%20Connect%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

Hi all,

 

In case it helps anyone out who sees a similar problem, we recently transitioned our company's domain from federated (through ADFS) to a managed domain using Pass-Through Authentication.

When running the Azure AD Connect configuration (version 1.5.30.0) the application crashed at the point where AD enterprise admin credentials were being entered. No information in the event viewer or AAD Connect logfiles - just a hang of AzureADConnect.exe, which needed to be killed and restarted.

After some digging with process monitor, it transpired that Trend Micro AMSP (Anti Malware Solution Platform) was blocking AzureADConnect.exe's attempt to write to MSOCredProv.txt within the profile of the user running the AAD Connect wizard.

Somewhat unhelpfully, the AV product wasn't giving any notification or other indication that it was doing this.

Anyway, whitelisting AzureADConnect.exe in the AV software allowed the configuration wizard to run through and complete the transition to a managed domain.

I don't *think* I've read anywhere that AzureADConnect.exe should be excluded from any AV scanning, but if you're seeing any strange behaviours - that might help you.

 

All the best,

 

Matt

0 Replies