Sorry to dig up an old email. We are also seeing Windows 7 X64 systems with
this issue. We have deployed some older Asset Intelligence patches
kb2261172,kb2528650 and the prereq patch for R3 kb977384.
Anyone have a fix that works?
I have tried installing the (latest?) AI patch kb2796738 and re applying
the prereq patch for R3 kb977384. Still getting the following message in
the pwrprovider.log
Setting AC Default index SchemePersonalityGuid:
db310065-829b-4671-9647-2261c00e86ef, SubGroupGUID:
238c9fa8-0aad-41ed-83f4-97be242c8f20, SettingGUID:
29f6c1db-86da-48c5-9fdb-f2b67b1f44da, ACIndex:
0x00000000 PwrProvider 7/3/2013 10:59:01 AM 2072 (0x0818)
Could not write AC Setting Value. Setting GUID:
29f6c1db-86da-48c5-9fdb-f2b67b1f44da, AC index 0 PwrProvider 7/3/2013
10:59:01 AM 2072 (0x0818)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of CLIMSG_POWERAGENT_ERROR_APPLY_POWERSETTING_FAILURE
{
ClientID = "GUID:C5FF50A4-D41F-45F8-A7D0-77F4B3A5DC2C";
DateTime = "20130703175901.919000+000";
ErrorCode = "1260";
MachineName = "computername";
PowerSettingGUID = "{29F6C1DB-86DA-48C5-9FDB-F2B67B1F44DA}";
PowerSettingName = "Sleep after";
PowerSettingValue = "Sleep after";
ProcessID = 3852;
SiteCode = "001";
ThreadID = 2072;
};
PwrProvider 7/3/2013 10:59:01 AM 2072 (0x0818)
On Sun, Mar 27, 2011 at 10:11 PM, Miriyala, Vasu <
[email protected]> wrote:
> I am afraid as I am deserted out alone…, trying both Power Mgmt and Asset
> Intelligence( J kidding )and got into below situation. I am sure there
> are others out there ..if so appreciate your observations or how did you
> manage it ****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Miriyala, Vasu
> *Sent:* 23 March 2011 18:05
> *To:* [email protected]
> *Subject:* [mssms] AI KB 2444668 breaks Power Mgmt Module ???****
>
> ** **
>
> Have any of you observed the order of “SCCM Agent + SCCM R3 (KB977384) +
> Asset Intelligence Patch (KB2444668) breaks Power Mgmt to fail on agents.
> You can just try the same order****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Miriyala, Vasu
> *Sent:* 22 March 2011 10:29
> *To:* [email protected]
> *Subject:* [mssms] RE: Failed to read ValueUnitsSpecifier - SCCM Power
> Mgmt****
>
> ** **
>
> *Issue*: We are evaluating SCCM R3 features and successful in 1)
> Collecting the power reports data from clients and 2) Enforce policy
> successfully for last couple of weeks, this was a working setup. Recently
> started to observe that SCCM R3 Clients, those which has KB 2444668 (Asset
> Intelligence KB) installed on them, fails to read the power policies from
> SCCM. Power Options in control panel doesn’t show the policy assigned from
> SCCM server but falls back to default one chosen randomly from OS. Below is
> some info that helps you to understand this issue… ****
>
> ****
>
> *1st level (Glimpse)*:****
>
> **1) **Pwrprovider.log (Failed to read ValueUnitsSpecifier)****
>
> **2) **Policyevaluator.log (Namespace =
> root\ccm\policy\machine\actualconfig; Query = SELECT __CLASS, __PATH,
> __RELPATH, NonPeakPowerPlanName, PeakPowerPlanName, PowerConfigID FROM
> CCM_PowerConfig****
>
> Unknown error encountered processing an instance of class CCM_PowerConfig:
> 80041017 )****
>
> *2nd level (Observations):*****
>
> **1) **CCM_PowerConfig has WMI class that is created along SCCM R3
> (KB 977384) which contains/should contain values DurationInSec,
> NonPeakPowerPlan, NonPeakPowerPlanName, PeakPowerPlan, PeakPowerPlanName,
> PeakStartTimeHoursMin, PowerConfigID, WakeUpTimeHoursMin. Power policies
> created on SCCM server are evaluated by client and then will be stored
> client OS Power Options, with the help of this WMI class. ****
>
> **2) **We found that Issue arise because PeakPowerPlanName
> andNonPeakPowerPlanNamevalues in CCM_PowerConfig doesn’t appear
> anymore/disappears and SCCM
> Agent/Policy expects these values for successful offerings of power policy,
> hence power policy fails ****
>
> *3rd level (Investigation):*****
>
> **1) **It was our observation that Asset Intelligence KB 2444668,
> once installed is removing above values and causing SCCM Power policy
> evaluation failures. Agent at 4.00.6487.2157 works, but 4.00.6487.2161
> which is result of AI KB and it fails****
>
>
> Have any of you observed the order of “SCCM Agent + SCCM R3 (KB977384) +
> Asset Intelligence Patch (KB2444668) breaks Power Mgmt to fail on agents.
> You can just try the same order
> ****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Miriyala, Vasu
> *Sent:* 21 March 2011 09:29
> *To:* [email protected]
> *Subject:* [mssms] RE: Failed to read ValueUnitsSpecifier - SCCM Power
> Mgmt****
>
> ** **
>
> < Resending due to no responses >****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Miriyala, Vasu
> *Sent:* 17 March 2011 10:51
> *To:* [email protected]
> *Subject:* [mssms] RE: Failed to read ValueUnitsSpecifier - SCCM Power
> Mgmt****
>
> ** **
>
> Reinstalling SCCM R3 KB Article “SCCM2007AC-SP2-KB977384-x86-ENU” didn’t
> help, any clues ?****
>
> ** **
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Miriyala, Vasu
> *Sent:* 16 March 2011 17:20
> *To:* [email protected]
> *Subject:* [mssms] RE: Failed to read ValueUnitsSpecifier - SCCM Power
> Mgmt****
>
> ** **
>
> It seems I am close to nail down the issue, though not sure on why it had
> occurred now.. where all Power mgmt aspects are functioning well. Second
> how to resolve (thinking to reinstall R3 Power Mgmt KB)…but that is huge
> taks as it even hampers client health and lot of other advertisements
> compliance as well due to restart agent etc …****
>
> ** **
>
> * *
>
> *Issue*: Power Policies crated at SCCM fails to read/interpret by Agent
> to create a local power policy. This is due to incorrect name that appears
> in WMI classes pertains to Power Mgmt on client, versus what SCCM policy
> from server wants to feed the data. Policy doesn’t find right container to
> place a policy. Policyevluation log shows that it fails to give the power
> policy to agents, because it doesn’t find values pertains to below WMI
> class ****
>
> ** **
>
> SCCM Policy from Server ****
>
> SCCM Client Contains (CCM_PowerConfig)****
>
> Got extra word “Name” as highlighted****
>
> NonPeakPowerPlan****
>
> PeakPowerPlan****
>
> PowerConfigID****
>
> ** **
>
> NonPeakPowerPlanName****
>
> PeakPowerPlanName****
>
> PowerConfigID****
>
> ** **
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Miriyala, Vasu
> *Sent:* 16 March 2011 16:21
> *To:* [email protected]
> *Subject:* [mssms] Failed to read ValueUnitsSpecifier - SCCM Power Mgmt***
> *
>
> ** **
>
> I have observed that some machines which used to work fine with SCCM Power
> Mgmt to enforce policies, now throws errors in Pwrprovider.log (Failed to
> read ValueUnitsSpecifier). ****
>
> Another error in Inventory.log is here…****
>
> Collection: Namespace = root\ccm\policy\machine\actualconfig; Query =
> SELECT __CLASS, __PATH, __RELPATH, NonPeakPowerPlanName, PeakPowerPlanName,
> PowerConfigID FROM CCM_PowerConfig; Timeout = 600 secs.
> InventoryAgent 16-03-2011 12:14:19 6396 (0x18FC)****
>
> Unknown error encountered processing an instance of class CCM_PowerConfig:
> 80041017 InventoryAgent 16-03-2011
> 12:14:20 6396 (0x18FC)****
>
> ** **
>
> Thanks****
>
> Vasu ****
>
>
>
>
>
>
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is
> intended only for the person to whom it is addressed. If you are not the
> intended recipient, you are not authorized to
> read, print, retain, copy, disseminate, distribute, or use this message or
> any part thereof. If you receive this message
> in error, please notify the sender immediately and delete all copies of
> this message.****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
>
