If you’re reading this article, you’re likely considering a switch to ConnectWise RMM as your Remote Monitoring and Management tool. Or you’ve already made the change and need help with planning/implementation. This article should help with a plan to complete a ConnectWise RMM migration. This article will focus on what items need to be considered for setup in CW RMM/Asio.
Inventory and Agent Deployment
To ensure a successful agent migration it’s essential to have a plan for how to deploy the agents appropriately. If the current RMM is still operational, we can leverage that for the agent installation. Note: If you have ConnectWise Automate, there is a migration tool that CW can provide for client/location/agent migration.
If the RMM no longer exists, then we’ll likely want to approach agent installation from InTune/Group Policy or using the RMM Scanning tool. This article from ConnectWise outlines how to get the agent installers and site tokens for the installs. It also holds some details about creating Group Policy deployment.
Creating Functionality
Depending on the previous tool that was in use, ConnectWise RMM can be very different. Understanding the approach in CW RMM will make things go more smoothly. Even if both tools are RMMs, they may approach solutions in different ways.
ConnectWise RMM is more modern and is originally configured as more of a “done for you” tool. Depending on the previous system in use, there can be some large differences in the approach to creating 1:1 parity in CW RMM.
There may be some items that will simply not be possible at this time. There are some items where you might need to get creative! But the bottom line is that most RMMs can accomplish 80-90% of the same functionality as other RMMs. Here are the items to consider when creating parity between the two systems.
Monitoring
ConnectWise RMM comes with a rather robust Intelligent Monitoring system – Intellimon. This system helps apply monitors to devices based on information about the device. This is essentially role-based monitoring. For example: a SQL server is going to have their SQL Server Services monitored automatically. Please review your current RMM monitoring configuration to compare the two systems.
In ProVal’s experience, most partners have not had a lot of trouble with CW RMM monitoring. It seems to work quite well out of the box. Thanks to this, the real goal is to find the client specific monitors that might not be standardized, things like specific line of business apps, or specific services that need to be running. These are where the custom monitors will be a huge help.
Scripting
Scripts/Tasks are there to help make life easier for technicians and to apply automation where possible. CW RMM has many task templates that can help technicians and admins create standardized Automation. For example, many MSPs like to set up power profiles for endpoints.
There is a template for that in CW RMM that will allow for the creation of power profiles. The same template can be saved for future use for a “standardized” power plan. It is best to review the scripts in use in the old RMM environment if possible. Also great to note down if there are any automated fixes tied to that monitor.
Patching
Windows Patching is a key component of almost all RMM systems. All RMMs have their own individual settings and abilities, and CW RMM is no exception. However, at the end of the day, it is still administrating the Windows Update Agent settings on devices. Not actively installing patches itself. Just instructing Windows Update on what it can install and when it can take actions.
Thus, patch install policies are similar enough between systems. Pick a time (or immediate) for install and pick a time/prompt the user for reboots on workstations. Servers can patch and reboot similar between the old RMM and CW RMM. Usually, weekly installs and reboots work fine for servers. Not all RMMs require approval and denial of patches for deployment. Generally, we believe that if Windows determines a system needs a patch, the system should likely install it. If the patch doesn’t cause any machine/client level issues. It can deploy to all devices.
A patch should only be denied if it causes issues for the user/client. Please note that in CW RMM the ConnectWise NOC team tests and approves security/critical updates only. All other patches will be the MSP’s responsibility to approve/deny. You can set up the policies to deploy all patches, but we don’t generally recommend this because Microsoft patches can sometimes be buggy.
Tip: In CW RMM watch out for the default filter timing. You may be missing older, unapproved patches!
Three large advantages for CW RMM are the ability to deploy OSX patches and upgrades, as well as deploy Windows feature updates and upgrades. Consider these features when setting up the new system. While this might go beyond achieving parity, it’s important to ensure devices are updated to the latest available version of Windows.
Reporting
In CW RMM there are a few inbuilt reports, but the real benefit comes from the integrated BrightGauge instance. If you’ve had BrightGauge in the past, you will likely need to rebuild gauges similar to the previous RMM. For example, there are many differences between CW Automate and C WRMM datasets. They all pull similar information, but it is by no means 1:1. Many of the default gauges will already offer some parity between RMMs, but you will likely need to customize the system to restore normal functionality.
Integrations
ConnectWise RMM is still a newer player in the game and does not have the same amount of integrations as some other RMMs. This is changing as more and more developers adopt the Asio/CW RMM platform. It’s important to review your current integrations and see what is available in CW RMM for the tools that the MSP is leveraging. Don’t forget, some integrations might work in other CW systems as well if it is not available for CW RMM today. Our thought process is that if a connection is possible, it’s likely a good idea to make it.
One large item to consider is ticket routing. Are you planning to use the CW RMM ticketing system? Will these tickets integrate into another PSA system like ConnectWise or Autotask? Proper PSA integration is one of the most critical aspects to ensure a smooth connection with CW RMM.
Training
Once the system has been configured and the agents have been migrated. It’s important the MSP techs/team know how to use the product properly. ConnectWise has great training videos that can help as well as some university courses that will give users an overview of the RMM. We recommend working through the CW University learning plans related to CW RMM.
To see CW RMM specific training, change the category to Unified Monitoring and Management > RMM. The ConnectWise RMM Onboarding learning plan will give everyone an overview of the system and how to leverage it properly. (You’ll need access to ConnectWise university for the links to work!) This plan is more geared towards administrators of CW RMM, but understanding the approach should help technicians better leverage CW RMM.
Summary
RMM tools are very useful and can benefit any technology business so long as the tool is leveraged properly. To summarize the ConnectWise RMM migration plan above:
- Agent Migration
- Use the old RMM to push agents if available, or leverage Group Policy/RMM Scanning Tool/ other tools to deploy agents.
- System Parity
- Monitoring
- Scripting
- Patching
- Reporting
- Integrations
- Training
- Ensure the team can use the new tool
Have you migrated recently? Any gotchas or tips that you want to share on Connectwise RMM migration? Please post them in the comment area below.
Contact us today if you’re needing assistance with ConnectWise RMM migration today! Thank you for reading!
