Here's my post install tasks. I can't get all the drivers to install properly and my sccm app at the end fails (it requires a reboot for bits 2.5 install) If I do them individually on the machine, they are install properly with start /wait <name of exe>.exe /s.

Without a reboot, ST Micro driver does not install properly. If I add in a reboot before the ST Micro, then the Control Point Driver Fails. Here's how I handle the reboot after the Ricoh driver,

batch file /start wait Shutdown -r -f -t 60
then a second batch file to delay the next task start /wait ping -n 20

Post install order for e6410:

Post install splash screen
Disable UAC
App Adobe Flash (ie active x)
App Adobe Flash (Plugin)
App Adober Reader X
App Java 6 update 24
App Crystal Reports Viewer 2008
App Office 2007 Pro
App Viewmail 7.0.2
App Symantec Endpoint Protection Managed 64bit
Files - Default background
Files - Default Theme
Files - Default Logo
Files - Default User Icon
Files - Shortcuts/Favorites
Files - Welcome screen backgrounds
Script - Computer Registry Changes
Script - Default user Registry
Script - Computer Rename
Script - Add support batch files
Script - Laptop Power Config
Driver - intel chipset
Driver - Video
Driver - Control Point Security Driver
Driver - Audio
Driver - Touch Pad
Driver - Ricoh
Driver - ST Micro Free Fall Sensor
Script - Legal Notice
App SCCM Client

This works perfectly with my desktop models, but they only have a few drivers to update (amt, heci, video and audio)

If anyone could provide me a driver install order for a e6410 or any dell laptop, that'd be great!
0 Comments   [ + ] Show 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.


To get this to work I had to build driver packs and then use a run once batch file, after forcing a reboot once all the applications and scripts were run. Hopefully they'll integrate this into the product in the future :)
Answered 04/19/2011 by: ngbrown24
Blue Belt

Please log in to comment
Assuming you are using a Windows 7 scripted install. If you haven't upgraded to 3.3 yet, upgrading will provide a new driver feed feature. The driver packs are in the driver feed for the E6410. Selecting them for download and recaching the Win 7 drivers should enable your Win 7 image to install them.
Answered 04/25/2011 by: mlathrop
Fifth Degree Brown Belt

Please log in to comment
driver feed only technically has network drivers in there at the moment... so you still have to script in the rest of the drivers into the image install :) Go take a look at you drivers and then under say any of the folders and the feed. They've offloaded the rest of the drivers to drivers_postinstall due to problems.
Answered 04/29/2011 by: ngbrown24
Blue Belt

Please log in to comment
I have a question 2 dumb q for ngbrown..

do you have all these drivers scripted to install in your k2000 from the post-install task????
do you have a scripted installation for each model??
Answered 05/19/2011 by: blizzster
Senior Yellow Belt

Please log in to comment
Yeah, I have a scripted install for all our models (and some models have more than one because of various hardware configs). I actually add a run once command after I reboot the machine and that kicks off the driver installs. Seems to work better after the scripted install with all the applications being installed.
Answered 05/20/2011 by: ngbrown24
Blue Belt

Please log in to comment
ngbrown, how are you identifying and building the driver installs? the post_install folder doesn't seem to help because there is no install.... Can you run down the process a little of how you start with a new machine build with regards to drivers? I'm supposed to be assesing this product for purchase and right now the driver feed not working is a major sticking point for us, essentially WDS just handles drivers better. Do I need to make a seperate custom install for every machine type and manually build driver post installs for every single driver? This is horrendously time consuming, because half the time the hardware that doesn't install is indicated as 'PCI simple communications controller' and it takes some time to even identify this thing.

As far as I understand it, the 'correct method' of deploying drivers is by downloading them all individually and creating a post install task of a silent install of the driver?
Answered 05/24/2011 by: dogfish182
Orange Belt

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