Jump to content

Recommended Posts

Posted

Any pointers on the best way to organise your drivers within OSD?

 

I've got a fresh start on the drivers right now, and tomorrow I'm going to start putting them all in but i want to start it right ... so any tips? because this can often get very messy as I'm sure you're all aware.

Posted

For us, unified drivers go in a 'common' folder since they are not model specific. Some examples...

 

This is what the folder structure looks like:

 

Common
|------\ Graphics
|---------------\ AMD
|---------------\ Intel
|---------------\ nVidia
|
Manufacturer
|------------\ Model
|-------------------\ Driver

  • Thanks 1
Posted (edited)

Perfect @Arthur just the sort of thing i was after :)

 

@Jamo at the moment I'm not making use of MDT, i have it installed and available to me but I'm still learning SCCMs in and outs, I'll probably get there eventually :p

 

EDIT: What are the main benefits of MDT? What additional functionality does it add specifically?

Edited by mrbios
Posted (edited)
What are the main benefits of MDT? What additional functionality does it add specifically?

When integrated with SCCM? This post explains a few reasons why you would want to use both.

 

That's what I do too

That's good to hear. I can't stand disorganized driver folders. :)

Edited by Arthur
Posted

We're currently using MDT to create images and SCCM 2012 to deploy... targeting drivers to specific machines via WMI queries.

 

Folder structure:

 

OS > Manufacturer > Model > OS Architecture > Driver

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...