<h2>CI binding is failing for Windows Cluster CIs</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul style="list-style-position: inside;"><li>CI binding is failing for Windows Cluster CIs</li></ul></section></div><div ><h3 >Release</h3><section><ul style="list-style-position: inside;"><li>All</li></ul></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li>Review the below comments on the binding page from the event rule<br /><br />"<strong>Default binding: Value of Node field will be used to try and match CI name, FQDN, IP or MAC Address for Host CIs, such as Computer, OS, Switch Router (any CI type extending cmdb_ci_hardware)</strong>"<br /><br /></li><li>Check if the event rule binding that is available now is supported for CI type extending <strong>cmdb_ci_hardware</strong>.<br /><br /></li><li>If so, to address this issue, you will have to create an event rule with the filter criteria that is unique to <strong>Windows Cluster</strong> and associate the CI Binding to "<strong>CI Identification</strong>" with class "<strong>Cluster</strong>" and provide identifier attributes.</li></ul></section></div></article></div>