Page 1 of 1

Any special considerations for Win 2012 non-GUI

Posted: Mon Sep 14, 2015 12:08 pm
by neworderfac33
Good afternoon,
I'm just wondering if there are any special considerations that I should be aware of when trying to monitor Windows servers running under Windows 2012 with no GUI i.e. text interface only?

The reason I ask is that I installed NSClient++ on two such servers before I had to leave work unexpectedly this afternoon (my son had locked himself out of the house, so I had to up sticks and move quickly!) and, realising that this isn't exactly precise reporting, the last thing I remember seeing in the interface was something like "Unable to retrieve information from host".

As I'm at home now, I'm unable to tell you the exact message , but if anyone out there can at least say "Ah yes, you need to...", it means I can get a good start when I go in in the morning (an hour early to make up for the time I lost today!) and I don't lose a day waiting for the Nahios community to come on line at 16:00! :-)

As always, thanks in advance for your help.

Pete

Re: Any special considerations for Win 2012 non-GUI

Posted: Mon Sep 14, 2015 3:46 pm
by jdalrymple
My installation scripts for Windows work equally well on both Full and Core installs for 2008 R2 through 2012 R2.

That doesn't necessarily help with your problem, but I can tell you that *it works fine*.

Re: Any special considerations for Win 2012 non-GUI

Posted: Mon Sep 14, 2015 6:40 pm
by Box293
In addition to this, creating or modifying the nsclient.ini file in 0.4.x versions can be done from the command line:
http://sites.box293.com/nagios/guides/n ... t-ini-file

Re: Any special considerations for Win 2012 non-GUI

Posted: Wed Sep 16, 2015 5:34 am
by neworderfac33
Not really sure what happened - I didn't change anything, but the servers are now being monitored

Also, if anyone is interested, I resolved my issue where i couldn't install NSClient++ 0.4.3.143 on Windows 2003 servers by reverting to version 0.4.0.169.

This thread can now be closed - thank you.

Pete