The ability to call Custom Details into variables during automation policies would be very helpful when you are tying to filter options
When creating an automation policy, I need a way to include the customer ID and the Site and the machine id in N-central (not necessarily the net bios name) in an email that is being sent out. If i could pull this information into a variable that would be great. An email that only contains the computer name is not very useful with you have thousands of computers.
I would like for the N-Central probe to be able to run SNMP SET commands and for these to be save as a script type object that can be run on demand or integrated into healing processes. Healing processes need to be to run the SNMP script against third party devices. For example, if I have a PoE powered wireless access point or security camera, if the connection service shows the device to be down, then I would like it ...more »
I think this should be discussed now and considered so we don't have to wait another year+ to use this described functionality after the CDP>AM/AMP integration is complete. When CDPs are able to be used and set by AMPs, this would allow for better use of CDPs. The idea would be to allow us to create different classifications or groups of CDPs and dictate the permissions to each classification independently of each other. ...more »
Hi, I have a successful failed check and run automated task setup for Windows Defender updates. However, the loop doesnt close when the automated task runs successfully. So I am left with an open alert and ticket. The suggestion is to run the associated DSC check(s) again manually. For full automation it would be good to have the associated DSC check run again, say 2 or 3 times max (to prevent an infinite loop on continuous ...more »
There's two parts to this feature request. I want a new type of Reboot Maintenance Window added (or add an option to the existing Scheduled Reboot Maintenance Window). This reboot would only occur if Reboot Required is true; otherwise its options would resemble the existing reboot maintenance windows. Use case here is different devices or clients have different acceptable windows to restart systems. Having the Reboot ...more »
At the moment it's only possible to set scripts (pre-backup and post-backup) through the local endpoint GUI (http://localhost:5000) and not through the central management console. I have to manage many Workstations where I have to configuare a pre and post backup script. This part of the software at the moment not fits the needs of an MSP. I hope this would be solved in a next version.
When selecting which Script or AMP to run, it would be very helpful if the search in the drop down was a contains instead of a starts-with.
Office 365 Exchange Online and Azure AD powershell scripting. The built in actions are limited given the variety of powershell commands that exist. Likely the amp actions are just powershell commands underneath, so open it up.
Create a username input type. Right now when you specify password, the technician can select the device credentials password as an input. That's great, but in many cases you need to pass a username, too. The technician has to then know what the name of the device username is and that's on a different screen. Interestingly, in the drop down for the password parameter one could select the username, but that is useless because ...more »
Continue running an automation after the automation triggers a reboot - e.g. need to join computer to domain, reboot, then do more stuff in one automation.
When we reply to an assigned ticket or start a timer on a ticket the status should change from Assigned to In-Progress. Likewise when we set the ticket on hold or pending customer reply and the customer replies it should be taken to a pending technician review status or something similar. We are still missing important messages since the system continues to e-mail us for the changes we put into the system, if we made ...more »