Hello!

Our VMM Server 2008 R2 manages 6 lusters Hyper-V 2008 R2.

One had a problem, so I decided to remove and add it again.

Trying to add, it returnos the following error:

• my.cluster.fqdn is not listed in Active Directory Domain Services.
• Verify that the computer name and the domain name are correct, and then try the operation again.
• ID: 10403

When I try to add using the "Skip Active Directory Name Verification", the job sarts and then:

• Error (415)
  Agent installation failed copying E:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\I386\2.0.4521.0\msiInstaller.exe to \\my.cluster.fqdn\ADMIN$\msiInstaller.exe.
   (The network name cannot be found)
• Recommended Action
  1. Ensure my.cluster.fqdn is online and not blocked by a firewall.
  2. Ensure that file and printer sharing is enabled on my.cluster.fqdn and it not blocked by a firewall.
  3. Ensure that there is sufficient free space on the system volume.
  4. Verify that the ADMIN$ share on my.cluster.fqdn exists. If the ADMIN$ share does not exist, reboot my.cluster.fqdn and then try the operation again.

I cant access access the path \\my.cluster.fqdn\ADMIN$ using Windows Explorer, but if I try each node name \admin$, it access ok.

Any idea how to solve this?

• Edited by FabioMartinsRB Wednesday, August 26, 2015 9:03 PM

Hi Elton!

Thanks for helping.

Firewall are all disabled on all related servers. 

But I didnt try to access the shares from the DCs before. I tried just now, and the name resolves OK but it doesnt work for the cluster name. 

Cluster is OK, I can do live migrations OK, Cluster validation only shows warning for pending updates, but both servers show no updates when running windows update.

PS C:\> setspn -L myclustername

Registered ServicePrincipalNames for CN=myclustername,OU=HOST,OU=SERVERS,OU=VCA,OU=COMPANYNAME,DC=COMPANYDOMAIN,DC=com,DC=
br:
        MSServerCluster/myclustername.redebahia.com.br
        MSServerCluster/myclustername
        MSServerClusterMgmtAPI/myclustername.fqdn
        MSServerClusterMgmtAPI/myclustername
        MSClusterVirtualServer/myclustername.fqdn
        MSClusterVirtualServer/myclustername
        HOST/myclustername.fqdn
        HOST/myclustername

PS C:\>

Any other idea?

• Edited by FabioMartinsRB Friday, August 28, 2015 2:23 PM

Hi Sir,

It's really an odd issue .

The VMM server and that problematic cluster are in same domain , right ?

Did you check each NIC configuration for each cluster node ( IP configuration and The DNS suffix ) .

(Based on my understanding of cluster best practice , except management NIC , the remains should only be configured with IP/subnet different than management NIC's if it is not needed to access the resource in other subnet  ).

Please try to use command "setspn -x " to check if there is any conflict SPN record .

Also , please check the DNS record on VMM server , you can use command " ipconfig /displaydns " to list the DNS record .

In addition , you may try to collect the trace log for "adding host/cluster":

http://blogs.technet.com/b/jonjor/archive/2011/01/07/vmmtrace-simplified-scvmm-tracing.aspx

Hope it is helpful to you .

Best Regards,

Elton Ji