Customer Story
Why CTS Switched from Connectwise Automate to NinjaOne
With Lorenzo Kopari, Service Manager at Computer Technology Solutions (CTS)
See NinjaOne in action!
Customer Story
With Lorenzo Kopari, Service Manager at Computer Technology Solutions (CTS)
Endpoints supported:
With NinjaOne since
Company
Computer Technology Solutions helps their partners eliminate technology concerns by using the products and services, at the right scale, with the highest degree of integrity.
Headquarters
North Mankato, Minnesota
Website
https://www.yourcts.net/
Computer Technology Solutions (CTS) provides fast and effective IT support services to businesses across the greater Mankato, MN area. Founded in 2003, CTS has used a variety of remote monitoring and management tools to support clients including Solarwinds n-Central and Connectwise Automate. “We switched to Connectwise Automate from n-Central because we were looking for something more comprehensive,” says Lorenzo Kopari, Service Manager at CTS.
After over 20 hours working with the Connectwise implementation team, and countless more working internally, CTS began adding customers to Automate and deploying agents via Group Policy. “It was a long setup process for something that didn’t end up working as well as we anticipated,” says Lorenzo. While some outstanding concerns still lingered, CTS’s team of experienced technicians felt they could learn their new tool on the job. Automate’s level of complexity, outdated user interface, and multiple different user interfaces contributed to a steep product learning curve and in-product inefficiency.
“We didn’t have a full understanding of how much management overhead Automate required,” says Lorenzo. Even with implementation and customer support, CTS felt they would need a full-time employee dedicated to Connectwise Automate to manage it effectively and capture the promised value. Hiring an RMM manager would pose a significant challenge however: they couldn’t just shift an experienced technician to the role, they would need an expert in Automate and it’s proprietary scripting language. Hiring a specific RMM manager to act as inhouse support for other CTS technicians would also cost the company money without directly contributing to revenue. “Logistically, Automate just didn’t make sense for us,” explains Lorenzo. “We’re a smaller MSP with only 15 technicians – it doesn’t make sense to hire someone just to manage our RMM.”
In addition to the steep learning curve and high management overhead, Automate just didn’t deliver on key functionality. The proprietary scripting language forced CTS’s technicians – many of whom had years of scripting experience – to start back at zero, effectively erasing their experience. “We had a hard time automating anything in Automate – even something that would take 5 minutes to write in Powershell took too long to bother with,” according to Lorenzo. Another core functionality – Windows patching – was the final straw. Managing Windows updates is a core deliverable for any MSP, and CTS is no different. Even after going through the full implementation process with Connectwise, Lorenzo says, “We got to a point where we couldn’t reliably push out Windows updates. We spent over 8 hours of our time with their support team trying to get Windows updates to work, but we never could.”
When evaluating which RMM to switch to, Lorenzo and his team had very specific technical criteria:
Lorenzo spent a lot of time in MSP communities, getting a feel for how other MSPs felt about specific RMMs. Rather than rely on a strong sales team, he was determined to rely on his peers for reliable feedback. Lorenzo’s research led him to NinjaOne. “I was a little hesitant to try NinjaOne as there was some community feedback that Ninja wasn’t as robust as Connectwise. Maybe this is the case if you’ve invested very heavily in Automate, but ultimately the functionality we wanted either existed or was added shortly after we adopted Ninja,” says Lorenzo.
While still using Automate, CTS rolled out Ninja to a single client and began testing in earnest. “Honestly, it took us 30 minutes to an hour with Ninja’s support team to get us fully up and running.” When something wouldn’t work in Automate, or when an automation took too long to setup, they’d try it in Ninja, “It just worked. Windows updates were reliably delivered. Remote connections were reliable. Everything we were having a problem with in Connectwise was resolved when we moved those devices over to Ninja.”
Lorenzo sites the short learning curve as one of the greatest benefits of switching to Ninja: “It has really benefitted us as a team. Whenever we hire a new employee, we can onboard them really quickly. We do a 5-10 minute run through of Ninja and tell them to go play around. Even brand-new technicians can usually figure out everything they need to in just a few minutes.” Ease of use hasn’t just helped with new technicians, it’s benefitted existing team members as well by reducing frustration and improving morale.
“NinjaOne’s automation abilities have been invaluable to us as a company,” says Lorenzo. CTS uses Ninja to automate Windows updates, schedule simple tasks, install and uninstall applications, and make scheduled changes to registries across many devices. Technicians at CTS can now write a script in as little as five minutes and deploy those automations reliably.
“We’ve come a long way in the last few years due to the tools we use – including Ninja. We went from a company that didn’t prioritize organization to comfortably using tools that encourage that. We can onboard customers more efficiently, feel comfortable with our tools and even enjoy using them. Our focus has always been to treat customers as best as we can and thanks to Ninja, we can do that better than ever.”
Get 5 bite-sized ways to grow your business or career every week!
Never Miss Out - Subscribe to the NinjaOne Newsletter
Cookie | Duration | Description |
---|---|---|
_vwo_ds | 3 months | This cookie is set by the provider Visual Website Optimiser. This cookie is used for collecting information on how visitors interact with the pages on website. |
_vwo_sn | 30 minutes | This cookie is set by the provider Visual Website Optimiser. This cookie is used for collecting information on how visitors interact with the pages on website. It collect statistical data such as number of visit, average time spent on the website, what pages haves been read. |
_vwo_uuid | 10 years | This cookie generates a unique ID for every visitor and is used for the report segmentation feature in VWO. Also, this cookie allows you to view data in a more refined manner. If you have the campaign running on multiple domains, you will notice campaign-specific UUID values. |
_vwo_uuid_v2 | 1 year | This cookie is set by Visual Website Optimiser and is used to measure the performance of different versions of web pages. |
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
ninja | 1 month | No description |
ninja_added | session | No description |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie is set by CloudFlare. The cookie is used to support Cloudflare Bot Management. |
_vis_opt_test_cookie | session | This cookie is set by Visual Website Optimiser and is a session cookie generated to detect if the cookies are enabled on the browser of the user or not. |
geoData | First-party cookie. Stores geoIP data in order to display appropriate phone numbers and content for your region. |
Cookie | Duration | Description |
---|---|---|
_biz_flagsA | 1 year | This cookie is set by Bizible. A single cookie that stores multiple information, such as whether or not the user has submitted a form, performed a crossdomain migration, sent a viewthrough pixel, opted out from tracking, etc. |
_biz_nA | 1 year | This cookie is set by Bizible and is used to store a sequence number that Bizible includes for all requests, for internal diagnostics purpose. |
_biz_pendingA | 1 year | This cookie is set by Bizible. Temporarily stores analytics data that has not been successfully sent to Marketo Measure server yet. |
_biz_sid | 30 minutes | This cookie is set by Bizible. The cookie is used to store the session ID of the user. |
_biz_uid | 1 year | This cookie is set by Bizible and is used to store the user ID on the current domain. |
_hjIncludedInSessionSample | 2 minutes | This is a Hotjar cookie set to determine if a user is included in the data sampling defined by the site's daily session limit. |
YSC | session | This cookie is set by YouTube and is used to track the views of embedded videos. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | This cookie is set by Google Analytics and is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | The cookie is set by Google Analytics. The cookie is used to determine new sessions/visits. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmc | session | The cookie is set by Google Analytics and is deleted when the user closes the browser. The cookie is not used by ga.js. The cookie is used to enable interoperability with urchin.js which is an older version of Google analytics and used in conjunction with the __utmb cookie to determine new sessions/visits. |
__utmz | 6 months | This cookie is set by Google analytics and is used to store the traffic source or campaign through which the visitor reached your site. |
_BUID | 1 year | This cookie is used to store a universal user ID to identify the same user across multiple clients' domains. |
_dc_gtm_UA-100000610-1 | 1 minute | This is a Google Analytics cookie used to store the number of service requests. |
_fbp | 3 months | This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
_gat_UA-100000610-1 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 2 years | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_uetsid | 1 day | This cookies are used to collect analytical information about how visitors use the website. This information is used to compile report and improve site. |
_vis_opt_s | 3 months 8 days | This cookie is set by Visual Website Optimiser and is used to detect if the user is new or returning to a particular campaign. |
6suuid | 2 years | This is a 6sense cookie. Registers user behaviour and navigation on the website, and any interaction with active campaigns. This is used for optimizing advertisement and for efficient retargeting. |
DriftPlaybook | session | This is a Drift cookie. |
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
page | 1 month | No description |
pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
vuid | 2 years | This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | This is a 6sense cookie. Presents the user with relevant content and advertisement. The service is provided by third-party advertisement hubs, which facilitate real-time bidding for advertisers. |
_rdt_uuid | 3 months | This cookie is set by Reddit and is used for remarketing on reddit.com |
_uetvid | 1 year 24 days | This is a Bing Ads cookie to store and track visits across websites. |
MUID | 1 year 24 days | Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
Cookie | Duration | Description |
---|---|---|
_hjAbsoluteSessionInProgress | 30 minutes | This is a Hotjar cookie used to detect the first pageview session of a user. |
_hjIncludedInPageviewSample | 2 minutes | This is a Hotjar cookie set to determine if a user is included in the data sampling defined by your site's pageview limit. |
_hjTLDTest | session | This is a Hotjar cookie. Hotjar tries to store the _hjTLDTest cookie for different URL substring alternatives until it fails. Enables Hotjar to try to determine the most generic cookie path to use, instead of page hostname. After this check, the cookie is removed. |
ARRAffinity | This cookie is set by websites that run on Windows Azure cloud platform. The cookie is used to affinitize a client to an instance of an Azure Web App. | |
campaign | 1 day | No description |
content | 1 day | No description |
conversion_page | 1 day | No description |
landing_page | 1 day | No description |
sliguid | 5 years | Salesloft cookie for use in live website tracking to help identify and qualify leads. |
slireg | 7 days | Salesloft cookie for use in live website tracking to help identify and qualify leads. |
slirequested | 5 years | Salesloft cookie for use in live website tracking to help identify and qualify leads. |
source | 1 day | No description |