Problem
You see the following warning appear in the Review problems and solutions list in SharePoint 2010 Central Administration:
This posting presented steps for resolving the Health Analyzer warning, Built-in accounts are used as application pool or service identities. For additional detail on this topic, see the references below.
References
You see the following warning appear in the Review problems and solutions list in SharePoint 2010 Central Administration:
Built-in accounts are used as application pool or service identitiesSolution
- Click on the warning title. The warning description dialog appears:
- The error description dialog identifies the cause of the problem: the DCLoadBalancer14, SPSearch4 and DCLauncher14 services are being run by a built-in account of the machine hosting the services.
In this case, all of the services are running on a single application server, part of a small two-tier farm. In multi-server farms where services may be running on other machines, you will need to perform this check on each server.
- In Central Administration, go: Security > General Security > Configure service accounts.
- From the service dropdown (upper one), select Windows Service - Document Conversions Load Balancer Service. This is what is referred to in the warning as "DCLoadBalancer14(Windows Service). The page is updated to show the service components and the account running the service:
- From the Select an Account for this component dropdown, select a managed account. For this posting, the Contoso\sp_app account was used.
- Click OK.
- Navigate back to the Review problems and solutions page in Central Administration.
- Click on the warning title, Built-in accounts are used as application pool or service identities:
- Click Reanalyze Now.
- Wait a minute or two, and then click on the warning title again.
- Verify that DCLoadBalancer14(Windows Service) is no longer included in the warning:
- Repeat the above steps, this time choosing Windows Service - Document Conversions Launcher Service. This is what is referred to in the warning as "DCLauncher14(Windows Service)."
- Verify that DCLauncher14(Windows Service) is no longer included in the warning:
- Repeat the above steps, this time choosing Windows Service - SharePoint Foundation Search. This is what is referred to in the warning as "SPSearch4(Windows Service)."
- Verify that the warning, Built-in accounts are used as application pool or service identities, is no longer listed:
- This concludes this procedure.
This posting presented steps for resolving the Health Analyzer warning, Built-in accounts are used as application pool or service identities. For additional detail on this topic, see the references below.
References
- Built-in accounts are used as application pool or service identities (SharePoint Foundation 2010)
- Account permissions and security settings (SharePoint Server 2010)
- Plan administrative tasks in a least-privilege environment (SharePoint Server 2010)
- Initial deployment administrative and service accounts (SharePoint Server 2010)
- Service Account Suggestions for SharePoint 2010
- Health Analyzer – SharePoint 2010 Tracing (SPTraceV4)
No comments:
Post a Comment