Environment
ZENworks Configuration Management 2020 Update 1
Situation
Support for Windows 21H1 and 20H2 is officially supported in ZENworks 2020
Update 2. However, a Field Test File (FTF) has been released
for ZENworks 2020 Update 1 for those who can't upgrade to 2020
Update 2 right away.
Resolution
For an official Field Test File for ZENworks 2020 Update 1 see "Support Windows 21H1 TID - 7025188" on the Micro Focus Software Licenses and Downloads (SLD) site.
ZCM: https://kmviewer.saas.microfocus.com/#/1157627
The
patch fixes three things:
- Device registration use the correct display version instead of XXXX. Example: "Windows 10 21H1 Professional N (Build 19043)" or "Windows 10 21H1 Enterprise (Build 19043)"
- Inventory details use, for example, "Windows 10 21H1 Professional N (Build 19043)" or "Windows 10 21H1 Enterprise (Build 19043)" instead of "Windows 10 Professional N Version 2009 Build 19043" or "Windows 10 Enterprise Version 2009 Build 19043"
- System Requirements for bundles will show, for example, "Windows 10 21H1 Professional N (Build 19043)" or "Windows 10 21H1 Enterprise (Build 19043)"
Note the caveats for use of this file in the Additional
information below.
Warning: The patch includes a bundle that installs core agent dlls and has an action to reboot!
Additional Information
The Field Test File is for version 2020.1 only. Both agent
and primary server must be at that version. The Field Test
File includes changes to both primary server and ZENworks agent for
managed devices. Both must be patched for the fix to fully
apply. Older agents will still register as XXXX version and
inventory will show 2009 version.
Note: Unpatched or older agents will not evaluate system requirements correctly.
Note: The patch programmatically adds the support to ostargets, so no custom/manual changes are necessary. If custom ostargets was modified prior to the FTF to add support for 21H1, that customization can be reversed or ignored. Since the agent is sending up a different string, prior changes should not affect the FTF.
Note: The patch programmatically adds the support to ostargets, so no custom/manual changes are necessary. If custom ostargets was modified prior to the FTF to add support for 21H1, that customization can be reversed or ignored. Since the agent is sending up a different string, prior changes should not affect the FTF.