How is ApplicationID and UpdateID used by the script runner on endpoints

[steadybird]

Currently on our servers we are manually installing software to them as our CIO did not want to deprecated WSUS and we didnt get budget approval for SCCM.

This has often simply just been us exporting a copy of an APP package from Intune, copying to the target device and running the script runner exe as admin. Works well enough and also means we have a consistent experience for things like user notifications, conflicts etc. etc.

Though looking at the XML with the packages configs I am a little curious how the ApplicationID and UpdateID fields are used by the script runner if at all.

The software appears to install perfectly fine on these non-intune managed devices and I am not aware of any direct upstream connectivity from the script runner to the Intune graph from the target endpoints.

Does anyone know how these values are utilised if at all?


As I was thinking of user notifications just made me wonder on a second thing...

When running the script runner as an admin, or as system, how many users get the notifications? If its a multi-user device do all users get the notification or only a subset?

[Michael (Patch My PC)]

The AppID and UpdateID are mostly used to correlate installations with the specific versions of the product. And as you've noticed, there is no direct communication between scriptrunner and Intune. The Packages are self contained. You'll notice the values are used in the log as well.

Are the Intune Apps/Updates you are copying built by the Publisher, or our Cloud Portal? I ask because you'll notice our packages from the Cloud Portal can use a new command line parameter that has configurations built into it. So if you just run the patchmypc-scriptrunner.exe only, it's possible some of your configurations are not being passed to the 'installation'.

For the MCP notifications, they are only shown if the process is running. If no user has the app open, then the installation will continue and run.

With multi user devices, it will show the notification to which ever user has the process open. But I think we have an active bug right now that if more than one user has the process open, the installation will be skipped.

[steadybird]

Thanks!

Re the notification bug. Yeah I think I spotted that previously running a PMPC package where the conflicting process was running on multiple users. I ended up killing the processes manually and running again and it worked fine.

Re the ID's. PMPC desktop publisher and it was 7-Zip by memory. Not a custom app.
Am I correct in understanding your response that this is mainly a logging thing? Just a plain text thing used to quote into the log files for troubleshooting purposes?

Or is there some functionality impacted beyond that?

[Michael (Patch My PC)]

For ConfigMgr, ScriptRunner can use the ID's to pull some information from the ccm client for additional information, but it's not strictly necessary. Intune deployments don't do any of that, so nothing really beyond that for the actually installation.

ConfigMgr App publishing will also use the values in the package.xml for doing some checking on what specific version is created.