Forum Discussion
Intune - Cannot change screen lock timeout
Hello community, I'm writing this post 'cause I'm facing a strange issue with the lock screen setting on our AE devices managed from Intune.
The configuration policy was created by my predecessor years ago, and was configured for lock teh screen after one minute. Everything working and all happy.
Then I got the request for create an exception group for that, and everything I tried failed.
I tried to change the global policy to 5 mins, but it did not worked, and the maximum lock screen time is still one minute.
Also remove the setting at all and left it Not Configured didn't had any effect.
Then I tried to disable One Lock. With this I was able to change the system lock screen settings but on Settings - Security and Privacy - More Security Settings - Work Profile Security - Use one lock I cannot set anything longer than one minute.
Pretty sure this is coming from somewhere in Intune, but also involving Microsoft and sending them the verbose logs wasn't enough.
Did any of you ever encountered a similar issue and found a solution?
Many thanks in advance for everyone that will try to help.
7 Replies
This sounds like a bug in Intunes side. Do you have different Android versions with the same issue?
Can you verify if some devices work and some don't? This might narrow it done a bit.
I've never had this issue, you should always be able to change that. But what might happen, if its not a bug, is that your test device is still recieving the original policy. In that case Intune will apply to stricter policy.
Hi LFagni ,
you might successfully found a "feature" of Intune:Source: Questions with policies and profiles in Microsoft Intune - Microsoft Intune | Microsoft Learn
As you are trying to be be less restrictive it might be necessary to "just" re-enroll the devices ;-) (I never saw a similar behaviour with other MDMs).
In order to verify this enroll a new device and check if on that the new policy is successful.Wow. Add it to the ever increasing list of why Intune is a bad choice for managing Android devices.
You have got to be kidding me?!?!
I've had a lot of experience with Intune and Android, and it is indeed not the best MDM, but this beats everything. Did they really take the time to write this article? i'm lost for words...
mattdermody , i'm kind of curious about the list haha, maybe we should make one just to see how far we come.
Intune is really bad, i can't say otherwise but in this case, i confirm we done it without re-enroll !
When i read the first message, i see something that Intune doesn't know how to manage properly, it is exception group.
