Following a week long community feedback session that was Microsoft Ignite, the Driver Automation Tool has been redesigned and additional features added as per requests received. So let’s go through the new layout and features introduced below.

Layout Update

The layout of the tool has been updated to allow for better visibility and flow of features. The initial tab provides you with access to select the core options for the deployment type, the model listings selection has been made much larger per your request. The addition of “ConfigMgr – Standard Pkg (Pilot)” in the deployment platform type assists in the ability to test newer builds of Driver/BIOS packages as part of your testing process. For those of you using our MDM solution, all you need to do is change the “Filter” option to either “Drivers Pilot” or “BIOS Update Pilot” to match based on “Pilot” packages.

The next two tabs in the tool deal with options for ConfigMgr downloads. The first of which is the ConfigMgr Settings tab, here you will find input for the ConfigMgr Site Server name, along with options for distribution and clean up. New in this version is the ability to select the distribution priority of the packages created, which is something quite a few of you had asked for.

ConfigMgr Package Management

The next tab is completely new to this version and allows you to manage your Driver and BIOS package deployment states within the tool. Piloting of Driver and BIOS update packages is obviously something you should undertake as part of testing new builds of both the OS and Driver/BIOS package. In order to make it easier to migrate packages between production, pilot and retire stages I have added this into the tool for you.

Simply select the package(s) you wish to move and then use the actions drop down to move the packages as required. The packages storage paths are maintained therefore you do not need to maintain multiple copies on your storage or redistribute your packages as only the package name is changed.

Package state change in action:

MDT Settings

 

The MDT settings tab is another new addition in this release. Here you now have the ability to specify alternative paths for your MDT PowerShell module as well as the ability to select multiple MDT deployment shares and driver folder structure. At present I have included two options here;

Option 1 – OperatingSystemDir\Make\Model\DriverRevision
Option 2 – Make\Model\OperatingSystemDir\DriverRevision

Below is an example of the structure created by both options when used for a HP EliteBook 1030 G1:

Common Settings

Settings common to all deployment scenarios are now included in the “Common Settings” tab

Event Log

The event log now runs in its own full tab when the tool is running. Additional logging is also included in the log file itself for troubleshooting.

 

Microsoft Technet Download

The script can be downloaded along with instructions from the Microsoft Technet Gallery – https://gallery.technet.microsoft.com/scriptcenter/Driver-Tool-Automate-9ddcc010

 

Maurice Daly
Maurice has been working in the IT industry since 1999 and was awarded his first MVP Enterprise Mobility award in 2017. Technology focus includes Active Directory, Group Policy, Hyper-V, Windows Deployment (SCCM & MDT) and Office 365.

(2111)

comments
  • John
    Posted at 14:16 October 10, 2017
    John
    Reply
    Author

    Thanks for another update for this fantastic tool! You guys are the best!

  • Thomas
    Posted at 14:43 October 10, 2017
    Thomas
    Reply
    Author

    New Model and this doesnt like my TS at all.

    Got a new XPS 15 9560 model, and the bios update script part kills my TS.

    There are no bios available, so the process completed with ecit code 1, which should be normal.

    but it fails with:Failed to run the action: Dynamic Bios Package Detection.
    Incorrect function. (Error: 00000001; Source: Windows) and ends the TS

    if i copy my TS and remove the 3 BIOS update lines, it goes on as normal, so something isnt correct here.

    • Maurice Daly
      Posted at 14:53 October 10, 2017
      Maurice Daly
      Reply
      Author

      Hi Thomas,

      What do the logs say on this?. Are you having issues with other models?.

      Maurice

      • Thomas
        Posted at 18:16 October 10, 2017
        Thomas
        Reply
        Author

        Just this new model, never had any XPS before. there is nothing more in the logs basically then what shows there..

        It downloads the powershell script, and ends with process completed with exit code 1.
        then i get on the line below:
        Failed to run the action: Dynamic Bios Package Detection.
        Incorrect function. (Error: 00000001; Source: Windows)
        Let the parent group (Bios Upgrades) decides whether to continue execution

        Let the parent group (Install) decide whether to continue execution
        Let the parent group (Execute Task Sequence) decide whether to continue execution
        The group (Execute Task Sequence) ignored action failure and continue execution on the next step following the group.
        Start executing an instruction. Instruction name: Gather Logs and StateStore on Failure. Instruction pointer: 118

        and the TS is finished as it just gather logs.

        But its also the first model that doesnt have any BIOS updates available. Im not sure if the Model info might be a contributor to the whole thing, as in The Automation Tool, the model is listed as “XPS Notebook 9560”, but the WMI specifies “XPS 15 9560”. But that shouldnt affect BIOS, as i have renamed the driver package to adjust for this, and it finishes the TS if i remove teh BIOS update part of the TS

        • Maurice Daly
          Posted at 22:07 October 10, 2017
          Maurice Daly
          Reply
          Author

          Hi Thomas,

          Exit code 1 indicates that the script is having issues connecting to the web service. I have sent you a separate email on this.

          Maurice

  • Mike
    Posted at 08:33 October 12, 2017
    Mike
    Reply
    Author

    Great tool . When I select Lenovo T440s BIOS it creates the folder but it is empty .

    • Maurice Daly
      Posted at 16:21 October 12, 2017
      Maurice Daly
      Reply
      Author

      Hi Mike,

      What did it say in the logs. I have just tried this for the T440s with no issues.

      Maurice

  • Dave
    Posted at 14:44 October 12, 2017
    Dave
    Reply
    Author

    I can’t find HP EliteBook 840 G1 and HP Elitebook 840 G2 in the model list for either Windows 10 1607 and 1703. Can you work with HP to get the list updated?

    Sorry I’m relatively new to this site, so if there is a more appropriate place for this type of request please let me know!

    • Maurice Daly
      Posted at 16:23 October 12, 2017
      Maurice Daly
      Reply
      Author

      Hi Dave,

      I can request it from HP, however it might not fit their OS supported model listings internally.

      Maurice

  • T
    Posted at 16:51 October 17, 2017
    T
    Reply
    Author

    awesome tool! does this tool include improvements to parallel processing? i.e. download package whilst creating another package on SCCM?

    • Maurice Daly
      Posted at 23:28 October 17, 2017
      Maurice Daly
      Reply
      Author

      Multi threading is currently not a future of the tool, however this might change with a move to a different programming language.

  • Leave a Reply