Modern driver management in Configuration Manager Current BranchUpdated after MMS 2. Theres a multitude of ways to handle driver management in Configuration Manager and OSDeployment. Intro. This post introduces a new way of handling drivers that me and my colleague Tom Degreef have started implementing at our customers with the release of Configuration Manager Current branch. Hi We are starting to use SCCM 2012 to deploy manager applications on windows 7. When creating the task sequence to build and capture the. LcSpbZXDU/VwzyUrwaT9I/AAAAAAAAFAY/1rHwaYqAHswONNFG_BxwO5qmPKtistTHACK4B/s1600/Capture.JPG' alt='Driver Packages Sccm' title='Driver Packages Sccm' />My team and i have set up Microsoft System Center 2012 for deploying Windows 7 to all of our Staff computers. We use driver packages wich we install per OS. The new features in Microsoft System Center 2012 Configuration Manager SCCM 2012 are well worth the time and money it takes to migrate from System Center. In this file you can setup default values for the textboxes, servername, log file path, check update and license agreed. Change it manually if you require that the. Part 3 of a fourpart series about SCCM Windows deployment troubleshooting, deals with networking issues, XML and media errors. We delivered our new methodology first at a popular MMS 2. I am updating this blogpost where I first introduced some of the concepts back in 2. Driver Management desires. The new way of doing driver management in Configuration Manager is more dynamic than it used to be. It offers the following advantages Full control over the drivers that get installed. Dynamically select these drivers based on the detected hardware model. Install drivers during OSD without importing them into Configuration Manager. Add a new hardware model without modifying your tasksequence in any way. Remove static content references from the tasksequence. Intrigued yet, lets get startedThe unseen potential of Download Package Content. The new Configuration Manager current branch has a new Tasksequence step called Download Package Content. My MVP pall, Jrgen Nilsson, blogged about it here, http ccmexec. On the surface, the step seems to lack the ability to do driver packages, and it doesnt appear to be Dynamic in any shape or form. But, thats why this sections title is the Unseen potential of the step. This particular step actually has an OVERRIDABLE tasksequence variable called OSDDownload. Download. Packages. This particular variable takes Package Ids as values, and then goes ahead and download those. So we can dynamically set that variable based on the hardware model and download the relevant package to a fixed path locally on the deployed machine. Piece 1 of the puzzle is handled by a script that reads the relevant package id from an exported listed of available packages. Short description. DESCRIPTION. Long description. Skype Premium Softonic Pc. Example of how to use this cmdlet. Another example of how to use this cmdlet. Cmdlet. Bindingparam Param. ParameterValue. From. Pipeline. By. Property. Name. Position 0stringMatch. PropertyMif. Name. Param. 1 help descriptionParameterValue. From. Pipeline. By. Property. Name. Position 1stringModel. NameGet Wmi. Object Class win. Namespace rootcimv. Name. Param. 2 help descriptionParameterValue. From. Pipeline. By. Property. Name. Position 2stringPackage. XMLLibrary. packages. Param. 3 help descriptionParameterValue. From. Pipeline. By. Property. Name. Position 3Validate. SetWindows 7 X6. Windows 7 X3. Windows 8 X3. Windows 8 X6. Windows 8. X6. 4,Windows 8. X3. 2,Windows 1. X6. Windows 1. X3. 2,stringOSVersionfunction Get CMCEDynamic. Package. Output. TypestringParam Param. ParameterValue. From. Pipeline. By. Property. Name. Position 0stringMatch. PropertyMif. Name. Param. 1 help descriptionParameterValue. From. Pipeline. By. Property. Name. Position 1stringModel. NameGet Wmi. Object Class win. Namespace rootcimv. Name. Param. 2 help descriptionParameterValue. From. Pipeline. By. Property. Name. Position 2stringPackage. XMLLibrary. packages. Param. 3 help descriptionParameterValue. From. Pipeline. By. Property. Name. Position 3Validate. SetWindows 7 X6. Windows 7 X3. Windows 8 X3. Windows 8 X6. Windows 8. X6. 4,Windows 8. X3. 2,Windows 1. X6. Windows 1. X3. 2,stringOSVersionProcessinteresting properties pkgsourcepath, Description, ISVData, ISVString, Manufacturer, Mif. File. Name, Mif. Name, Mif. Publisher, MIFVersion, Name, Package. ID, Share. Name, VersionxmlPackagesGet Content Path Package. XMLLibraryenvironment variable call for task sequence onlytrytsenvNew Object Com. Object Microsoft. SMS. TSEnvironment. InitializedtruecatchWrite Host Object Not executing in a tasksequencetsenv. InitializedfalseifOSVersion eq Package. IDImport ClixmlPackage. XMLLibrary. Match. Property. Split,. ContainsModel. Name. Package. ID. Package. IDiftsenv. Initializedtsenv. ValueOSDDownload. Download. PackagesPackage. IDelsePackage. IDImport ClixmlPackage. XMLLibrary. Match. Property. Split,. ContainsModel. Name and. Mif. Version eq OSVersion. Package. IDPackage. IDiftsenv. Initializedtsenv. ValueOSDDownload. Download. PackagesPackage. ID. Get CMCEDynamic. Package Match. Property Match. Property Model. Name Model. Name Package. XMLLibrary Package. XMLLibrary. The script takes the following optional parameters Model. Name. Match. Property. OSVersion. Package. XMLLibrary. Modelname is an optional variable that should typically be left blank. It grabs the Model. Name from the Win. WMI class on the machine were the script is executed. Match. Property is an optional variable that verifies whether the specified property contains the value of the Model. Name detected. Default. Value Mif. Name property of a regular Configuration Manager package. XMLLibrary takes an optional path to the XML file you want to use, default is packages. Powershell command Get Wmi. Object class smspackage Namespace rootsmssitesitecode Select Object pkgsourcepath, Description, ISVData, ISVString, Manufacturer, Mif. File. Name, Mif. Name, Mif. Publisher, MIFVersion, Name, Package. ID, Share. Name, Version export clixml path packages. OSVersion is an optional variable that takes one of the following values Windows 7 X6. Windows 7 X3. 2, Windows 8 X3. Windows 8 X6. 4, Windows 8. X6. 4, Windows 8. X3. 2, Windows 1. X6. 4, Windows 1. X3. 2How the script Works. The script starts with reading the XML generated with the command above, and initializing the Tasksequence COM object. The script subsequently grabs the hardware model from WMI, it then goes through the XML to capture the package id that goes with that model. The script expects the hardware model to be present in the Mif. Name Field of a regular SCCM Package by default, if that doesnt suit your needs, this config can be overridden by defining your own matchproperty. Note The above script is Powershell, so your boot image will need to contain Powershell, or youll have to come up with something similar in VBS and CSV files. The script ends by setting the OSDDownload. Download. Packages variable used in the Download package content step. Wistje. Datje This tasksequence variable takes a comma seperated list of packages to downloadWe are now ready to run the download package content step and dynamically download the relevant package. Once the package is downloaded we can DISM apply it to our deployed OS image using the following command DISM. Image OSDTarget. System. Drive Add Driver Driver SMSTSMData. PathDrivers Recurse logpath SMSTSLog. Pathdism. log. The Dism apply drivers step is a simple run command line step, without a package defined, and no filters on any of the options pages. Setting it all up. Create the Package Holding the script and Packages XML File. Create a regular Package whose data sourcepath contains the script as listed above, and note the package name down youll need it later on. Give the script a name eg Get CMCEDynamic. Package. ps. 1 and save it to the sourcepath above. Run the following Power. Shell Command line and copy the packages.