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.]]

Community Reputation

0 Neutral

My Information

  • Agent Count
    1000+

Recent Profile Visitors

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

  1. Anyone know if this is still working in LT12 ? Not able to get it working if it does work. Thanks, Stephen
  2. We just installed LT 12 patch 10 and we are seeing this all the time now. Is there a setting we can change to push the time out longer ? Thanks, Stephen
  3. Automate support finally got back to me and had us install the "Eset Direct Management Plugin" which promptly broke our integration with Automate. That said, it did add the entries and they are working so I thought I would add them. ESET File Security v7 {%-HKLM\SOFTWARE\ESET\ESET+Security\CurrentVersion\Info:InstallDir-%}\ecls.exe {%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ScannerVersion-%} "{%-HKLM\SOFTWARE\ESET\ESET+Security\CurrentVersion\Info:InstallDir-%}\ecmd.exe" /update {%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductType-%}{%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductVersion-%} {%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductType-%}{%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductVersion-%} ekrn* \((20[12]\d[01]\d[0-3]\d)\) Windows ^(efsw7\.*) ESET Endpoint Antivirus v7 {%-HKLM\SOFTWARE\ESET\ESET+Security\CurrentVersion\Info:InstallDir-%}\ecls.exe {%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ScannerVersion-%} "{%-HKLM\SOFTWARE\ESET\ESET+Security\CurrentVersion\Info:InstallDir-%}\ecmd.exe" /update {%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductType-%}{%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductVersion-%} --action=clean --quarantine /files ekrn* \((20[12]\d[01]\d[0-3]\d)\) Windows ^(efsw7\.*) ESET File Security v6 {%-HKLM\SOFTWARE\ESET\ESET+Security\CurrentVersion\Info:InstallDir-%}\ecls.exe {%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ScannerVersion-%} "{%-HKLM\SOFTWARE\ESET\ESET+Security\CurrentVersion\Info:InstallDir-%}\ecmd.exe" /update {%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductType-%}{%-HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info:ProductVersion-%} --action=clean --quarantine /files ekrn* \((20[12]\d[01]\d[0-3]\d)\) Windows ^(efsw6\.*)
  4. Hey All, Looking to see if anyone has the entries for the Virus Scanners section in the Dashboard for Eset 6 and 7 Thanks, Stephen
  5. I see that this is no longer possible... https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/040/010/060 How is everyone else handling this ? Thanks, Stephen
  6. Hey All, Took the plunge into LT 12 today and it looks like all of our old hidden clients are now visible in the company tree. How can we hide these like we could in LT11 ? Thanks, Stephen
  7. I want it to NOT be detected as a server also. The Mac's seem to appear as a server if they have the OSX server app installed Thanks, Stephen
  8. Does it just look at the OS name ? I guess that would make sense... Thanks, Stephen
  9. Is there a way to force Labtech to see the agent as a server instead of just a workstation, aside from installing the Mac Server software package? Thanks, Stephen
  10. Hey All, We are running into an issue with machines running the latest version of OSX (10.13) Apple has enabled a feature blocking apps that touch the kernel (Eset in our case), and make you click a couple buttons to allow it. May not seem like a big deal on the face, but tracking down users and clicking a couple buttons on over 100 machines is going to become a lot of work fairly quickly Her is the Eset and Apple KBs: https://developer.apple.com/library/content/technotes/tn2459/_index.html#//apple_ref/doc/uid/DTS40017658 https://support.eset.com/kb6512/ Eset just told me they don't have a workaround. I wanted to know if you guys have any ideas on getting around this in an automated fashion. Thanks, Stephen
  11. Do you know where LT is deciding what drives are flagged as SSDs (ie scheduled script, backend code,...) ?
  12. We were already on LT11P10 and still had the issue after running the wizard again I worked with Matt Reid in Labtech Dev Support (our ticket # 8686065 for reference) and he was able to get us up and running. It was a combination of DB tables not being created correctly and an IIS redirect issue. Hope this helps
  13. We are still waiting to hear back from Dev on when this will be patched. Anyone else have any updates ?
  14. I would suggest submitting a ticket, that way if it is a Dev fix, you'll be notified when it is patched. Ill let you know if there is a workaround when they get back to me. Thanks, Stephen
  15. Talked to LT and my ticket is being escalated to Development. We were missing a bunch of rows in the DB and it looks like it tried to create the set, but was breaking at some point. This is currently was not a known issue until now Ill follow up when I hear back again Thanks, Stephen
×
×
  • Create New...