Highlighted is Child Task Sequence called above to download the driver package and apply it with DISM HPIA Step to record missing updates - Reaches out to HP on the internet and scans machine for updates, running in "report" mode. Updated Pack Test (NP): Ran same Task Sequence but with Driver Pack created with New-HPDriverPackĭISM Drivers Step (Part of Child Task Sequence) I ran OSD with the basic driver pack, then ran HPIA scan to determine missing updates. Original Pack Test (OP): I've taken four of my HP Models I have in my lab and ran tests. Manifest JSON File Legacy Package with the Driver Files TESTING PROCESS I really like this structure, I know exactly what driver and what SP# it included, and for PowerShell automation for updating driver packs, the manifest.json file makes it easy to compare between driver pack creations. You would take this output and build a driver package in CM for deployment during OSD Outcome, a folder with inf drivers that you can DISM into the Offline OS during OSD. New-HPDriverPack -Platform 8730 -Os win10 -OSVer 21H2 -Path C:\HPStaging
New-HPDriverPack, this command will allow you to feed it the platform code, OS (Win10 or Win11), and OSVer (21H2, etc), and build a driver pack based on those findings. Now, you can create your own custom updated driver packs and be far better after the first time the Full OS comes online. Most vendors provide tools then to update drivers on machines running the Full OS, but until today, that meant having to first run OSD with old drivers, have the OS installed, then run HPIA to update the drivers to current versions. rarely, lets go with that, but individual drivers get updated much more frequently. The issue HP tackled? Stale driver packs! Typically driver packs get updated. This fills a void with driver packs that has been plaguing us for years. HP is about to release an update to the HP Client Management Script Library, (1.6.5) and with it, a new Commandlet, New-HPDriverPack.
0 kommentar(er)
