Skip to main content
Level 1.6: Donut
November 14, 2023
Solved

Zero-Touch-Registration is not available

  • November 14, 2023
  • 28 replies
  • 37 views

Dear Community Members,

 

We are currently encountering an issue with the enrollment of three recently acquired Samsung S23 devices. While we are able to successfully enroll other devices, these specific models are presenting a persistent problem.

 

The error message displayed is as follows: "Zero-Touch Registration is not available. Check your internet connection and try again."

 

To address this, we have attempted the following troubleshooting steps:

  1. Utilized mobile data from various carriers as well as Wi-Fi connections, yet the error persists.
  2. Formatted the devices.
  3. Completely removed the devices from the Zero-Touch portal (https://partner.android.com/zerotouch#) and subsequently re-added them.
  4. Attempted manual enrollment using the QR Code provided by Intune.

Despite these efforts, the issue remains unresolved. Interestingly, we have successfully enrolled a Samsung XCover 5 without encountering any similar difficulties.

 

We are reaching out to inquire if others in the community are experiencing similar challenges with Samsung S23 devices. Any insights or suggestions would be greatly appreciated.

 

Thank you for your attention to this matter.

 

Kind regards,

Zackory

Best answer by Lizzie

Hello everyone, 

 

I hope you are doing well. 

 

I wanted to come back to you all with some positive news a fix has been implemented for this issue. I've heard from a couple of you that this is now working. If you could all check your impacted devices please to see if this has been resolved and let me know, that would be a great help. 

 

Once again a massive thank you for all the feedback you have shared in this discussion, it has really helped to get this resolved. 

 

Hope to hear from you soon and thanks again.

 

Lizzie

 

P.S - I will mark this as resolved and update the service announcement, but do keep me posted if you believe this isn't the case. Thanks.

28 replies

ZackoryAuthor
Level 1.6: Donut
November 14, 2023

Moombas
Level 4.4: KitKat
November 14, 2023

Hi Zackory, have you tried Samsung Knox to direct the device to your MDM instead? Is the network you use, unrestricted?

ZackoryAuthor
Level 1.6: Donut
November 14, 2023

Hi Moombas,

we do not use Samsung Knox currently. The network we are using ist unrestricted. 

jasonbayton
Level: 4.1: Jelly bean
November 14, 2023

Hi Zackory, 

 

Are you using Knox Mobile Enrolment at all? Any chance they may be registered there by a reseller? If so they should be removed.

Lizzie
Community Manager
December 7, 2023

Hello @treborny and @Zackory,

 

Thanks for your posts here and for highlighting. 

 

I've reported this back to our team internally. When I hear more on this I'll let you know. 

 

Thank you,

Lizzie

Welcome to the Community everyone!
Level 1.5: Cupcake
December 8, 2023

We are also experiencing the same problem. Samsung S23+
Please give this issue a high priority. We have several users who are now without a working phone.

New Member
December 8, 2023

We have the same problem, it just looks like it only affects Android 14 Enrollment.

Older devices with Android 13 work just fine.

Lizzie
Community Manager
December 8, 2023

Hello @Zackory@HarmonJames@EdwinK@treborny,

 

To those who I haven't met yet, nice to meet you, my name is Lizzie and I manage the community here. 

 

I am sorry to hear you are experiencing this issue and thanks again for your highlighting here in the community. I wanted to come back and recommend, if you haven't already, would you mind please contacting Samsung in the first instance. 

 

I'll also continue to provide your updates to our team internally. 

 

Thanks again and speak to you soon.

Lizzie

Welcome to the Community everyone!
Level 2.0: Eclair
December 11, 2023

@Lizzie Hi all! We are using MS Intune and Samsung Galaxy A54 devices enrolling into COPE via Zero Touch. Since Tuesday last week, we are experience the exact same situation as described here.

Everything to workaround this did not succeed. Waiting for some solution and raised a Google case with one of our Resellers to have a priority on this.

 

 

Moombas
Level 4.4: KitKat
December 11, 2023

@all with the issue here (as this has turned out to be a Samsung related issue) is there a reason that you don't use Knox instead of Google ZTP?

Level 2.0: Eclair
December 11, 2023

For us, simplicity in forms of "just use one entry point for all manufacturers". If we decide to switch to another manufacturer or use multiple manufacturers devices we can still use the same setup process (internal guides ...)

Moombas
Level 4.4: KitKat
December 11, 2023

Ok, so just simplifying. 

Just asking because we use Knox for the Samsung and Google ZTP for the rest as Knox provides more functionality (adding Tags etc.) but completely understand the reason for simplifying.

 

Was some how more a hint if someone maybe can check if it'S one Google ZTP related and maybe works via Knox instead as Samsung devices always look into Knox first and later (if solved from Google side) you can just remove them from Knox and then all are using G ZTP again.

New Member
December 11, 2023

I assigned a knox mobile enrollment profile AFTER the device ran into the zero-touch enrollment error > the knox enrollment profile does not take effect.

Moombas
Level 4.4: KitKat
December 11, 2023

Interesting, not what i would expect but very good to know.

Definitely also something to let Samsung know.

Moombas
Level 4.4: KitKat
December 12, 2023

And FYI: Just enrolled a Samsung A34 5G EE with Android 14, enrolling fine using Samsung Knox as the system pointing to our MDM.

New Member
December 12, 2023

Hello Community! A52 5G has the same issue with Zero-Touch as described.