NinjaOne Review - Revisiting

Our main use case for NinjaOne is for patching all machines in the organization. It is also leveraged for remoting into machines for assistance or to fix servers as needed. NinjaOne has also proved useful when looking at deploying fixes via scripts on a mass scale across the tenant or changing certain settings for certain subgroups of machines / servers across the organization.

It has been a positive impact overall. Users are able to receive assistance quickly compared to the other remote tool we used prior to NinjaOne. It is a smoother step for users and techs all around in that regard. Simpler way to also deploy scripts / changes to machine settings via NinjaOne than with other avenues we have on prem. Patching has also become much easier since switching to NinjaOne.

Keeping systems up to date is the biggest impact NinjaOne has had on our environment. Prior to this, we had an on-prem solution that was very difficult to leverage for patching. NinjaOne also helps keep a monitor on tracking when certain aspects of servers are down or out of line in terms of their normal usage throughout the day with alerting built into NinjaOne.

Deploying certain tasks, icons, files, registry changes and other similar tasks have now been done through NinjaOne. Overall, we do not have an exact number on time saved but it is for sure a fact that it has saved a decent amount of time for the IT team. Compared to how things were done manually before or through on-prem only solutions, NinjaOne is much quicker to reach everyone who needs things implemented since it is cloud based.