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

SteveYates last won the day on October 24 2018

SteveYates had the most liked content!

Community Reputation

2 Neutral

My Information

  • Agent Count
    < 500 Agents

Recent Profile Visitors

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

  1. I'd wondered that also and looked at ours at the time. As I recall now we are on 5.6.39 and 5.6.x is supported. I wonder if maybe it was trying to create the same trigger twice and errored out, and the message is not really the cause? Anyway, we didn't have issues with 2019.7.
  2. If the probe is correctly set up to use valid credentials then this isn't necessary. The probe push basically doesn't work on workgroups unless you jump through a few hoops to allow the remote connection on each PC. It usually works on a domain. The probe push connects with the supplied credentials and runs psexec on the remote PC.
  3. Oh I know about the agent running as localsystem (should have clarifed that...I was looking at the comment about the env var and the ones being discussed). Nice you found a PS solution, I'll have to remember that. I was just confused from the OP why the profile dir is necessary at all, based on the stated goal. I would think Console Shell or Console Execute script functions should work to read the user's env var? (haven't tried)
  4. We never had issues until we installed the "Windows Defender 10" config from the updated solution this spring, and since then it seems like it takes overnight for PCs to correctly detect Bitdefender GZ is installed and running, despite the process/def file/etc being correct. Until then it detects Defender 10 with the service not running, because duh it shouldn't be. There are also problems with the Defender 10 config, but support says Defender isn't supported (https://product.connectwise.com/communities/5/topics/14284-fix-windows-defender-10-antivirus-definition). You can always delete virus configs from the Dashboard...? In direct answer to your question I don't know if there is a way to force one detection over the other, for instance if it goes "in order" somehow and stops at the first detected.
  5. Windows has a %USERPROFILE% env var. To elaborate a bit, the directory gets named to be unique so if the directory already existed for whatever reason (local user same name) it could be user.domain, user.001, etc. Perhaps I'm misunderstanding but can't you transfer it to %windir%\temp, the default location, and then move it where you want it?
  6. It does seem silly to have combined the "enable deployment" and password and auto-push options, as for years we manually pushed with the probe if desired. However it looks like the docs have changed a bit since I last read them? (or I missed this) https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/090/080/120/100 has an "Agent Deployment Attempts" setting that can be set at zero...does that mean if set to zero it will not auto-push?
  7. There's another one: https://www.dell.com/support/article/in/en/inbsd1/sln317291/dsa-2019-084-dell-supportassist-for-business-pcs-and-dell-supportassist-for-home-pcs-security-update-for-pc-doctor-vulnerability?lang=en https://safebreach.com/Post/OEM-Software-Puts-Multiple-Laptops-At-Risk
  8. I know this is an old thread but just for posterity I'm pretty sure this "Symantec Corporate 14" definition existed from many years ago, back before there was a version 14. I recall pointing that out to them at the time...
  9. See the May 8 solution center update: https://university.connectwise.com/university/pageview.aspx?short_name=solution-center-release-notes
  10. Do you mean SEPC (Endpoint Protection Cloud), vs. Symantec.cloud aka Small Business? Per support one has to run the uninstaller manually, on the PC, and the help doc that says one can do it from the portal is incorrect. Would really like a way to remotely uninstall, because of: https://www.symantec.com/connect/forums/no-alerts-invalid-licensesdisabled-antivirus
  11. I asked support a while back about SC agents not self-updating. The answer: "You can update clients Automatically through the Integration settings. If you go to System>Configuration>Dashboard>Config Tab>Integration Tab>Connectwise Control. Then click on "Control Server Settings" to open the Settings Editor. Then scroll to find the setting "AutoReinstallOldVersionClient" and make sure that check box is selected. Once that's done just click "Save" and the clients should start updating automatically after the Control services restart. If you want to do it manually the best thing is to use the "Reinstall" command on each client." From the bottom of page https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/080/020/020/020 it sounds like redeploy is for when someone removes (Ends) it in SC?
  12. Are the files being quarantined by a/v? We've had no such issues with probes and have run them for years. Have a handful on the new probe.
  13. Windows PCs need the latest servicing stack update (SSU) to see patches released later...see if it's missing one of those? If it is missing the PC won't see updates. run Windows Update on the server and see if it sees that update and/or installs an SSU first.
  14. You might check your CWA server's firewall/router. Long ago when starting out we had a lower end router that could not handle "n" simultaneous connections. The sporadic connections got progressively worse as we added agents. For instance does it get better at night when PCs turn off? Sometimes it's more subtle, for instance with some advice from others I got AT&T to confirm the router they supply with their AT&T Business Fiber can't handle a high number of connections (forget the number exactly), so even if we have our own behind it, it would be a problem.
  15. Two people on Reddit are saying the latest version of the Control plugin, or reinstalling the Control plugin, fixes this...
  • Create New...