Skip to main content

I cant be the only one experiencing this. S1 seems to be causing issues with Windows Servers being consistently patched. We have exclusions in place, but this doesn't seem to help. When we want patches to be fully applied across all servers, we have to disable the S1 agent completely during patching window. This is of course unacceptable. Anytime I contact support all they say is they see the device that had issues when trying to scan and receive this error:

 

{"args":"","response":":\"255\",

 

They then point me to their documented S1 exclusions. I’ve attached our S1 exclusions that we have in place but they don't seem to help. I even tried changing the amagent execution directory to C:\ProgramData\amagent and that didn't help either. 

 

Hi rav001,

 

Thanks for posting!

 

I reviewed the ticket you submitted with Support about this and the KB they provided to you. The screenshot you submitted has the correct exclusions set for the Automox Agent, whether you have it in the default location or if you moved it.

 

The device you submitted to Support hasn’t had this error 01/04/2025 (which is after you submitted the ticket) so it appears the device is properly excluded from SentinelOne. If you have another device that’s still encountering this, it may be the device is not scoped for this exclusion, or the device hasn’t been restarted.

 

  1. Reboot and Test:
    • Restart the device to apply the changes.
    • Verify whether Automox is functioning correctly.

The support engineer did not receive a follow-up from you after you submitted the case, however I will ask the engineer to follow back up with you on the ticket.

 

If you have any questions, please don’t hesitate to reach back out!


Reply