I have a few of the machines being shipped to me right now for testing this 
exact thing.


Chris Barnes
Senior Technical Specialist - Penske Automotive Group

[email protected]<mailto:[email protected]>
Desk:  (248) 648-2528
Cell:     (248) 767-4415

From: [email protected] [mailto:[email protected]] On 
Behalf Of Danny Guillory
Sent: Thursday, October 31, 2013 2:35 PM
To: [email protected]
Subject: RE: [mssms] OSD Driver Packages with Dell Inspiron 660 and 660s

I don't want to seem to simplistic here but have you tested to see what drivers 
you will need after u laydown the OS?

Will those built in drivers work for your needs?

I have noticed that mostly when I encounter those consumer machines 95% of them 
will be just fine with the built in drivers. (given there's NOTHING TOTALLY 
WEIRD/NON-STANDARD ABOUT THE PC), I only mention that because you may only need 
a select few drivers to make you & device manager happy :)

________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] OSD Driver Packages with Dell Inspiron 660 and 660s
Date: Thu, 31 Oct 2013 12:59:11 -0500
Chris,

A lot of drivers are shared across platforms, even between consumer and 
enterprise grade PCs. You should be able to find drivers that match the PNP 
device IDs of the Dell Inspiron 660 and 660s systems in your current driver 
repository. If not, then you can download the drivers individually from Dell, 
categorize them into some logical folder structure on the filesystem, and then 
import them and associate them with Driver Packages, just as you normally 
would. It's a bit more work than using driver CABs, but it should work just the 
same.

If you want to search your current driver repository for compatible INF files, 
use PowerShell:

Get-ChildItem -Path 
\\sccm01\e$\Packages\Drivers<file:///\\sccm01\e$\Packages\Drivers> -Filter 
*.inf -Recurse | Where-Object -FilterScript { !$PSItem.PSIsContainer -and 
(Get-Content -Path $PSItem.FullName -Raw) -match 'VEN_8086&DEV_1502' };

In plain English, this command reads: "Get me all child items, recursively, 
that end in '.inf' from the root of my Drivers folder on the SCCM server, where 
the item is not a folder (container), and the files' contents match the device 
ID string 'VEN_8086&DEV1502'"

Once you get the results from the command, you know which INF file, in which 
folder, should be associated with the target system's Driver Package. Rinse and 
repeat for each device that you want to pinpoint a driver for, that already 
exists in your Driver "Repository."

Cheers,
Trevor Sullivan

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Barnes,Chris
Sent: Thursday, October 31, 2013 12:49 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] OSD Driver Packages with Dell Inspiron 660 and 660s

Hey guys, I am needing to potentially image a bunch of Dell Inspiron 660 and 
660s machines (I don't want to, but we are taking over an entity that bought 
all of their machines at Best Buy.)

Has anyone attempted this yet, and have any advice for setting up the driver 
packages? I know that Dell doesn't offer the CAB files due to this being a 
consumer class machine, and not an enterprise class machine.


Chris Barnes
Senior Technical Specialist - Penske Automotive Group

[email protected]<mailto:[email protected]>
Desk:  (248) 648-2528
Cell:     (248) 767-4415


________________________________
Penske Automotive Group and its affiliates will never sell or rent your email 
address in violation of applicable law. This email and any files transmitted 
with it are confidential and intended solely for use of the individual or 
entity to whom they are addressed. Please delete all copies if you are not the 
intended recipient.






Reply via email to