Waiting for the management server after log and Password with DEP Enrolment

[Maxime LELEU]

Hi,

I created a DEP profile to wrap my MacOs,
All my DEP profiles work for my IOS

But when I want to wrap my MacOs after switch on,
I get the login screen so I can enter my login and password, 
I fill in the fields and the wrapping is accepted, 
Then I get a page that keeps turning up ‘Waiting for the management server’ and I often see the ‘address of my CnXXX.awmdm.com’ then ‘Waiting for the management server’.

My Mac appears embedded in the Workspace One UEM console but no profile comes down ....

after factory reset of MacOS I test again and it passes, I take another mac, same ....
this problem is random .... I may have missed something in my settings but the randomness makes me wonder.

It's not a network problem, I tested on an internet network without a firewall and found the same thing.

Do you have any ideas? 

Thanks in advance,

Regards

Maxime

Translated with DeepL.com (free version)

Edited October 8 by Maxpong
upload picture

[RJEMDM]

@Maxpong - I am also seeing this problem when enrolling a Mac for testing.

The process hangs at the 'Remote Management' screen looping between 'Waiting for management server' and 'Connecting to cnXXXX.awmdm.com...'

[Jason Misleh]

Sometimes when we see this issue, it is because there are multiple macOS devices in the console with the same serial number. Please do a search by serial number from the top OG and verify that only one device populates. If there are multiple devices, please delete them and try enrollment again.

After deleting the devices, you may want to navigate to the lifecycle screen and perform an ABM sync. Log into ABM and ensure that the device in question is assigned to the proper MDM server. You may want to unassigned and reassign it. Then perform another ABM sync. 

If the issue persists, you can always open an SR or report back here. 

[RJEMDM]

Thanks @Jason Misleh - I tried your recommendation and took it one step further stripping back the build to deploy 0 apps and 0 profiles to rule out a profile or app getting stuck during provisioning. The problem persists.
What are the next steps, please.

[Jason Misleh]

Do you have "await configuration" turned on in the DEP profile? If so, turn it off and see if the enrollment completes. If this is the issue, then there is some configuration that the device is waiting for and I would recommend opening an SR to review logs and/or troubleshoot further.

[Maxime LELEU]

16 hours ago, Jason Misleh said:

Do you have "await configuration" turned on in the DEP profile? If so, turn it off and see if the enrollment completes. If this is the issue, then there is some configuration that the device is waiting for and I would recommend opening an SR to review logs and/or troubleshoot further.

yes, we have this option to enable, but if we disable, we lose the ability to create an admin account automatically - and silently.

this is not the desired behaviour

[Maxime LELEU]

I've tried it with another blank DEP profile with no application or profile, and I get exactly the same result

and sometimes after 2 or 3 restorations the enrolment goes well,

the problem is random, I don't understand

Edited October 10 by Maxpong

[Jason Misleh]

I would open an SR so our teams can do a log analysis. I wish I had more for you. 

[Maxime LELEU]

I don't understand why I can't open a ticket......

[Maxime LELEU]

2 hours ago, Jason Misleh said:

I would open an SR so our teams can do a log analysis. I wish I had more for you. 

@Jason Misleh can you open a support request for me please, I don't understand that I can't open it

[Jason Misleh]

I cannot open requests on behalf of customers via communities. 

[Jason Misleh]

@Maxime LELEU - since you can't open a request online, I would suggest you call in and open an SR. Please see this KB: https://kb.omnissa.com/s/article/6000004

[RJEMDM]

Hi @Jason Misleh - Turning off 'awaiting configuration' in the DEP did not cure the issue. I will raise a technical support case.

[Jason Misleh]

Thank you, you can send me a DM with the SR number and I will track it as well.

[RJEMDM]

Hi @Jason Misleh & @Maxime LELEU - The issue appears to have cured itself. Validated multiple times with different Macs running various OS versions. I did not raise a technical support ticket in the end.

[Maxime LELEU]

Yeterday It' Work , Today it doesn't work ... I don't Understand, my Case Number is:

 

Case 00831394