Determine what is pushing power plan onto device (Weird problem)

[Devastator0]

Hi TPU Brainstrust,

I need some help (please bare with me while I do my best to explain this).

I have this weird problem at my work (I'm a Field engineer) whereby when we build devices using our SOE via an SCCM build process, the devices, once the build has completed, get this weird power policy pushed to them (basically the power policy is configured that even though devices are on AC power, they are set to turn off at 24 hours. This is annoying for us - Field IT - because there is a backend compliance process whereby we need the device to stay online so it can grab up to date Windows Updates, AV definitions and have other software auto deployed to it to become compliant. Having the machine shut off is quite annoying while you're in this phase). It's a custom made power policy, not anything built into Windows. I initially thought that there was something weirdly configured in group policy that was causing this power plan to be pushed out but our AD team assure me that it's nothing being done on the domain/GPO side of things (and a gpresult /h sort of confirms that).

I've hit up our SCCM team and they say that they aren't pushing any sort of power policies from their end either. We also utilise McAfee as our AV solution and I've even hit up our InfoSec team to make sure that something isn't being pushed from them via ePO (management console side) and they confirm that it isn't them.

The AD team (an annoying outsourced vendor) keeps telling me to check the PC's themselves and any "local policies" but I just laugh because we (at a country level - I work for a global business) don't set or specify anything like that, all policies applied to endpoints come either via a GPO or SCCM.

What this essentially boils down to is that I'm trying to figure out if there is a way, on a Windows 10 device, to find out what is causing a specific power policy to be applied. Like is there somewhere I can look at in Windows where it'll say something like "app/process xxx has modified power plan blah blah blah".

I hope my above text wall makes some sort of sense to someone because I'm at my wits end with my internal support teams so if someone can point me in the right direction, believe me when I say that I will be extremely grateful. If you need any further info on this, drop a comment in and I'll do my best to supply the details.

Many thanks to anyone who replies!

 

[Bill_Bright]

First, no clue.
Second, just thinking out loud to maybe trigger something useful in someone else.

basically the power policy is configured that even though devices are on AC power, they are set to turn off at 24 hours.

You seem to suggest this should not happen because they run on AC. I don't see what being powered by AC has to do with it. My TV, for example, will shut off after so many hours if there is no input from me (adjust volume, change channel, change signal input, input source, etc.). And do you really mean the device actually runs off AC? Or is it like a computer, or monitor, or printer or so many other devices today that plug into the wall, but then the AC is immediately converted to DC by a transformer or switching PSU, which then powers the device?

Does the machine really turn "off" or is it just going into a standby state? Big difference.

And before you connect it to the network, what does the power plan say?

You say it connects on line, how? Ethernet or wireless? What if you disconnect the network connection? Does the power plan change and does the device still turn off?

As for where to look, I don't know. Maybe you can look in the event logs to at least get a timestamp of when a change took place.

 

[thewan]

Did you try disabling power management, or exclude those devices from power management? If it is not necessary, or detrimental to have those devices power managed, it might be best to not enable power management or totally excluding them.