Wau image

Windows 10 Driver Update Procedure

Install drivers from the Windows catalog

Description

This procedure will utilize a 3rd party PowerShell module PSWindowsupdate to check the Microsoft catalog for any available drivers against Windows 10 machines. One custom field is required before importing. This pack also includes a view that will read the custom field and show you machines that are found to be missing drivers.

Developer
  • Name: Brian Honeycutt
  • Company: Kaseya
  • Website: http://www.kaseya.com
  • Contact Developer
  • Summary
  • Windows 10 Driver Update Procedure
  • 117 Downloads
  • Version: 1.0
  • Released on January 3rd, 2020
  • Reviews

    Windows 10 Driver Update Procedure has no reviews.

    Discussion
    Gravatar for Matthew Sanchez
    Matthew Sanchez 8 months ago

    I haven't been able to get this to import into our Kaseya SaaS. Kaseya accepts the file/XML paste but the procedure never actually shows up. Any advise?

    Gravatar for Petter Kollind
    Petter Kollind 8 months ago

    You need to import this by the "Import Center" under System -> Server Management. Read the "Windows 10 Driver Update Procedure.pdf" for details :)

    Gravatar for Matthew Sanchez
    Matthew Sanchez 8 months ago

    That did it. Thanks!

    Gravatar for Brian Honeycutt
    Brian Honeycutt 8 months ago

    Thanks for the assist Petter, I was typing up the response when yours came in. 

    I am working on a report currently to key off the defined metrics I put in the procedure log at the individual steps of the procedure. I have it already built but just thinking if I can make it a little better, once decided I will update the file to include the report. 

    Thanks

    Gravatar for Petter Kollind
    Petter Kollind 8 months ago

    Glad i could help, thanks for the script yourself :) 

    Sounds great, even tho i'm only following up on errors but a report is always good to have in use.

    Gravatar for Brian Honeycutt
    Brian Honeycutt 8 months ago

    Petter,

    I have actually found the error tracking to be difficult, if the module installs successfully that's fine but as we know driver installs are variable, they can fail from a myriad of reasons. It's possible to return from the install process if a patch failed or not, which I had initially built into the procedure but it appears some drivers report failed on install because an automatic reboot is not done and then once you reboot, it is successful....Because of this, I excluded this to avoid so many false positives. 

    Gravatar for Petter Kollind
    Petter Kollind 8 months ago

    That's true, good call! Drivers is always hard to manage and therefor its good to have a procedure that used the Win-update client to do this. I can only imagine Microsoft will include more and more drivers to be installed this way instead of using 3d party applications or the vendor drivers manually.