who else is seeing devices becoming non-compliant after the latest SMC app version update to 9.7.10088? Nearly all of our devices need to be brought back in by the users to fix this issue on the device. Most of our users are not so skilled and a language barrier makes it even harder to explain by phone what they have to do.
The update collides with our compliance policy: "SMC permissions can be denied"
Sophos told us it was a bug in prior version or versions that did not set the setting correctly. With us it is only about 80 devices spread around South Germany but what are you guys doing who manage > 100 or even > 1k devices?
Hi All,We got advice from our Dev team that the battery optimization we have seen with the last release is caused by the changes Google asked us to do.The user would have to confirm the permission on the…
Hi Benedict,Thank you for reaching us. our team is currently working on the fix for this issue and based on this article, Our team has started the staged release for the new client version that will solved this issue.
this is the Case-ID: 04932405. It is an ongoing case as you might see when you open the case file.
As we have employees who are not tech savvy and have language barriers we cant tell them what to do via phone or mail. We already prepared a PDF but that did only work with around 3% ...
Hi Benedict,Our team successfully rolled out the new client version 9.7.10088 which will fix the issue that you've currently faced.
That is the thing. The issue came with the newly released version! We are already in contact with an escalation team who is reviewing everything from our setup and the app in collaboration with the developers.I posted here to get tips/info on how others are handling this bug/problem. I imagine that, if auto-update is active thousands of devices must no be non-compliant irreversible. So how to tackle that? Reset every device and let them set it up again through SSP?