The description of the policies is as followed: This behavior is caused by one specific group policy, “Interactive logon: Machine inactivity limit” which can be found in:Ĭomputer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options. To be clear, this is not specific to a VDI environment and can be reproduced on any Windows 10 device. After the two minutes the device will be locked, even when it should not.įurther in this blog post there is a video that will show behavior including the solution. When switching to the “(none)” screensaver the wait time is grayed out with the value of two minutes. For example, when configuring a screensaver with a wait time of two minutes, screensaver will work after two minutes. Somehow the settings from the “(none)” screensaver is used, which is based on the last configured wait time. This resulted a double logon from the managed device and the VDI session, which has a very negative user experience.Įven when the screensaver is not configured using Group Policies this behavior still applies when it is configured manually. While polices where correctly applied somehow the VDI desktop will still lock after 15 minutes. When reconnecting from a managed device this will be switched to none screensaver without any timeout. When connected from a not managed device a blank screensaver will be configured with a wait time of 15 minutes. Based on the connecting device specific screensaver policies are configured using a UEM solution. In this specific use-case it was a requirement for a VDI environment. There are multiple reasons why you would configure a screensaver. This blog post will explain the strange screensaver behavior including the solution to resolve this issue. In this case while none screensaver was configured the machine still locks on the last configured screensaver wait time. Sometimes you encounter strange behavior which cannot be explained while troubleshooting.
0 kommentar(er)
