tl;dr Azure AD Connect install error Error:An error occurred executing ConfigureAAD Sync task: user_realm_discovery_failed: User realm discovery failed How to resolve the error In my case, adding the proxy settings to a machine.config file associated with .NET framework v4

***

Today (Tuesday October 11th) I started a routine install of Azure AD Connect. This project isfor an upgrade from FIM 2010 R2 for a long time client; if you were wondering.

Unfortunately at the end of the process, when essentiallythe final part of the install was running, during the “Configure” process, I ran into some trouble.

Strike 1

I received the following error:


Azure AD Connect: An error occurred executing configure AAD Sync task: user real ...

An error occurred executing ConfigureAAD Sync task: user_realm_discovery_failed: User realm discovery failed

This happened with the current, as of this blog post, version of Azure AD Connect: 1.1.281.0 (release: Sep 7th 2016).

I did a quick Google, as you do, and found a few articles that matched the same error. The first one I went to was by Mark Parris. His blog post ( available here ) had all the makings of a solution. Ifollowed thoseinstructions to try and resolve my issue.

The solution required the following steps (with some of my own additions):

Open Explorer Navigate to the following path:C:\windows\Microsoft.NET\Framework64\v4.0.30319\config Find the file called machine.config Create a new folder in the same directory called “Original” Copy the file there as a backup in case things go wrong Openmachine.config with notepad to edit it At the bottom, before the </configuration>, enter in the following: <system.net>
<defaultProxy enabled=”false”></defaultProxy>
</system.net>

I followed those instructions andsaved the file to my desktop. I removed the notepad added .txt extension and before saving the file to the directory, I checked the logs to make sure I was indeed having the same issue. Small error on my part there. I’ll just blame it on the jet lag. Something (the log file) I should have checked first. Nevertheless, I checked.

Strange. I didn’t have the same error as Mark. My install had the following error:

Operation failed. The remote server returned an error: (400) Bad Request.. Retrying…Exception = TraceEventType = RegistrationAgentType = NotAnAgentServiceType

I know my client was using a proxy though, so, for the sake of testing, as this deployment was in staging mode anyway, I copied the machine.config file from the server desktop to the path and overwrote the file. My logic was that the .NET config with proxy “false” setting would bypass the proxy. Unfortunately that was not the case.

Strike 2

I selected the retry option in the Azure AD Connect installer and waited for the result. Not quite the same error, but, an error nonetheless:


Azure AD Connect: An error occurred executing configure AAD Sync task: user real ...

An error occurred executing ConfigureAAD Sync task: the given key was not present in the dictionary.

What a dictionary has to do with Azure AD Connect is beyond me. Technology is complicated, so I didn’t judge it. I went back to a few other of the search results in Google. One of the others was fromTarek El-Touny. His blog post ( available here ) was similar to Mark’s, but, had some different options regarding the proxy settings in the machine.config file.

Here’s what Tarek suggested to enter in that machine.config file:

<system.net>
<defaultProxy enabled="true" useDefaultCredentials="true"><proxyusesystemdefault="true"proxyaddress="http://<PROXYADDRESS>:<PROXYPORT>"bypassonlocal="true"/>
</defaultProxy>
</system.net>

Since I did have a proxy, this made more sense. Originally with the proxy “false” setting, I thought that would bypass or disable usage of the proxy. I was wrong.

Here’s a sample of the machine.config file for your reference:


Azure AD Connect: An error occurred executing configure AAD Sync task: user real ...

After I amended the machine.config file and saved it to the correct location, I started another retry of the installation. This time there was good news! It successfully finalised the installation and went on to configuration.

Final words

Over the last few monthsI’ve not done any hands on technical work. Yes, some architecture and design, some work orders and pre-sales, but, to get back on the tools was good. Unfortunately for me, a little rusty, but, thanks to the blog-sphere out there and the brains trust of other awesome people, I managed to work my way through the problem.

Best,


Azure AD Connect: An error occurred executing configure AAD Sync task: user real ...

本文系统(windows)相关术语:三级网络技术 计算机三级网络技术 网络技术基础 计算机网络技术

主题: Windows
分页:12
转载请注明
本文标题:Azure AD Connect: An error occurred executing configure AAD Sync task: user real ...
本站链接:http://www.codesec.net/view/483871.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(windows) | 评论(0) | 阅读(34)