In CW Automate, Ninja, and a couple of other RMM solutions, the probe did a MUCH better job of probing the network and bringing in the proper data. Routers, Printers, VOIP phones, WAP's and all that were easily identifiable because of this, especially when some devices such as VOIP phones get their IP via DHCP and the system can still keep up with the custom name given to the phone for identity purposes. Obviously, ...more »
So the probe is great when your client has a machine that's on 24 x 7 (such as a server as opposed to a workstation) but with many clients going to completely cloud-based environments, it can become a bit more difficult to dedicate resources to a probe machine. raspberry pi units all in including storage cost around $60-$70, and are perfect to act as a probe unit that can be put at a customer site in a network room, ...more »
This might be a rather large feature, so I won't flesh it out completely here.
We need a way to have a probe collect running and saved configurations from a network device and store them in a versioned repository so we can see and track changes to the configuration of a device.
It would be nice to have a ping originate from the probe as well as from the Central Server.
There would only be one ping that would be used to determine "connectivity", however this way, the system could test to see if a firewall, or other edge network device, was LAN reachable as well as WAN reachable.
I think it would be real important to be able to access the web portals of network devices (ex: printers, firewalls, etc.) remotely from the Max RemoteManagement Dashboard. I remember when I used N-Able back in 2013 I had that ability. I don't think it would be too difficult to implement. Basically we just use the backend connection to a workstation/server to create a tunnel and access the HTTP/HTTPS portal of these network ...more »
If the Linux agent starts and internet access isn't available yet, the agent just exits. It should continue running and retry at regular intervals like the Windows and Mac agents do.
It is an extension to a other idea about network devices check. See screenshot.
It is OK to have it "under" server check but it is hard to set priority that way. It would be great to have a separate tab and have separate tickets and escalation alerts specifically for network devices.
Can we get a check that verifies how long since the servers last reboot, and gives us the ability to customize how many days since the last boot before the check fails? Personally I'd like to know how many of my servers haven't been rebooted in the last 30/60/90 days so I can make sure they get rebooted.
This might already been in the pipeline for the 'network discovery' feature in RM. But it would be ideal if it could put together a network diagram automatically based off the information that is available to it. I understand it might not be perfect or the diagrams generated are 100% accurate or represented in a way that the client wants but it would definitely allow for easier visualization of the network and assist ...more »
Fix how Network Discovery sorts IP Addresses. It is grouping IP addresses that begins with the same first digit.
Network Discovery is a good feature but ... Once you set a preferred discovery agent (and an alternate agent <==new feature suggestion), the service should stop on all other devices. Allow a mechanism to disable the agent on any machine which 'travels'. If you have a device that moves from network to network either physically (e.g. a laptop you carry around from site to site) or logically (e.g. using a SSL VPN to ...more »
We are aksed what this "AMANM" is,
When we tell our customers, some say "we don't want you to scan our netwerk"
This asks for optionality of this feature.