Skip to main content

SCCM 2012 Drivers

DRIVER MANAGEMENT


1.1 KEY STEPS
Identify drivers that match Hardware IDs
Installing, and capturing drivers
Importing drivers, categorising, and creating a driver package
Updating Task Sequences
Identifying missing drivers if necessary.

1.2 IDENTIFYING DRIVERS 
The first step in identifying drivers can be timely depending on the hardware vendor.  Vendors provide self-service support pages; it is possible to find the model and specific supported drivers.
With the example of Dell computers; it is possible to download all the drivers for a particular model via driver CABs from the community pages.  This does allow you to proceed quickly but the CAB will typically contains extra drivers to cater to all variances of the model. NOTE: do not import the whole CAB into SCCM.  The install and capture procedure will ensure the driver package is a small as possible.
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-command-deploy-driver-packs-for-enterprise-client-os-deployment 
Extract the CAB using 7-Zip/WinZip.  This will produce several subfolders including an x64 and x86 architecture.  Copy the appropriate folder to a USB key for the next stage.

1.3 INSTALL AND CAPTURE DRIVERS
This section will describe how to capture a Dell Latitude E7440 laptop.
It is important to start with a freshly built computer; built using an ISO image without any drivers or applications installed. It is not necessary to set a specific hostname or password as this system will not be joined to the domain; it should reimaged upon completion to fully test driver package.
Once the system is installed open the ‘Device Manager’ devmgmt.msc and you will see a lot of missing driver, unidentified devices.
   
Using the Dell driver cab previously extracted, right click each device to update/install a driver. Specify a specific install location by ‘Browsing your computer to the USB stick and then let Windows search the folder and subfolders for a matching driver. Some devices are identified and installed with Generic drivers; ensure they are also updated i.e. RAID controllers, Audio, graphics.  It is recommended that all devices are reviewed before proceeding to next step, this will ensure the lastest drivers are in use on all devices.
1.4 INSTALL AND CAPTURE PROCE
Once all the device drivers have been installed or updated we are in a position to capture these drivers for SCCM.
Navigate to: C:\Windows\System32\DriverStore\FileRepository 
Sort this directory by Date modifed. Assuming the day is 29/06/2015 select all folders with this modified date and copy to a subfolder on your USB stick with a suitable name i.e. Dell_E7440_Drivers_Captured_A01

1.5 IMPORTING DRIVERS INTO SCCM
The drivers identified and copyied into folder Dell_E7440_Drivers_Captured_A01 should now be copied to the SCCM server ready to be imported.
\\PriSCCM01\SOURCES$\OSD\DriverSource\Dell_E7440_Drivers_Captured_A01 
1. Import the drivers capture above into SCCM with a unique category 
2. Specifying location \\PriSCCM01\SOURCES$\OSD\DriverPackage\Dell_E7440_Driver_Package_A01 
3. Create a package and leave update distribution point selected. DO NOT select or update boot images
4. Select all drivers with category and move to subfolder i.e. Drivers\Dell\E7440
5. Create a similar folder structure within Driver Packages clearly identify drivers packages and models. Move the new driver package from the root locations.
6. If you review the Driver \\PriSCCM01\SOURCES$\OSD\DriverPackage\Dell_E7440_Driver_Package_A01 this folder has been populated with UUID stype folders and these should not be modified (they are managed by SCCM).
1.6 UPDATING THE TASK SEQUENCE
1. To avoid complications during testing copy your live task sequence then modify the ‘Apply Device Drivers’ step.
2. Click ‘Add’ > Apply Driver Package.  Modify the Name to reflect model, version etc
3. Browse and select the new driver package
4. Select Options tab
5. Add a condition. WMI Query will only apply this step if the condition is evaluated to be true. 
SELECT * FROM Win32_ComputerSystem WHERE Model LIKE '%Latitude E7440%'


1.7 IDENTIFY MISSING DRIVERS


Deploy the new task sequence and build the E7440 previously used to capture drivers. After the build is complete review the device manager for any missing drivers.  In most cases if if step 1.3 was thourough this will be complete; if drivers are missing install and capture the missing drivers as outlined in step 1.4 and import into SCCM and assign to the Driver package. Ensure the new Driver Package is distributed to all in scope DPs before runnign the Task Sequence again.

Comments

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...