Error Registering User There Was a Problem Understanding the Server Please Try Again
Microsoft has released a new characteristic in Intune called "Intune Connector for Agile Directory" which currently is a preview release feature. This feature is used to join devices to the on-premise Agile Directory domain (using ODJ – Offline Domain Join) and the Azure Ad tenant within Intune, during Autopilot device enrollment. This creates a Hybrid domain joined scenario for customer devices to process local group policy and be managed by Intune. This is especially useful as many customers have on-premise services such as, grouping policy, mapped network drives and printers that must authenticate from the local Advertising domain controllers. While testing this feature in my lab and working with a client, I accept seen "Server Error Lawmaking 80180005" or "Error code 80070774" on customer devices. It turns out in my experience, this error was occurring because the reckoner name prefix was incorrectly configured.
Others in the IT customs and Microsoft TechNet forums linked here take noticed this or similar errors with different results on the customer devices. In this blog post, I will outline my experience with this issue, and what Intune settings are needed to resolve this effect. I'll also show examples of the correct computer name prefix for Intune Hybrid domain join, and what y'all can and cannot currently use. This feature is yet in "Preview" so Microsoft may make improvements later after feedback from the It customs.
Feature: Intune Connector for Active Directory (Preview) – Console View
Surround Setup & Configuration Requirements
Here is the setup for both the lab I used and the client's environment for the testing performed that produced the aforementioned errors during Autopilot Hybrid domain join (aka ODJ – Offline Domain Join).
Lab Surroundings
- For Hybrid Domain Join, a "Domain Join (Preview)" device configuration profile created in Intune that includes computer proper noun, Domain, and OU.
- Windows Server 2016 (hosting the Intune Connector for Advertizing)
- Domain / Woods Functional Level = Server 2016
- Windows x 1809 x64 ISO media pre-patched using OSDeploy.com OSBuilder
- Client VM devices connected to BOTH the local LAN and the internet. If the device is non able to connect to the local LAN, your local domain login will fail.
Customer Environment
- For Hybrid Domain Bring together, a "Domain Bring together (Preview)" device configuration profile created in Intune that includes reckoner name, Domain, and OU.
- Windows Server 2016 (hosting the Intune Connector for AD)
- Domain / Woods Functional Level = Server 2008 R2
- Windows 10 1809 x64 ISO media pre-patched using OSDeploy.com OSBuilder
- Client laptops/desktops connected to BOTH the local LAN and the internet. if the device is not able to connect to the local LAN, your local domain login will fail.
Issue Clarification
One of the Autopilot deployment profile options for this feature is Computername prefix. When y'all mouse over the data icon it says "Computers are assigned 15 characters long name. Specify a prefix, remainder of xv characters will be random." Typically in Intune, you tin can use %Series% to ensure the calculator name uses the serial number as a prefix or %RAND%. Withal, this causes a problem for Hybrid Domain Join currently. For the Hybrid Domain Bring together preview feature you currently cannot use whatever variables , but only a simple Prefix such every bit W10-, XYZ- or ABC-with or without a dash. If you attempt to use a variable, you volition get "Server Fault Code 80180005" or "Error code 80070774" equally mentioned before on the client devices during the Autopilot enrollment phase. Let's run into the details of the of the mis-configuration.
Incorrectly Set Computer Name Prefix
Although the light-green checkmark appears when you enter a variable as a prefix, the net issue is an fault and failure on the Autopilot customer device. This makes sense since a computer cannot use the % character as part of the computer proper noun.
In addition, in Event Viewer of the Intune Connector server, y'all will encounter other failure errors and the Computername prefix as a variable, and not the actual devices serial number as expected. Navigate to "Applications and Services Log" > "ODJ Connector Services" (Offline Domain Bring together) to see the events registered by the client device and one of the error letters every bit mentioned before on the client device during OOBE.
Unfortunately, in Event Viewer on the Intune Connector server, nosotros don't get run into a descriptive reason WHY the failure occurs. As a result, after logging into the client device during Autopilot enrollment, we become the error below as mentioned after some time passes. The client device volition testify an mistake that says "Something went wrong. There was an error communicating with the server. You tin try to do this again or contact your organization administrator with the mistake code 80180005" .
Solution (How To Ready information technology)
To resolve this issue, the calculator proper name prefix needs to simply exist a prefix. For example, ABC- or ABC or WIN10- to name a few. Microsoft allows variable prefixes for the standard "Azure Advertising joined" Autopilot deployment profile blazon but non currently for the " Domain Join (Preview)" device configuration profile type. Change the settings every bit shown here for the "Device Configuration contour" you previously created. Even though the screen shows a green check box if yous enter a variable, it will fail.
Correctly Set Computer Name Prefix Steps
Login to Azure and navigate to your Hybrid Domain Join device configuration profile in Intune, and remove the %SERIAL% variable (or any other variable) and use a uncomplicated prefix as shown below.
Microsoft Intune > Device configuration – Profiles > NAME OF YOUR AZURE HYBRID JOIN Contour – Backdrop > Domain Join (Preview)
Annotation: Make sure you Active Directory domain name (Full FQDN that users login to) and Organizational Unit of measurement (Full path)are correct and properly formatted or yous will go different errors.
When y'all re-run the Autopilot process on the device and log in, you volition see the Upshot Viewer ODJ Connector Service log (Offline Domain Bring together) shows the domain join blob was successful. The Autopilot device enrollment will proceed the process as normal and the devices's Active Directory computer object will be listed in the OU used by the Intune Connector hosted by your on-premise 2016 server.
After all of this, you still may see this error below considering at that place currently is an outcome with the USER enrollment status page (ESP). If you get this error on the "Business relationship Setup" folio every bit shown below, review the Microsoft blog post from Michael Niehaus about how to disable the USER enrollment status page using a custom OMA-URI. That'southward not ideal but the all-time workaround currently until the issue is resolved by Microsoft.
Disable SkipUserStatusPage enrollment folio using the steps outlined here. I've tested this and information technology works pretty well merely again, non ideal for production.
This concludes this blog post about the Intune Hybrid Domain Join Error 80180005.
I hope you found this helpful. Allow me know if yous have questions by commenting below (no login required).
References
"Trying out Windows Autopilot User-Driven Hybrid Azure Advertising Join" web log post by Michael Niehaus: Linked here.
"Intune – Hybrid Domain Join Error" Microsoft TechNet forum discussion: Linked hither.
/ / Filed Under: Azure, Azure AD, Azure Preview, Deject, Domain Join, Intune /
Source: https://www.moderndeployment.com/intune-hybrid-domain-join-error-80180005
Post a Comment for "Error Registering User There Was a Problem Understanding the Server Please Try Again"