I've been having issues with the above models of hp computers booting up in my kbe environment. I have the most recent driver pack from kace and have made my kbe around that.

Currently I do have some dx2200's that will boot into my kbe just fine however every dx2200 with a different part number just blue screen before I can get to the kace deployment screen. Some say irq not less or equal. Others just say stop and blue screen.

As for the dx2000's they just always hang just before the kace recovery screen and I've never actually gotten to even try to do a scripted install to them.

Has anyone ever had issues like this? Or have any links that may be of use to help?

I will provide part numbers ASAP for the pc's
Also I called hp already. They informed me they were all out of warranty and even if they were covered they wouldn't help..

Thanks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The working DX2200 part number on the top of the case is EN245UA#ABA. The DX2200 part number that 100% of the time will blue screen is EN286UT#ABA.

Also the DX2000 part number that has never worked and always hung up right before the deployment screen is PX836AA#ABA.

All of these systems are based on P4 CPU's.
Answered 08/03/2011 by: Boz
Senior Yellow Belt

Please log in to comment
1
Boz, are the storage modes set differently on the non-working systems versus the working ones? What mode are they set to (usually AHCI/RAID/ATA)? Are the storage controllers or NICs different on the non-working systems versus the working ones?
Answered 08/11/2011 by: warmep
Second Degree Green Belt

Please log in to comment
0
Warmep, I've searched through the BIOS for AHCI and went into every menu/submenu looking for it. Apperently this BIOS either does not let me configure it, or even display what the setting is.

Kfeid, I've done as you suggested and have made it further then ever. Currently my test machine that previously blue screened with my last KBE has made it almost to the scripted install page. I've passed the initializing of the win PE and now have a white screen with a white box in front of it. No text or anything has appeared in the last 10 minutes. This machine was a known problem machine so I'm not too surprised it is not functioning normally. I will try with a different box to see if I can get to the scripted install page.
Answered 08/18/2011 by: Boz
Senior Yellow Belt

Please log in to comment
0
So I got the HP 2200's past the KBE area and into where Kace has the deployment screen with the blue background. They are hanging at starting VNC for some reason and its haulting the whole process. I went into the K2000 and disabled the VNC in boot environments in hopes to avoid this but it still does not work. Currently the HP dx2200 is sitting at a white screen, with a white box in front of it. No text or anything, but if you close the white box, sometimes it goes to a Kace screen and says in large black font. "Logging into server" I've let it sit for about 10 minutes on the screen and nothing seems to happen.
Answered 08/18/2011 by: Boz
Senior Yellow Belt

Please log in to comment
0
Also I've flashed and updated the BIOS to the most recent update as of 2008. And I've learned that the part number on the dx2200's that is working is actually an older box then the ones that are failing. Thanks HP...
Answered 08/18/2011 by: Boz
Senior Yellow Belt

Please log in to comment
0
So today the issue has been resolved.

Apperently these machines have 512 mb of ram and the video card defaults to using 64mb (onboard). Although even after lowering the ram to as low as we could go to 32 for the video it still would not go, however it did go further in the setup. We added 256 mb to our 512 machine and it began working just fine. So there you have it, Weird things happen when you do not have enough ram. Thanks guys for all the suggestions!
Answered 08/18/2011 by: Boz
Senior Yellow Belt

Please log in to comment
1
Boz, thanks for the updates!

The KBE boot environment requires at minimum 496MB of RAM to properly deploy. As more drivers are added to the KBE share, the memory requirement goes up. As you found, integrated devices like audio and video can also take their own chunks out of your total RAM.

http://www.kace.com/support/kb/index.php?action=artikel&cat=70&id=1044&artlang=en
Answered 08/22/2011 by: warmep
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity