Jump to content

Search the Community

Showing results for tags 'symantec'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • Announcements
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development

Categories

  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 4 results

  1. Hey Guys, So for the last 2 years, we've had to put up with SEPC (Symantec Endpoint Protection Cloud - not to be mixed with SEP, SEP SBE or Symantec Cloud) and their BS. I now can finally move away from their product after being given the green light by the directors.. Except heres the catch. All my research shows that everyone is having the same drama.. that SEPC will NOT allow you to do any un-attended or silent removal away from their rubbish product. You can see everyone else who has this product taking their disapproval out on reddit here and here. It's been the worst product since deployment, but has now been announced that they will no longer sell (even exsisting licences/tenants) and are being forced to migrate to SES, shown in this article from Boardcom. Making matters worse, Broadcom don't respond to support emails, their portal is trash and it's the absolute worst timing because of COVID-19. Over the last 6 months, I have searched for scripts, programs, 3rd party tools and nothing has worked to remove SEPC un-attended.. these scripts have worked on other Symantec products but we've been un-successful in modifying it to suit SEPC. So if anyone has an answer where it be script/program/anything to help me out, that would be awesome.. otherwise i'll be needing to manually uninstall SEPC on around 5, 000 devices.. and don't even get me started on what that'll look like. Cheers Guys.
  2. Has anyone had any luck with this since the updates to Cloud Protection Agent. I had a script that ran SEPPrep.exe with the RemoveSymantec=Y option, but that no longer seems to work. None of the msexec methods or wmi methods seem to work either. Any ideas?
  3. Despite using the ConnectWise atricles provided by the support team, I am unable to get Automate to detect Symantec.Cloud 22.14.2.13 is installed on workstations. I have created a new definition in System Dashboard>Configuration>Virus Scan as per the screenshot, but this has not resolved the issue. Can anyone advise if I need to make additional changes. Thanks
  4. Hi all,We us Symantec Endpoint Cloud is our Labtech environment. I have previously reached out to Labtech support (years ago) to set up a customized template. AS the versions have changed, I have updated the templates without any issues. Now I am seeing problems with some systems detecting Symantec cloud version 22.9.3.13 on windows 7 64 bit systems. I have reached out to Connectwise Automate support and I was promptly told they do not support customized templates, which was amazing to me since the tech that helped me remoted into our server to set it up originally. Needless to say the support was no help. So now I am stuck with this challenge. These are the templates I have setup:A.) Program Location: C:\Program Files\Symantec.cloud\EndpointProtectionAgent\Endpoint Protection.cloud\Engine\22.9.3.13\NIS.exeDefinition Location: %ProgramFiles%\Symantec.cloud\EndpointProtectionAgent\NortonData\22.9.3.13\Definitions\AntiSpamDefs\definfo.datB.) Program Location: %ProgramFiles%\Symantec.cloud\EndpointProtectionAgent\Engine\22.9.3.13\NIS.exeDefinition Location: %ProgramFiles%\Symantec.cloud\EndpointProtectionAgent\NortonData\22.9.3.13\Definitions\AntiSpamDefs\definfo.datC.) Program location: %Program Files%\Symantec.cloud\EndpointProtectionAgent\Endpoint Protection.cloud\Engine\22.9.3.13\Nis.exeDefinition Location: %ProgramFiles%\Symantec.cloud\EndpointProtectionAgent\NortonData\22.9.3.13\Definitions\VirusDefs\definfo.datThe directories are varied across systems. I have verified that some systems have created duplicate directories within Symantec.cloud folder. I assumed this happened during the big update last year. On one of the affected machines, I ran the dir cmd and pulled the location right from there. The problem is Labtech still is not detecting the software. The only difference I see is that there is a space in the bolded directories. Would this matter? I'm really banging my head on the wall with this one. Any help would be great, since support is less supportive of issues these days.
×
×
  • Create New...