Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - LeapfrogIT

#1
General Support / Re: WMI Query filtering
November 19, 2008, 02:03:37 PM
That worked perfectly thankyou victor :)
#2
General Support / Re: WMI Query filtering
November 19, 2008, 05:40:05 AM
Sorry to be a bother , but I am really having a hard time getting this to work for me

As an example , I am trying to run

WMI.Query(root\CIMV2,select * FROM Win32_Service WHERE Name = 'WsusService', Status)

When I use scriptomatic or WMI Query tester it works fine giving the resullt that I expect  however Netxms Console tells me that it's an unsupported DCI , and when I try and run it via nxget i get an internal server 500 error .

Could this possibly be an extention of the current WMI.nsm bug for 2.22 ?  I was seing similar signs happening when I first installed 2.22 without upgrading the wmi part of the agent to the 2.23 rc release
#3
General Support / Re: WMI Query filtering
November 19, 2008, 12:54:17 AM
excellent :) that certainly opens up the queries I can run.


Now I know that I can go back degugging my WQL queries themselfs will add them to Toads Pinned list once I have a decent number of queries made up. Like with most of these things it will probably be the first querie that takes some time afterthat I should be able to duplicate the priciples nice and easly :)


#4
General Support / WMI Query filtering
November 17, 2008, 04:51:30 PM

Is it possible to use more complex wmi queries ad DCI's ?

For example something like

WMI.Query(root\CIMV2,select * FROM Win32_Service WHERE Name = 'ApacheTomcatApplicationServer',status)

Thankyou to any assistance some can provide


kindest regards

#5
Hi ,

I have been playing with netxms for a few weeks now and am ready to test it out at a different location , what I can't seem to find the answer to though is what is best practice for managing multiple Sites from a central location .

What I am trying to avoid is a poll on 70+ servers constantly happening across vpn site link, to make the system happy to run that way I would have to ease back on some of my security which I am not willing to do for the sake of monitoring.

I noticed a hint of hope that I am wondering if someone can confirm for me. Duing the server install you are asked for the master server name ,  for your first install you obiously put that as the localhost , however if your trying to achive what i am could I just put in the address of the original Netxms Server ?

  My thinking is that if I can have the agents at that site polled by a local netxms server which reports back to my master server then it would be a far more efficient way of managing my network.

Anyone have any thoughts views , suggestions etc ? am sure I am not the first to hope and use the product in this manner