Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 19 ] [+]
Allow the capability (AMP policy(?)) to script the clearing of all manually entered device level maintenance windows (IE, those windows NOT DEFINED BY A RULE).
Allow the capability for user access groups to use device classes or filters as the method by which to target which parts of N-Central machines a user has access to.
Allow the default connection type for certain device classes to be restricted/set to ONLY one type with the typical non-root user being unable to change it.
In the All Devices view of a customer, allow individual machines to be selected and a task to be run which re-installs the agent. This functionality would be exactly the same as you would find if you went into an individual machine > Settings > Local Agent > Reinstall Local Agent.
This way I could run this command on multiple machines at once instead of having to go into each one individually.
Currently the AV Status service does not recognize AMP for Endpoints (with Tetra enabled) as a valid AV solution and doesn't report on it even when Windows itself recognizes AMP for Endpoints.
Please add AMP for Endpoints compatibility into the AV Status service.
Currently when a new Microsoft OS update is released it changes how it uses Metadata and so N-Central will NOT automatically approve it even though the category of updates in which the OS update resides is set to Automatically Install. Once N-Central updates its code base to read the new Metadata correctly, then the approvals will NOT re-apply. N-Central case # 00921398. Desired Behavior: Once N-Central's code is updated ...more »
Allow us to save/configure the options for VPN connections to client environments. Maybe have a button "Connect via VPN" in each client environment. There would have to be a configuration section for VPN to store credentials.
If you didn't want to store the credentials, then maybe have a plugin to LastPass, AuthAnvil, etc that will, given the name of the password, go and pull it to use in the VPN section.
It would be very helpful to be able to manage our client's DHCP environments via N-Central.
Allowing the management of the client DNS environment would be very helpful to be able to do straight from N-Central.
Currently N-Central allows management of AD Users. It shouldn't be that much more difficult to allow management of client Group Policy environments.
This would be a great functionality and would work on eliminating the need to ever remote into a client system to perform admin tasks.
In the User > User Details > Login Information page, please add a calendar to the options for selecting WHEN the notification period for that user will be active.
This will be useful for scheduling notifications and taking into account user vacations and the like.
Currently, there is no way to filter what disks are being monitored on a PC if the disks (WMI) built-in template is used. I would like a way to say that "if a drive is greater than 1 GB monitor it, otherwise ignore it). This is connected to ticket # 00917650.