starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #756] BUG: Screen Lock Time in Endpoint Manager Template should be set in seconds not minutes #383

New issue

Closed

opened 2026-03-02 12:41:48 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 12:41:48 +03:00

Owner

Originally created by @JPT62089 on GitHub (Feb 15, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/756

Describe the bug
Added the "CIPP Default: Set screen lock time to 5 minutes to one of our clients. The value applied by this template is "5" which is meant to be 5 minutes. However, this should be 5 minutes in seconds (300 seconds) per the Microsoft Docs

To Reproduce
Steps to reproduce the behavior:

Go to MEM -> Apply Policy
Select Client and add the "CIPP Default: Set screen lock time to 5 minutes" per the defaults
Click Next and then Submit
Apply to a computer and it will lock after 5 seconds of inactivity.

Expected behavior
The computer should lock after 5 minutes of inactivity

Desktop (please complete the following information):

OS: Windows 10

Originally created by @JPT62089 on GitHub (Feb 15, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/756 **Describe the bug** Added the "CIPP Default: Set screen lock time to 5 minutes to one of our clients. The value applied by this template is "5" which is meant to be 5 minutes. However, this should be 5 minutes in seconds (300 seconds) per the [Microsoft Docs](https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/interactive-logon-machine-inactivity-limit) **To Reproduce** Steps to reproduce the behavior: 1. Go to MEM -> Apply Policy 2. Select Client and add the "CIPP Default: Set screen lock time to 5 minutes" per the defaults 3. Click Next and then Submit 4. Apply to a computer and it will lock after 5 seconds of inactivity. **Expected behavior** The computer should lock after 5 minutes of inactivity **Desktop (please complete the following information):** - OS: Windows 10

kerem

2026-03-02 12:41:48 +03:00

closed this issue
added the
unconfirmed-by-user
label

kerem commented

2026-03-02 12:41:50 +03:00

Author

Owner

@homotechsual commented on GitHub (Feb 15, 2022):

Ooof - that's a doozy!

@homotechsual commented on GitHub (Feb 15, 2022): Ooof - that's a doozy!

kerem commented

2026-03-02 12:41:50 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Feb 15, 2022):

whoops! I actually did this on purpose for my tests, and forgot to rollback. Fixing. :)

@KelvinTegelaar commented on GitHub (Feb 15, 2022): whoops! I actually did this on purpose for my tests, and forgot to rollback. Fixing. :)

kerem commented

2026-03-02 12:41:50 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Feb 15, 2022):

fixedin dev

@KelvinTegelaar commented on GitHub (Feb 15, 2022): fixedin dev

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#383

No description provided.

Rows
Columns