Skip to main content

Good afternoon!

Has anyone else seen or had an issue with any of their endpoints reporting back a very vague “1” in the activity log when trying to push manual updates to it? I’ve put in a ticket on this previously, but the only answer I was able to get was that it could possibly be something stopping the script from running on the computer. I am not sure what it could be since we’ve had no issues before, but this started a few weeks ago. It also seems to be random. The logs only say “Error in Wait” and are also a bit vague. 

I’ve tried implementing solutions such as turning the powershell mode to unrestricted on a few computers, but have still gotten the error after. The interesting thing is that we have no issues with automatic updates each night going through. It seems to only be with updates we manually push through the console.

 

Has anyone else had anything similar or have any suggestions?

Thanks

Hi,

I took a look at the case history in our support system and see behavior consistent with Sentinelone. I saw you did mention you allowlisted the operating directories, did you do that by taking a look at this KB article? https://help.automox.com/hc/en-us/articles/23505268771348-SentinelOne-Exception

 

Another quick and dirty way to validate root cause is to temporarily disable Sentinelone on the endpoint and try to update. One of the other indicators of it being at least EDR related is also that the scans are failing on some endpoints. This also impacts the ability of Automox to provide updated information in the Software section of the device page.

 

Let me know some more details and we’ll keep into this for you.

Regards,

Mark

Thanks for the suggestions. I’ll see if I can take another look at the sentinelOne portion of this. We did follow the guide to allow the directories through SentinelOne, but there may be something else with SentinelOne that could be blocking this.

If that fails, we can try temporarily disabling SentinelOne on any computers that run into this issue in the next day or so. It is a bit unusual since computers that do have SentinelOne installed don’t always run into the issue so I can’t really see a specific pattern or setting just yet.

We have noticed the same behavior (sporadic) even on the same machine across multiple days. The biggest indicator to me is not just on the update failure but the scan failures, but it appears that only the software collection portion of the scan rather than the other elements. 

Reply


Terms & ConditionsCookie settings