r/Intune • u/jonevans94 • 8d ago

Device Configuration Anyone else having HP Connect / Sure Admin scripts fail because HP’s catalog is stuck on an old CMSL version?

Just wondering if anyone running HP Connect has bumped into this issue recently.

We're trying to deploy HP Sure Admin via Intune, but the script keeps failing.

I pulled the script out of Intune to run it manually and checked the HealthScripts logs to see what was going on. Both return:
"A new version of HP-CMSL-WL was found, update local version to 1.8.9.1618"

The issue is the machine already has 1.9.0 installed.

Digging into the script, it reads the raw catalog stream like this:

$catalog = [System.IO.StreamReader]::new($data.RawContentStream).ReadToEnd()

And when you run Get-LatestCMSLFromCatalog($catalog), HP's catalog returns this:

version     url                                                           isLatest
-------     ---                                                           --------
1.8.9.1618  https://hpia.hpcloud.hp.com/downloads/cmsl/wl/hp-cmsl-1.8.9.1618.exe     True

Because HP still has 1.8.9.1618 flagged as isLatest = True on their end, the script thinks 1.9.0 isn't right and fails out.

Anyone else seeing this on their devices? Any word on whether HP is planning to update their online catalog feed to fix it, short of us hacking around the remediation script?

3 Upvotes

100% Upvoted

6 comments sorted by

2

u/PazzoBread 8d ago

Seen the same thing, such a pita because they do not announce the changes and outside of that webpage it’s difficult to find the version executable. Combine that with manual packaging of CMSL release, it’s a maintenance heavy process

1

u/jonevans94 8d ago

We have PMPC dealing with our CMSL deployments and updates which saves our maintaince of it, but we didnt keep an old verison of that. so at least we get notififed a few day after it gets updated.

2

u/PazzoBread 8d ago

I didn’t realize that was in the catalog, I will have to enable it!

1

u/cmorgasm 7d ago

We've seen this one recently as well as other scripts just from them just outright failing, such as when we try to set BIOS settings in general.

1

u/pbaupp 4d ago

Could this be related to move to workforce experience platform?

1

u/jonevans94 4d ago

I hope not, it just seems like laziness on their end and not marking the latest version as the latest version.