Since SCCM 2007 is an involved tool there is of course different opinions on how to perform certain tasks, all with merit. We have built out our SCCM environment and we are getting ready to deploy the client. Once deployed we will use SCCM to then install Windows 7. We've have been told two different methods of handling drivers for OSD. They are: 1. Import your drivers 2. Create driver packages Is one method better than they other or are they both doing the same thing? Doing #1 above we've seen in our test lab things gets very messy, very fast. Does Microsoft reccomend one method over the other? Why even have two ways of doing the same thing? Any info would be great....thanks. mqh7

I wouldn't import the drivers into SCCM. That's just my opinion. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

John, thanks. Why do you prefer the driver package method? mqh7

Drivers can be imported in different folders in SCCM, with specific labels on them. That way you keep them organized and clear. When there's an error message displayed, because drivers are multiple times imported, use this hotfix: http://support.microsoft.com/kb/2213600 Blog post for that: http://henkhoogendoorn.blogspot.com/2011/03/advanced-driver-management-in-configmgr.html Then selecting drivers and create driver packages of them. When adding all of them in Task Sequences put WMI queries on them for device recognition. Blog post for that: http://henkhoogendoorn.blogspot.com/2010/10/driver-management-in-configmgr-2007.html My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

The best method is the method that works for you. There are essentially three different methods and most people use hybrids of these mthods for their environments. Here are three great posts on the subject: http://www.deployvista.com/Home/tabid/36/EntryID/82/language/en-US/Default.aspx http://blogs.technet.com/b/mniehaus/archive/2010/04/29/configmgr-2007-driver-management-the-novel-part-1.aspx http://myitforum.com/cs2/blogs/cnackers/archive/2010/04/09/configuration-manager-2007-r2-sp2-driver-management.aspx Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I don't think they are two differeent method. This is one method with two steps. When you run the import driver wizard it will walk you through to the point asking you whether adding the drivers (imported) to an existing driver package or create a new one. Thus, if you want to import drivers into a new driver package you may either create the package (an empty one) before running the wizard or create it within running the wizard. If you want to import new drivers into an existing driver package just run the wizard.

I don't think they are two differeent method. This is one method with two steps. There are definately two differenet methods. It's not a requiement to import the drivers at all. IMO, it's easier to manage if you do not import them. But Jason is right, whichever way works best for you is the way you should do it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

I don't think they are two differeent method. This is one method with two steps. There are definately two differenet methods. It's not a requiement to import the drivers at all. IMO, it's easier to manage if you do not import them. But Jason is right, whichever way works best for you is the way you should do it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|