Auto-Discovery status keeps running ...

[abrist]

The newest version of the component is 2.04, but you will not be able to update it on an eval account. It should update though with an upgrade to XI 2014r1.0.
Is upgrading XI an option?

[PhilG]

The newest version of the component is 2.04, but you will not be able to update it on an eval account. It should update though with an upgrade to XI 2014r1.0.
Is upgrading XI an option?

It is possible, but as I stated a couple of posts ago that upgrading to a version "1.0" (with anything) is not always the best solution, too.

Please explain your term "eval account" since we are licensed, and I have upgraded Nagios XI once, possibly twice, since Fall 2013?

[tmcdonald]

Please explain your term "eval account" since we are licensed, and I have upgraded Nagios XI once, possibly twice, since Fall 2013?

Most of the time when people are posting in our General forums instead of Customer it's because they are not licensed yet, so I think that was the assumption here.

[PhilG]

Please explain your term "eval account" since we are licensed, and I have upgraded Nagios XI once, possibly twice, since Fall 2013?

Most of the time when people are posting in our General forums instead of Customer it's because they are not licensed yet, so I think that was the assumption here.

Sorry about that. I'll make sure to post in the Customer Forum next time.

[PhilG]

I discussed this issue with my Director, and he stated that I should go ahead with the upgrade.

Latest Available Version: 2014R1.0
Installed Version: 2012R2.9

I will remove my 2 test servers/Hosts and their respective Services, first, then Apply and Write Config.

I have also found out that Nagios XI is not accepting complex passwords that utilize "!" (or any special character??) and will post my question about that in the Customer Forum.

[tmcdonald]

We'll keep this thread open so you can update us on the component after the update. If you have other issues go ahead and open up separate threads.

[PhilG]

I checked the Auto-Discovery component version and noted
"Auto-Discovery
Provides device and service auto-discovery.
Version: 2.04 Author: Nagios Enterprises, LLC
"

I am running an Auto-Discovery job at this time (I noted that there were a couple of changes) and will report back with result.

[slansing]

I want to address this point specifically until we hear back on your auto-discovery test:

I have also found out that Nagios XI is not accepting complex passwords that utilize "!" (or any special character??) and will post my question about that in the Customer Forum.

Are you talking about using passwords to access XI itself? Or for your checks? If you are talking about using this with your checks you can set passwords via $USERn$ macro's in the /usr/local/nagios/etc/resource.cfg and then call those specific macro's in your check commands. If you can clarify this when you post this question in the customer forums that would be greatly appreciated, thanks!

[PhilG]

I want to address this point specifically until we hear back on your auto-discovery test:

I have also found out that Nagios XI is not accepting complex passwords that utilize "!" (or any special character??) and will post my question about that in the Customer Forum.

Are you talking about using passwords to access XI itself? Or for your checks? If you are talking about using this with your checks you can set passwords via $USERn$ macro's in the /usr/local/nagios/etc/resource.cfg and then call those specific macro's in your check commands. If you can clarify this when you post this question in the customer forums that would be greatly appreciated, thanks!

With the Windows WMI checks.
During the Windows WMI wizard job I enter our Domain service admin account (with all Domain access and permissions) and it's associated complex password (which contains a non-alphanumeric character), and things that need to be monitored like the disk partition or Windows service are reporting with an error. I found in the Nagios forum that the error was related to passwords using a "!".

If I can get Auto-Discovery to work, then I'll check back into the WMI checking a complex password issue.

[abrist]

If I can get Auto-Discovery to work, then I'll check back into the WMI checking a complex password issue.

Alright. To use a password with an '!', you will need to use a $USERn$ macro in /usr/local/nagios/etc/resource.cfg. But we will cross that bridge when you get there. Enjoy the weekend!