Operating System ReleaseId is 2009 on Windows 10 20H2 and 21H1

book

Article ID: 225920

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Asset Management

Issue/Introduction

For Windows 10 20H2 and 21H1 the ReleaseId for Operating System in General Inventory is wrong and displayed as 2009 :

Cause

Starting Windows 10 20H2, ReleaseId is stored in following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DisplayVersion
 
Before it is stored in registry key ReleaseId :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ReleaseId

Environment

Client Automation - Any Versions.

Resolution

If ITCM Agent is in version 14.5, download and install patch SO99111178 on the Agents.

SO99111178 - ITCM 14.5 -Windows 10-21H1 Certification

 

If ITCM Agent is in older version following workaround could be used :

1- Create an Asset Job of type Script and give it a name (ex: Update ReleaseID)

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=DC9y0L85ENli+6cXDeLOoQ==

 

2- In Script tab Copy/Paste the content of attached file Windows_ReleaseID.dms

3- In Scheduling Options, under Miscellaneous tab check the option "This job is allowed to run unattended".

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=RFH6IBB4NWwB4MxDPmzbXg==

 

4- Link this job to a group of machines or on all machines.
This job does nothing on oldest version of Windows 10 machines
 
After execution of AM Agent on the machine, ReleaseId should appear as 20H2 or 21H1 for Windows 10 20H2 or 21H1
 
Example :
 
https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=OMuFZMBAyFRupBILnNZ5pQ==

Attachments

1634029752643__Windows_ReleaseID.dms get_app