DriverPaths doesn't copy drivers OSD

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

DriverPaths doesn't copy drivers OSD

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Operating System Deployment >> DriverPaths doesn't copy drivers OSD

Page: [1]

Message

<< Older Topic Newer Topic >>

DriverPaths doesn't copy drivers OSD - 6/3/2008 4:11:51 PM

Joel b

Posts: 1
Score: 0
Joined: 6/3/2008
Status: offline

Hello all I am in need of your expert help.

I am trying to use DriverPaths=\\%SMSDP%\Share\%Model% to copy drivers to the local c:\drivers folder. From looking at the logs I can see that the DriverPaths variable is being populated (DriverPaths001). But it does not copy the drivers to the local drivers folder on the pc being deployed. Below is a copy of my customsettings.ini file. Your help is greatly appreciated.

[Settings]
Priority=Locations, LSettings, LPackages, LApps, LAdmins, LRoles, DynamicPackages, Model, Default
CustomKeysUserData=DriverPaths(*)
Properties=MyCustomProperty

[Default]
OSInstall=Y
DriverPaths1=\\%SMSDP%\Drivers\%Model%
ScanStateArgs=/v:5 /o /c
LoadStateArgs=/v:5 /c /lac
UserDataLocation=None

[DynamicPackages]
SQLServer=Server
Database=MDT2008
SQLShare=SMSClient

[DB_DynamicPackages]
SQLServer=Server
Database=MDT2008
StoredProcedures=RetrievePackages
Parameters=MacAddress
SQLShare=SMSClient

[SMS]
SQLServer=Server
Database=SMS
Table=v_Program
Parameters=PackageID,ProgramName
SQLShare=SMSClient

[Locations]
SQLServer=Server
Database=MDT2008
Netlib=DBNMPNTW
SQLShare=Distribution$
Table=Locations
Parameters=DefaultGateway

[LSettings]
SQLServer=Server
Database=MDT2008
Netlib=DBNMPNTW
SQLShare=Distribution$
Table=LocationSettings
Parameters=DefaultGateway

[LPackages]
SQLServer=Server
Database=MDT2008
Netlib=DBNMPNTW
SQLShare=Distribution$
Table=LocationPackages
Parameters=DefaultGateway
Order=Sequence

[LApps]
SQLServer=Server
Database=MDT2008
Netlib=DBNMPNTW
SQLShare=Distribution$
Table=LocationApplications
Parameters=DefaultGateway
Order=Sequence

[LAdmins]
SQLServer=Server
Database=MDT2008
Netlib=DBNMPNTW
SQLShare=Distribution$
Table=LocationAdministrators
Parameters=DefaultGateway

[LRoles]
SQLServer=Server
Database=MDT2008
Netlib=DBNMPNTW
SQLShare=Distribution$
Table=LocationRoles
Parameters=DefaultGateway

Thanks
Joel B.

Post #: 1

RE: DriverPaths doesn't copy drivers OSD - 6/9/2008 11:11:33 PM

rbennett806

Posts: 786
Score: 13
Joined: 6/14/2006
Status: offline

So you're using MDT and SMS 2003? And you want to inject drivers? I'm a little lost because if I understand what you're wanting, this should be built into the process, so all you need to do is specify a resource root (under the Details tab on a Role or computer entry within the Deployment Workbench you'll find a line that says "ResourceRoot").

Otherwise what I do is include a few drivers in the actual .WIM file itself (like monitor .INFs) before I capture my reference machine, and I put them in "C:\Drivers\Other" so as to not conflict with any coming down within the OSD process. Then I edit my sysprep.ini file to "OemPnPDriversPath="\Drivers;\Drivers\Other\Monitors"".

If both of those sound like gibberish, give us a little more info as to what you're trying to do and what your deployment infrastructure is like (and chalk those two remarks up to me being brain dead tonight)...

(in reply to Joel b)

Post #: 2

RE: DriverPaths doesn't copy drivers OSD - 6/10/2008 9:56:10 AM

dmartin561

Posts: 8
Score: 0
Joined: 12/10/2007
Status: offline

quote:

(in reply to Joel b)

Joel,
Can you post a snippet of your BDD.log with the driverpaths001 populated? ? Verify that the entire path name is populating correctly. (%SMSDP% *and* %MODEL%) i'm using this same structure and mine pulls and populates just fine unless there is model info somehow incorrect. (EG: HP computers sometimes put a random string at the end of a model number, so you will need to use a variable to truncate them.)

-Dustin

(in reply to Joel b)

Post #: 3