OptiPlex 7080 Unable to Boot via PXE or USB "Could Not Ping Appliance Error"
Recently purchased 50 new OptiPlex 7080 for our environment. However I'm unable to boot to the SDA
Appliance is up to date with v8.0.194. I've uninstalled and re-installed the DELL 7080 driver feed package.
DHCP options 66 and 244 are correctly set, yet still receiving the "could not ping appliance error"
Also, attempting to ping manually in Windows PE (CMD) returns a "PING: transmit failed. General failure."
What would be the next step for resolution, all of my other systems will successfully boot into the environment without any issues via PXE or USB
Any Ideas / Solutions.... Thanks in advance!
Answers (2)
on the point where the script ends test if the device got an IP:
enter ipconfig.
If no IP is given it is likely that the network driver is missing.
This can happen with new systems to your environment where you did not have the latest driveers.
Other causes on the network are unlikely since all other stuff is working correctly.
Follow this article to create a new KBE:
https://support.quest.com/kb/126093/
Inject the nessesary driver before building the KBE:
Download the driver from Dell.
Unzip it and put the contents into the \\SDA\drivers\kbe_drivers_x64 folder (add additional subfolders here for all systems you need)
After that step a recache of the drivers ( Settings |Appliance Maintenance) is nessesary before building the KBE.
Comments:
-
Nico, Thanks for following up, much appreciated!
As you suggested, ipconfig returns no configuration.
Unfortunately, the Dell 7080 network Driver downloads are all exe. files and therefore nothing there to unzip.
Is it possible to install/update to an existing 7080 system, then extract them from there?
If so, how should I proceed in doing so?
Also, when injecting the drivers into the \\SDA\drivers\kbe_drivers_x64 folder, do the copied files live directly in the "kbe_drivers_x64" folder? Or, would a specific file path therefore need to be created?
Thanks in advance for any assistance you can provide.......... - Sharkfish 3 years ago
Top Answer
I had this same issue!
I got through it by downloading the most recent KBE driver pack (A22) from Kace (KACE Systems Deployment Appliance - Download Software (quest.com)) and throwing these into the Samba share and creating a new KBE to use, as Nico_K said above. Further instructions for how to do this: How to add the Driver Pack to KBE (111719) (quest.com)
Hope that help you as well.
Comments:
-
Resolved! Driver Pack update along with a new KBE Worked flawless.... No additional driver injections were needed...Thank you so much! - Sharkfish 3 years ago
