After upgrading our site to R3 and applying the 977384 hotfix to our clients I've still got a handful of systems that still show the ConfigMgr Power Managment Agent at 4.0.6487.2000. Actually, in the Control Panel Applet, the Agent is not listed but in Resource Manager for the client we see SMS Power Management Agent 4.0.6487.2000. Is there a way to 'add' the Power Management Agent back in, manually?Orange County District Attorney

Well, that is a WMI specific issue now similar to this one: http://support.microsoft.com/kb/937634. Have you tried reinstallaing the hotfix on one of those clients? Note that you can directly check on the client agent versions in the registry on a client system: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/0a830641-5b76-44eb-b047-979701460eb4.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Well, that is a WMI specific issue now similar to this one: http://support.microsoft.com/kb/937634. Have you tried reinstallaing the hotfix on one of those clients? Note that you can directly check on the client agent versions in the registry on a client system: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/0a830641-5b76-44eb-b047-979701460eb4.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Have you verified that the update actually ran successfully on those systems and that they have reported their hw inventory recently?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I see the update (977384) in View Installed Updates. I've also peeked inside the installation log file and that showed it installed correctly. The machine is getting inventoried daily as well. I re-ran the client install from the SCCM console but no change with that. Orange County District Attorney

I would check the on the last HW inventory time as that seems to be the only possibility now. You can see this resource explorer under workstation status. If this proves to be the issue, we need to start troubleshooting hw inventory on those systems.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

The last HW Inventory was at 11:19 today. The interesting thing was what happened after reading the power stuff. I'm not sure if this has any bearing on anything. Collection: Namespace = root\ccm\policy\machine\actualconfig; Query = SELECT __CLASS, __PATH, __RELPATH, NonPeakPowerPlanName, PeakPowerPlanName, PowerConfigID FROM CCM_PowerConfig; Timeout = 600 secs. Unknown error encountered processing an instance of class CCM_PowerConfig: 80041017 We haven't configured any power settings yet. Orange County District Attorney

The last HW Inventory was at 11:19 today. The interesting thing was what happened after reading the power stuff. I'm not sure if this has any bearing on anything. Collection: Namespace = root\ccm\policy\machine\actualconfig; Query = SELECT __CLASS, __PATH, __RELPATH, NonPeakPowerPlanName, PeakPowerPlanName, PowerConfigID FROM CCM_PowerConfig; Timeout = 600 secs. Unknown error encountered processing an instance of class CCM_PowerConfig: 80041017 We haven't configured any power settings yet. Orange County District Attorney

I reapplied the hotfix and it fixed my issue. Thanks for the help. I can now see the ConfigMgr Power Managment Agent back in the components section. I think my problem arose when I mistakenly re-installed the SCCM client again. It appears that I need to be sure if I reinstall any client I make sure that I reapply any hotfixes. Lesson learned! Orange County District Attorney