KBE fails to load when Windows logo appears
I would still consider myself a KACE newbie, so keep that in mind...
I've used our K2000 to install both scripted installs and system images over the past several months. However, on a new batch of laptops we just received, I'm experiencing a problem with KBE loading that I haven't seen before.
I first tried to load KBE x64, and the KBE image begins to load from the K2000. However, when WinPE starts to load and I can begin to see the Windows logo appear on the screen, the screen flashes black and the system becomes unresponsive. There is no text or information on the screen after the logo disappears.
I first thought this might be a missing driver, so I added the nic driver to the kbe_windows_64/kace folder, recompiled the drivers, and built a new KBE. The problem still happens.
I have also tried to manually install Windows 7 from the original disc, and when doing so, everything works fine. The fresh install does list many missing drivers, including nic, graphics, audio, chipset, etc. I have all of the drivers available from the company.
Here's a few specifics that may be important:
Laptop model: System76 GAZP6 (Clevo P150HM)
OS: Windows 7 SP1 x64
K2000 version: 3.3.43982 with KBE 3.3 driver pack loaded.
I've used our K2000 to install both scripted installs and system images over the past several months. However, on a new batch of laptops we just received, I'm experiencing a problem with KBE loading that I haven't seen before.
I first tried to load KBE x64, and the KBE image begins to load from the K2000. However, when WinPE starts to load and I can begin to see the Windows logo appear on the screen, the screen flashes black and the system becomes unresponsive. There is no text or information on the screen after the logo disappears.
I first thought this might be a missing driver, so I added the nic driver to the kbe_windows_64/kace folder, recompiled the drivers, and built a new KBE. The problem still happens.
I have also tried to manually install Windows 7 from the original disc, and when doing so, everything works fine. The fresh install does list many missing drivers, including nic, graphics, audio, chipset, etc. I have all of the drivers available from the company.
Here's a few specifics that may be important:
Laptop model: System76 GAZP6 (Clevo P150HM)
OS: Windows 7 SP1 x64
K2000 version: 3.3.43982 with KBE 3.3 driver pack loaded.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
rmeyer
12 years ago
Sound strange, i would try to remove all drivers except the 1 NIC driver the macine use and rebuild the PE to take out as many possible issues as possible to start with that you can.
Is this from a RSA or the main K2000 ? ( after reading this: http://itninja.com/question/how-to-wrap-a-.exe/.msi-installer-in-a-custom-.msi-packet2 I was wondering if it might be a problem related )
Is this from a RSA or the main K2000 ? ( after reading this: http://itninja.com/question/how-to-wrap-a-.exe/.msi-installer-in-a-custom-.msi-packet2 I was wondering if it might be a problem related )
Posted by:
bowmantech
12 years ago
This is using the main K2000.
I'll try your suggestion later today and update this thread.
I'll try your suggestion later today and update this thread.
Posted by:
bowmantech
12 years ago
Just tried using a KBE with only the specific nic driver, and WinPE still fails just after the Windows logo comes together on the "Starting Windows" screen.
From the looks of this, it seems like WinPE is the issue?
From the looks of this, it seems like WinPE is the issue?
Posted by:
bowmantech
12 years ago
Okay, here's another update:
I tried to update the WinPE image from 3.0 to 3.1 using the WAIK Supplemental pack for Win 7 SP1. Still no luck. I've reverted back to the original 3.0 WinPE files for future KBE builds.
However, I did see by chance that the KBE build I tried earlier this morning (per advice from rmeyer) did in fact connect to the k2000 and is listed in the system inventory. I tried to use this KBE again and see if I could log in through VNC. When I did, the VNC client launched and I was able to enter the VNC password. I then saw this error: "Error: Width (0) and height (0) cannot be <=0". I'm guessing that this error simply means that it cannot connect to the KBE VNC server.
I am able to see the system detail page for this laptop, and I can provide it if needed. There are numerous drivers missing, most notably two Base System Device drivers.
I tried to update the WinPE image from 3.0 to 3.1 using the WAIK Supplemental pack for Win 7 SP1. Still no luck. I've reverted back to the original 3.0 WinPE files for future KBE builds.
However, I did see by chance that the KBE build I tried earlier this morning (per advice from rmeyer) did in fact connect to the k2000 and is listed in the system inventory. I tried to use this KBE again and see if I could log in through VNC. When I did, the VNC client launched and I was able to enter the VNC password. I then saw this error: "Error: Width (0) and height (0) cannot be <=0". I'm guessing that this error simply means that it cannot connect to the KBE VNC server.
I am able to see the system detail page for this laptop, and I can provide it if needed. There are numerous drivers missing, most notably two Base System Device drivers.
Posted by:
bowmantech
12 years ago
I added the Intel mass storage drivers, recached, and built a new KBE. The same problem still occurs though.
I've removed most of the other drivers, leaving only the specific nic and storage drivers. Here's the 3rd party driver list:
I can try to provide anything else if you think it may help.
EDIT: One thing I did notice this time is that the K2000 immediately loses connection with the laptop after it updates the inventory. I can see that the system inventory gets updated with a new Last Network Boot time, but when trying to view the system details, the ping status always lists failed.
I've removed most of the other drivers, leaving only the specific nic and storage drivers. Here's the 3rd party driver list:
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Obtaining list of 3rd party drivers from the driver store...
Driver packages listing:
-------------- | ------------------ | ----- | ----------- | ------------------------ | ---------- | -----------
Published Name | Original File Name | Inbox | Class Name | Provider Name | Date | Version
-------------- | ------------------ | ----- | ----------- | ------------------------ | ---------- | -----------
oem0.inf | iaahci.inf | No | hdc | Intel | 11/6/2010 | 10.1.0.1008
oem1.inf | iastor.inf | No | SCSIAdapter | Intel | 11/6/2010 | 10.1.0.1008
oem2.inf | jme.inf | No | Net | JMicron Technology Corp. | 11/10/2010 | 6.0.24.7
I can try to provide anything else if you think it may help.
EDIT: One thing I did notice this time is that the K2000 immediately loses connection with the laptop after it updates the inventory. I can see that the system inventory gets updated with a new Last Network Boot time, but when trying to view the system details, the ping status always lists failed.
Posted by:
bowmantech
12 years ago
This morning I tried to use a new KBE that included drivers collected using the DriverHarvester tool provided by KACE. The drivers were uploaded into the K2000, the driver cache rebuilt, and a new KBE created. The same problem occurred. I also tried to use an x86 KBE today, with the included nic driver, but again, the system seems to crash shortly after the Windows logo disappears.
I unfortunately am running out of time as I need to deploy these machines soon. Any help or insight is greatly appreciated.
I unfortunately am running out of time as I need to deploy these machines soon. Any help or insight is greatly appreciated.
Posted by:
bowmantech
12 years ago
Update: Booting using a KBE CD works. I meant to try this earlier, but I became sidetracked by several other things and forgot about doing this until this morning. I used the KBE that only contained the nic drivers and burned a bootable CD. The laptop proceeds to start WinPE as normal and loads the deployment center. I've successfully performed a scripted install several times today using this KBE CD.
So in effect, it looks like this is a K2000 issue and not the KBE. In every other instance though, including using both Dell and HP machines, the PXE/KBE boot performs normally. It is only with this specific laptop make/model.
So in effect, it looks like this is a K2000 issue and not the KBE. In every other instance though, including using both Dell and HP machines, the PXE/KBE boot performs normally. It is only with this specific laptop make/model.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.