@scottalanmiller said in VULTR NJ location: Partial Power failure.:

But how did you determine that? I just looked at my servers and their specs only match server class Xeon processors (Skylake 16MB L3) so not sure how it is possible for them to be consumer.

I don't remember exactly. A couple of years ago you could determine that there was actually no xeon of that architecture that would fit with the GHz. Since they are obscuring the actual CPU in their linux kernel you can't read the model number outright. I going from memory here, but that was the gist of it.

@DustinB3403 said in OSX Power Saving Settings:

@black3dynamite said in OSX Power Saving Settings:

Does that also prevent it from sleeping when the lid is closed?

The lid closed is powernap 🙂

giphy.gif

@wrx7m said in Windows 10 goes to sleep outside listed sleep times:

@Dashrender said in Windows 10 goes to sleep outside listed sleep times:

@wrx7m said in Windows 10 goes to sleep outside listed sleep times:

@Dashrender said in Windows 10 goes to sleep outside listed sleep times:

@wrx7m said in Windows 10 goes to sleep outside listed sleep times:

Trying to find the console lock display timeout settings for the GPO. Doesn't exist as far as I can tell. I guess I will just have to modify the reg and manually make the change.

I had to make reg changes via GPO for mine.. it was pretty easy.

Now, if I could figure out which registry setting is to set the "Console lock display off timeout" option to 0, I could just do a single step using a reg GPO.

You could also do a logon script that runs the powercfg line

I think I am just going to use PDQ Deploy for the powercfg command and set the command to run during the initial deployment phase. It should only need to be run once.

I'd be worried that future major updates (the twice yearly thing) might reset it... so finding a way to keep it (stateful) would be good.

@thecreativeone91 that looks really promising!