We have a small list of OID's we'd like to have added to the back-end of our NCentral server to the discovery process of Ncentral. These OID's are for Ruckus Wireless devices. The idea is that in discovery, these devices will return a Make/Model data that is associated with the OID and be listed within the Device Asset data. Can you pass along the OID's and this ticket to whomever can assist with this task. The OID: ...more »
Sample Patch Feature update to Windows 10, version 1803 Description: Install the latest update for Windows 10: the Windows 10 April 2018 Update. KB Number: 4345421 Release Date: 2018-07-17 Classification: Upgrades Severity: Unspecified Status: Needed Approval: No Approval Products: -- Superseded: No Removable: No Restart Behaviour: Can Request Reboot Request User Input: No Installed Exclusively: ...more »
Looking to have the ability to train my employees with tracking of their usage. This could also be additional tailored to allowing end user access and reporting to help partners create additional revenue in training. While adding a deeper layer of service it will help partners keep in front of customers without the additional work involved. ConnectWise has some of this for partners, would like team training at least, ...more »
In rolling out N-central, I had planned to make use of the external ID fields for filters but found that the external ID set at the customer level is not equal to the external ID at the site level. Even worse, if a value is set at the customer level for external ID, filtering won't include devices at the site level unless they too have external ID filled out. I would propose: - Give us the ability to create multiple ...more »
When we Create Auto Patch Approval Rules in the SO Level, they do not actually display in the Customer and Site Levels. Even though the system does propagate them, it would be useful to be able to actually see them as inherited from parent as you would with the all other Rules. I.e. If you click on "ACTIONS --> Patch Approvals --> Automatic Approvals" on SO Level and create a rule there; Then go To Customer Level, "ACTIONS ...more »
I have found (especially with Windows 10/Windows Server 2016 server devices), that the following patches will be downloaded into the Agent Patch Cache (C:\Program Files (x86)\N-able Technologies\Patch Management\archive\): - Patches that have been set to "Approved for Install" which are not yet installed, and are superseded by other another patch that is also in the list of "Approved for Install" and "Not Installed" list. ...more »
it would useful to have custom device information be populated by an AMP script.
So for example we have a specific asset tag which is entered into the registry. We would like to be able to obtain this via AMP script and then update the custom asset information with it.
Then it would be handy to filter by the custom asset information.
It would be awesome to be able to access "environment variables" from within an AMP such as Client Name / ID
That way we could write an AMP to install a client-specific software (such as Sophos AV) that automatically determines which client it's installing for, and configures the software appropriately.
Hate to say it, but Labtech has always done this and it's awesome.
I'd like to see the ability in administration\defaults to setup default settings for custom device properties at the customer level. Currently I can go to Administration\Custom Device Properties and setup new CDP's at SO or Customer levels, but what if i want to setup a customer to have an existing CDP fill out a CDP by default (for example roughly half of my customers have SEP managed by us, I'd like to setup a SEP ...more »
The ability to pre-define CDP's as dropdrop options (or radio buttons, yes/no, etc). So when someone goes to change a CDP on a device, they're presented with the only available options and don't have to refer to external documentation (also: if perhaps there could be the additional comment field that allows a description of what the CDP option does). These drop-down CDPs will need to be editable after the fact, in ...more »