It will be really helpful for you during your Nagios journey.ġ) Nagios Monitoring Server – A working Nagios Core Server.Ģ) Windows Host – A windows machine, in which we are going to install NSClient++. Therefore, it is highly recommended that you should have Learning Nagios - Third Edition. In this post, we will install NSClient++ Nagios Core Agent on a Windows host to add it to Nagios Monitoring Server.īefore moving forward, it is required to have basic concepts of Nagios Core 4. But after having some research we have selected NSClient++. There are many Monitoring Agents are available, that works well with not only Nagios, but also with other forks of Nagios (such as Icinga). For this purpose, we need to install a Monitoring Agent software in our Host. Now, its time to add some hosts to our Nagios Monitoring Server. Policies, used properly, can be your best friend, but used inappropriately can be your worst nightmare and can significantly impact the VSA performance.We have already configured our Nagios Monitoring Server in my previous post Install & Configure Nagios Core 4.2 on CentOS 6. Some of our clients have done new hardware deployments of nearly 100 agents/day by 2 techs with nothing more than an agent install and manual host rename to meet client standards. The results of our audit, however, do control the policies that apply specific monitor sets, configure and schedule workstation patching and 3rd party updating. That monitor, unfortunately, is a manual-set only option, but - with that one alarm (to give you an idea of what's possible) - our software will configure the agent (rename VSA service, set workstation AC power, etc.), push out our tools, perform VSA and our custom audits, run a series of procedures to deploy software, join the domain, and perform other per-class (server/workstation) and per-client tasks. That should be part of onboarding, not continuous operation.įor onboarding, set the 'new agent' alarm and use it to trigger a response to deploy what you need.

I can't imagine why you'd need a policy to run a procedure to check AV status on an 'every few hours' basis. In fact, there are probably less than 10 agent procedures that we schedule through policies - the rest are for applying monitors, configuring updates, and scheduling (especially server) patching. One thing we never do is run things more than once daily, or schedule things that should happen just one time ever.

Install kaseya agent on windows 10s