cancel
Showing results for 
Search instead for 
Did you mean: 
  • ×
    Information
    Fix Windows 10 Update Issues

    Resolve Windows 10 or update issues on HP computer or printer– Click Here

  • post a message
  • ×
    Information
    Fix Windows 10 Update Issues

    Resolve Windows 10 or update issues on HP computer or printer– Click Here

  • post a message
Highlighted
Level 1
8 7 0 0
Message 1 of 16
514
Flag Post

HP MIK - BIOS Authentication Error

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

I'm trying to set up the HP MIK software with our SCCM installation.  I'm attempting to create baseline configurations that will enable wake on lan for our machines since everyone is working from home and some are remoting into desktop.  The baseline is going to each machine i've deployed it to but I'm getting an error on those machines that it can't enable wake on lan with the following error -

 

<si:put_response_value name="_WOL" code="999" info="Unknown error - please refer to the logs."
subcode="4" subcode_info="WMI result code - Operation failed." />

 

Any help would be appreciated.

15 REPLIES 15
Highlighted
Level 7
758 751 77 150
Message 2 of 16
Flag Post
HP Recommended

Hello

 

I know that I can ask stupid questions but:

  1. did you installed HP MIK client on pcs ?
  2.  which is/are the models are you trying to enable WOL ?
  3. did you read and saved in a file the current BIOS setting for each model, then checked if the paramenter has always the same string and as some models could use "Enable" and some others use "Enabled".

bye

0 Kudos
Highlighted
Author
Level 1
8 7 0 0
Message 3 of 16
Flag Post
HP Recommended

1.  Yes.  The client is what is giving me the error code through reporting.

2.  I'm testing right now on a group of ProOne 600 G3s.

3.  There is no Enabled or Enable.  The choices are in a drop down and include: Disable, BootOrder, BootNetwork, and Boot HD.  I'm trying to use BootOrder but I've tried BootHD it doesn't work either.

 

Thanks

0 Kudos
Highlighted
Level 7
758 751 77 150
Message 4 of 16
Flag Post
HP Recommended

Hello

When you install HP MIK, on the client PC you will find C:\Program Files (x86)\HP\BIOS Configuration Utility\BiosConfigUtility64.exe

 

On that ProOne 600 G3, open a command promt than run:

C:\Program Files (x86)\HP\BIOS Configuration Utility\BiosConfigUtility64.exe /get:600G3_bcu.txt

 

open 600G3_bcu.txt with an editor and cut and paste here WakeONLan section.

it could be something like this:

Wake On LAN
     Disabled
     Boot to Network
     *Boot to Hard Drive
     Boot to Normal Boot Order

 

* at the begin of the line, means how to computer is set.

in HP MIK , when you create the baseline, in the available setting provided by HP , you must check if the label are exactly the same, space included.

 

what is the current BIOS setting and what if what you wanto to have ?

 

BIOS setting can be changed via SCCM even sending a powershell command provided by HP with HP Client Management script library.

 

bye

 

 

0 Kudos
Tags (1)
Highlighted
Author
Level 1
8 7 0 0
Message 5 of 16
Flag Post
HP Recommended

Mine actually ended up being c:\Program Files (x86)\HP\HP MIK Client>BiosConfigUtility.exe /get:600G3_bcu.txt.

 

The file shows:

Wake On LAN
Disabled
Boot to Network
*Boot to Hard Drive
Boot to Normal Boot Order

 

So it went at some point.  I should make mention that I am using the SCCM integrated MIK with the Bios Configuration building the Baselines.  That is where I'm getting the failures.

 

I'm still getting the error from ProgramData\MIK\Logs:

 

 

====================== Discovery Script ======================
Configuration Item Name = ProOne 600 G3 - BIOS Configuration
Provider Namespace = root\HP\InstrumentedServices\v1
Provider Classname = HP_BIOSConfig
Property Name = _WOL
Expected Property Value = BootOrder


__GENUS : 2
__CLASS : __PARAMETERS
__SUPERCLASS :
__DYNASTY : __PARAMETERS
__RELPATH :
__PROPERTY_COUNT : 2
__DERIVATION : {}
__SERVER :
__NAMESPACE :
__PATH :
ReturnValue : 0
xmlResponse : <?xml version="1.0" encoding="UTF-8"?>
<si:get_response xmlns:si="http://frameworks.hp.com/siam"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://frameworks.hp.com/siam siam.xsd">
<si:header/>
<si:security><si:blob>
not implemented
</si:blob></si:security>
<si:disposition code="Success">OK</si:disposition>
<si:values>
<si:get_response_value name="_WOL" code="0" info="OK" subcode="0" subcode_info="Operation
succeeded." interpretAs="string" >BootHD</si:get_response_value>
</si:values>
</si:get_response>

PSComputerName :

 

Property Value = BootHD
Expected Property Value = BootOrder
Compliance Result = Non-Compliant

 

====================== Remediation Script ======================
Configuration Item Name = ProOne 600 G3 - BIOS Configuration
Provider Namespace = root\HP\InstrumentedServices\v1
Provider Classname = HP_BIOSConfig
Provider Method = put
Property Name = _WOL
Property Value = BootOrder
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='_WOL' />
</si:values>
</si:get>
Put XML Payload =
Put XML BEAM Payload =


__GENUS : 2
__CLASS : __PARAMETERS
__SUPERCLASS :
__DYNASTY : __PARAMETERS
__RELPATH :
__PROPERTY_COUNT : 2
__DERIVATION : {}
__SERVER :
__NAMESPACE :
__PATH :
ReturnValue : 0
xmlResponse : <?xml version="1.0" encoding="UTF-8"?>
<si:put_response xmlns:si="http://frameworks.hp.com/siam"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://frameworks.hp.com/siam siam.xsd">
<si:header/>
<si:security><si:blob>
not implemented
</si:blob></si:security>
<si:disposition code="Success">OK</si:disposition>
<si:values>
<si:put_response_value name="_WOL" code="999" info="Unknown error - please refer to the logs."
subcode="4" subcode_info="WMI result code - Operation failed." />
</si:values>
</si:put_response>

PSComputerName :

 

Compliance Result = Non-Compliant
Failed to set BCU policy settings

0 Kudos
Highlighted
New member
1 1 0 0
Message 6 of 16
Flag Post
HP Recommended

i have the same problems 😞 Helllp Guys

0 Kudos
Highlighted
Level 7
758 751 77 150
Message 7 of 16
Flag Post
HP Recommended

Hello Mbriskey

 

your ProOne is currently configured with "Wake on LAN" enabled and it will "Boot to Hard Drive".

I see it from BiosConfigUtility output.

IF I have time I will start my VM where I have installed SCCM + HP MIK server version 3.1.15.1 released Jan 29 2020 and on client , I have an 800 G3 DM available , where I will install latest MIK CLient version 3.1.7.1 November 2019

 

and I'll see what happens.

 

in your SCCM console , in Monitoring , Overview , deployments, you should see the baseline you created to change BIOS setting.

in the "action" column, which is the status "Remodiate" or "Monitor" ?

 

bye

 

 

0 Kudos
Highlighted
Author
Level 1
8 7 0 0
Message 8 of 16
Flag Post
HP Recommended

They are remediate.  5 have the error 0x800703E7 with Error performing inpage operation.  The 6th has error 0x80070001 incorrect function.

0 Kudos
Highlighted
Level 7
758 751 77 150
Message 9 of 16
Flag Post
HP Recommended

Hello

 

before I start to create a baseline using my equipment , did you check if your environment is updated, following what is written in the guide about system requirements ?

https://ftp.hp.com/pub/caps-softpaq/cmit/whitepapers/HPMIKWhitepaper.pdf

 

bye

0 Kudos
Highlighted
Author
Level 1
8 7 0 0
Message 10 of 16
Flag Post
HP Recommended

Yes.  Those are the directions I'm following.  Our SCCM is updated to version 1910 and the latest MIK is installed. 

0 Kudos
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