Event ID - 1221

Event Id	1221
Source	Microsoft-Windows-FailoverClustering
Description	Cluster network name resource '%1' has a name '%2' which does not match the corresponding computer object name '%3'. It is likely that a previous name change of the computer object has not replicated to all domain controllers in the domain. You will be unable to rename the network name resource until the names become consistent. If the computer object has not been recently changed, please contact your domain administrator to rename the computer object and thereby make it consistent. Also, ensure that replication across domain controllers has been successfully completed.
Event Information	According to Microsoft : Cause : This event is logged when the Cluster network name resource has a name which does not match the corresponding computer object name. Resolution : Check for completion of rename process After a change to a computer account name, the change must replicate to all domain controllers in the domain. Allow enough time for this replication to complete so that the Network Name on the cluster matches the computer account name in Active Directory. If you do not currently have Event Viewer open, see "To open Event Viewer and view events related to failover clustering." To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority. To open Event Viewer and view events related to failover clustering: If Server Manager is not already open, click Start , click Administrative Tools , and then click Server Manager . If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue . In the console tree, expand Diagnostics, expand Event Viewer , expand Windows Logs , and then click System . To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log . On the Filter tab, in the Event sources box, select FailoverClustering . Select other options as appropriate, and then click OK . To sort the displayed events by date and time, in the center pane, click the Date and Time column heading. Verify : To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority. Verifying that an IP Address resource can come online To verify that an IP Address resource can come online: To open the failover cluster snap-in, click Start , click Administrative Tools , and then click Failover Cluster Management . If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue . In the Failover Cluster Management snap-in, in the console tree, make sure Failover Cluster Management is selected. Then under Management , click Validate a Configuration . If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications . In the console tree, click a clustered service or application. In the center pane, view the status of the Network Name resource you want to verify. If a Network Name resource is offline, to bring it online, in the center pane, right-click the resource and then click Bring this resource online . To perform a quick check on the status of a resource, you can run the following command. Using a command to check the status of a resource in a failover cluster To use a command to check the status of a resource in a failover cluster: On a node in the cluster, click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator . Type: CLUSTER RESOURCE ResourceName /STATUS If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.
Reference Links	Event ID 1221 from Microsoft-Windows-FailoverClustering

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught