![]() ![]() Reg.exe load HKEY_LOCAL_MACHINE\defuser c:\users\default\ntuser.dat I’ve created the script, added it to my Windows 10 OSD Package, in the same folder I keep my LockScreen Wallpaper. You could push this via Group Policy, but I’m always a fan of using ConfigMgr, so I’ve created a simple script to deploy during OSD. Now that we have the setting, we can deploy it. To change it, you need to set the registry to: “RotatingLockScreenOverlayEnabled”=dword:00000000 After some guess work, I found the key in the registry that pertains to the setting: So now it was time to look for another way to do it. On my test machine, I still saw the tooltips and the settings under personalization still showed the setting as “ON” I enabled the setting, pointed the GPO at the locally copied Wallpaper and checked the box. We still allow our users to change it, but it starts with a corporate branded wallpaper. I am already controlling the initial lock screen image via OSD, which changes a registry setting to point to a wallpaper I copy local. This is a group policy that controls the Lock Screen image and this tooltip. Once I logged in, IE would launch w/ a Bing search about what I had clicked on. ![]() Then I noticed in the upper right corner of my lock screen little messages, I could click on it, but nothing would happen. So it looks like the system is locking on reconnect on its own.This only came up recently as I’ve been exploring removing the Ctrl+Alt+Del requirement for logon. If I configure DEM to send a message on unlock I get three messages instead of one. After Windows lock has been triggered even once reconnections after a tsdiscon will always prompt for a password.Įdit: Another behavior has been identified. Interestingly enough, if the user hasn't triggered a Windows lock the session will return without prompting the user for the password. The session will disconnect at that point and can reconnect without issue. I should note that triggering a tsdiscon via command line without the two triggered tasks does not cause the same issue. Are there any additional settings that may need to be applied for the provided fix to work? At this point I'm forced to reboot the desktop via Horizon Admin. The DEM logs show a user environment refresh on the first disconnect but nothing on subsequent reconnection attempts. I get an instant disconnect on every reconnect attempt. Unfortunately triggering a tsdiscon.exe on lock along with the refresh on disconnection doesn't have the same results for me. Not sure where this 2nd unlock attempt is coming from.ĭoes anyone have a way around this either a Horizon setting to disable that 2nd ctrl+alt+del or a different way to remove the abilities for users to lock the screen from start, Ctrl+alt+del and Windows L ![]() I have monitored the desktop in vcenter and the screen still gets locked after disconnect by Horizon which is great. This works as expected on initial logon but when we reconnect to a desktop after about 5 seconds of seeing the desktop its as if something presses ctrl+alt+del and that brings up the pre lock screen menu. To do this we also implemented the Remove Lock Computer user GPO. So the goal is the disable the lock screen and use the Idle Time Until Disconnect (VDI) GPO to disconnect back to that initial logon after our time limit. A windows lock screen does not pass out audit requirements. We are meeting our authentication requirements using the initial logon and then a timed disconnect (below) reconnect through the UAG appliances. We are trying to meet those wonderful audit requirements and I have one issue standing in my way. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |