Node.js - LTS not distinct

[mc_edwards]

I just inadvertently updated a dev's Node.js from 12.8.3 to 14 using the main Node.js x64 update (Intune only).  This seems to be a quirk from the Node.js .msi, as their version 14 .msi and their LTS .msi have the same upgrade code (but different product codes) (see attachment).

Should the Intune update for [Node.js x64] have a requirement script that considers the product code for version 12 not applicable?

[Cody Mathis]

Hi there, looks like we might need a major version filter on this! I'll do some testing and let you know.

[Cody Mathis]

Hello,

We have just updated this on our end.

Can you please delete your Intune Application / Update for Node.JS, and then run a sync in the Publisher to recreate the app?

Node.JS NON LTS should now only update a version 14 install. So the Node.JS app will not update the version 10, or version 12 versions of Node.js.

Worth noting, it will also not update a version 13 build.

Let us know if this solves your issue.

[mc_edwards]

Confirmed:  device with 12.8.3 installed WILL not be upgraded to version 14 now...thanks for fixing so quickly!

[Cody Mathis]

Good to hear! Thanks for making us aware of the issue.