Screenlock windows 11 Samsung

Maurizio Giuffredi 20 Reputation points
2024-03-01T08:14:30.9133333+00:00

Good morning everyone.

Recently in the company we have enabled Microsoft Intune and in particular a lock screen policy set on 5 minutes for synchronized products.

I have a samsung along with a colleague of mine, in applying the policy it is as if we have awakened a daemon.

Let me explain better it has activated a local policy that sets the screenlock time to 1 minute and it won't listen to reason, we have tried everything.

How can we do to disable the local policy using only the Intune level policy?

We have already tried changing the power balance and screen lock settings from the classic Windows settings.

We have followed all kinds of procedures on the web but nothing

Can anyone please help me?

Thanks

Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
9,589 questions
Microsoft Intune Configuration
Microsoft Intune Configuration
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Configuration: The process of arranging or setting up computer systems, hardware, or software.
1,893 questions
0 comments No comments
{count} votes

Accepted answer
  1. ZhoumingDuan-MSFT 13,085 Reputation points Microsoft Vendor
    2024-03-04T03:15:23.8733333+00:00

    @Maurizio Giuffredi,Thanks for posting in Q&A.

    From your description, I know you have deployed a Screen Lock policy, but it did not work as expect.

    To narrow down this issue, please do some checks below.

    1.Please be sure your computers meet the Device Lock CSP requirement.

    https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-devicelock#maxinactivitytimedevicelock

    2.Please check the policy status in Intune portal and whether the device applied the policy.

    • You can check the Event log: Applications and Services Logs – Microsoft – Windows – Devicemanagement-Enterprise-Diagnostics-Provider – Admin and look for Event ID 813
    • Check the reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\DeviceLock MaxInactivityTImeDeviceLock

    3.Please check whether there exist Local Group Policy in targeted device. GPO takes precedence over Intune policy.

    • Run RSOP to see if any GPO settings on the device affect this

    If there is any unclear, feel free to let me know.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


1 additional answer

Sort by: Most helpful
  1. glebgreenspan 2,230 Reputation points
    2024-03-01T16:01:18.17+00:00

    Hey Maurizio

    Did you try this steps?

    Check the Intune policy assignment: Make sure that the lock screen policy you want to enforce is properly assigned to the user or device group that the Samsung devices belong to. Double-check the scope and targeting of the policy to ensure it includes the affected devices.

    Perform a policy sync: On the Samsung devices, try to force a policy sync by going to the Intune Company Portal app and checking for policy updates. This may trigger the device to pull the latest policy settings from Intune.

    Verify device compliance: Ensure that the Samsung devices are compliant with the Intune policies. If a device is out of compliance, it may not apply the lock screen policy correctly. Check the device compliance status in the Intune portal.

    1. Reset device settings: As a last resort, you may need to reset the device settings to default to remove any conflicting local policies. You can do this by performing a factory reset on the Samsung device but be sure to back up any important data before doing so.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.