So if you force a machine to sleep, maybe you interrupt a process or prevent remote access to the pc. My opinion is we are all consenting adults, if you break it, the pieces are yours to keep for free.
So if it were me, I'd post a warning on the reset portal or even raise a dialog of the consequences. But back to your question, I am looking at a GPO were we set various aspects and I see behaviors for computer prefs for power options. You can state Sleep after x etc, does that not work for you? My 2 cents, jlc From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Sunday, August 7, 2016 9:38 AM To: NT <[email protected]>; [email protected] Subject: [NTSysADM] Force sleep downside Hi all, We recently deployed ADSelfService to give users the ability to reset, change passwords and unlock their account, we went to this after finally convincing "the powers that be" that password complexity and expiration is a GOOD thing. After a couple of users started complaining about "not being able to get in or unlock their account", one of the causes turned out to be that they weren't logging off their office PC, and they were changing their passwords via the ADSS portal. So we've decided that if they cant learn to log off, we'll force the machines to sleep or hibernate to prevent this, which brings me to my question Why is that every time I lookup "windows 7 sleep gpo" or any variation of that, all the hits explain how to DISABLE sleep or hibernate, is there a downside to forcing sleep or hibernation? example; https://www.google.com/#q=sleep+windows+7+gpo
