Highlighted
Acclaimed Contributor.
Acclaimed Contributor.
203 views

ZENworks Agent Status connection request delay in ZCC

Jump to solution

Hi!
ZENworks 20.1. I noticed that in ZCC takes much longer for ZENworks Agent Status to get updated for 20.1 Agents installed devices than it takes for earlier Agent versions. Well, this not bother much (as everything seems to work ok), just curious … is this normal? (hopefully it is) and why? Perhaps just cosmetic … problem, sort of. For ZENworks server Status goes green right away.
More thanks, Alar.

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Delay while retrieving ZENworks Agent status

Explanation:At times there is a considerable delay while retrieving the ZENworks Agent Status in the Device Summary page.
Possible Cause:As the server has to contact both the ZENworks Updater Service (ZeUS) as well as the ZENworks Agent, there is a delay in retrieving the status.
Action:In ZCC, navigate to Configuration > Device Management > System Variable, add the system variable PING_DEVICE_TO_SEND_QUICKTASK and set the value as True. This system variable will bypass ZeUS and directly obtain the status from the ZENworks Agent.

NOTE:If the system variable is set to True, quick tasks from ZCC are also sent to the agent instead of through ZeUS.

 

See https://www.novell.com/documentation/zenworks-2020-update-1/zen_discovery_deployment/data/bfxac1t.html#t4cv05a766vm

View solution in original post

7 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Delay while retrieving ZENworks Agent status

Explanation:At times there is a considerable delay while retrieving the ZENworks Agent Status in the Device Summary page.
Possible Cause:As the server has to contact both the ZENworks Updater Service (ZeUS) as well as the ZENworks Agent, there is a delay in retrieving the status.
Action:In ZCC, navigate to Configuration > Device Management > System Variable, add the system variable PING_DEVICE_TO_SEND_QUICKTASK and set the value as True. This system variable will bypass ZeUS and directly obtain the status from the ZENworks Agent.

NOTE:If the system variable is set to True, quick tasks from ZCC are also sent to the agent instead of through ZeUS.

 

See https://www.novell.com/documentation/zenworks-2020-update-1/zen_discovery_deployment/data/bfxac1t.html#t4cv05a766vm

View solution in original post

Highlighted
Micro Focus Expert
Micro Focus Expert

Also make sure HKLM\Software\Novell\ZCM:EnableTraditionalUpdate is not set to True.

This should only be enabled for troubleshooting and then disabled.  This will disable ZEUS can cause delays in the ZEUS status returning.  This key is not expected to be supported in 2020.2 or later as only ZEUS updates will be supported.

 

--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hi and thanks!
Yes, did the trick. But … does this setting mean we may miss some vital … (status) info from device? Or … does not matter much?
More thanks, Alar.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hi and thanks!
No such registry value present.
More thanks, Alar.

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

As far as I know HKLM\Software\Novell\ZCM:EnableTraditionalUpdate is mainly only used enabling the old method of updating the agent and shouldn't affect regular status information. The update status info with the method will most likely be different with the two different methods.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.
Hi!
But, anyway, bypassing ZeUS … is this good setting? I mean, it was set on reason, right?
More thanks, Alar.
0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

When ZeUS was introduced, this setting (EnableTraditionalUpdate) was provided as a fallback. But as ZeUS is stable now, this setting is not required anymore.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.