The account that is used to start the Cluster service must be a minimum of a domain-level USER account, and it must be added to the local administrative group on each node in the cluster. Add the account to the Local Administrators group on each node in the cluster by using Computer Management in Microsoft Windows Server 2003.

To change the account that is used to start the Cluster service, you must use Computer Management for Windows Server 2003 to change the account information on each node in the cluster.

To achieve this, please follow these steps:

	*  Start Computer Management for Windows Server 2003, expand the Services and Applications branch, and then click the Services branch.
	*  In the right pane, double-click Cluster Service. Select the Log On tab, and then update the account information.

To function correctly in Microsoft Windows Server 2003, the Cluster service account explicitly requires the following rights for all nodes in the cluster:

•	Act as part of the operating system
•	Adjust memory quotas for a process
•	Back up files and directories
•	Increase scheduling priorities
•	Log on as a service
•	Restore files and directories

Also, make sure that the Local Administrator Group has access to the following user rights:

•	Debug programs
•	Impersonate a client after authentication
•	Manage auditing and security log

You can grant these rights in the following locations: Note If you create a Group Policy setting to update the Impersonate a client after authentication rights policy setting, make sure that the Cluster service account is listed in the policy setting in addition to the Local Administrators group and the account that is called SERVICE. If the Cluster service account is not listed, the computer may no longer have access to Windows Management Instrumentation (WMI). By default, these accounts are listed in the Impersonate a client after authentication rights policy. However, if you create a Group Policy setting without adding the Cluster service account, the local policy setting is overwritten, and WMI access fails.