PENDING SCCM Power policy applied and then it's not

[steve42399]

We have been deploying Power Profiles for years successfully to our devices. Within the past week somethings changed to cause those settings to still get applied but at times it then gets unapplied and is changed to Balance. We have workstations on PDUs and this is causing me to have to login to the PDU and restart them.
My first guess was a change to Group Policy which would win over MECM policy. I ran gpresult /h C:\gpo. html and opened the log and the only thing power management applied is require Password on wake Plugged in or not.

There were some changes made to the Client Settings but couldn't find anything of interest there. These settings were specific to the Servers and not Workstations.

I noticed this in the log
Existing power config $$$00283 deleted successfully ($ = Confidential)
This is the Device Collection for the power profile where this laptop is present.. Why would it delete it. I verified that the collection still exists

I looked at the Status Message Queries and couldn't see where this was modified in any way.

I ran the Action in Config Manager and restart ccmexec.exe and the policy is reapplied. Peak or Non-Peak

The log then shows that $$$00283 was applied
(New Config $$$00283 received successfully)

It does have that "Group Policy power settings are detected on this computer." but as I explained above the only settings I found is making sure users are prompted with a password.

I ran gpupdate /force and wait but the plan does not change.

The question is why are these settings not "sticking" within the last week or so?

I should add that we are an Hybrid environment. I checked with our MDM administrator and he checked for power management policy and found none. We do apply power management to our AVD but that's it.

 

[steve42399]

We have been deploying Power Profiles for years successfully to our devices. Within the past week somethings changed to cause those settings to still get applied but at times it then gets unapplied and is changed to Balance. We have workstations on PDUs and this is causing me to have to login to the PDU and restart them.
My first guess was a change to Group Policy which would win over MECM policy. I ran gpresult /h C:\gpo. html and opened the log and the only thing power management applied is require Password on wake Plugged in or not.

There were some changes made to the Client Settings but couldn't find anything of interest there. These settings were specific to the Servers and not Workstations.

I noticed this in the log
Existing power config $$$00283 deleted successfully ($ = Confidential)
This is the Device Collection for the power profile where this laptop is present.. Why would it delete it. I verified that the collection still exists

I looked at the Status Message Queries and couldn't see where this was modified in any way.

I ran the Action in Config Manager and restart ccmexec.exe and the policy is reapplied. Peak or Non-Peak

The log then shows that $$$00283 was applied
(New Config $$$00283 received successfully)

It does have that "Group Policy power settings are detected on this computer." but as I explained above the only settings I found is making sure users are prompted with a password.

I ran gpupdate /force and wait but the plan does not change.

The question is why are these settings not "sticking" within the last week or so?

I should add that we are an Hybrid environment. I checked with our MDM administrator and he checked for power management policy and found none. We do apply power management to our AVD but that's it.

This issue is resolved it was the priority change that a contractor made to the Client Settings. Reverting the settings back fixed the issue.