Forum Discussion
Zero-Touch-Registration is not available
- 2 years ago
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.
- 8 months ago
Hey everyone,
I hope you are doing well. As this issue is now resolved and it's quite a long discussion, to avoid confusion with any future comments I'm going to close this topic for new replies now. I hope this is all fine with you.
If you are experiencing something similar or want to discuss something related, please do create a new topic here in the community (here is the direct link to do it) and we can carry on the conversation.
Thanks so much,
Lizzie
Maybe if someone is interested:
We faced the issue as well, that some (in this case a batch of 5) devices now weren't able to detect zero-touch and enrolled as a consumer device.
It didn't help to set them to "no configurtion" and assign back the correct one manually per device BUT doing the same via a batch file solved it for us (at least for those).
Lizzie Not sure if it makes sense for Google to look into this if there's any difference and why this can happen.