XP "Scripted Install" Driver Install FAIL
I have my K2000 Trial appliance set up and able to send an XP "scripted install" to a system. I have harvested all of the drivers off of the system (after manually installing them all) and have attempted another "scripted install" and each time the drivers are not being installed.
Am I missing something here?
After "harvesting" I recached all of the drivers on the KACE 2000 and waited 20 minutes like it suggested.
System I'm testing with is a Dell Latitude D630. Trying to just load XP SP 3 and base drivers, oh and I did add the .net 20 sp1 post install task to the scripted install.
Am I missing something here?
After "harvesting" I recached all of the drivers on the KACE 2000 and waited 20 minutes like it suggested.
System I'm testing with is a Dell Latitude D630. Trying to just load XP SP 3 and base drivers, oh and I did add the .net 20 sp1 post install task to the scripted install.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
trentderby
14 years ago
i have had issues with harvesting, what i found best to do was install win rar, download the drivers from dells site - then right click the files, extract the .exe files and put the folders created directly into the \\WHATEVER YOU CALLED YOUR KBOX\drivers\windows_xp folder, its best to divide the folder structure (sub folders of drivers\windows_xp as follows (copied from admin guide):
\c Chipset drivers
\cpu CPU drivers.
\g Graphics drivers.
\l LAN drivers.
\m Mass storage drivers
\mo Modem drivers.
\s Sound card drivers
\w Wireless LAN drivers
i also added an \o folder for other things such as bluetooth or other drivers.
i have found so far that you should avoid the broadcom card reader driver - it causes a crash upon install in win XP - snymsico.dll not found (which you then have to search for and delete from the drivers directory on the kbox)
this and other drivers that fail can be added as a post install task, but to be honest i found that just copying everything to the folders direct will work ok for 99% of it.
be sure to read the readme.txt of all the drivers as dell give them ambiguous names like R8945762 - if you extract the .exe and then read the readme.txt you should know what driver you have and where to put it.
***RECACHE YOUR DRIVERS BEFORE PERFORMING ANOTHER SCRIPTED INSTALL***
best of luck.
\c Chipset drivers
\cpu CPU drivers.
\g Graphics drivers.
\l LAN drivers.
\m Mass storage drivers
\mo Modem drivers.
\s Sound card drivers
\w Wireless LAN drivers
i also added an \o folder for other things such as bluetooth or other drivers.
i have found so far that you should avoid the broadcom card reader driver - it causes a crash upon install in win XP - snymsico.dll not found (which you then have to search for and delete from the drivers directory on the kbox)
this and other drivers that fail can be added as a post install task, but to be honest i found that just copying everything to the folders direct will work ok for 99% of it.
be sure to read the readme.txt of all the drivers as dell give them ambiguous names like R8945762 - if you extract the .exe and then read the readme.txt you should know what driver you have and where to put it.
***RECACHE YOUR DRIVERS BEFORE PERFORMING ANOTHER SCRIPTED INSTALL***
best of luck.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
