Back in September back I posted a Power Shell script to allow the automatic querying of Dell client models from your SCCM environment, download the associated drivers and bios updates and import them into SCCM (The script had the initial task of automating the following steps for your Dell driver imports; I had a lot of great feedback on the script and I am happy to hear it helped a lot of you automate your driver update process.We were already forced to create separate images for different hardware abstraction layer (HAL) families.Additionally, in order to deal with different hardware models within the same HAL family, the standard practice was to usually have a folder called directory) for the Windows Plug and Play process to locate and install the driver.Script Download Link – https://gallery.technet.microsoft.com/scriptcenter/SCCM-Dell-Client-Bios-ee577b04 [Cmdlet Binding(Supports Should Process = $true)] param ( [parameter(Mandatory = $true, Help Message = "Import drivers into which product? ", Position = 1)] [Validate Set("SCCM", "MDT", "Both")] [String]$Import Into, [parameter(Mandatory = $true, Help Message = "Download just BIOS updates, driver packages or both?", Position = 2)] [Validate Set("All", "Drivers", "BIOS")] [String]$Download Type, [parameter(Mandatory = $false, Help Message = "Site server where the SMS Provider is installed", Position = 3)] [Validate Not Null Or Empty()] [Validate Script()] [string]$Site Server, [parameter(Mandatory = $true, Help Message = "UNC path for downloading and extracting drivers", Position = 4)] [Validate Not Null Or Empty()] [Validate Script()] [string]$Repository Path, [parameter(Mandatory = $false, Help Message = "UNC path of your driver package repository", Position = 5)] [Validate Not Null Or Empty()] [Validate Script()] [string]$Package Path, [parameter(Mandatory = $false, Help Message = "Source path to the CSV containing your list of models for MDT", Position = 6)] [Validate Not Null Or Empty()] [Validate Script()] [string]$MDTCSVSource, [parameter(Mandatory = $true, Help Message = "Please select an operating system", Position = 7)] [Validate Set("7", "8", "8.1", "10")] [String]$Windows Version, [parameter(Mandatory = $true, Help Message = "Please select an operating system", Position = 8)] [Validate Set("x86", "x64")] [String]$Architecture, [parameter(Mandatory = $false, Help Message = "Set the maximum number of current jobs", Position = 9)] [Validate Set("1", "2", "3", "4", "5")] [String]$Max Concurrent Jobs ) Clear-Host # Import SCCM Power Shell Module $Module Name = (get-item $env: SMS_ADMIN_UI_PATH).parent.Once you’ve gotten yourself a deployment share, it will show up as a subfolder of the “Deployment Shares” tree, and the first thing you’ll want to do is add the version(s) of Windows you want to use MDT to install.We have discovered yet another reason to leave Windows 7 behind.

MDT creates is own folder structure under the deploymentshare.

We will focus on how drivers get installed via MDT, how to specifically control the drivers that get installed, and general best practices around proper driver management.

We will cover the following topics in this article: Those of us who created images for the deployment of Windows XP were often met with an enormous challenge of dealing with drivers for many different models of hardware.

Full Name "\Configuration Manager.psd1" Import-Module $Module Name # Defaults maximum concurrent jobs to 3 if the value is not set in the commandline if ($Max Concurrent Jobs -eq $null) # Query SCCM Site Code function Query Site Code ($Site Server) function Query Models ($Site Code) function SCCMDownload And Package ($Package Path, $Repository Path, $Site Code, $Dell Products, $Windows Version, $Architecture, $Download Type, $Import Into, $Max Concurrent Jobs) function MDTDownload And Import ($Repository Path, $Dell Products, $Windows Version, $Architecture, $Max Concurrent Jobs) if (($Import Into -eq "SCCM") -or ($Import Into -eq "Both")) else Lets step through the options available to you when running the script; Run the script using the following opening syntax: .\Dell Downloads.ps1 -Import Into SCCM – for SCCM only or .\Dell Downloads.ps1 -Import Into Both – for both SCCM and MDT –Download Type :: Selects the type of download, the options available are All, Drivers or BIOS –Site Server :: The name of your SCCM site server than you are running the script on –Repository Path :: The location for your bios and driver downloads and cabinet extracts –Package Path :: The location for your SCCM driver packages –Windows Version :: Options include, 7, 8, 8.1 and 10 –Architecture :: Options include x86 or x64 –Max Concurrent Jobs :: Options for 1-5 concurrent jobs .\Dell Download -Import Into Both -Download Type Drivers -Site Server SCCM01 -Repository Path "\server\drivers" -Package Path "\server\driverpacks" -Windows Version 10 -Architecture x64 -Max Concurrent Jobs 3 The MDT only option differs from the SCCM functions in the fact the script does not query SCCM for a list of Dell enterprise client systems.

In this instance a CSV is required with an initial column heading labelled “Model”, example; Model Optiplex 7040 Optiplex 7010 Latitude E5470 –Download Type :: Selects the type of download, the options available are All or Drivers –Repository Path :: The location for your bios and driver downloads and cabinet extracts –Windows Version :: Options include, 7, 8, 8.1 and 10 –Architecture :: Options include x86 or x64 –Max Concurrent Jobs :: Options for 1-5 concurrent job (defaults to 3 if not entered) -MDTCSVSource :: Location of Models CSV file Working example of MDT only command; Maurice has been working in the IT industry since 1999.