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).
Right now, the only way to allow "Patch on demand" is to grant the "Patch configuration" permission which allow the users to create new patch profile, edit existing one. Having a separate permission would allow administrator to configure the patch profile and service desk agent to use patch on demand.
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.
I've noticed that some of our clients' devices have not been getting AV Defender agent updates. Our maintenance windows are usually set on the weekends or late at night, so I suspect that the users are turning off their PCs despite us telling them otherwise. For Windows updates, there's an option to have the updates installed the next time the machine boots up. It would be great if there was a similar option for AV Defender. ...more »
It may sound a bit redundant, but there are scenario's in which we would like to be able to give a user the ability to access administration and configuration options with some Device options at the SO level while stopping them from access Client/Site specific options. Not sure if there is a better way to word this suggestion, but I feel it's worth mentioning.
It would be nice to be able to use booleans in an automation policy with the added effect of allowing certain input parameters to only show when certain boxes are checked. This would allow for more complex and user friendly Automation Policies without the need to give the user to many options when they are running specific Automation Policies. To give a small example, I have a disk cleanup script that has multiple sections ...more »
We would like to see the ability to set the default connection to either the user's remote desktop (which is the current default) and add the capability to set to connect in Chat mode first like MSP Anywhere and the Mobile App does now.
We would like to make our scripts as general as possible to be able to use on multiple clients. We encounter that during the running an automation policy page having a long description and/or variables is too difficult for new technicians. Can we add the option to have a dropdown menu with custom variables from the input section.
New report proposal for report manager, which shows users which are concurrently logged in on multiple devices. Shows user and the different devices the user is logged into concurrently at different times during the report period. Would like it to be configured so that either a time period can be entered for an overview, or enter a username to find all accounts of the user.
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.