Sometimes ZCM agents can be 'broken' to the point where no services are running. When a Discovery Task is run these devices are flagged as not running the agent as they won't respond to a ZENworks Ping. A Deployment Task is created, but because these devices already have an agent installed the task fails.
There seems to be a disconnect between what the Discovery Task scans for and the agent files existing on a device.
Is there a way a Discovery Task can check for the existence of an agent, such as looking for files and registry keys? A way to give an accurate picture of where the agent is installed, even if it's not working correctly.
by: Stuart P. | over a year ago | Other
Comments
Suggestions from Engineering:
How about reading the remote registry? We can check the key we create for ZENworks.. HKLM\Software\Novell\ZCM -> AgentInstallPath, Version.. We may be able to use these fields to determine whether agent is installed or not.
WinAPI reads remote registry. Maybe we can enhance discovery to read these registry entries and factor this info while processing the discovered device list.