Intel® NUCs
Support for Intel® NUC products
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
11882 Discussions

Keyboard locked on BIOS screen when provisioned with SCCM 2007 SP1

idata
Community Manager
2,905 Views

Hello!

I seem to have encountered another strange issue (or is it a feature) when using the Out of Band management console in SCCM 2007 SP1 to manage vPro clients. If I access the BIOS on a client once using SOL on the OOB console, I cannot then access the BIOS directly on the machine. The F2 keypress works and shows me the initial BIOS screen, but the keyboard locks up. I did NOT select Lock Keyboard in the OOB console when I booted to BIOS.

My problem is compounded by the fact that the machine is no longer properly provisioned in SCCM. This means that I cannot connect to it via OOB console, and hence I'm completely locked out of the BIOS. Even using the motherboard jumper to go into maintenance mode does not work, since the keyboard remains locked even in maintenance mode.

My questions are - a) Is this a security feature or a known issue? and b) How do I do a hard reset of the bios?

0 Kudos
8 Replies
Matthew_R_Intel
Employee
705 Views

This indeed is a strange issue and I have not personally sense this. I am assuming that you have rebooted the device and you have not regained control of the keyboard locally? Can you initial an AMT power control from the Collection context menu (right click on the client, select OOBC, then power control). From previous posts, I believe you are using a HP 7800, To reset the BIOS, you should be able to push and hold (for about 5 seconds) the yellow button near the memory slots or pull the CMOS battery; you need make sure you have the AC power unplug prior to doing so.

In regards to OOB not contenting... you can look in the <ConfigMgrInstallationPath>\AdminUI\AdminUILog/Oobconsole.log. I'm guessing you are going to something like unable to retrieve power state. This traditional is related to Kerberos issues. If you are able to perform Collection Based power control, then I'm almost certain that kerberos is the problem. The strange thing is you mentioned that you were previously in OOBC, which if you where able to get into it your configuration is most likely OK. I have seen issues where the Kerberos authentication token becomes invalid and simply logging off the OS that you are running the OOBC from and back in resolves the issues.

--Matt Royer

idata
Community Manager
705 Views

Ok here's a little more infomation :

The strange thing is that I DO have keyboard control of all my AMT test machines once they get past the POST stage. It is only in the BIOS setup (after hitting F2) that they keyboard locks up. I know its only the keyboard that has locked up and not the machine, because I can still see the BIOS clock ticking away happily. I can use the bios setup screen properly through the OOB console.

I am not using HP machines, we are a PC manufacturer and I'm testing on our own kit. The only modification we have done to the JO boards is to add our own splash screen, everything else is standard.

I've tried EVERYTHING possible to hard reset the bios... including moving the yellow jumper, popping the battery, and flashing the BIOS with the appropriate switches to reset defaults.. and nothing seems to work. the AMT settings are still intact, there appears to be no way to wipe them without explicitly selecting "Reset AMT" in the BIOS. This is a problem because the keyboard is locked out in maintenance mode as well.

I appear to be in a Catch 22 situation, because OOB console refuses to connect to this one machine.. the only way around it seems to be to reset AMT, and I cant do that because I cant get into the BIOS

idata
Community Manager
705 Views
<![CDATA[<div>This is a problem introduced with one of the more recent JO BIOS revisions. This has been seen with BIOS versions JOQ3510J.86A.0925.EB and JOQ3510J.86A.0931.EB. The desktop motherboard BIOS team has reproduced this failure and is working on a solution. I will update with a date on a new BIOS release as soon as it is available. ]]><![CDATA[<div>Dan Borud ]]>

idata
Community Manager
705 Views

Thanks Dan.. that confirms my suspicion that it was a bug in the BIOS (as opposed to a "feature" that some people said it was). Just so you know, I've tried version 933 (pre release) of the BIOS (upgraded the machine that had locked up), and I still cant use the keyboard in the BIOS.

idata
Community Manager
705 Views

Just to add on to my last post, I have now tried the release version of firmware version 0933 and it still exhibits the same problem.

Daniel_B_Intel1
Employee
705 Views
<![CDATA[<div>There is a new BIOS available for download for the DQ35JO board that fixes this keyboard lockout issue. Below is a portion of the release notes detailing the keyboard lockout issue is fixed, this has been verified in our lab as well and solves the issue. ]]><![CDATA[<div>[http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&# 38;Inst=Yes&# 38;ProductID=2783&# 38;DwnldID=16737&# 38;strOSs=164&# 38;OSFullName=Windows] Vista* 32&# 38;lang=eng ]]>

BIOS Version 0942

About This Release:

  • August 11, 2008

  • JOQ3510J.86A.0942.2008.0807.1958

  • VBIOS info:

Build Number: 1653 PC 14.34 06/08/2008 20:37:36.

  • SATA RAID info:

Intel(R) RAID for SATA - v7.6.0.1011

  • SATA AHCI info:

Version UPSD src 05-09-2008 for ICH9

  • PXE Nahum2 info:

Intel(R) Boot Agent GE v1.3.22.

  • ME firmware build: ME FW binary PV build iAMT_ASF2_QST_3.2.1.1022.

*

New Fixes/Features:

*

  • Locked MCH configuration.

  • Added support to DQ35JO for ME Power Package 2 and 4 (Only take

effect after doing BIOS Recovery).

  • Fixed keyboard permanently locked in BIOS Setup after using AMT

SOL session.

  • Updated Intel Branding String in BIOS Setup.

  • Fixed issue where keys pressed in POST are visible after boot in

the BIOS Data Area (BDA) keyboard buffer.

  • Fixed Incorrect Memory Size Decrease report.

  • Updated PXE code Intel(R) Boot Agent GE v1.3.22.

  • Updated Video BIOS v1653.

idata
Community Manager
705 Views

Thanks for the update Dan... we have tested the new bios and it does indeed fix the keyboard lockout issue! We have found some other little "issues" with this bios release, but we escalate them through the correct channels.

idata
Community Manager
705 Views

patient safety <![CDATA[<a href=http://forums.sjgames.com/member.php?u=45948>buy generic propecia It is required by law for a person http://forums.plaxo.com/member.php?u=17186 dirt cheap cigarette provide up-to-date news and information about http://board.talibkweli.com/index.php?showuser=2920 levitra online]]>

Reply