Identify Windows 10 sub version for Lifecycle Planning

[JosephKaufman]

Please add subversion (1809, 1903, etc.) details for Windows 10 recognition for FNMS Cloud (and on-premises) customers. Client needs to track Windows 10 versions that are going EOL to mark as unauthorized as they may not be covered by current maintenance.

[erwinlindemann · Accepted solution]

Hi Joseph,

Flexera has announced supporting the Windows Build # with the upcoming next FNMS release. FNMS 2021 R1 is tentatively scheduled for end of Q2 2021.

If you look into any NDI file created using a recent Flexera agent on a Windows computer, you should see that the Windows Build # is already extracted from the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion branch of the Windows registry. This property is not imported into the [FNMSInventory] database and not exposed to the FNMS UI (yet).

And I believe that Flexera would like us to post this sort of feature request into the Ideas portal instead of posting as an article in the forum (regardless if we like this concept or not ..).

The Ideas portal will become visible only after you use your account for logging into the community.