N-central deployment
March 01, 2019
N-central deployment
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with SolarWinds N-central
We use N-central for a variety of end user/endpoint purposes. We monitor laptops, desktops, and servers. We deploy security patches with n-central. We monitor suspicious activities with n-central. We also utilize n-central for anti-virus. We group internal devices, customer-facing devices, as well as various portions of the infrastructure within the GUI interface.
- Endpoint monitoring.
- Deployment of security patching.
- Deployment of agents on new assets.
- Group policy integration.
- Initial setup/categorization of devices.
- Pricing per device.
- Holistic monitoring and AI of devices.
- Positive impact on external device deployment.
- Scales well for customer devices.
- Allows SLA-based device management.
All three systems integrate with Connectwise Manage. All systems have integration to active directory. Automation does configuration deployment better. Ninja is a SaaS, N-central is a Saas, whereas Automate is on-premise. Automate is more scalable. Pricing and seat deployment is complicated on all three platforms. I would recommend that any organizations that are considering deployment test all three for the best fit.
Using SolarWinds N-central
Pros | Cons |
---|---|
Technical support not required Well integrated Feel confident using | Unnecessarily complex Inconsistent Slow to learn |
- Addition of devices to the org
- GUI/web interface
- AD integration
- Agent deployment with auto discover
- Remote access
- Parsing
Yes, but I don't use it