locked
Automating driver updates, including firmware? RRS feed

  • Question

  • Hi,

    Found this great article: http://www.oscc.be/sccm/osd/The-holy-grail-of-ConfigMgr-diver-management,-or-whatever-you-want-to-call-it/

    Anybody tried it? It would save us enormously time in configuring task sequences with drivers for different models.

    Would like to know if it also contains firmware updates (see Meltdown, Spencer vulnerability).

    J.


    Jan Hoedt

    Wednesday, January 10, 2018 1:01 PM

Answers

  • Yes, this is used by many organizations, and I've been recommending it to customers recently as well. If you're still on 2012 though (this is a 2012 forum) I don't think the exact technique that Kim lays out will work as it relies on some tasks that were introduced in CB. The core principle is still valid though: using a normal package to contain and deliver the driver files to the system and then use DISM to inject those drivers into the OS image offline after it has been extracted to the client system.

    Firmware updates are completely different beasts so no, this won't handle them. It is for OS drivers only.


    Jason | https://home.configmgrftw.com | @jasonsandys



    Wednesday, January 10, 2018 4:25 PM
  • Yups,

    I've tried it plenty, works awesome. (Could be slightly biased)

    I doesn't include firmware updates for now. Although it would be easy enough to extend it with that. A friend and colleague of mine is doing exactly that.

    Kim

    • Marked as answer by janhoedt Friday, February 2, 2018 10:55 AM
    Monday, January 22, 2018 1:10 PM

All replies

  • That blog post was written by a well known SCCM MVP, who has been known to present on the subject. So yes I was say that it has been used before. I'm sure that Kim will be at MMSMOA.com this may too, as such, he will be glad to talk to you about it. 

    Garth Jones

    Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased

    Wednesday, January 10, 2018 1:24 PM
  • Yes, this is used by many organizations, and I've been recommending it to customers recently as well. If you're still on 2012 though (this is a 2012 forum) I don't think the exact technique that Kim lays out will work as it relies on some tasks that were introduced in CB. The core principle is still valid though: using a normal package to contain and deliver the driver files to the system and then use DISM to inject those drivers into the OS image offline after it has been extracted to the client system.

    Firmware updates are completely different beasts so no, this won't handle them. It is for OS drivers only.


    Jason | https://home.configmgrftw.com | @jasonsandys



    Wednesday, January 10, 2018 4:25 PM
  • What would you then recommand for deploying firmware updates?

    Jan Hoedt

    Monday, January 22, 2018 10:46 AM
  • What would you then recommand for deploying firmware updates?


    There is no standard way to handle that as each manufacturer provides different mechnisms to do that. If unattended support is available at all.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, January 22, 2018 12:19 PM
  • Yups,

    I've tried it plenty, works awesome. (Could be slightly biased)

    I doesn't include firmware updates for now. Although it would be easy enough to extend it with that. A friend and colleague of mine is doing exactly that.

    Kim

    • Marked as answer by janhoedt Friday, February 2, 2018 10:55 AM
    Monday, January 22, 2018 1:10 PM
  • Correct, this relies on the download content task sequence steps, and CM12 doesn't have that. Excellent reason to upgrade :)
    Monday, January 22, 2018 1:11 PM
  • Thanks for the kind words, and the heads up Garth.
    Monday, January 22, 2018 1:12 PM