Jump to content

SteveYates

Members
  • Content Count

    16
  • Joined

  • Last visited

  • Days Won

    1

SteveYates last won the day on October 24 2018

SteveYates had the most liked content!

Community Reputation

1 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. 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 .
  2. 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/
  3. 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.
  4. 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.
  5. 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.
  6. 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)
  7. Hi, in the original post the text for "Agent ID Sharing" monitor doesn't match the .zip file. I tried to create the monitors manually and just got the "circle of hope" on the Query Results tab until I closed the window a few minutes later. After importing "Agent ID Sharing*" I see: table to check: h_computers field: NewData check condition: NotEquals result: computers.`Name` identity: (SELECT GROUP_CONCAT(DISTINCT UPPER(hc.NewData) ORDER BY hc.When SEPARATOR ',') FROM h_computers AS HC WHERE hc.What LIKE 'Name' and hc.When>DATE_ADD(NOW(),INTERVAL -7 DAY) AND hc.computerid = computers.computerid GROUP BY hc.computerid) additional cond: h_computers.What LIKE 'Name' AND h_computers.When>DATE_ADD(NOW(),INTERVAL -2 DAY) ...also on the Alerting tab the "message on failure" has what I assume is an extra "v" at the end: This agent ID might be shared by the following computers: %FIELDNAME%v The "Duplicate Agent Detection*" monitor looks the same as the original post to me. I've seen CWA get hung up if a query is hung so possibly my difficulty with it was due to the first monitor query still running, not sure there. We do have the MAC address detection enabled which usually rejoins reinstalled agents back "into" (as?) the same ID number as before uninstallation. (the exception being if the PC switches from wired to wireless and thus changes MACs). We did have one client's remote site manage to clone a laptop and did get the back-and-forth behavior which was unexpected!
  8. SteveYates

    Rebooting when BitLocker is enabled

    RunDll32.exe user32.dll,LockWorkStation Can run as a task at login, for instance.
  9. SteveYates

    Run custom script when device is offline

    Brainstorming, I'm thinking of copying the default "LT - Offline Master Computers" or "LT - Offline Servers" monitor, put it on a group that has this PC in it, and have it call a script that uses "LTServer Download to Server" script function to call your URL?
  10. SteveYates

    Modify Event Monitor To Use Event Log Source

    Perhaps I'm misunderstanding but if the source is Disk, why does the condition show 'microsoft-windows-wininit'?
  11. SteveYates

    Mystery Computer Showing up in New Computers

    We have on rare occasions had an overzealous client that installed our agent on a home PC for no reason that made sense. The agent installer download is on your web portal. Otherwise yes if a PC was "retired" and the client/location was deleted it will end up in New Computers when it comes online and rejoins. One more...I believe I saw a thread once suggesting some sort of antivirus company would execute the installer in a sandbox environment to test?
  12. SteveYates

    Norton Security w Backup

    The AP Process is the process name, so that needs to be "nortonsecurity*". The Program Location helps it detect what is installed. SEP SBE also uses Norton Security on workstations so see that section here: SEP SBE: https://support.symantec.com/en_US/article.TECH236439.html
  13. Well I don't know why but they started detecting as Running today so I guess those are the correct settings. Maybe it just takes some time to process before "update configs" actually updates? Hmmm...
  14. Does anyone have a virus config definition for any of the Norton antivirus 7.x programs on Mac OS? We specifically are using the Norton 7.7 a/v from Symantec Endpoint Protection Small Business Edition. I had found this info: Program Location: /Applications/Norton Security.app/Contents/Info.plist Definition Location: /library/Application Support/Symantec/Silo/NFM/Definitions/virusdefs/definfo.dat AP Process: SymDaemon Date Mask: (.*) OS Type: MAC That didn't work at first but after we installed v12 patch 10, which includes a newer Mac agent, I noticed the a/v was now detecting, although we get "service not running." I also tried "SymDaemon*" with an asterisk which I've had to use on Windows before to no avail (pretty sure that is because of 32 vs 64 bit process naming). A SymDaemon process is showing in the list of processes, process path /Library/Application Support/Symantec/Silo/NFM/Daemon/SymDaemon.bundle/Contents/MacOS/SymDaemon. Any tips on getting this detecting with the service running? Thanks, Steve
  15. SteveYates

    Symantec.Cloud 22.14.2.13

    FYI Symantec has KB articles for these two: SEP SBE: https://support.symantec.com/en_US/article.TECH236439.html SEP Cloud: https://support.symantec.com/en_US/article.TECH251363.html I have also had luck in the past opening a support ticket with Symantec and asking.
×