I am also seeing this same issue. We just made the switch to JAMF and not a promising start....

This may be in relation to an open product issue with Jamf (PI-002379) which generates excess DeviceInfoAccountHash, DeviceInfoITunesActive, and ProfileList MDM commands. When these build up, MDM seems to slow down and DEP also seems affected. I would reach out to your TAM/Jamf support to see if you can confirm that you are experiencing this PI. They have a temporary fix for it until they address the issue in product.

Restarting DNS services did the trick for us

I do not know what is causing this but I do know how I was able to fix it for the systems experiencing it in my organization. I took their serial numbers and searched in "Devices" (where iOS devices would go) and found that they were all in there with the name: [No Name] After I deleted these entries and reinstalled a fresh copy of MacOS on each system they connected via DEP without issue.

I ought to follow up on this for posterity...

Turns out that the 34011 error relates to the device being able to contact DEP servers (iprofile/albert), but not being able to reach the CRL servers (.symcb.com, .symcd.com) in order to validate that the certificate being presented to by the DEP servers has not been revoked.

Anyone has a good fix for this? My instance intermittently gets bug down with this issue. I would get this issue for a few days and suddenly, it would start working again.

I had the same issue on different servers:
1. Check the Jamf Pro URL in the settings
2. Check the Organization Name (don‘t use special characters like „ä“)

We had exactly the same issue.
Turned out to be a policy scoped to a (static) group that did not existed anymore.
Jamf is going to fix this is in the new update.

We fixed it by re-creating the missing groups.

If you still having issues, then go to the deploy wsite, download the token and upload it back to the JSS..

done!

Hi all need your help on below error while i am trying to register my iMc to DEP

We have allowed 17.0.0.0 subnet with port allow ports 80, 5223, 2195, 2196, 443

We were recently having issues with apps not installing in iOS and in particular the Native apps at activation
Apple has updated this document:

https://support.apple.com/en-us/HT201999

Our fix was to whitelist: bag.itunes.apple.com

Since we did this I am also not seeing the random messages on my prestages saying they cannot connect

We have the exact problem at the moment. svc-sbdjamfadmin Did you find any proper solution?

We are still having enrollment failures. This seems to be the only source of knowledge on the matter
https://nstrauss.github.io/mitigating-mac-enrollment-failures/

We had the same issue and I flushed DNS cache on the client machine which fixed it.

Big sur:  sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder