This solution is provided to the Community by Daniel Gråhns and Nicklas Eriksson, Twitter(Sigge_gooner), thank you for sharing it! Great work!
As the title says it is a solution for deploying drivers and software during a Task Sequence using HP Image Assistant. The benefit of using this is that you can automate the whole process of downloading and updating drivers and solve the additional software needed for HP devices. Including the software needed as that is not included in the driver packs.
The purpose of this solution is to:
In the folder with the scripts, we have the following files.
All configuration is done in the Config.xml file by editing the variables there. Site Code, Package path and more, It is well documented in the script.
In the Import-models.csv file we simply put the Basebord ID, Modelname and OS version as shown below.
Then we run the script, it will download the Softpaqs, create a Package and distribute it to the dp group we select in the config. We will cover that later in this post.
The script will automatically install HPCSML and update it if needed.
In the task sequence we run the following commands that will use the Configmgr Webservice to populate the variables for which package should be used.
Then it is downloaded and installed by using the image assistant and the files downloaded to the local disc as source.
If a second pass of HPIA is needed, which could be the case simply just add that model to the Conditions for the “Second HPIA Pass if needed”
The solution uses the following components:
We will not cover how to install the ConfigMgr webservice, that is included in the manual provided with the download above.
We need a Package in Configuration Manager with the HP Software Framework. Here is how to download and extract the .msi file.
As we install all drivers using HP Image Assistant we still need storage drivers and network drivers to be installed during OSD to be able to get Windows 10 up and running.
Use the following conditions so it only installs for HP devices.
Before we run the script for the first time, we need to configure it for our environment.
Then we are ready to run the script for the first time, there is a log file as well you can use to check for errors if the script is run as a Scheduled Task for example.
The result in my case will look like this.
And the packages have gotten the information needed for the Configmgr Webservice to pull them down.
The steps needed in the Task Sequence can be downloaded from Github and then imported to make it as easy as possible.
Edit the “import-models.csv” file with your information as mentioned above.
Then it is time to run the script and watch it download the drivers for our models and then test out the deployment. You can schedule it as well of hours and let it update the driver packages if needed.
Again thanks to Daniel Gråhns and Nicklas Eriksson for sharing the solution. Great work!