Driver quality in general has improved and Windows 7 (and newer) OS’s are a bit more forgiving than XP. My opinion is that the need to use the “no import” method has diminished a little over the years. * Update * As noted in the comments, Achim has posted a way to apply drivers without importing them into the database in SCCM 2012 – and it is detailed here – however, there are still a couple of options when it comes to allocating these drivers in task sequences. In SCCM 2012, there is now only one real method of importing “good drivers”, which is importing the drivers into the database…. Whenever working with drivers, you should always try and install everything possible as a “good” driver. exe format, but can be extracted to expose the inf/sys/cat files. It is very important that the driver type is correctly identified. Bad Drivers: Drivers which come with a setup program and must be installed (common examples are laptop Bluetooth drivers).Good Drivers: Drivers which come in an inf/sys/cat format and can be installed on systems easily.For an SCCM 2007 version of this article, go to ĭrivers can very broadly be split into two categories:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |