And I guess that way, it will rid SCCM of potentially old/outdated drivers, correct? Otherwise, would I reimport drivers on top of the old ones, and have a bunch of duplicate/old versions of drivers?
From: [email protected] [mailto:[email protected]] On Behalf Of Mears, Mark Sent: Friday, June 26, 2015 2:47 PM To: [email protected] Subject: [External] [mssms] RE: Updating Driver Packages If you are changing the files under the UNC, it would be better if you deleted the entire driver package from SCCM and created a new one. Thanks, Mark A. Mears, Sr. MCSA, MCTS, MCITP, MCT Microsoft Architect | En Pointe Technologies | www.enpointe.com<http://www.enpointe.com/> HQ: 18701 S. Figueroa Street, Gardena, CA 90248-4506 | 310-337-5200 Direct: (310) 337-4580 Office Ext: 4580 Mobile: (757) 945-2651 [cid:[email protected]]<http://www.enpointe.com/> [cid:[email protected]]<http://www.enpointe.com/microsoft> Systems Integrator Licensing Solution Provider (SI-LSP) Software Asset Mgmt Gold Partner Volume Licensing Gold Partner Server Platform Gold Partner Communications Gold Partner Virtualization Gold Partner Collaboration Gold Partner From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Friday, June 26, 2015 3:44 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Updating Driver Packages I'm trying to figure out if I have a problem or not on how I'm updating driver packages. In this case, for a SurfacePro3. How I've been doing it, is deleting the old driver files form the UNC driver path, replacing them with the new ones, and then updating the distribution points. Looking at the monitoring tab, it shows that all the DP's update successfully. However, the driver package source UNC is not changing. It still has old files, with old time stamps. Any ideas what is wrong?
