Jump to content

ITGuyFromIA

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Location
    Iowa
  • Agent Count
    < 500 Agents

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. How did this end up turning out for you? We are also a Dell shop and I am just revisiting hardware monitoring after VMWare/Dell broke the ability for ESXi to see / report on disk status with 6.7.0
  2. First forum post for me (I've posted in the Slack channel once or twice). We are running ConnectWise Mange v2018.4 and Automate v12.0.327 (Patch 5). The integration was never performed between these two products (the reason why is no longer with the company). It has been tasked to me to get these integrated and our Automation up and running. We have been using CW Manage as our daily-driver for roughly 4 years. We have been using Automate about the same length of time. We have played around in Automate, but there is nothing of true significance there. The main function Automate plays for us is the ScreenConnect side of things. One of the things that has kept my company from performing this integration in the past is trepidation with regards to the potential flood of tickets. We have been discussing what options we have and have come up with the three following options: 1) ConnectWise Manage/Automate “Current” a. Clear and disable all monitors that will create tickets in Automate b. Clean up old client accounts i. Automate has quite a few old clients that were not offboarded properly c. Clean up unwanted agents d. Create new monitoring and provisioning settings in Automate i. Connect Automate clients to Manage clients ii. Map them via integration setup Notes: This will leave us with some possible monitoring and/or ticket creation in Automate (ticket explosion in Manage) as it would be easy to miss a client or monitor rule 2) ConnectWise Manage/Automate “Clean” a. Uninstall all Automate Agents. i. Leave all ScreenConnect agents installed. ii. Document what Agents we will want to reinstall in the end b. Purge all clients and locations in Automate i. Need input on how to achieve this c. Integrate Manage and Automate. i. This will allow all client names to be imported and match d. Fix password structure on Manage side i. We are currently storing our passwords in a “wall of text” in the notes field of Manage Configurations. This needs to change (working on a solution) e. Create monitoring and provisioning settings f. Reinstall Agents identified in first step and reinstall through ScreenConnect Notes: This would be the least likely option to cause unplanned tickets or alerts. Would also provide Client name consistency. Also, we would have the ability to better control the deployment/provisioning of all clients going forward as we can crate a series of client types for monitoring and control all installs from the start. 3) ConnectWise Manage/Automate “Hybrid” Would need to check into this option – but maybe we can just ignore all current data in Automate a. Clear and disable all monitors in Automate b. Integrate Manage and Automate i. This will allow client names to be imported (NOT mapped) ii. Leave ALL old clients alone. c. Ignore the current clients and locations d. Fix password structure on Manage side i. Same as item D in 2 e. Create new monitoring and provisioning settings f. Move all the current agents to the imported clients and locations Notes: This would need to be researched more if this is what we decide to go with. Downsides are the same as option 1 “Current”. Could also have an issue where the import syncs bad data (from ‘ignored’ clients) back into Manage. We are heavily leaning towards option 2 as we feel we would have the most control to: minimize our chances of a ticket flood, control the names of clients as they are imported, minimize labor involved with the cleanup/integration. I'm brand new to the world of Automate, and this will be my first step (of many) to get our Automation up and running. What I'm looking for is any input any of you would have before we pull the trigger on this. Thanks in advance.
×
×
  • Create New...