I just received the “MenrollEDeviceUnknownError” or “Unknown server error.” in my newly setup Workspace ONE UEM environment. After some troubleshooting, the issue was quite easy to solve.
The HUB shoed this error:
Unknown Server Error:
From DeviceEnrollment.log
2021/03/23 11:30:58.426 DESKTOP-K6CJ5Q8 94c89925-a344-4a19-9569-e21e279b438a [0000000-0000000] (26) Warn VMware.WUA.Diagnostic.Business.DeviceStatus.State.HubState.GetSfdVersion GetSfdVersion - No registration status found for AirwatchMDM.dll
2021/03/23 11:30:58.426 DESKTOP-K6CJ5Q8 94c89925-a344-4a19-9569-e21e279b438a [0000000-0000000] (26) Error VMware.Hub.Win32Agent.Enrollment.Business.Execution.Implementation.RedirectMdmInstallUrlStep+<Execute>d__10.MoveNext SOURCE: [RedirectToMdmInstallUrl], ERROR_CODE: [-2145910776], ERROR_MESSAGE: Unknown server error., ERROR_RESPONSE: Method: VMware.Hub.Win32Agent.Enrollment.Business.Execution.Implementation.RedirectMdmInstallUrlStep+<Execute>d__10.MoveNext;
2021/03/23 11:30:58.441 DESKTOP-K6CJ5Q8 94c89925-a344-4a19-9569-e21e279b438a [0000000-0000000] (26) Info VMware.Hub.Win32Agent.Enrollment.Business.Execution.Implementation.RedirectMdmInstallUrlStep+<Execute>d__10.MoveNext RedirectToMdmInstallUrl: ENDED Executing
2021/03/23 11:30:58.441 DESKTOP-K6CJ5Q8 94c89925-a344-4a19-9569-e21e279b438a [0000000-0000000] (26) Info VMware.Hub.Win32Agent.ClientCommunication.Client.ClientCommunicationHandler`1+<IsHubAppReadyAsync>d__26.MoveNext checking for UI Ready
2021/03/23 11:30:58.441 DESKTOP-K6CJ5Q8 94c89925-a344-4a19-9569-e21e279b438a [0000000-0000000] (19) Info VMware.Hub.Win32Agent.ClientCommunication.Client.ClientCommunicationHandler`1+<IsHubAppReadyAsync>d__26.MoveNext Hub UI Ready status True.
From NativeEnrollment.log
2021/03/23 11:30:55.441 DESKTOP-K6CJ5Q8 06cd91ee-3a9f-44c4-9312-03e463816713 [0000000-0000000] (1) Debug AW.Win32.Utilities.MDMRegistration.DmEnrollmentHandler.RegisterDeviceWithManagement Method: AW.Win32.Utilities.MDMRegistration.DmEnrollmentHandler.RegisterDeviceWithManagement; Parameters: upn = *****, mdmServiceUri = https://ds1678.awmdm.com//deviceservices/Discovery.svc, accessToken = *****;
2021/03/23 11:30:55.441 DESKTOP-K6CJ5Q8 06cd91ee-3a9f-44c4-9312-03e463816713 [0000000-0000000] (7) Debug AW.Win32.Utilities.MDMRegistration.DmEnrollmentHandler.RegisterDevice Management Registration Allowed True
2021/03/23 11:30:56.926 DESKTOP-K6CJ5Q8 06cd91ee-3a9f-44c4-9312-03e463816713 [0000000-0000000] (7) Debug AW.Win32.Utilities.MDMRegistration.DmEnrollmentHandler.RegisterDevice MDM Registration return code MenrollEDeviceUnknownError Description Unknown server error.
2021/03/23 11:30:56.926 DESKTOP-K6CJ5Q8 06cd91ee-3a9f-44c4-9312-03e463816713 [0000000-0000000] (1) Debug AW.Win32.Utilities.MDMRegistration.DmEnrollmentHandler.RegisterDeviceWithManagement Method: AW.Win32.Utilities.MDMRegistration.DmEnrollmentHandler.RegisterDeviceWithManagement; Returns: MenrollEDeviceUnknownError; Duration: 1484 ms;
2021/03/23 11:30:56.926 DESKTOP-K6CJ5Q8 06cd91ee-3a9f-44c4-9312-03e463816713 [0000000-0000000] (1) Info NativeEnrollment.Program.Main Hub -Native Client enrollment code MenrollEDeviceUnknownError. The solution
Make sure that a Device Root Certificate was created:
The Device Root Certificate can only be generated at a Customer Type OG. So, please ensure that Type is set to pfx. The child OGs will just inherit the settings.
Please follow and like us:
No responses yet