Not sure if this has been posted but has anyone found a way to launch a probe without utilizing the UMP and or Infrastructure Manager?
Thanks in advance.
Are you talking about activating a probe? You could use the APIs or the "probe utility" applications to do that as well.
(s) name = PS C:\Program Files (x86)\Nimsoft\bin> .\pu.exe -u administrator -p xx controller probe_deactivate audit
Feb 7 07:39:43:769 pu: SSL - init: mode=0, cipher=DEFAULT, context=OK
Address: controller Request: probe_deactivate
PS C:\Program Files (x86)\Nimsoft\bin> .\pu.exe -u administrator -p xx controller probe_activate audit
Feb 7 07:40:07:798 pu: SSL - init: mode=0, cipher=DEFAULT, context=OK
Address: controller Request: probe_activate
If you wish to do this on a remote host, you'd need to replace "controller" with the full path to the controller "/Domain/Hub/robot/controller"
No, not activating a probe but actually launching a probe. teleporting the probe to a user so that user can make the necessary changes from within a probe itself. what I am trying to avoid is the end user not to use the IM and or the Administrator Portal.
Oh, you mean configuring. If you want to go commandline, you could use the probe_config_get and probe_config_set in a similar fashion. You could also use the APIs to build your own portal or configuration utility.
Are there examples using API to build those "portals and or configuration utilities". As for the "teleportation" of the current UI, ie net_connect probe to appear as it does when launched in the IM, there is no way?
I'm sure there is a way. The probe GUI is fetched from the archive package and then placed into a directory (temp often). Then the probe GUI executable launched by IM and gets passed some arguments, which include some key parameters such as the probe address and sid.
You could copy / extract GUIs from the archive packages (they are version dependent to an extent) and save them to your custom location. Then you'd need to have your own launching mechanism that passes the necessary parameters to the GUI executable.
There may be some additional stuff you'd need to figure out and may eventually cause real problems, but that's just a matter of investigating
This is of course applicable to the Infrastructure Manager type of GUIs, I havent investigated the Administration portal GUIs really, but they basics are very likely the same.
As for examples, I suggest you look at codewizard and the API documentations, they provice some helpful samples. Here's a link to the .net api as I happen to have it bookmarked: http://docs.nimsoft.com/prodhelp/en_US/Monitor/SDK/dotNET-API/Index.html
Retrieving data ...