Configuring a SentinelOne Exception for Automox
This guide provides instructions for configuring an exception in SentinelOne to resolve potential conflicts with Automox. Follow the steps below to add the exception and address related issues.
1. Add SentinelOne Path Exclusion
To configure a SentinelOne exception for Automox, follow these steps:
- Open the SentinelOne Management Console:
- Log in to your SentinelOne console with an account that has the necessary permissions.
- Navigate to the Exclusions Menu:
- Go to Policy Settings or Global Settings (depending on your configuration).
- Select the appropriate group or device policy where you want to apply the exclusion.
- Add the Exclusion:
\Device\HarddiskVolume*\Program Files (x86)\Automox
- Include Subfolders: Yes
- Exclusion Type: Path exclusion for both alerts and mitigations.
- Exclusion Mode: Interoperability - extended.
- Save the Configuration:
- Save your changes and allow approximately 5 minutes for the exclusion to propagate.
- Reboot and Test:
- Restart the device to apply the changes.
- Verify whether Automox is functioning correctly.
2. Alternative Solution: Change Automox Script Execution Directory
If adding exceptions does not resolve the issue, consider changing the Automox script execution directory to a location with permissions for file creation. Follow these steps:
- Identify a New Directory:
A commonly used location is: C:\ProgramData\amagent
- Reconfigure Automox:
- Change the execution directory within the Automox platform settings to the new location.
- Test and Verify:
- Ensure Automox scripts execute successfully in the new directory.
3. Verifying and Troubleshooting
After completing the above steps, confirm that the Automox agent is functioning as expected. If issues persist, consider the following:
- Double-check that the exclusion paths are correct.
- Verify that SentinelOne policies are syncing correctly with endpoints.
- Contact Automox or SentinelOne support for further assistance.
Things to Remember
- Ensure you have administrative privileges before making these changes.
- Refer to your organization’s IT policies before uninstalling or modifying security software.