Jump to content

SteveYates

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    1

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 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...
  2. See the May 8 solution center update: https://university.connectwise.com/university/pageview.aspx?short_name=solution-center-release-notes
  3. SteveYates

    Script to remove Symantec Cloud

    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
  4. SteveYates

    Patch 2019.3

    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?
  5. SteveYates

    Probe Causing System Files Missing ?

    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.
  6. SteveYates

    Inconsistant Patching

    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.
  7. 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.
  8. SteveYates

    Patch 2019.3

    Two people on Reddit are saying the latest version of the Control plugin, or reinstalling the Control plugin, fixes this...
  9. SteveYates

    Pushing Windows Updates

    CW has a script for this: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Scripting%3A_Windows_10_Install_Feature_Update_Script Looks like they updated the page and it's a Solution now? The concept from what we had drawn from, there and elsewhere, was to download the iso, mount (via PowerShell) or extract it, and run setup.exe /auto upgrade /quiet. That works but since it's in the background the PC will reboot with no warning to the user after an hour or so whenever the FU finishes installing. A subtle thing is you'll need to download each .iso file when they come out because after the next version is out MS only lets you download the latest.
  10. SteveYates

    Automate - Patch Upgrade Guide

    We are on v12 patch 12 (12.0.12.496). As of tonight, https://university.connectwise.com/university/AutomateResources/ProductsAndUpdates.aspx doesn't show 2019.2 yet for us but does show a new patch 12 (12.0.12.497). Presumably that's the hotfix mentioned at https://forums.connectwise.com/community/automate_hotfixes/f/automate-hotfixes-forum/43420/please-take-action-on-your-automate-server .
  11. SteveYates

    Automate Client Constant Crash

    Perhaps try uninstalling and reinstalling. To do so remotely via CW Control command line (in the Control web portal): https://www.reddit.com/r/labtech/comments/9qfncx/agents_stuck_executing_after_v12_patch_10/
  12. I asked support but figured I'd post here also. In the Gen 2 probe it looks like there is only one checkbox, Enable Remote Agent Deployment. The docs at https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/175/120/030 say it will try to install the agent when a PC is next scanned. Is there any way to allow (only) the manual push via password (commands/probe/deploy Automate agents) or has that essentially been removed in favor of automatic push? We have typically either manually pushed, or set up a domain login script to install the agent if we want it automatic. That way it isn't trying to install on any other devices on the network, third party PCs, etc. Edit: Disregard my question. I was pointed to Deployment Manager. I had seen Deployment Manager a while back and then totally forgot about it since it essentially duplicated the probe feature. Interesting it still refers to its settings as “probe” which is apparently not related to the gen 2 probe.
  13. SteveYates

    Automate, slow?

    In ...the poster suggested raising the maximum worker processes limit for the relevant IIS application pools. I tried it at 2 and saw no ill effects...didn't really benchmark anything so I can't say it helped that dramatically. We don't have 4000 agents though. Loading the client has always taken a while for me. If you open Task Manager first I suspect you'll see that one CPU core is pegged while the client is loading. If so a faster PC will speed that up.
  14. SteveYates

    BU - Shadow Protect Expired*

    What version of SP? The newer versions use the newer plugin and I don't think use that spjobs table anymore.
  15. SteveYates

    Rebooting when BitLocker is enabled

    (re: " RunDll32.exe user32.dll,LockWorkStation ") If you run that at user login (or any other time) it will lock the screen. The handful of times we've had to enable an automatic login, we create a Scheduled Task to run that at user login. It can also be added to the Run key in the registry I would think. Creating a shortcut in Startup folder would work but holding Shift I suspect would bypass that (not sure if that bypasses the Run key also)
×