You may see the following error in the Exchange Hybrid Configuration Wizard saying:
Note: This issue has been fixed in HCW version 17.0.4466.0, but you must uninstall the old version first, then reinstall from https://aka.ms/HybridWizard.
Note: Hybrid Configuration Service may be limited
If you examine the HCW logs you will see the following errors:
2020.02.05 18:52:00.006 10265 [Client=UX, Page=Credentials, Thread=1] START via Next2020.02.05 18:52:22.992 10306 [Client=UX, ValidateHybridServiceRequest=StandaloneHCWGetClientNetInfoCommand, Thread=1] START2020.02.05 18:52:23.789 *ERROR* 10308 [Client=UX, ValidateHybridServiceRequest=StandaloneHCWGetClientNetInfoCommand, Thread=1]FINISH Time=797.0ms Results=System.Net.WebException: The remote name could not be resolved: 'asl.configure.office.com'at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)at System.Net.HttpWebRequest.GetRequestStream()at Microsoft.Online.CSE.Hybrid.Provider.HybridConfigurationService.HttpClientProvider.Client.Microsoft.Online.CSE.Hybrid.Provider.HybridConfigurationService.IHttpClient.ValidatePostRequest(String requestUri, StringContent content)at Microsoft.Online.CSE.Hybrid.Provider.HybridConfigurationService.HybridConfigurationService.ValidateHybridServiceRequest(ServiceRequest request)2020.02.05 18:52:23.852 *ERROR* 10309 [Client=UX, Thread=1] HCW8108 Hybrid Configuration Service may be limited.
If you do an NSLOOKUP on asl.configure.office.com you'll see that it resolves to 0.0.0.0 in DNS.
I reached out to Office 365 support and was told that the asl.configure.office.com endpoint is deprecated and is no longer being used. An update will be coming out soon for the HCW.
I also confirmed that running the HCW completes without error.
No comments:
Post a Comment
Thank you for your comment! It is my hope that you find the information here useful. Let others know if this post helped you out, or if you have a comment or further information.