Jump to content


adurrant

Push HP BIOS Settings via OSD (Windows 10)

Recommended Posts

Hi guys,

Hoping to find people that have managed to push HP BIOS settings via OSD (Windows 10), I've pretty much followed this guide (only the folder structures are slightly different) but I'm having issues actually deploying the settings, setting the BIOS password seems to work okay and I've read that for certain TPM settings to be pushed then a BIOS password must be set prior.

My folder setup:

image.png.495880ef7086ff328e488e2cdb403de4.png

image.png.c819d2462605b4de4740978dc059c82d.png

image.png.db1505008a6ee162aaeb81cdf446bfe1.png

BIOS Config settings to push:

BIOSConfig 1.0
;
;     Originally created by BIOS Configuration Utility
;     Version: 4.0.24.1
;     Date="2018/03/20" Time="14:53:23" UTC="0"
;
;     Found 215 settings
;
Virtualization Technology (VTx)
    Disable
    *Enable
    Reset to default
TPM Reset to Factory Defaults
    *No
    Yes
Reset of TPM from OS
    *Disable
    Enable
OS Management of TPM
    Disable
    *Enable
Activate TPM On Next Boot
    Disable
    *Enable
TPM Device
    Hidden
    *Available
TPM Activation Policy
    F1 to Boot
    Allow user to reject
    *No prompts
    Hide
TPM Device Security Level
    Change
    *View
    Hide
OS Management of TPM Security Level
    Change
    *View
    Hide
Reset of TPM from OS Security Level
    Change
    *View
    Hide

Task sequence setup:

image.png.b9af1c1bad55f7ff1ae007b1c7c059ff.png

image.png.33f72d5f2e9f31c7d11027424bb7d1b5.png

The bios password sets just fine, but in the SMSTS log I see the following for BIOS settings - HP EliteBook 840 G2 itself:

image.thumb.png.0073de6bc1ea7eefe149e91916cc39ff.png

Have attached the SMSTS.log.

Any help would greatly be appreciated, I've been working on this for the last couple of days without success, I've tried:

  • Adding CMD.exe /C prefix (same error)
  • Changing the format of the file to repset (same error)
  • Ran the command manually on the device and works just fine with the same configuration files (as .txt and .repset)
  • Tried running the steps in WinPE rather than in the operating system (same error)

Thanks in advance.

smsts.log

Share this post


Link to post
Share on other sites


Hi Ath3na,

Sure, I looked at this error code, I don't how it's not valid as it works manually and it's in the same folder in the package, I'm thinking it's a red herring... 

Share this post


Link to post
Share on other sites

should the command be something like ?

biosconfigutility.exe /CurSetupPasswordFile:"passwordfile.bin" /setconfig:Elitebook820.REPSET

Ours are like this.

The password is set at an earlier stage, both occur during winpe

Share this post


Link to post
Share on other sites

Hello,

Thanks, I have tried something like this, I will try this and get back to you. :) curious, where abouts in your task sequence do you have these steps? Before partition disks I assume?

Share this post


Link to post
Share on other sites

I could do this, I'm not sure if I'll have any joy, the BIOS settings don't get applied when the task sequence fails. I'm currently trying running the command line as a defined user rather than system.

Share this post


Link to post
Share on other sites
48 minutes ago, Ath3na said:

should the command be something like ?

biosconfigutility.exe /CurSetupPasswordFile:"passwordfile.bin" /setconfig:Elitebook820.REPSET

Ours are like this.

The password is set at an earlier stage, both occur during winpe


Exactly as this post says. The manual refers to the proper config file that is .REPSET

 

Additionally, I believe I ran into this issue with my Elitebook 8560P. What I did was use the bios tool to extract the current REPSET, and then ensure that the commands I am using match what my existing configuration file says. I found that some of the setting names didn't match what the instructions said.

Share this post


Link to post
Share on other sites

Thanks both, trying this config out now:

image.png.ff7fda5fe301cec89fdc12e3496789bd.png

 

Can confirm that the contents of the repset file is good as when ran manually, it does what I need it to do...

Share this post


Link to post
Share on other sites

Hi gents,

 

Unfortunately my last screenshot exited with the same error code, I'm going to try the 32-bit application tomorrow and post results here.

Share this post


Link to post
Share on other sites

What version of BiosConfigUtility64.exe are you using?  I am not sure when the change occurred, but I believe the /CurSetupPasswordFile switch was replaced with /cpwdfile.  This is what v4.0.21.1 is showing.  We also have continue on error checked on the step as I believe it will technically fail as it is trying to write to some lines from the config file to read-only things in the bios.  I think you could go through the config and remove what is read-only as an alternative also.  We reference a package without a program to accomplish this during OSD.

image.png.4ae91b94233e3a3d97cb7b6bd512abf0.png

image.thumb.png.e2f478672cba3e992b6f892c192e1a01.png

image.png.36c64beaf1018eabfd34df86ea0f2fea.png

Share this post


Link to post
Share on other sites

Also, what path is your package source referencing?  You are using the same package on the two steps, but you have two separate sub folders where the password .bin files are kept.

EDIT: In reviewing the 4sysops post, I see they specified the ~configs subfolder within their command in the TS.  Assuming your COL0009C package source is the root of the "HP EliteBook 840 G2 Configuration Files" folder, you would need to specify the subfolder in the path to the config files and encrypted password bin files.

Share this post


Link to post
Share on other sites

@danielclasson your procedure worked perfectly. Thanks for putting all of that information together.

I have begun to play around with HP's Client Management Script Library. It's a (surprisingly) robust set of PowerShell modules for a lot of activities - Softpaq repositories, BIOS/firmware updates, BIOS config baselines and the like. It seems to do a lot of things and do them well. 

Still, though, we don't adjust procedures like BIOS updates until we've done significant testing over a period of months. CMSL is worth a test drive for sure, though.

https://ftp.hp.com/pub/caps-softpaq/cmit/hp-cmsl.html

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...