{"id":9921,"date":"2026-09-16T22:07:31","date_gmt":"2026-09-16T22:07:31","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=9921"},"modified":"2026-09-16T22:07:32","modified_gmt":"2026-09-16T22:07:32","slug":"connectwise-monitors-resetting-after-updating-ignite-to-current-in-solution-center","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/connectwise-monitors-resetting-after-updating-ignite-to-current-in-solution-center","title":{"rendered":"Connectwise Monitors Resetting after Updating “Ignite to Current” in Solution Center"},"content":{"rendered":"\n

Below is the advice given by connectwise support.<\/p>\n\n\n\n

Key Points Provided:<\/p>\n\n\n\n

    \n
  1. Basically rather than deleting monitors we don\u2019t care about we should \u00a0be disabling them instead<\/li>\n\n\n\n
  2. If we make changes to any of them then yes they will default back when Insight isupdated in solution management. There advice is to export each of the ones changed to a xml file and import them back in.<\/li>\n<\/ol>\n\n\n\n

    AI has provided a better option that I will implement

    A Safer Alternative: The “Duplicate” Strategy<\/strong><\/p>\n\n\n\n

    Instead of just backing them up, a common practice among Automate administrators is to\u00a0duplicate the monitor<\/strong>\u00a0and rename it with a custom prefix (e.g., Company – [Monitor Name]). You can then disable the default Insight monitor. When the Insight solution updates, it will update its own disabled monitor but will leave your custom, renamed duplicate completely untouched.



    When updating “Ignite to Current” in Solution Center, whatever item is listed as “Local Changes” is an item that was customized by a user. Therefor, after the update, those changes will revert back to the latest default settings. It is always recommended to copy a monitor or script before making changes so that you do not lose your customizations.<\/p>\n\n\n\n

    Additionally, we do not recommend deleting any default monitors. If a default monitor is not required for your environment, the recommended approach is to disable it rather than deleting it. This helps maintain the integrity of the default monitoring configuration and avoids any potential issues in the future.

    Here is a way to take back up of monitors and scripts :<\/p>\n\n\n\n

    ConnectWise Automate offers several export options in various areas.??<\/p>\n\n\n\n

    Back up a specific monitor<\/p>\n\n\n\n

      \n
    1. Open ConnectWise Automate Control Center.<\/li>\n\n\n\n
    2. Navigate to Automation ? Monitors.<\/li>\n\n\n\n
    3. Select the monitor you want to back up.<\/li>\n\n\n\n
    4. Right-click the monitor.<\/li>\n\n\n\n
    5. Choose Export.<\/li>\n\n\n\n
    6. Save the exported file (.xml) to a secure location.<\/li>\n<\/ol>\n\n\n\n

      To import From the Control Center, select System > General > Import > XML Expansion.<\/p>\n\n\n\n

      Similarly Scripts can be exported as XML files and imported into other Automate instances. Please refer to Export and Import Scripts in ConnectWise Automate<\/a><\/p>\n\n\n\n


      <\/p>\n\n\n\n

      <\/p>\n","protected":false},"excerpt":{"rendered":"

      Below is the advice given by connectwise support. Key Points Provided: AI has provided a better option that I will implementA Safer Alternative: The “Duplicate” Strategy Instead […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-9921","post","type-post","status-publish","format-standard","hentry","category-research"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t