Jump to content

srproductmanager

Members
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    2

srproductmanager last won the day on January 14

srproductmanager had the most liked content!

Community Reputation

11 Good

My Information

  • Agent Count
    Less than 100

Recent Profile Visitors

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

  1. srproductmanager

    URGENT - Automate update needed by March 9th 2019

    Update Status: • More than 4,100 partners have completed the full 2019.2 patch since it was released earlier this month • All cloud partner servers have been updated to 2019.2 • We have seen good adoption of hotfixes across all impacted versions since they were released on 2/8/19 • Currently there are no negative support trends related to the 2019.2 release or the hotfixes • New messaging will be sent out today to Automate administrators and primary contacts for partners that are still impacted by this issue We will continue to message impacted partners until all partners have completed the patch. We are tracking all impacted partner instances and have plans in place to push out hotfixes to those that remain unpatched if required. Our goal is to have all partners’ servers resolved by Friday, 2/22/2019. We will continue to use this forum to update you on progress related to this issue.
  2. srproductmanager

    URGENT - Automate update needed by March 9th 2019

    Update status: We have over 800 partners on the full 2019.2 patch since it was released to general availability last Wednesday We will be upgrading all cloud partner instances this week as part of their monthly maintenance window We have seen good adoption of hotfixes across all impacted version since their release last Friday There are no current support trends related to the 2019.2 release or the hotfixes If you have not received an email and are running an impacted version listed above, we do not have a valid Automate Administrator email address for your instance. We recommend that you apply one of the resolutions option above for your server as soon as possible. We are tracking all impacted partner instances and have plans in place to contact and push out patches to those that remain unpatched. Our goal is to have all partners servers resolved by the Friday the 22nd. We will continue to use this forum to update you on progress related to this issue. Sincerely, ConnectWise Automate™ Product Management
  3. srproductmanager

    URGENT - Automate update needed by March 9th 2019

    Hi there, I work for ConnectWise. We have been working to solve an issue discovered by the LabTech Geek/MSP Geek Community Administrators, for the past week. We take this issue seriously and have been working to build and test solutions for all impacted versions. Automate partners on the following versions are affected : • Automate 2019.1 [19.0.1] • Automate version 12 patch 12 [12.0.12] • Automate version 12 patch 11 [12.0.11] An update must be applied to your Automate server that addresses how we handle the transition to our new code signing certificate. Failing to address this issue this month will result in the failure of agent and control center communication. Next Steps: - All Automate cloud partners will be upgraded to 2019.2 next week to resolve this issue. - On premise Automate administrators running impacted versions will be receiving emails today with options to address this issue. If you have additional questions about this issue, we have created a forum to answer and share related questions here. For further critical updates, please visit here and select the Critical Updates tab.
  4. srproductmanager

    Automate Security Issue- Patch 11 and 12

    From a Corporate Level, I have begun working on a resolution to this concern.
  5. srproductmanager

    Automate Security Issue- Patch 11 and 12

    @GeekOfTheSouth , I apologize that your report was not properly escalated. We were able to track your original ticket down and it appears that it was closed waiting on response. The ticket you opened on Thursday has been escalated to T3 support. We are going to pull that directly into development. We take security reports seriously, and I want to make sure they are escalated to development to be handled as soon as possible. On the issue that you are reporting: Our documentation is in error. The file reporting service is purely meant for communication on a single server via localhost or in a split web server installation between the web servers hosted in a DMZ and the Automation Server. In both cases the IIS worker processes communicate via this port to download/upload files from the Automation server. At no time should port 12413/TCP be opened to any other systems just as we recommended that MySQL 3306/TCP is also closed. We have requested that documentation be changed be to avoid other partners configuring their servers in this way. We have verified with our cloud team that instances maintained or created by them have 12413/TCP firewalled. We have verified that implementation documentation does not list 12413/TCP as a required open port for Automate servers. Our architecture team has reviewed the traversal behavior and we are working to address that issue in an upcoming patch. We are also going to separately assess the file service communication to increase security between Web Servers in a DMZ environment and the Automate server for further enhancements. If anyone has open access to 12413/TCP configured to their Automate server, we recommend that it be closed as soon as possible. We are assessing our options internally to identify partners that may have their servers with this port open so we can reach out to them directly. While we failed to get the original ticket escalated due to issues reproducing the problem, Thursday’s ticket was moving through the proper escalation path. Development relies on the reproduction steps generated by T3 as an important requirement to quickly analyze and solve issues. If you feel you are not getting a response please touch base with your Account or Support Manager and they will directly escalate issues to product so we can look into the ticket to get the reproduction steps we need. We also ask that before publically disclosing potential vulnerabilities that you consider the impact on the Automate community of a zero day disclosure.
  6. srproductmanager

    LabTechGeek Updates/Annoucements

    Have you looked into UserEcho?
  7. srproductmanager

    ScreenConnect Integration Mac / Linux

    ScreenConnect/LabTech integration that supports Mac Deployment is currently in Pilot and due to be released soon. The plugin is not bundled with LabTech 10.5, it will actually be released sooner.
  8. srproductmanager

    ScreenConnect split a dual screen session

    All "Stable" versions of ScreenConnect are supported with the LabTech Integration. PLEASE, make sure that you update your LabTech Integration Extension on the ScreenConnect server too. There are typically changes that have been made from version to version, to better support the changes.
  9. The upcoming release of the LabTech/ScreenConnect plugin v1.2 has the functionality to capture the audit data from the ScreenConnect Server. This is information is not yet in a report, but will be available to you as soon as it releases from Pilot.
  10. srproductmanager

    ScreenConnect split a dual screen session

    The LabTech/ScreenConnect integration works with ScreenConnect 5.3. BUT you must update the LabTech Integration Extension on your ScreenConnect Server.
  11. srproductmanager

    ScreenConnect Integration Mac / Linux

    The update to the ScreenConnect integration plugin is due out with LabTech 10.5. It is actually due out much sooner.
  12. srproductmanager

    ScreenConnect Integration Mac / Linux

    It's Coming... http://www.labtechsoftware.com/roadmap.php The next phase of the ScreenConnect plug-in includes support for Mac agents, enhanced deployment options to exclude by client, location or computer, and the ability to upgrade the ScreenConnect server when new versions are released.
  13. srproductmanager

    ScreenConnect / exclude several systems

    It's Coming... http://www.labtechsoftware.com/roadmap.php The next phase of the ScreenConnect plug-in includes support for Mac agents, enhanced deployment options to exclude by client, location or computer, and the ability to upgrade the ScreenConnect server when new versions are released.
  14. srproductmanager

    ScreenConnect / exclude several systems

    If you upgrade your ScreenConnect server the agents don't automatically upgrade. This will allow you to Auto-Update your ScreenConnect Agents 1. The 'web.config' is created upon installation. 2. File Location on the ScreenConnect Server- C:\Program Files (x86)\ScreenConnect\ 3. The following key can be updated (Change from FALSE to TRUE) i.
  15. srproductmanager

    ConnectWise aquires ScreenConnect

    There are 3 webinars on Thursday that will demo the full integration that is being released with LabTech 10 Register Here - http://www.labtechsoftware.com/webinars.php
×