/
Why is the Snare service stopping when using a Service Account instead of Local Service Account
Why is the Snare service stopping when using a Service Account instead of Local Service Account
SUMMARY
Jul 06, 2015
Random stopping of the agent service could be caused by the following:
Ensure that user associated with service has proper rights and none of the domain (group policy objects, GPO) policy prevents the user to run service.
The following link describes how to add/confirm 'Log on as a service' right associated with an account. Confirm that account has Log on as a service and specially check this when there is a service stop error. It might be possible that initially the account has this right but some GPO policy overwrites (removes) this right, causing the agent service to stop.
For further information see https://technet.microsoft.com/en-us/library/cc739424(v=ws.10).aspx.
, multiple selections available,
Related content
Appendix H - Running Snare Agent with Non-admin Service Account
Appendix H - Running Snare Agent with Non-admin Service Account
More like this
Permissions and UAC
Permissions and UAC
More like this
Licenses Available
Licenses Available
More like this
The Web UI crashes after installation of Snare Windows agent
The Web UI crashes after installation of Snare Windows agent
More like this
Populate the SAM server details
Populate the SAM server details
More like this
Can’t get Snare Agent working on Domain Controllers
Can’t get Snare Agent working on Domain Controllers
More like this