So, after a clean install of SharePoint 2010 you sometimes get a warning that a service is using a built in account. This is found in yellow in the Monitoring panel in Central Administration.
Upon further examinination, the service at fault is SPTraceV4 (though the actual error on the console (rather than the error detail) is SPTimerServiceV4 is failing).
Sure enough, upon checking the windows services console, the account for SPTraceV4 is the built in local service account.
So, is there a proper way to update this account to something other than local service OR to prohibit its provisioning with a local service account? Is this a bug?
Another thread with similiar detail is here: