I think Google is giving you all those links for it just because it is much more common for people to disable sleep and hibernate then to enable it. It could be a convenience for them or it could be because CEOs around the world cannot wait the tens of seconds for their machine to wake up.
As for the disadvantages, Hibernate will write the contents of memory to disk. Since everything running on a computer is in memory (that includes things like the private keys which can be used for decryption) it is best practice to disable hibernation when using full disk encryption. It is more important to disable (or better yet not even have) Direct Memory Access ports like thunderbolt. Hibernate will also create a file that is the same size as the computer's memory which can cause space issues if the computer has a lot of RAM and a small SSD. Sleep doesn't suffer from the above two issues but scenarios where a user signs into the VPN and then does a remote desktop connection to their work desktop can have problems with sleep and hibernate. WOL helps but you have to be able to connect to a running device on that network to send the magic packet and users may only have access to the VPN and their own box. - Stephen From: [email protected] [mailto:[email protected]] On Behalf Of J- P Sent: Sunday, August 07, 2016 12:41 PM To: NT <[email protected]> Subject: RE: [NTSysADM] Force sleep downside I thin I didn't explain my question properly, While I agree with your comments, as a wise man once said "there are seldom good technological solutions to behavioral problems", (Ed Crowley) In this case though, I can do something. WOL will resolve the Remote Access issue, and I will update the portal page with a warning (however if they use the app on the their phones they probably wont see it) I do know how to apply the policy, my concern was why all hits/docs/articles were geared towards disabling it thx ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Force sleep downside Date: Sun, 7 Aug 2016 15:59:22 +0000 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]> [mailto:[email protected]] On Behalf Of J- P Sent: Sunday, August 7, 2016 9:38 AM To: NT <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[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
