Os x screensaver start after greyed out12/15/2023 When the domain name doesn't resolve the "F15" key is "pressed", causing enough activity that Windows will not activate the screensaver. (The strange gyration of executing itself again is necessary because, if executed only by wscript.exe, a window will briefly appear on each polling interval- not a good thing at all.) ![]() It polls every 10 seconds, but you can modify that by altering the Const POLL_DELAY line. This script sits in a polling loop, using nslookup to resolve the domain named in the USERDNSDOMAIN environment variable. (If it is able to be resolved externally then, frankly, you get what you deserve.) Here's a little VBScript program, suitable for execution by wscript.exe (meaning that you could deploy this w/ Group Policy Preferences directly into the computer's "Startup" folder) that should do what you're looking for, assuming that your domain's DNS name isn't able to be resolved externally to your network. There any number of third-party programs that can do what you're looking for, but there's a certain "elegance" to doing things with only built-in OS components. Short of writing some kind of hackish client-side service program to reach into the user's registry and toggle the Group Policy screen saver restriction value (since the user can't do it themselves because of registry permissions) I think you're stuck in a situation where you're going to have to choose the lesser of the evils and either disable screen saver restrictions for users on the laptop computers, use some third-party "mouse jiggler" or keyboard simulation software, or just tell the users to live with it. When next those machines are rebooted (because the switch from non-Loopback to Loopback requires a reboot- background policy refresh won't enable it) you'll see the machines begin to pick up the screensaver settings from this new GPO. For your application, you could create an link a GPO to a hyopthetical "Remote Laptop Comptuers" OU that enables Loopback Policy Processing in "Merge" mode in its "Computer Configuration" section and, in its "User Configuration" section, sets the screensaver properties to whatever you'd like. It has a couple of different "modes" (Merge versus Replace) that make it even more confusing. The feature is, unfortunately, confusing to a lot of people. Loopback Policy Processing allows you to apply user settings to a computer irrespective of the user who as logged-on. ![]() You'll need to invoke Loopback Policy Processing because screensaver settings are per-user, not per-computer. ![]() I wasn't aware of this behavior but it certainly makes sense, given that users would just use this tool to exempt themselves from screen savers when nothing presentation-related was happening.Īs mentions you may want to change the Group Policy, as it applies to the "remote" laptop computers. I've been able to demonstrate to myself that the presentationsettings tool that I originally suggested does "respect" the Group Policy settings that prevent a user from changing their screen saver.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |