https://community.hpe.com/t5/operating-system-microsoft/failing-service-manager/m-p/4489187#M11874 When I try to create a cluster to a specific blade (a BL460c), it fails.<BR />I've rebuilt the entire thing from the ground up, reinstalled W2K8 R2, re-added it to the domain, reset all admin passwords, updates, networks, etc.<BR />It fails.<BR /><BR />The first time I run "Validate a configuration wizard" I get the error:<BR />"Failed to connect to the service manager on 'systemThree.domain.test'.<BR /><BR />Occasionally I get the message:<BR />"The computer 'systemThree' does not have Failover Clustering feature installed. Use Server Manager to install the feature on this computer."<BR /><BR />But of course, Failover Clustering is installed, and I can actually set up the entire cluster from systemThree... except with these sort of communication errors it doesn't last long and usually corrupts any configured Virtuals I have running in Hyper-V.<BR /><BR />All systems being clustered are BL460c units.<BR /><BR />Any ideas on how to resolve this?<BR /><BR />Thank you,<BR /><BR /><BR />-Aaron Mon, 31 Aug 2009 21:28:09 GMT Aaron.S 2009-08-31T21:28:09Z https://community.hpe.com/t5/operating-system-microsoft/failing-service-manager/m-p/4489187#M11874 When I try to create a cluster to a specific blade (a BL460c), it fails.<BR />I've rebuilt the entire thing from the ground up, reinstalled W2K8 R2, re-added it to the domain, reset all admin passwords, updates, networks, etc.<BR />It fails.<BR /><BR />The first time I run "Validate a configuration wizard" I get the error:<BR />"Failed to connect to the service manager on 'systemThree.domain.test'.<BR /><BR />Occasionally I get the message:<BR />"The computer 'systemThree' does not have Failover Clustering feature installed. Use Server Manager to install the feature on this computer."<BR /><BR />But of course, Failover Clustering is installed, and I can actually set up the entire cluster from systemThree... except with these sort of communication errors it doesn't last long and usually corrupts any configured Virtuals I have running in Hyper-V.<BR /><BR />All systems being clustered are BL460c units.<BR /><BR />Any ideas on how to resolve this?<BR /><BR />Thank you,<BR /><BR /><BR />-Aaron Mon, 31 Aug 2009 21:28:09 GMT https://community.hpe.com/t5/operating-system-microsoft/failing-service-manager/m-p/4489187#M11874 Aaron.S 2009-08-31T21:28:09Z