N-central Troubleshooting
N-able N-central deployment in a Windows Workgroup environment
Last Modified
Tue Mar 20 20:10 GMT 2018
Description
- This article provides steps to best deploy N-able N-central in a Windows Workgroup network. This also applies to agent deployment to devices that are not part of the domain.
- N-able N-central discovery jobs work best in on Windows Domain networks. This is because the Domain Admin account configured during the probe installation has the necessary permissions to remotely install agents to Windows devices within the domain.
- It is possible in a Windows Workgroup network to configure the same Admin username and password on every Windows device within the network. If this is already configured then install the probe using the same local admin username and password and the probe will remotely install agents on the devices in the workgroup.
Environment
- N-able N-central 10.0 or later
Solution
You most likely do not have the same username and password on every device within the Workgroup network.
Two Options:
- Add the same username and password to every device with the workgroup, then perform a Probe based discovery.
- Manually install the customer specific agent on every device within the workgroup.
Option 2 is recommended since it guarantees agents on all devices. Once the agent is installed, you can automatically create or edit admin usernames and passwords using Automation Manager.