How Does eG Enterprise Monitor Dell Wyse Thin Clients?
eG Enterprise monitors Dell Wyse thin clients in an agentless manner.
Pre-Requisites for monitoring Dell Wyse Thin Clients
-
For internal monitoring of the Dell Wyse thin clients, an extremely light-weight, Endpoint Agent has to be installed on each of the Dell Wyse thin clients.
By default, an eG remote agent on a remote Windows/Linux host is used for monitoring the Dell Wyse thin clients. However, the remote agent does not initiate any communication with the Endpoint Agent on the individual Dell Wyse thin client. This is because, this remote agent has no knowledge of the hypervisor on which the Dell Wyse thin clients are operating. Therefore, it can neither discover the IP address/host name of the Dell Wyse thin clients, nor can it communicate with them to collect the 'inside view' metrics.
This is why, the Endpoint Agent installed on the Dell Wyse Thin Client has been specifically engineered to initiate all communication. The Endpoint Agent on an Dell Wyse Thin Client first communicates with the eG manager to know which remote agent has been assigned to that Dell Wyse Thin Client. Then, the Endpoint Agent pushes the cached 'inside view' metrics to that remote agent via TCP. To enable this communication, a TCP port has to be opened on the eG remote agent. If the remote agent is behind a firewall, then make sure that the firewall is configured to allow one-way communication from the Endpoint Agent to the remote agent. Upon receipt of the 'inside view' metrics, the remote agent sends the metrics to the eG manager.
Figure 1 : The Endpoint Agent - eG Remote Agent communication when monitoring Dell Wyse thin clients
-
When monitoring Dell Wyse thin clients, the remote agent needs to be in the same subnet as that of the Endpoint Agent or accessible on the local network of the Endpoint Agent.
-
Ensure that the Endpoint Agent communicates with the IP address of the remote agent directly and that the communication is not via a NAT or port forward.