In this mode HPIA will be used to only download the driver and driver software suitable for the model its currently running on.Since version 1.0.2, a new operational mode parameter named ‘HPIAAction’ was added to the script, that allows you to decide which of the actions below the script should perform: C:\IntuneWinAppUtil\Source\Drivers, as we’ll use it later when packaging this script as a Win32 app. Save it as Invoke-HPDriverUpdate.ps1 in e.g. Download the scriptĭownload the following script from our GitHub repository: This method can easily be a part of a regular User Driven provisioning but also fits perfect with White Glove provisioning flows with Autopilot. The idea here, using Bruce’s original idea, is to use the HPCMSL PowerShell module to download and run HP Image Assistant to download and apply the required drivers and driver software applicable for the current device that’s being provisioned. I’ve taken Bruce’s approach and expanded it into a fully fledged script version with extended logging and a single script file instead of multiple. But what if we could actually control this, using the tools available from HP? That’s what this blog post is going to cover.īefore we dig into how we can accomplish that, I want to shout out to Bruce Sa who originally came up with the idea behind the method that I’ll be sharing in this post. We’re currently in the hands of HP to provide the drivers injected into the image that’s shipped on the device. Managing drivers when provisioning Windows 10 device using Autopilot, there’s currently not any native built-in functionality in Microsoft Intune to ensure the device is provided to the end-user with the latest and greatest drivers available from the manufacturer, in this case HP.
0 Comments
Leave a Reply. |