cancel
Showing results for 
Search instead for 
Did you mean: 
gmihailo
Level 1
9 5 0 0
Message 1 of 3
567
Flag Post

HP MIK Client - Calling the MIK Provider returned null.

HP Recommended
MIK Client
Microsoft Windows 10 (64-bit)

I can't get the MIK toolkit to change any bios options.

 

I am using SCCM 2002.

The PC I'm doing testing on is an Elitebook 840 G5.

 

I have the following installed

Windows 10 2004

HP BCU  (4.0.30.1)

HP Manageability Integration Kit (4.1.4.1)

HP MIK Client (4.1.1.1)

 

I have created a baseline configuration policy using the MIK toolkit to perform only one function: Enable Bluetooth.

 

When I evaluate the baseline on the PC I can see an error. If I view the report SCCM provides I can see the following:

Summary:

Name Revision Type Baseline
Policy Compliance
State Non-Compliance
Severity Discovery
Failures Non-Compliant
Rules Remediated
Rules Conflicting
Rules 4  Baseline   Error Critical 2 0 7 0 2  Application Configuration Required Compliant None 0 0 7 0 3  Application Configuration Required Error Critical 2 0 0 0

 

Errors:

Error Type Error Code Error Description Error Source Enforcement Error 0x80070001 Incorrect function. Windows

 

 

When I check the log file produced by HP, this is what i see

 

Here is an excerpt from the log file located at 

"C:\ProgramData\HP\HP MIK\Logs\CB - HP BIOS Authentication - Default - BIOS Configuration\_IntegratedBT.txt"

====================== Discovery Script ======================
Configuration Item Name = CB - HP BIOS Authentication - Default - BIOS Configuration
Provider Namespace = root\HP\InstrumentedServices\v1
Provider Classname = HP_BIOSConfig
Property Name = _IntegratedBT
Expected Property Value = Enable
Failed to retrieve the _IntegratedBT value
Compliance Result = Non-Compliant
====================== Remediation Script ======================
Configuration Item Name = CB - HP BIOS Authentication - Default - BIOS Configuration
Provider Namespace = root\HP\InstrumentedServices\v1
Provider Classname = HP_BIOSConfig
Provider Method = put
Property Name = _IntegratedBT
Property Value = Enable
Get XML Payload = <?xml version='1.0' encoding='utf-8'?>
<si:get xmlns:si='http://frameworks.hp.com/siam' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:schemaLocation='http://frameworks.hp.com/siam.xsd'>
<si:header />
<si:security>
<si:blob />
</si:security>
<si:values>
<si:get_value name='_IntegratedBT' />
</si:values>
</si:get>
Put XML Payload =
Put XML BEAM Payload =
Compliance Result = Non-Compliant
Calling the MIK Provider returned null. Please check whether 'HP_BIOSConfig' is installed.

 

 

I just don't understand why this tool has endless issues. Every few months I attempt to consider implementing it and every month there is some new issue that arises. Firstly the password wouldn't be recognised by mik, then with a new version of the client and the mik kit that was resolved. Now this issue. 

 

I have read every requirement and implemented it. 

 

why is it not working?

2 REPLIES 2
Timur_89
New member
2 2 0 0
Message 2 of 3
Flag Post
HP Recommended

Hello,

 

We have same issue.

After upgrade MIK client to version 4.1.1.1 there is 1 empty instance in  "root\HP\InstrumentedServices\v1" namespace and 'HP_BiosConfig" Class. 

MIK Client 4.0.13.1 (SP104252) - same issue

Latest working version is 3.1.7.1 (sp99711) - correctly create WMI Instance:

1 instance:

Description : HP_BIOSConfigProvider
ID : 1AEA8D13-F8F7-4F18-A4FE-BFFAFA7AC2BC
IsManaged : True
MinorSchemaVersion :
Publisher : HP Inc.
RebootRequired : True
Version : 3.1.7.1

 

 

0 Kudos
Timur_89
New member
2 2 0 0
Message 3 of 3
Flag Post
HP Recommended

I have found workaround:

 

For upgrade to latest version of HP MIK Client remove old version. Then remove "HP_BiosConfig" Class in  "root\HP\InstrumentedServices\v1" namespace. After install latest version. It should work correctly.

0 Kudos
Warning Be alert for scammers posting fake support phone numbers and/or email addresses on the community. If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation