Start a Conversation

Unsolved

This post is more than 5 years old

M

1503

August 29th, 2018 12:00

5050, Bios Auto On hr command doesn't apply

Hello Guys 

I am using the command configure tool to build a bios setting update.

Currently trying to change the Auto On time from 12:00 AM to 8 PM (20:00) 

and once I go into the bios its still set to its default values

Below are the logs :

2018/08/29 13:13:58 cctk - The option 'WakeOnLanBootOvrd' is not available or cannot be configured
through this tool.
2018/08/29 13:13:58 cctk - AcPwrRcvry=Off
2018/08/29 13:13:58 cctk - AdminSetupLockout=Disabled
2018/08/29 13:13:58 cctk - AutoOn=Everyday
2018/08/29 13:13:58 cctk - AutoOnHr=20
2018/08/29 13:13:58 cctk - AutoOnMn=15
2018/08/29 13:13:58 cctk - BlockSleep=Disabled
2018/08/29 13:13:58 cctk - ChasIntrusion=SilentEnable

192 Posts

March 4th, 2019 08:00

Hi chrisp6825,

I use these commands to get the BIOS version on the remote PCs we manage running Windows.

Command Line
wmic bios get smbiosbiosversion
Powershell (Local)
(Get-WmiObject win32_bios).SMBIOSBIOSVersion


The following will get you the Service Tag

Command Prompt (Local)
wmic bios get serialnumber
Powershell (Local)
(Get-WmiObject win32_bios).SerialNumber

1 Message

March 4th, 2019 08:00

I'm having a similar issue regarding the --AutoOnHr parameter on some of our Optiplex 3050 PCs.

I've found it will only accept hour values of 0-12 and will ignore any value over 12, without any errors returned.

I fear a BIOS firmware update may be applicable to the PCs with this issue, but I've not been able to verify the BIOS versions on these remote PCs.

 

As a side note, when I first came across this issue I noticed that querying the value for --AutoOnHr returned 34, and would not store any different value until I stored a value between 0-12.

No Events found!

Top