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)