Valuable Historical Insights, Consistently Reliable Over the Years
What do you like best about the product?
The newest updates show historical performance stats back to 90 days.
What do you dislike about the product?
In our multiple years of using NinjaOne there has been minimal things to dislike.
What problems is the product solving and how is that benefiting you?
Automation of simple processes, starting with cleaning up disk space.
A reliable and easy tool that saves time and simplifies IT management
What do you like best about the product?
NinjaOne makes IT management simple and efficient. The dashboard is intuitive, and features like patch management, remote monitoring, and automation save a lot of time. The platform is reliable and customer support is always fast and helpful.
What do you dislike about the product?
The mobile app could have more advanced features for remote management, but overall the experience is excellent.
What problems is the product solving and how is that benefiting you?
NinjaOne helps us manage all our endpoints across multiple locations from a single dashboard. It saves time by automating patch management, monitoring, and updates. The system also improves security and reduces downtime, allowing our IT team to focus on strategic tasks instead of manual maintenance.
Has improved remote access while reducing the need to open SSH or RDP ports
What is our primary use case?
I have been using
NinjaOne for about two years to manage servers, automations, and scripting. Because we are using
NinjaOne, our employees' devices are also shown there. For example, if we have a developer, their device is also shown, and we can remotely access those devices through NinjaOne. I use NinjaOne for everything, including server configuration, logging in to resolve issues, installing TeamViewer, and remote control of servers without needing TeamViewer anymore. NinjaOne provides scripting, maintenance, automation, configuration management, and handling server-level issues, since we require compliance without needing to open SSH ports.
We have Microsoft servers running on a database, and I recently dealt with a tablespace issue. I accessed the server using RDP through NinjaOne since we do not open the RDP port. I logged into the database to check the issue and had to extend that space. For example, if there is an issue with the IIS server giving 500 or 403 errors, we resolve it through NinjaOne. When migrating to AWS VPN, I created a script to deploy the AWS VPN installer to all employees' devices, automating that installation process. If there is any downtime, we access the server through NinjaOne; we do not use any other tools for SSH or RDP.
Our main use case for NinjaOne is compliance, meaning we do not need to open SSH or RDP ports. The agents we install manage the SSH or RDP access. By logging into NinjaOne console, we see a list of servers and can access them directly. This is secure since we can transfer files between local and server locations under PCI compliance. Recently, when migrating to AWS VPN from FortiClient VPN, I scripted the deployment of AWS VPN to all employee devices. I also write scripts for maintenance, such as turning off QA servers over weekends to save costs. We perform maintenance after hours via NinjaOne using RDP for Windows servers and SSH for Ubuntu or Linux servers. Our main use cases involve resolving developer problem reports, server issues, and a seamless access process without opening ports.
What is most valuable?
The standout feature of NinjaOne is that we do not have to open any ports for access, which is great for security. We can also transfer files easily, which is beneficial. The scripting and automation features allow us to run cron jobs and create backups. Overall, security is a significant aspect since we only need to install the agent on the server or employee device for comprehensive management, including remote control and TeamViewer functionalities.
The feature I use the most is the ability to perform RDP or SSH without needing to open ports for specific individuals. This ability to remotely control devices simplifies my workflow significantly. Additionally, the scripting and automation for maintenance and backups are prominent features that enhance our operational efficiency.
The health check feature helps in identifying server issues quickly since I can check logs without needing SSH or RDP. If a server appears unhealthy, I can review its logs to determine the cause without logging in, which speeds up problem resolution significantly. This setup has allowed us to manage our AWS-deployed servers more efficiently by accessing NinjaOne dashboard directly rather than logging into each server individually.
Since we started using NinjaOne, one of the most prominent features has been the dashboard that displays installed agents on servers. If something is wrong with a server, it shows as unhealthy on the dashboard. This feature tells us whether the service is healthy or not and provides operational logs detailing what has occurred over time, allowing us to investigate server problems effectively.
What needs improvement?
NinjaOne can improve in several areas, particularly when it comes to SSH sessions. Maximizing the screen during an SSH connection is not possible, which hampers usability on Linux servers. Also, when entering long commands, it sometimes truncates commands or cuts off words, affecting the user experience, and these are enhancements they could work on.
In addition to previous points, I believe NinjaOne should consider adding notifications about script executions to email, Teams, or Slack channels. Integrating this feature would provide valuable updates on automation outputs or process completions to team members, enhancing overall communication.
Improvements can be made in speed and performance for RDP connections, as it sometimes takes too long to respond. Additionally, enhancing the UI for Linux servers could be beneficial, especially regarding command entry and display for larger scripts to prevent truncation.
For how long have I used the solution?
I have been using NinjaOne for about two years to manage servers, automations, and scripting.
What do I think about the stability of the solution?
I find NinjaOne to be very stable; in the two years I have used it, I have never experienced any downtime or reliability issues.
What do I think about the scalability of the solution?
NinjaOne's scalability is exceptional; we easily install the agent on new servers and can create scripts to automate agent installation. This capability has been beneficial for handling growth within our organization.
How are customer service and support?
I have never had to contact customer support for NinjaOne; I have had no need to reach out to them.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I did not use any other tool before NinjaOne; when I joined my organization, NinjaOne was already deployed. In my previous role, I handled SSH access and had to open ports to specific IPs, which was time-consuming, making NinjaOne an appealing solution.
Which other solutions did I evaluate?
I did not evaluate other options when I joined my organization as NinjaOne was already in use.
What other advice do I have?
In my previous role, I handled SSH access and had to open ports to specific IPs, which was time-consuming, making NinjaOne an appealing solution.
My advice for others considering NinjaOne is that if you require compliance, it is a great option. NinjaOne dashboard consolidates everything, which is helpful for maintenance and backups across various cloud platforms including AWS, Azure, or GCP, making it a preferred choice. I would rate this product an 8 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Excellent Workstation Management, But NMS Features Need Improvement
What do you like best about the product?
Management of workstations and servers is one of the best features. Ninja remotes is a great feature that we use all the time. I also like how easy it is to schedule time with a sales support person to review, explain and assist with any issues we run into from time to time.
What do you dislike about the product?
The NMS side isn't as robust as I would like it to be, and I stopped using it due to the cost and limited features. There was some talk about integrating netflow into the workstation and server agents and that would have been a great feature but I don't think it ever was implemented.
What problems is the product solving and how is that benefiting you?
Windows and Software patching and remote access via Ninja remote is our selling points to clients. Having add ons allows us to add more services over time with clients. This is something we plan on working on next year with upselling to clients.
Feature-Rich Platform, But Support Needs Improvement
What do you like best about the product?
I enjoy all the wide feature set that Ninja offers, and appreciate how they are constantly adding new features and improving existing ones. I feel like Ninja is easy to use, with as many features as there are as well.
What do you dislike about the product?
I have not had great experiences with support when opening tickets. Typically the response time is not great and when I finally do hear back from support, they are not generally helpful and tickets seem to drag on.
What problems is the product solving and how is that benefiting you?
Ninja provides patch management and allows us to continue to automate processes.
Effortless Device Connectivity and Review
What do you like best about the product?
Easy connectivity and review of our devices.
What do you dislike about the product?
Currently a feature request that I had to put in place to be able to connect to Android devices.
What problems is the product solving and how is that benefiting you?
Remote support, device app configuration, MDM management.
Effortless Deployment & Top-Notch Patching, But Room for Improvement
What do you like best about the product?
Ninja One is very straightforward to deploy, with the agent installing rapidly. Among the various RMMs I have used, the patching experience stands out as the best. The patching features are robust, offering options such as forcing updates after a set number of user postponements and ensuring installations occur even if a device was offline during the scheduled patch window. I also appreciate the mobile app, which is excellent for performing quick reboots and other immediate fixes. Third-party application patching works well, too. While the built-in Ninja managed apps list isn't the most extensive, it does include many major applications, and its capabilities can be further enhanced through a winget integration. It has also been refreshing to see that the dev team takes the feature request seriously and so far we have seen many great additions from the upcoming feature releases page.
What do you dislike about the product?
The main challenge I've encountered with NinjaOne so far is the lack of granular permissions. There have been situations where I wanted to enable a specific feature for our service desk team, but to do so, I was required to grant access to several additional features as well. This may make certain features unavailable to give to certain roles if you need to lock actions down very specifically. Another drawback is that the Linux agent currently falls short when it comes to automatically installing or enforcing certain AV/EDR providers, and it does not yet support NinjaRemote. I have been informed that NinjaRemote support for Linux is in development, so I am hopeful that this will be available soon.
On the MacOS side, patch management can feel somewhat divided between NinjaOne's managed patching and patching through the NinjaOne RMM, which can make it challenging to determine the best approach for your particular environment.
What problems is the product solving and how is that benefiting you?
The NinjaOne platform benefits us through its features around patching, monitoring, remote support, remote access, AV enforcement, and drive encryption key management.
NinjaOne: Powerful Customization, But UI Navigation Needs Improvement
What do you like best about the product?
Coming from LabTech, holy smokes... NinjaOne is a breath of fresh air. It's absolute best feature is everything it does NOT have. Every MSP shop of course does generally the same thing, but let's face it, we all like to do it "our own special way". NinjaOne + Custom Fields + PowerShell = Heaven. All the patch management and alerting I leave to the RMM, but so many status checks, cleanup routines, custom software installs, OEM firmware updates, etc... are all scripted. All our scripts are neatly organized in a private Github repo and easily updated in Ninja as needed. Life is a breeze. Fanboy? Maybe a little... but it truly has been that great thus far. Oh... and I love how fast everything is. Very snappy UI.
What do you dislike about the product?
The main thing I find difficult to this day is keeping track & remembering where all I need to go in the interface to do certain things. I recall having the same, if not worse, problem with LabTech, but just "feels" different with Ninja. Meaning, with LabTech there were just so many options buried so deep it was hard to find something. But with Ninja it's an issue where 5 different settings for a Backup, let's say, MUST all be configured... but they are all found in completely different areas of the UI. You would think you could go to the "Backup" settings, but no. Past that, there are many other general wish list items. One that comes to mind is that you cannot see the results of a script as it's running. You have to wait before the output is available. And if the script is hung with a pop-up, you'll never know. So I often end up remoting into the machine to check the log files for long running scripts to see if they are still running or hung.
What problems is the product solving and how is that benefiting you?
Keeps an eye on all our systems and alerts us when anything at all we want alerted on needs attention. Support for software updates and maintenance using our own custom scripts is a game-changer for employee and end user productivity.
Effortless Automation, But Lacks One-Time Screen Connect
What do you like best about the product?
How easy it is to use and run automations.
What do you dislike about the product?
That it does not have one time screen connect capabilities.
What problems is the product solving and how is that benefiting you?
We are a construction company so we have a bunch of employees working remotely. This gives us the ability to help end users out that may not be in the office. Also, we have a branch in Texas and have no IT employees out there. WIthout Ninja One, I can only imagine how hard it would be to help our users out there.
Excellent Onboarding and Support at a Great Price
What do you like best about the product?
Good customer service. Good onboarding experience. Competitive pricing.
What do you dislike about the product?
No real complaints at the moment. We have been a customer for about 4 months at the moment.
What problems is the product solving and how is that benefiting you?
UEM, RMM, Remote Support, Enterprise IT Management, Patch Management, MDM.
