Anyone have a good step by step tutorial for using DPInst.exe? I downloaded the WDK.
From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Friday, April 1, 2016 5:45 AM To: [email protected] Subject: [mssms] RE: General question on Driver updates We just recently changed positions on this. Before, we held the same perspective, "if it aint broke, don't fix it". We had a RAP with Microsoft for 'Windows Desktop' in 2014 and again last year and two of our top issues were no standardization cross drivers and BIOS versions. Now we standardize on all network and graphics drivers with a 6-12 month true up. Surprisingly, deploying the driver files and using dpinst.exe to load them works great, even for laptops over wireless and updating the wireless driver. We now have all of our top models standardized across the enterprise as well as in OSD, so we have a baseline to work with. We haven't started the BIOS standardization yet. Daniel Ratliff From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Friday, April 01, 2016 8:39 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] General question on Driver updates Hey I need to take the pulse of the community on a specific subject. When Drivers are updated (like the Intel Chipset, etc.) if you do not have a reported issue that needs to be addressed, do you still keep the driver sets as current as possible on your workstations or do you leave well enough alone. I started in 1998 with SMS 1.2 and was the Desktop Engineer for ~4,000 systems before getting to the Enterprise team where we now manage over 150,000 systems and someone is proposing that we update Drivers when they come out on all systems - Not just the SCCM Client and the WUA. But in all my years we only deployed drivers when an issue was reported and verified. If it ain't broke - don't fix it - but is this something new with Windows 10? Thanks for your thoughts. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
smime.p7s
Description: S/MIME cryptographic signature
