The remote name could not be resolved: ‘nexus.microsoftonline-p.com’

Bij het opzetten van een Azure AD Connect configuratie met een bestaande ADFS server kreeg ik de volgende foutmelding:

[15:02:17.121] [ 21] [ERROR] An error occurred while executing the ‘Update-MsolFederatedDomain’ command. The remote name could not be resolved: ‘nexus.microsoftonline-p.com’
Exception Data (Raw): Microsoft.Online.Deployment.PowerShell.PowerShellInvocationException: An error occurred while executing the ‘Update-MsolFederatedDomain’ command. The remote name could not be resolved: ‘nexus.microsoftonline-p.com’ —> System.Management.Automation.RemoteException: The remote name could not be resolved: ‘nexus.microsoftonline-p.com’
at System.Management.Automation.PowerShell.CoreInvokeRemoteHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
at Microsoft.Online.Identity.Federation.Powershell.PowerShellSession.Invoke(Command command, Collection`1& results)
at Microsoft.Online.Identity.Federation.Powershell.PowerShellSession.<>c__DisplayClass46_0.<InvokeCommand>b__0()
at Microsoft.Online.Identity.Federation.Powershell.Utility.InvokeOperationWithRetry(Action operation, Type exceptionType, String errorId, Int32 retryCount, Int32 retryWaitTimeInMilliseconds)
at Microsoft.Online.Identity.Federation.Powershell.PowerShellSession.InvokeCommand(Command command, Collection`1& commandResults)
at Microsoft.Online.Identity.Federation.Powershell.GenevaCommands.CreateRelyingPartyTrust(Boolean isMultiDomain)
at Microsoft.Online.Identity.Federation.Powershell.GenevaCommands.SetupWindowsLiveTrust(Boolean isMultiDomain)
at Microsoft.Online.Identity.Federation.Powershell.UpdateFederatedDomainCommand.UpdateDomain()
at Microsoft.Online.Identity.Federation.Powershell.UpdateFederatedDomainCommand.DoProcessing()
at Microsoft.Online.Identity.Federation.Powershell.BaseCommand.ProcessRecord()
— End of inner exception stack trace —
at Microsoft.Online.Deployment.PowerShell.PowerShellHelper.InvokeAndThrow(IPowerShell powerShell, Command command, Boolean throwExceptionOnError)
at Microsoft. Online. Deployment. Types. MsolDomainExtensions. UpdateMsolFederatedDomain Utility.(IPowerShell powerShell, String domainName, Boolean enableSupportMultipleDomain)
at URMicrosoft.Online.Deployment.PSModule.Tasks.AAD. CreateFederatedAADTrustTask ' 1. ConfigureMsolDomain(IPowerShell powerShell, Domain MsolDomain, Boolean enableSupportMultipleDomain)
at URMicrosoft.Online.Deployment.PSModule.Tasks.AAD. CreateFederatedAADTrustTask ' 1. ConfigureSelectedDomain(IPowerShell powerShell, String domainName, String primaryAdfsHostName)
at URMicrosoft.Online.Deployment.PSModule.Tasks.AAD. CreateFederatedAADTrustTask ' 1. Execute()
at Microsoft. Online. Deployment. Framework. WorkflowTask. ExecuteWrapper Workflow.()

The cause turned out to sit .Net in the configuration. In the environment uses a proxy server. It turns out that you not only have the .Net configuration of the Azure AD Connect server must adjust, but also by the ADFS servers.

Open on both the ADFS as on the Azure AD Connect servers in URnotepad.exe the following config file C:\WindowsMicrosoft.NETFramework64v4.0.30319Configmachine.config

Replace the following line at the end of the file

</configuration>

In:

<system.net>
<defaultProxy>
<proxy usesystemdefault =”true” ProxyAddress =”http://proxyserver.domain:portbypassonlocal =”true”/>
</defaultProxy>
</system.net>
</configuration>

Then change the proxy server components, domain, port by your own value.

Leave a Reply