No. I don't think you were looking at the right section.
The section of interest would be the one that indicates the specific permissions that need to be granted to the user. I just had to do this for a Windows 2008 MSSQL installation and to run it anything other than a domain admin these were the required permissions:
*Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)
*Bypass traverse checking (SeChangeNotifyPrivilege)
*Log on as a batch job (SeBatchLogonRight)
*Log on as a service (SeServiceLogonRight)
*Replace a process-level token (SeAssignPrimaryTokenPrivilege)
I realize this may be slightly different in 2005 though so here's what I would suggest.
- Create a simple regular user in the domain e.g DOMAIN\USER.
- Before adding it to any groups, assign the above permissions to it via GPO under Computer Configuration > Windows Settings > Security Settings > Local Policies/User rights assignment
- Do a gpupdate /force as admin so the policy is refreshed. Then try running the SQL service with that account i.e. DOMAIN\USER. If it doesn't work, add the additional permissions indicated in the link by Graeme such as Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)...Add one at time, refresh and then try. See section labelled Reviewing Windows NT Rights and Privileges Granted for SQL Server Service Accounts for the extra permissions.
Hope this helps.