User Profile
LFagni
Level 2.0: Eclair
Joined 3 years ago
User Widgets
Contributions
Re: Unexpected error when adding new GZT admins
Hi Emilie_B the image was this one: But Lizzie was right, the user I was trying to add wasn't a google account(yet). After we fixed that everything worked. Maybe the error message could be a bit more clear than "Unexpected error" but apart of that we fixed.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.Re: Unexpected error when adding new GZT admins
Hi Emilie_B and Flo , this is the error I got: Anyhow I found the issue, I was trying using a corporate email but no google account was yet created for this address. We created the Google account for this login and after that I was able to add it to GZT in seconds.Re: Intune - Compliance policy not assigned
Hi KellyGM , I found the issue on one of my test device 1st time July the 25, but I was working on something different the days before so I cannot be 100% sure when it’s started. I had issues with assigned application too, I started investigating due to that and only after I discovered the missing compliance policy. I also opened a ticket with Microsoft, but nothing popped out from them. Then, the day after, Itried again and always was working without any change from our side, on the same devices that failed many times the day before. I did not hear about any other issue from our customers, so I assume that’s resolved and that was just a temporary issue. I’ll try again tomorrow just for being sure and let you know. /LucianoIntune - Compliance policy not assigned
Hello people, I'm writing here 'cause I'm facing a strange issue, if I enroll an Android Enterprise device it no longer receive the assigned compliance policy, and the default one is in error state. The other admin tried and all is working as normal on his device, so I'm not yet sure about the impact. The dynamic rule that populate the group for assign the policy is working fine, the devices are added. Another thing is that all the application that are required for the same group are no longer installed, and they're also not available looking for them in the Managed Play Store. Did any of you encountered similar issues? Not sure when it started 'cause I was busy on different stuff and did not enrolled any test device in the last month... Thanks in advance to anyone.Re: Force settings on Dedicated devices during enrollment
Hi Moombas , thanks for your reply. This is exactly my question, compliance policies are really similar, but on the other enrollment profile the user is asked to create a passcode during the device setup, this not happen only for the Dedicated Device ones. As example, I just made some fresh test and an S22 configured as Corporate Device with Work Profile on GZT ask to create a passcode after device registration: For the Dedicated Device this is not happening at all if I use the Token QR from Intune, and I'm just asked to create one if the profile is assigned from GZT, but as example my policy set a minimum lenght of six chars and other settings, that are just ignored in this phase (now I just tried with a Pixel 8Pro) The device at the end is just not compliant, but the error is not self-explanatory and might create confusion.Re: Force settings on Dedicated devices during enrollment
Hi ReeceK , all good here, hope the same on your side. During the enrollment of standard Corporate Device with Work Profile we're asked to protect the device, just after the device registration. and this is fully fine, same happen on Personally Owned Devices with Work Profile and also on Device Administrators (I'm anyhow working for remove them). Device administrators are not in GZT so I suppose that the PIN request is part of the standard setup of the device, so I do not understand why it's not requested for dedicated devices. I created a compliance policy too, that require the presence of a PIN protection, but those devices are marked as non-compliant with no real useful indication about the reason for the users, and PIN need to be created manually for make the devices compliant.Force settings on Dedicated devices during enrollment
Hello all, I'm trying to deploy a Dedicated device profile in Microsoft Intune, I created the configuration profiles and the compliance policy with some settings, in specific about PIN creation and complexity, but during the setup users are not asked to enter any PIN, and at the end the device result non-compliant until the PIN is set and is fulfilling the rules I set. Is there by any chance a way to force the PIN creation request during the enrollment phase as happens for user-associated devices? Thanks in advance /Lucius
