-
Sign in to the
Microsoft Endpoint Manager admin center
.
-
Select
Devices
>
Configuration profiles
>
Create profile
.
-
Enter the following properties:
-
Platform
:
-
Profile
: Select
Custom
.
-
Select
Create
.
-
In
Basics
, enter the following properties:
-
Name
: Windows10_ScreenSaverSetting
-
Description
: Policy to change Screen Saver setting
-
Select
Next
.
-
In
Configuration settings
click
Add
and fill with the following parameters:
-
Name:
ScreenSaverSetting
-
Description:
Update the Screen Saver Setting
-
OMA-URI:
./Device/Vendor/MSFT/Policy/Config/DeviceLock/MaxInactivityTimeDeviceLock
-
Data Type:
Select
Integer
-
Value:
15 (Time given in minutes)
-
Select
Next
.
-
In
Scope tags
(optional), assign a tag to filter the profile to specific IT groups. Select
Next
.
-
In
Assignments
, select the users or groups that will receive your profile. Select
Next
.
-
In
Review + create
, review your settings. When you select
Create
, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.
Any suggestions for when the change does not seem to consistently work? For example on my machine, my setting updates to 5 mins as I configured, but then when I test it takes 8-9 minutes for my screen saver to pop (it never seems to be exactly the same).
Based on your verbiage above, I’m assuming the targeted assignments should be user groups and not device groups?
I tried the above mentioned but however the registry under HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\DeviceLock does change for MaxInactivityTimeDeviceLock
But the wait time in your screenshot doesn’t change.
Need to know how to do that?
Hi Zahid,
Thank you for your comment, so If I understood correctly, the property is not being updated?