Jump to content

Search the Community

Showing results for tags 'migration'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development

Categories

  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 4 results

  1. A couple years ago I worked with a CW consultant who mentioned a "core-only" migration of Automate -- that is moving over only the tables needed to make the application run. I couldn't find the list of tables posted anywhere, so I wanted to post them here. Please note that there's an awful lot of items missing here (think of this like a "reset my server, keep my agents and users" measure). I'd advise anyone thinking about this that groups, scripts, monitors, searches, EDFs, and Connectwise Control are all missing. So too are all the tables for Patch Manager -- so with that, most partners
  2. Hi Everyone, Since ConnectWise no longer supports MariaDB I've created a guide to help partners migrate to MySQL. The vendor provided documentation involves a long and convoluted logical backup process that can be avoided. This guide is the fastest method of upgrading to MySQL while allowing 100% ability to revert back in case of failure (since we'll be leaving MariaDB intact). Before we go any further please note that you can farm out this task if you want to focus on automation and not database administration: https://automationtheory.org/product/mysql-patching/
  3. Just wanted to see if anyone would have any experience to offer or opinions on this. We are working to setup a new on-prem server to be our new Automate Server. We currently have an on-prem Automate server but just working to move it to a more robust and better server than where it currently sits. We were thinking to have a split server setup where we would set the application server in the DMZ and then have the database server in our main production network in hopes to increase the security by placing the publicly accessible items in a DMZ and to keep the database more protected. As we ha
  4. CW Automate Database Migration Guide I recently performed a successful database migration for our org to a new server with higher specs. I spent some time with CW consulting before the migration, reviewing the new server base install and working through some of the initial issues there (like making sure all our connectors really ARE the right version, and dropping the default anonymous MySQL user). They also gave me some pointers for the actual database migration process which are not in the CW documentation. This guide is not a replacement for proper consulting. If you don't know what th
×
×
  • Create New...