Dell Latitude E6400 Laptop PXE Issues
Updated: 21 May 2010 | 5 comments
When running a ghost console task, and connecting via Ghost Console PXE each time the ghost console sends the command to reboot, when the system reboots it goes into booting from the HDD not executing the next tasked from the console, the only way to stop this and to have Ghost Console connect again or to execute the next item in the imaging process is to hit f 12 to reconnect to PXE. Very Strange.
We are using the universal driver in the Ghost Console Clientfor 3COM PXE
discussion Filed Under:
Comments
BIOS?
Mike,
A shot in the dark here...but is the BIOS up to date? The 6400 is still relatively new and there were a ton of BIOS updates in the months following release...?
There is a Dell Client Configuration utility that can be used to build .exe's which can set boot order (among other things); not sure if the Ghost console normally supports this anyway (we don't use it here; we run Ghost via Deployment Server).
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
Kyle, I did flash the BIOS
Kyle,
I did flash the BIOS with the most current one offered on Dell's support site (A17) prior to running into this issue. I've also tried it on machines with BIOS version A15 to the same result.
Thanks for your input!
What is the boot order?
Have you checked that the bios boot order has the NIC ahead of the local HDD ?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
The HD is ahead of the NIC in
The HD is ahead of the NIC in the boot order, but this has never affected this porcess before. In fact we do have some of these E6400's that everything has worked? I will try rearranging the boot priority, but this causes a pain in having to go back and change all the machines back as we do not want them attempting to boot to the network first all the time...
Is there a failed task for th client?
Hi,
It is difficult to think that this is related to hardware or firmware. One possibility is having a incomplete task for that client in the Console. If that's the case, when client connects to the Console again it will try to restart the machine. Second possibility is when booting from PXE,
Do you start the task from Console and get the client to boot to PXE instead of GBP or VP, which ever is set in the Console?
Krish
Would you like to reply?
Login or Register to post your comment.