MSP N-central

Submitted by (@joncz.doiseriouslyneedatleast6characters)

Split Notification recipients on Success / Failure / Expired

I would like to see the Notifications tab reworked throughout the NC server. Right now, you can only notify on success or failure, and you can only select a single group of recipients to be notified in all instances. What I want instead is to have a section each for Success, Failure, and Expired with the ability to [x] Sent task output file and select recipients distinctly for each section. Use case is to receive a ...more »

MSP N-central

Submitted by (@jervydc)

Notification Profile when device is deleted/modified/etc

Default or System Notification when a device has been deleted. -> User should be able to identify to which customer or partner it will be applied. -> Included on the default reports under status which includes time of deletion, customer where the device is deleted, device name and account who deleted it. -> Notification should include to user who deleted it, device name and customer name This Notification and reporting ...more »

MSP N-central

Submitted by (@dylan.oblena)

AV notification exclusion for specific file/file types

We'd like to have the ability to exclude alert notifications for certain scanned file/file types. This is for instances where a file type that is just ignored (e.g. ost, html, cab) are still logged but wont notify as "Present" status repeatedly. The Global Exclusion excludes the file/file type from getting scanned but we would prefer to still see it on the audit trail, that way it would still be included on the reports ...more »

MSP N-central

Submitted by (@pcnet.andy)

Default notification profile for Probes

In v11.1, N-Central added a feature that automatically adds the default "Agent/Probe Status" notification profile to all new Probes. This is excellent... unless you don't use the default notification templates. I would like to have the ability to automatically add non-default notification profiles to a Probe. Preferably this functionality would be implemented through the existing Rules structure, just like any other automatic ...more »

MSP N-central

Submitted by (@kaneio)

Add Disconnect to Notification State

Could we please get "Disconnected" State added to New Trigger Settings? We are trying to create a notification for when a server is placed in maintenance mode for longer than 3 days. This will also catch corrupt agents that do not respond from a scheduled task, that places the agent into Maintenance mode, like a Post Patch Reboot.

MSP N-central

Submitted by (@aaron.martinez)

Custom Email Notification for Maintenance Windows

Some customers require email notification at beginning and end of maintenance window. Would be great if we could schedule an email notification within the same patch management rule, to email out a notification at start and end. With ability to customize the email, include brief description, header and logo of company, a signature, as well as include list of targeted devices. Perhaps even generate a report to attach with ...more »

MSP N-central

Submitted by (@mschmit)

Ability to alert on Outdated Agents

Have the ability to configure and send notifications based on the last time an agent has communicated with the NCentral server. The purpose would be to review this on a monthly basis and connect with clients about devices that are offline to help keep NCentral more organized.


I know there are filters and dashboards that can be created, but the ability to generate a PSA ticket would also be nice.

MSP N-central

Submitted by (@sabir.ahmed)

Patch Management Notifications

I think we need to be able to configure notifications for end users to alert them that Patch Management will proceed on a given day. It will serve as a reminder to leave their PCs on as well as to save their work - might be worth making the notification itself customisable in the content. Currently, I've found two ways to notify users. One is through the patch profile but it will only alert users if a reboot is required. ...more »