MSP N-central

licensing anniversary notice pop up

We've had a licensing anniversary notice pop up. ... is it possible to send this only to administrative users, rather than have it on the login screen? It’s the licensing anniversary of your MSP N-central Server. To prevent your server from becoming unlicensed, please ensure that your server is publicly accessible over port 10000 and that we have your current FQDN or public IP address. If you need to contact us, log ...more »

Submitted by (@andrew.muriithi)

MSP N-central

Uploading AMPs that were created in AM 2.3

The 11.1 SP1 agent introduces the requirement for PS 3.0 with AMP's. If we don't upgrade the agent, then existing amp's will work. if we do upgrade the agent, then amp's will no longer work as the device doesn't have ps 3.0? So we don't upgrade. As the requirement for PS3 comes from AM2.4 on the device, shouldn't this mean that if we upload amp's to the server that were created in AM 2.3, they will work across all devices? ...more »

Submitted by (@andrew.muriithi)

Mail Assure

Unknown Users - Passthrough for nonlisted is missing

MSP Mail provides the setting "Mail Sent to Unknown Recipients" allowing to select one of the following --------- BLOCKED: rejected during SMTP conversation DROPPED SILENTLY: accepted during SMTP conversation then silently deleted PASSED THROUGH: all messages to unknown addresses will be delivered (unfiltered) to the customer mail server AUTOMATICALLY ADD: All unknown recipient addresses that are validated by the ...more »

Submitted by (@martinb)

MSP N-central

Use agentcleanup.exe tool when probe fails re-install

Support has pointed me to a file used for fixing broken agent installs called agentcleanup.exe, which should be used to fully remove the agent before re-install. I've run into issues with the probe re-install option failing for many reasons, and using this tool has been a real boon for us. Why not put it in the probe tools folder and let the probe try removal on initial failure, then schedule the re-install for 15 minutes ...more »

Submitted by (@paultm)

MSP Remote Monitoring & Management

Let the AV check fail on threat found not just on quarantined



currently the check for MAV BitDefender can only set to fail when successfully quarantining a threat, however that is not always possible (threat inside a currently used pst for example). Please allow us to let the check fail on finding a threat, not just on quarantining it.



thank you for your consideration.

Submitted by (@dratini)