HP DC7900 5.1.10 in SCCM is showing up as "Not Supported"

DPopr · ‎09-13-2009

Let me set this scenario up by laying out our environment.

We have about 2000 computers we manage in multiple building across our campus. We have 4 different model PC's. The last two purchases support AMT. 440 Dell Optiplex 755's and about 650 HP DC7900's.

We have been working to get our SCCM 2007 SP1 working with AMT for several months off and on. Having searched the AMTOPMGR.LOG file and going through errors one at a time I have found about 5 post SP1 patches to apply to the server. We couldnt get either machine provisioning in SCCM.

After talking to DELL and checking out their latest BIOS it updated us from version 3 to 3.2.1. We deployed that BIOS to our machines and once we did that the Dell 755's provisioned and are manageable now.

After that experience a coworker found that there was a new BIOS and new ME firmware for our HP's so we applied those updates and it brought our 5.0.1 ME firmware up to 5.1.10.

Either before or after the update they showed up in the SCCM console as "Not Supported" I have deleted a couple machines with no change in status when they return.

I do not see anything in the AMTOPMGR.LOG file for them so I can't really report anything from there.

This is repeating in the client log files:

BEGIN oobmgmt 9/13/2009 6:13:36 PM 3648 (0x0E40)

Retrying to activate the device. oobmgmt 9/13/2009 6:13:36 PM 3648 (0x0E40)

Can not read last OTP from [Software\Microsoft\Sms\Mobile Client\OutOfBand Management\OneTimePassword], (0x80070002) oobmgmt 9/13/2009 6:13:36 PM 3648 (0x0E40)

Can not set new OTP or load last OTP! oobmgmt 9/13/2009 6:13:36 PM 3648 (0x0E40)

Failed to Call GenerateOTPPassword provider method, 80041001 oobmgmt 9/13/2009 6:13:36 PM 3648 (0x0E40)

END oobmgmt 9/13/2009 6:13:36 PM 3648 (0x0E40)

I can report that hitting the yellow CMOS reset button will get the machine provisioned but that is not really a possiblity as I said the machine are all over our campus in multiple buildings.

DPopr · ‎09-15-2009

Today I can report that after reading more on these forums I tried to diable "Auto Provisioning" in SCCM on a machine let that setting take effect and then turn auto provision back on and the OTP error is gone in the machines oobmgmt log, in fact that log shows now errors and reports "activated".

The SCCM amtopmgr log now shows for that machine:

The provision mode for device XXXXX-P2205.XXX.tamu.edu is 1. SMS_AMT_OPERATION_MANAGER 9/15/2009 8:17:50 AM 7896 (0x1ED8)

Try to use provisioning account to connect target machine XXXXX-P2205.XXX.tamu.edu... SMS_AMT_OPERATION_MANAGER 9/15/2009 8:17:50 AM 7896 (0x1ED8)

Fail to connect and get core version of machine XXXXX-P2205.XXXX.tamu.edu using provisioning account # 0. SMS_AMT_OPERATION_MANAGER 9/15/2009 8:18:10 AM 7896 (0x1ED8)

Try to use default factory account to connect target machine XXXXX-P2205.XXXX.tamu.edu... SMS_AMT_OPERATION_MANAGER 9/15/2009 8:18:10 AM 7896 (0x1ED8)

Fail to connect and get core version of machine XXXXX-P2205.XXX.tamu.edu using default factory account. SMS_AMT_OPERATION_MANAGER 9/15/2009 8:18:30 AM 7896 (0x1ED8)

Try to use provisioned account (random generated password) to connect target machine XXXXX-P2205.XXXXXXX.tamu.edu... SMS_AMT_OPERATION_MANAGER 9/15/2009 8:18:30 AM 7896 (0x1ED8)

Fail to connect and get core version of machine XXXXX-P2205.XXXX.tamu.edu using provisioned account (random generated password). SMS_AMT_OPERATION_MANAGER 9/15/2009 8:18:50 AM 7896 (0x1ED8)

DPopr · ‎09-16-2009

I guess I need to hold off on that update above. Only one macine is not showing the OTPPassword generation error, I performed the same remove of the auto provisioning setting for all my machines, then added it back 4 hours later (update interval is 90 minutes) and no other machine seems to be exhibiting this change.