N-central Troubleshooting
Windows Agent was installed on a device after being imported from a Discovery Job, even though it was not configured to install the agent
Last Modified
Mon Sep 16 13:28 GMT 2019
Description
- Windows Agent was automatically installed on a device after being successfully imported from a Discovery Job
- This was not meant to occur as the Discovery Job was set to only import and not to push the installation of the agent
- Reviewing the associated rules on the new device, one is set enable one of the features, for example Patch Management
Environment
- N-able N-central
Solution
- This is by design as the features require an Agent to be on the device to be able to function correctly
- Going forward, please review your rules so it doesn't get automatically installed