© 1E 20113
1E efficient IT solutions, specifically NightWatchman Enterprise and NightWatchman Server Edition, require ITdepartments to install a software agent (which resides on a workstation or server) and collects data based on acentrally set policy. Agents collect, aggregate and process local data and only communicate changes when necessary.Many other software solutions on the market adopt an agentless approach, relying instead on a central service thatinterrogates systems remotely to retrieve data, without having a locally installed agent on each client.We look at the pros and cons of each approach and debunk the myths around installing agents. According to Gartnerthere is already a consensus that neither approach to monitoring is absolutely superior. Each has its strengths indifferent contexts.
An agent is like a spy in the ranks, giving youa lot more information than you would get from just looking through a telescope (agentless)
Why you want an agent working for you
Why does running an agent lend itself to power management?
An agent running on the system is capable of local data collection, correlation and processing. Taking PC powermanagement as an example, the agent can make better decisions based on activity that happens locally, for examplewhether the user is active before prompting to power off the system.An agent running on the machine can query the operating system to check when the user last used the machine andwhether he is logged on locally or remotely in order to defer or force the low power state. With multiple userslogged
on, each user’s documents can be saved before logging off. In summary, user productivity is not disrupt
ed.Using an agent for a server power management solution is the only way to identify whether useful work is beingcarried out on a server. This is the only way to accurately determine if a server is being used, enabling you to easilydiscover and decommission the 15% of servers doing no useful work.With agentless technology, there is reliance on remote methods to find interactive user sessions which have adependency on specific remote accessible APIs that cannot return whether the sessions are really active i.e. userlogged on and working. There is also no solution for true useful work detection with an agentless approach as thisdata is not exposed remotely.
Avoiding dependence on the network connection
Agentless solutions are entirely dependent on network connectivity to obtain any information from clients.. Forexample, if there is a network problem it may make the assumption that a workstation is in a low power state when