Each day I come across machines that have one or more McAfee services that did not start even though the services' recover tabs are set to restart after the first and second failure. The subsequent failures action is set to take no action. Is there any reason not to change the subsequent failures option to restart the service or would anybody know a better way to accomplish this such as changing the Windows Default Domain Policy?
The question that comes to mind is, what's stopping a service that is set to auto start - are you using "Access Protection Policies", specifically geared towards protecting McAfee Services from stopping or being modified?
As for the setting "subsequent failures", GPO should be able to accomplish this; a potential issue would be a "service loop" rendering the system unresponsive.
Access Protection Policies is set to prevent termination of McAfee processes. I didn't think a continuous attempt to start a McAfee service would affect the computer. Have you previously experienced the problem with service loops due to McAfee services starting?
I do recall some years ago running into a McAfee service loop; that was due to incorrect/corrupt policies. Also make sure to your have toggled on "Enable access protection" within Access Protection Policies. There are a couple of other APP's to check: under Common Standard Protection - are you blocking/logging any of the McAfee rules?
Under Common Standard Protection there is "Prevent termination of McAfee processes"; perhaps toggle on to log only.