Updating HP Docks with Intune or ConfigMgr using PowerShell

TLDR: Function on GitHub | ConfigMgr CI / Intune PR Script on GitHub

So I’m going to cover several docks in one process. I originally started out with supporting the HP USB-C G5 Essential Dock, but I ended up going down a rabbit hole and adding several with the collaboration of my coworker Dan Felman.

Related Posts

• HP Dock WMI Provider Deployment & Inventory with ConfigMgr
• HP Dock Registry & Inventory with ConfigMgr

HP White Paper: HP_Firmware_Installer_for_Docks_L33010-004.pdf

Supported Docks | Firmware Softpaq Downloads (as of 2024.04.01 when I checked last)

• HP USB-C G5 Essential Dock* | Softpaq Info | sp151760.exe | 01.00.10.00 | Mar 14, 2024
• HP Thunderbolt Dock G4* | Softpaq Info | sp151762.exe | 1.5.22.0 | Mar 14, 2024
• HP Thunderbolt Dock G2* | Softpaq Info | sp143977.exe | 1.0.71.1 | Dec 15, 2022
• HP USB-C Dock G5* | Softpaq Info | sp150455.exe | 1.0.20.0 | Dec 20, 2023
• HP USB-C Universal Dock G2** | Softpaq Info | sp150473.exe | 1.1.20.0 | Dec 4, 2023

Recently added support in my function, but uses completely different process then newer devices, so connect with me if you run into any issues, as a lot of additional code was needed.

• HP USB-C Dock G4* | Softpaq Info | sp88999.exe | F.37 | Jul 15, 2018

* Tested myself with units I have on hand
** Waiting for test Units to arrive… will update post if anything is wrong from my original findings.

Overall Process

• Detect Dock that is attached to device
• Download latest firmware for device (via HPCMSL if available or hardcoded URL in script)
• Run HPFirmwareInstaller -C to run a check of the system.
• If Check determines Update needed… continue to update… else exit

Methods to detect current HP Dock Firmware

HP Thunderbolt docks and others as well have their information in the Registry, ONCE you run the HPFirmwareInstaller.exe command. You can run this as a check, and it will add the values. However, this information for the Thunderbolt G4 dock is also available via WMI like the HP USB-C Dock G5 (see below), so that’s a good way to standardize gathering the information:

The subkey is unique as it is the Serial Number of the dock. The script I wrote will look in all child keys to find the “InstalledPackageVersion”.

HP USB-C Dock G5 (NOT the Essential dock) have their information in WMI (from what I’ve read, I’m still waiting on my test device to confirm). You do need to install the WMI provider for it, which would be in the firmware downloads for the docks. I’m using WMIExplorer to show where it is…

$computer = $env:COMPUTERNAME
$namespace = "ROOT\HP\InstrumentedServices\v1"
$classname = "HP_DockAccessory"

Write-Output "====================================="
Write-Output "COMPUTER : $computer "
Write-Output "CLASS    : $classname "
Write-Output "====================================="

Get-WmiObject -Class $classname -ComputerName $computer -Namespace $namespace |
    Select-Object * -ExcludeProperty PSComputerName, Scope, Path, Options, ClassPath, Properties, SystemProperties, Qualifiers, Site, Container |
    Format-List -Property [a-z]*

Related Posts: HP Dock WMI Provider Deployment & Inventory with ConfigMgr – GARYTOWN ConfigMgr Blog

If you download the firmware, you can grab the WMI Provider in the Manageability Folder and deploy it out, then you can use that to collect the inventory in ConfigMgr pretty easy by adding that WMI namespace for hardware inventory. Once I get one of these docks, I’ll plan to blog that process too. On my test machine, I ran HPDockWMIProvider.exe, and let it do it’s thing. The “HP Dock Accessory WMI Provider” App shows under Add / Remove programs.

HP USB-C G5 Essential Dock.. I haven’t found any place to get this without running the HPFirmwareInstaller.exe tool, which creates an output file with the information, so that’s what I end up doing.
HPFirmwareInstaller.exe -C to run a check, which creates a file called: HPFI_Version_Check.txt

Note: Error Code:105 = ‘Out – of – date firmware detected when running with ‘check’ flag.’

Custom Function: Get-HPDockUpdateDetails

Based on what I learned and how to test if an update is needed, I, with the help of coworker Dan Felman, wrote a function to get information about the HP Dock attached, and update with additional parameters.

Using Get-HPDockUpdateDetails Function to Update Dock & Create Log

I’ll be running the function with three parameters:

• UIExperience set to NonInteractive = Shows the display for the update, so user can see progress but not interfere.
• -Update = To allow the update to happen if device finds an update available
• -Transcript = Create a transcript log of the process in C:\swsetup\dockfirmware

Get-HPDockUpdateDetails -UIExperience NonInteractive -Update -Transcript

HP Dock Updates via Intune Proactive Remediation

For this, you’ll want to take the main script in GitHub, create two copies of it.

• HPDockUpdater_Detect.ps1
  • Set variables: $Purpose = “IntunePR” & $Remediate = $false
• HPDockUpdater_Remediate.ps1
  • Set variables: $Purpose = “IntunePR” & $Remediate = $true

Then upload to Intune:

HP Dock Updates via ConfigMgr Configuration Items

For this, you’ll want to take the main script in GitHub & the Detection Script in GitHub, then create a new Configuration item, choosing Windows Desktops & Servers and check the box for “This configuration item contains application settings.”

On the Detection Methods Screen, paste the Detection Script in from GitHub:

In both the Discovery & Remedition script areas, you’ll paste in the script from GitHub

Make minor adjustments on both scripts:

• Discovery
  • Set variables: $Purpose = “ConfigMgr” & $Remediate = $false
• Remediation
  • Set variables: $Purpose = “ConfigMgr“ & $Remediate = $true

On the Compliance Rules Tab, click “New”, set the Value to “Compliant”, and check the two boxes.

Then finish up, and add it to one of your baselines, or create one for it to deploy. I’ve added it to my HP Clients Baseline and make sure you set it to optional, so it only runs on devices that has a dock detected.

Note, This did work for me, however due to the amount of time the script takes to run, I did get a time out error:

But it did successfully update the Dock Firmware:

And the next time the Baseline Ran, it went back into compliance:

If a dock is not connected, it will report “Not Detected” and not impact your compliance.

PowerShell Simple Method..

If you just want to play with the function and test updating a system, grab this code, then grab the function from github and paste into that area, and trigger it.

### Grab Function Get-HPDockUpdateDetails and Paste Here: https://github.com/gwblok/garytown/edit/master/hardware/HP/Docks/Function_Get-HPDockUpdaterDetails.ps1


### Function Ends

$DockInfo = Get-HPDockUpdateDetails
if ($DockInfo.UpdateRequired -eq $true){ #Update Required
    Get-HPDockUpdateDetails -UIExperience NonInteractive -Update -Transcript 
}

Wrapping Up

With the examples I’ve provided, you can either create your own Proactive Remediation or Configuration baseline based on these two examples, or you can use any method you want leveraging the custom Get-HPDockUpdateDetails function, like scheduled tasks, Tanium, or other endpoint management systems.

Please provide feedback, as I had very limited ability to test.

GARYTOWN.COM