Review Problems and Solutions after upgrade question

Question

I have recently migrated from WSS 3.0 to Sharepoint Foundation 2010.  I now have a the following messages in Sharepoint Admin.
The SharePoint Health Analyzer has detected some critical issues that require your attention. View these issues.
Accounts used by application pools or service identities are in the local machine Administrators group.
Using highly-privileged accounts as application pool or as service identities poses a security risk to the farm, and could allow malicious code to execute. The following services are currently running as accounts in the machine Administrators group: SharePoint
Central Administration v4 (Application Pool)
SPTimerV4(Windows Service)
Built-in accounts are used as application pool or service identities.
Using built-in accounts like Network Service or Local System as application pool or as service identities is not supported in a farm configuration. The following services are currently running as built-in identities on one or more servers: SPSearch4(Windows
Service)
The last time I tried to correct this type of issue I wound up creating a problem that I was unable to correct.  I had to  reinstall Sharepoint.  How critical is this and what is the best way to make these changes without causing larger problems? 
I am using two accounts to run the services/pools/etc.  Well 3 if you count the Local System.  Account #1 and #2 are not in the Admins group.  They were when I installed everything but I have since removed them.

Answer 1

Hi Poly,
I recommend to follow the steps below to see if the warning message remains:
1.   Re-run Rule Definition.
In Central Administration, go: Monitoring > Health Analyzer > Review rule definitions. On the Health Analyzer Rule Definitions page, in the Category: Security group, click the rule definition link, Accounts used by application pools or service identities
are in the local machine Administrators group. Click the Run Now button, then click Close. Wait a minute or two, and then return to Review problems and solutions page.
2.   Reset Farm Service.
Login to the local machine hosting the farm Central Administration application. Go to Start > Administrative Tools > Services and scroll down to the SharePoint 2010 Administration service. Double-click this service, select the Log On tab. If not selected,
select  the This account option and then enter or re-enter the farm account. At the warning prompt, "The new login name will not take effect until you stop and restart the service," click OK. Stop and restart the service, and then
click OK. Wait a minute or two, and then return to Review problems and solutions page.
3.   Reset the Farm Timer Service.
Login to the local machine hosting the farm Central Administration application. Go to Start > Administrative Tools > Services and scroll down to the SharePoint 2010 Timer service. Double-click this service and select the Log On tab. If not selected,
select  the This account option and then enter or re-enter the farm account. At the warning prompt, "The new login name will not take effect until you stop and restart the service," click OK. Stop and restart the service, and then
click OK. Wait a minute or two, and then return to Review problems and solutions page.
More references:
http://alstechtips.blogspot.com/2013/12/health-analyzer-accounts-used-by.html
http://technet.microsoft.com/en-us/library/hh344224(v=office.14).aspx
http://technet.microsoft.com/en-us/library/ff805066(v=office.14).aspx
Victoria Xia
TechNet Community Support