Opmanager MSP issues

Opmanager MSP issues

I will try to keep the list as short as possible.

1.) where is MSSQL backend database support?

2.) As you tell a probe to discover a network and it finds a router, it queries the routers interfaces for thier network and subnet mask to allow for this network to later be activated and autodiscovered. Where do I find this discovered NEW network to tell it to autodiscover. This is bad because when i goto Autodiscover that unmanaged hidden network, it tells me that it cannot add the network because it already exists. Please refer to next issue as possible reason for me missing it.

3.) The webclient on the Central server ""C:\Program Files\AdventNet\ME\Probe\jre\bin\javaw.exe" -Dwebserver.protocol=https -cp .\classes\OpManagerStartupClasses.jar com.adventnet.me.opmanager.start.OpManagerStarter StartOpManagerWebClient" does NOTHING. It will not spawn the client.

4.) PING and TRACEROUTES are not aware of PROBES.. they try to initiate from teh Central Console.

5.) Adding Custom "Device Types" still dont allot for "Catagory" of the device your adding. So they all show up as "DESKTOPS"

6.) When adding a device manually, there should be an interactive setup displaying all information found about the device so that you can enable/disable certain features/interfaces prior to submitting it to the database for activation.

7.) Opmanager STILL DONT LIKE NAT!!!!!!!!!!!!!!!!

8.) there is no "RE-AUTODISCOVER NOW" button anywhere to tell it to initiate a new autodiscovery on a network.

9.) You cannot turn OFF the global Autodiscovery, it has to be set to between 1 and 15 days.

That should do it for now... I think this should keep them busy for 6 months or so... :)



















                  New to ADSelfService Plus?