To monitor multiple windows server using nagios, define multiple hosts in the windows.cfg mentioned in the step#3. For example, your \/usr\/local\/nagios\/etc\/objects\/windows.cfg will looks like the following:<\/p>\n\n\n\n
define host{\nuse windows-server\nhost_name remote-windows-host1\nalias Remote Windows Host1\naddress 192.168.1.4\n}\n\ndefine host{\nuse windows-server\nhost_name remote-windows-host2\nalias Remote Windows Host2\naddress 192.168.1.5\n}<\/pre>\n\n\n\n----===----<\/pre>\n\n\n\n got it working, but it took some trial and error. Essentially just making<\/pre>\n\n\n\ncopies of the sample windows.cfg wasn\u2019t working, so I had to comment out<\/pre>\n\n\n\neverything in copy and start one thing at a time until I got it right.<\/pre>\n\n\n\nFrom what I can tell, you need to keep the \u2018hostgroup\u2019 section commented<\/pre>\n\n\n\nout in all but the first .cfg you make. This will set the hostgroup for<\/pre>\n\n\n\nthe template \u2018windows-servers\u2019, so any other host added that uses that<\/pre>\n\n\n\ntemplate will automatically be added. I got errors if I included this in<\/pre>\n\n\n\nthe other .cfg\u2019s.\nI think multiple .cfgs, one for each server, is a better way for me to do<\/pre>\n\n\n\nit, because it will keep them more organized. I support tens of small<\/pre>\n\n\n\nbusinesses all over my area and am working to monitor them all over<\/pre>\n\n\n\nthe Internet. This is method just makes more sense to me.\n\nHope this helps, Carlos! Post back with your progress!<\/pre>\n","protected":false},"excerpt":{"rendered":"To monitor multiple windows server using nagios, define multiple hosts in the windows.cfg mentioned in the step#3. For example, your \/usr\/local\/nagios\/etc\/objects\/windows.cfg will looks like the following: define host{ use windows-server host_name remote-windows-host1 alias Remote Windows Host1 address 192.168.1.4 } define … Continue reading