Connectwise Automate MySQL 8 support is scheduled to arrive in October 2021. This will also introduce formal support for Windows Server 2019 to Automate. Here at Automation Theory, we wanted to clarify what that means for the day-to-day operations for Automate, and how to take
Connectwise Automate Patch 2021.5 was released on May 11, and it contains security fixes for device inventory. It also contains performance issues for large Automate partners. Patch performance woes After applying the 2021.5 patch partners with large servers started to report miscellaneous problems — login
After applying the Connectwise Automate 2021.1 patch, several partners reported different issues, unrelated to the database authentication changes. The symptoms varied from plugins not functioning to certain SQL queries not working, to issues with custom tables, all the way to major application issues. The cause
Automate patch 2021.1 includes major changes to application user authentication and the interactions with MySQL. Below we describe what changed and what Automate administrators need to know. What changed? Previously each user in Automate had a matching user in MySQL with the same password. This
The MySQL 5.6 end of life date is February 5, 2021. Many Connectwise Automate partners are on MySQL 5.6, so here at Automation Theory, we wanted to clarify what that means for the day-to-day operations for Automate, and how to take action. End of Life:
Connectwise Automate leverages Microsoft’s IIS webserver to facilitate application communications. Like other components of the Automate stack, IIS needs proper configuration to perform well under the heavy load of an RMM system. Below you’ll find the core IIS tuning config we use here at Automation
As we begin discussing myths about the Connectwise Automate database, we’d like to go on record and say that most of the published information is wrong or misleading. Databases are extremely complex, and most of the existing tuning or maintenance advise is not holistic in
Restricting access to parties that need it is a core tenant of IT security. As IT professionals, if a client wanted to leave well-known management ports (like 22 for SSH, or 3389 for RDP) accessible from anywhere, even with proper lockout measures, we’d likely explain
