What exactly is the problem?
One of the DLLs critical to encryption in the affected versions has a bug that means on the 9th of March it will stop working, subsequently taking all services that rely on it with it (Control Center/Agent/Automate Server).
How can I tell if I am affected? Step 1 - Check your server version
In your Automate Control Center, go into Help and go into About. You want to pay attention to the Current Control Center, Automation Server, Web Server and Remote Agent versions. The following versions are affected:
Automate 12 Patch 11 - 12.0.474 (AKA 126.96.36.1994)
Automate 12 Patch 12 - 12.0.496 (AKA 188.8.131.526)
Automate 2019 Patch 1 - 19.0.37 (AKA 184.108.40.206)
If you are on Automate 12 Patch 10 or below you remain unaffected and need to do nothing else.
Step 2 - Check your Automate Agent versions This is the version of Automate that gets installed on your Windows endpoints. Mac and Linux agents are not affected. Even if you install the latest Automate patch, unless you make sure the agents are updated too you will still lose agents.
In your Automate Control Center, go into Automate then Dataviews. Go in the Status folder and open Agent Status. Pay attention to page size and total in the top right. We recommend upping the page size to view all agents. You can see the current agent installed version in the Agent Version column. You can use the dropdown above the Agent Version column header to see what unique agent versions you have.
Any Windows agent in this Dataview on version 120.474, 120.496 or 190.37 by March the 9th will be permanently lost and will require a reinstall
For those of you who prefer an SQL method (please note this query won't be accurate AFTER patching unless you do the full patch)
SELECT `name` AS ComputerName,clientname,locationname,computers.computerid,serviceversion,lastcontact,IF((LastContact > DATE_ADD(NOW(), INTERVAL - 15 MINUTE)),"ONLINE","OFFLINE") AS AgentStatus FROM computers INNER JOIN v_xr_computers ON computers.computerid = v_xr_computers.computerid WHERE serviceversion > 120.451 AND serviceversion < 190.58
How do I fix this? Step 1 - Update or Patch your Automate Server
Install a full upgrade to Automate 19 Patch 2 - (Please see your product dashboard on ConnectWise University) (this is the option the majority of the MSPGeek Admin team chose)
Install a patch, without upgrading your version if you're on Automate 19 Patch 1 - (We will post this link when we get it)
Install a patch, without upgrading your version if you're on Automate 12 Patch 12 - (We will post this link when we get it)
Install a patch, without upgrading your version if you're on Automate 12 Patch 11 - (We will post this link when we get it)
Step 2 - Update your agents You can force an update on an agent basis by going into Commands > LabTech > Force remote to Update. We highly recommend though Darren White's excellent internal monitor available here https://www.mspgeek.com/files/file/45-cwa-agent-version-update-monitor/ . To import this, go to Systems > General > Import > SQL and that's all you need to do. The agent update process is cleverly embedded within the monitor, and it will do it in a staged way depending on how big your environment is.
I am on Hosted/Cloud Automate, does this still affect me?
Absolutely - we suggest that you contact support and ask for your instance to be updated ASAP.
What do I do next?
Continue to monitor your agent versions and ensure that affected versions gradually decrease. Get your clients to turn on machines that haven't been on for a few weeks.
Where can I get further help/discuss this further?
We have created a channel called #dday in Slack for discussion specifically relating to this.