Windows 7 has been good about containing most drivers needed for older Dells, so I've had just one scripted Win 7 install for all machines.
The new Dell M4500 an E6410 are missing a bunch of system drivers. I intend to build a scripted install for each model to add drivers. (I'm a little leary about throwing a bunch of drivers into the Win 7 driver cache, it has caused conflict in the past)
I've downloaded CAB files from Dell, however not sure how to use these in a post install task - is this possible? Show me the way...[:)]
0 Comments   [ + ] Show Comments

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.

Answers

0
Curious why you wouldn't use the new driver feed tool instead? Applying them as postinstall isn't a bad practice, but it does kind of defeat the idea of a hardware independent script. If you're set on doing it as a post install; might I suggest something more maistream, like the executables generally provided- the CABs are intended to be rolled into an MDT solution according to MS & Dell. There are multiple methods for installing CAB files via the command line. This isn't exhaustive, but potentially useful:
http://social.msdn.microsoft.com/forums/en-US/netfxcompact/thread/6238a232-1e87-4067-8720-6cbc548dcd2d/
http://stackoverflow.com/questions/644831/install-cab-file-from-firefox-or-command-line
Answered 04/11/2011 by: cblake
Red Belt

Please log in to comment
0
Chris, thanks for the reply. I have not been upgraded to version 3.3 yet, which I think may be needed for the driver feed? I am leery of adding drivers which may cause conflict with previous hardware models. I would prefer however to have a HW independant script.
I have Dell M4500 and L6420's which need additional drivers manually installed after image script. I don't neccessarily wish to script each one separately as a post install. Some of the threads I've read on driver feed are somewhat negative... Can you advise me on best approach?
Answered 04/12/2011 by: mlathrop
Fifth Degree Brown Belt

Please log in to comment
0
That conversation is best had with your jumpstart trainer if you're still in training, as it's usually specific to your environment, but as a best practice you're on the right track- only upload the drivers that you actually need in your environment to minimize conflicts. The driver feed is a feature introduced in 3.3; if you haven't already upgraded I'd encourage that as your first step towards harmony in your deployment world. When the feed was initially released there were some conflicts discovered but we've addressed that with a patch. Regardless of using the feed or not, you still want to use the driver cache- I'd simply harvest the known needed drivers from a working system.
Answered 04/12/2011 by: cblake
Red Belt

Please log in to comment
0
Upgrading to 3.3 did not help specifically, as there is no driver feed for the E6410 yet. The specific solution was to
1) Download the CAB file from Dell for this machine (not yet in the KBOX driver feed)
2) Extract the CAB using WinZip in order to maintain the directory structure
3) Copy the x64 driver directories into the Windows_7_x64 directory on the driver share
4) recache the drivers
This installs the correct drivers during W7x64 setup.
Answered 04/27/2011 by: mlathrop
Fifth Degree Brown Belt

Please log in to comment
0
weird. I have a driver feed for the e6410... just not for my newer e6420 :)
Answered 04/29/2011 by: ngbrown24
Blue Belt

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