Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

KI_EricS last won the day on November 29 2018

KI_EricS had the most liked content!

Community Reputation

1 Neutral

My Information

  • Agent Count
    4000 - 6000 Agents

Recent Profile Visitors

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

  1. We updated from 2019.3 to 2019.5 this past weekend. What happened: What was learned: Possible network performance/stability issues aside, LT Support identified the LT -side problem as being caused by User Permissions issues. Apparently, there were quite a few security-related changes made in 2019.4 and/or 2019.5 which were involved here. LT used to "tolerate" what I've called "ugly permissions": multiple User Classes assigned, sometimes with over-lapping Permissions and even including 'Super Admin' thrown in. Used to be you'd have performance issues due to LT having to sort that mess out. Now LT will kick a user to the curb. The biggie was having more than one User Class assigned that has the 'Super Admin' Permission, though I wouldn't rule out other Permissions as possible causes of either logon issues, or Control Center performance or functional issues.
  2. Is there a minimum required (or recommended) version of ScreenConnect/Control (Server/Access Agent) and/or the related LabTech/Automate Plugin in order to use the "Use Control to Update your Automate Remote Agents" Utility? Also, does ConnectWise have that utility "published" any where on their website? (Didn't see such a link in that Announcement.)
  3. @imurphyHow does your solution handle situations where the font is already present? Are you doing anything else in your LT Script to handle that? Also, please see my recent post in a similar topic.
  4. Not exactly from what I've seen while working on a similar task myself. Apparently there is a Windows Registry item that needs to be created along with each font (not font family) installed to actually register the font with the system. Here are two (external) sites that I'm currently referencing for my work: How to: Deploy New Fonts via GPO Pushing Fonts via GPO I'm leaning towards adapting this PowerShell script to being run from a LT Script.
  5. I've often wondered about how well that'd work, if at all... I have questioned LT Support within the last few months about the Share and/or NTFS file permissions that are needed for LTShare and the FileService to function properly. And they insisted those permissions (both types) need to be set to "Everyone" ("Full Control") for it all to function as intended. Needless to say, I have a fundamental problem with that being necessary. We were told by LT Consulting after FileService was deployed that the only users who might actually need to have LTShare mapped on their workstations are those who are doing system administration/development work such as writing scripts, reports, etc. (I have not tested that myself yet.) Manual human access of LTShare aside, what are the minimum permissions needed for the FileService, a local installation of the Control Center ("thick client"), LT Agents, Web Control Center, etc, and which system entities (by default) need any access whatsoever to LTShare? On a somewhat related note... Can we hide the LTShare network share without it hosing LT?
  6. @bmillerWhat is the configuration of that Alert Template? Also, is this related to a plugin, or is it purely custom work?
  7. I believe that is either set, or influenced by settings, on the Dashboard. One thing though, you need to check if there are any restrictions/limitations that will be imposed by any other applications you have integrated with LT.
  8. That sounds like some of the issues we've been experiencing as of late (Version 12 Patch 10; 4600+ Agents; Split Server). That's been attributed to an issue with the new(er/ish?) CWA File Service. Definitely need to check the permissions (share+NTFS) on your LTShare. I personally did not like having to do it, but I did have to. as per Support, grant 'Everyone' "full access" share permissions and open up the NTFS permissions likewise. I do not blame LT/CWA Support for having to do that, however I do blame Dev for apparently leaving us to have to use such loose permissions. We've been having other issues with v10 too and are looking into updating to v12 as several of those issues are supposedly resolved by that patch.
  9. @SparkerThe first (oldest) reply/comment might be of interest to you.
  10. I didn't find this here earlier and ended up contacting Support about it, but props to @svc_root for posting a solution for this issue first. However, allow me to elaborate on this matter... Affects: LabTech/Automate Control Center version 12 patches 9 and 10 Possible Symptoms: Users unable to log into the Control Center. Users already logged into the 'Control Center may suddenly begin experiencing "never-ending" refreshes of data and/or will be unable to effectively interact with the application. The Control Center may suddenly "crash"/exit/quit. Issues occur during certain time frames, usually reoccurring and possibly multiple times of day. Users across multiple time zones may experience issues during time frames that will resolve to the same UTC times. May not affect all users in a given time zone, or any users in a specific time zone. For us a confirmed "dead time" resolved back to 1700 to 1900 hours (CST, UTC-6) every day, with another reported time frame ending at 0700 hours (CST, UTC-6) at least on week days. [There are also messages in two logs (one client-side, one server-side) that will correlate and basically confirm the problem. Will edit in that info soon-ish.] Here's what LT Support had me do to resolve: What didn't get mentioned there was that restarting the LT Database Agent is needed to effect that change.
  11. What version of LabTech/Automate are you using? 😕 You shouldn't have to write a script for something like that. You should only have to set up the appropriate Policy/Group in the "new" Patch Manager, and/or set up a formal Maintenance Window. 'Patch Manager' 'Upgrade to the New Patch Manager' 'Configuration Screen' > 'Microsoft Update Policy Section' 'Maintenance Windows' However, I think that you can put a Computer/Location/Client into a temporary Maintenance Mode (and later clear it) in a script.
  12. I've looked into using Caching for very similar reasons to yourself: we have smaller, "bandwidth-challenged" customers and this could help with managing our tools' impact upon their business-hours use of the Internet, specifically, and network performance, overall. At one point I took that documentation to mean that LT expects there to be a preexisting, uniform drive mapping for it to use. Of course, I had also interpreted that documentation to exclude the use of proper FQDN's which our CWA consultant has since told us that is not the case. Regardless, there are three things I would start looking at: File-sharing configurations on both points A and Z, and possibly in-between User account (and maybe computer account) access and file permissions Consider the CWA KB article titled "Agent Failed to Login as User"
  13. Could this be related to the setting in the System Dashboard called "Disable timezone compensation in control center"? Configuring the Control Center > "System Options" section Lately I've been looking into how that global setting (and similar, more localized options) work and am about to contact CWA Support or our CWA consultant about it. We have customers coast-to-coast as well as technicians/engineers, and both the NOCs are in different timezones. And our CWA server is in EST/EDT. However, someone enabled that option and I've begun to wonder if some of our over-all system performance/behavior issues could be related to that setting. Also, timestamping behavior and displaying times within the 'Control Center is inconsistent and flat-out screwed up. Being left to wonder (at times) what time zone a given date/time stamp is from within the 'Control Center is bad enough, but having that uncertainty while reviewing an audit trial/log... I have been able to conclusively demonstrate those issues to our CW Automate consultant within the last few months (CWA/LT v12p06). I thought that he was going to direct that over to dev and need to follow-up with him on it.
  14. I realize this topic is old, but I'm going to post these two links here for consideration anyways: Malwarebytes Anti-Malware Deployment Issues Malwarebytes Anti-Exploit Deployment Issues
  15. We have been experiencing this issue as well for at least a week, but only on a limited number of managed hosts. I have an observation and an additional theory: Observation: Not all of our LT Agents are applying the 'Use Default' policy when set at the Client level for some reason. This issue is further complicated by a probable bug involving how a LT Agent's MalwareBytes Policy is being displayed/reported in different places in the LabTech Control Center. Theory: The value is being reverted by, or due to, the "new" LabTech Patch Manager or *possibly* our LT integrated Webroot SecureAnywhere software. While it is possible that WRSA is recognizing that LT is managing that Registry Key and is attempting to protect/preserve what LT says it should be, I think that it is more likely the LT Agent is responsible for that value flipping. Adding that Registry Key information to the Global Ignore List in the Dashboard's MalwareBytes console seems to help. However, you have to try to ensure the LT Agent receives the correct policy information before you can completely resolve the situation on a host-by-host basis. (Which has been painful to do so far.) Using: ConnectWise Automate (LabTech) version 12 patch 1 (12.0.256) MalwareBytes Plugin (Malwarebytes.dll) version MalwareBytes Remote Agent (MalwarebytesAgent.dll) version Webroot SecureAnywhere with Unity (Webroot.dll) version 3.0.162x Webroot SecureAnywhere with Unity RA (Webroot_remote.dll) version 3.0.162x MalwareBytes Blog: PUM.Optional.DisabledSecurityCenter An older, but still informative, forum discussion on this general subject
  • Create New...