Hokay. Lets see.
I'm using the add host wizard to add the hosts.
Trying to run the powershell command sequence you suggest above gives effectively the same error:
Discover-Cluster : Unable to contact cluster service on J-VM.mydomain.com. (Error ID: 13805)
Back to the VMM GUI, entering the second node name (J-VM02) results in it resolving to the cluster. Entering the first node name (J-VM01) actually gives an error:
Access has been denied while contacting the server J-VM01.mydomain.com.
1. Verify that the specified user account has administrative privileges on J-VM01.mydomain.com.
2. Verify that DCOM access, launch, and activation permissions are enabled on J-VM01.mydomain.com for the Administrators group. Use dcomcnfg.exe to modify permissions, and then try the operation again.
ID: 406
I actually did pull up dcomcnfg to check the permissions. The error doesn't say which objects to check the permissions on, but I checked the permissions on "Virtual Machine Management" and "Virtual Machine Worker Process" and both seemed to be correct for group Administrators.
Entering the second node name (J-VM02) has it resolve the cluster. If I tell it to continue and accept all the defaults from there, it starts the host adding job, whichimmediately fails with:
Error (13805)
Unable to contact cluster service on J-VM.mydomain.com
Recommended Action
Ensure that the provided name is a cluster name or the computer name of a node in the cluster, and that the cluster is listed in Active Directory Domain Services. For a newly created cluster, you might need to wait for the cluster name to be added to Active Directory Domain Services.
As far as tracing goes, I don't see an obvious way to attach a file or send to you privately, so I'm going to pick out what seems like the relevant bits in the trace and just post those, in the name of brevity. Full trace available on request.
[2404] 0964.1380::11/11-16:11:59.313#09: DiscoverCluster.cs(87): Starting discovery for cluster J-VM.mydomain.com
[4612] 1204.1298::11/11-16:11:59.313#21:ClientCache.cs(749): Waiting on 1 objects...
[2404] 0964.100C::11/11-16:11:59.328#21:EventClientConnection.cs(239): Server session uuid:e875e18b-e3cd-4966-bd27-d4530bb32263;id=1 - Sending 1 events
[4612] 1204.01A8::11/11-16:11:59.328#21:Callback.cs(50): Client uuid:7089dcaf-72e0-46b5-b2de-83a592f184bb;id=1 - 1 events
[4612] 1204.01A8::11/11-16:11:59.328#21:ClientCache.cs(599): New object: abe6449b-4e39-4e03-b5ac-e6d0af522229
[4612] 1204.01A8::11/11-16:11:59.328#21:Callback.cs(53): Client uuid:7089dcaf-72e0-46b5-b2de-83a592f184bb;id=1 - events processed
[2404] 0964.1380::11/11-16:11:59.531#09:ClusterHelper.cs(473): Error getting cluster details for J-VM.mydomain.com
[2404] 0964.1380::11/11-16:11:59.531#09:ClusterHelper.cs(473): System.Management.ManagementException: User credentials cannot be used for local connections
[2404] at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
[2404] at System.Management.ManagementScope.InitializeGuts(Object o)
[2404] at System.Management.ManagementScope.Initialize()
[2404] at Microsoft.VirtualManager.DB.Adhc.ClusterHelper.GetClusterObjects(String scopeString, String className, String computerName)
[2404] 0964.1380::11/11-16:11:59.531#19:Task.cs(246): Task failed error ClusterDoesNotExist (13805) with exception Microsoft.VirtualManager.Utils.CarmineException: Unable to contact cluster service on J-VM.mydomain.com.
[2404] Ensure that the provided name is a cluster name or the computer name of a node in the cluster, and that the cluster is listed in Active Directory Domain Services. For a newly created cluster, you might need to wait for the cluster name to be added to Active Directory Domain Services.
[2404] at Microsoft.VirtualManager.Engine.Adhc.DiscoverClusterTask.DiscoverNewCluster()
[2404] at Microsoft.VirtualManager.Engine.Adhc.DiscoverClusterTask.RunSubtask()
[2404] at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
[2404] at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
[2404] *** Carmine error was: ClusterDoesNotExist (13805)
[2404] *** J-VM.mydomain.com ** |TaskID=ABE6449B-4E39-4E03-B5AC-E6D0AF522229
So it does correctly detect that J-VM02 is part of the J-VM cluster. The interesting parts seem to be..
System.Management.ManagementException: User credentials cannot be used for local connections
... and ...
Task failed error ClusterDoesNotExist (13805) with exception Microsoft.VirtualManager.Utils.CarmineException: Unable to contact cluster service on J-VM.mydomain.com.Ensure that the provided name is a cluster name or the computer name of a node in the cluster, and that the cluster is listed in Active Directory Domain Services. For a newly created cluster, you might need to wait for the cluster name to be added to Active Directory Domain Services.
The first of those almost implies to me that one shouldn't be running the VMM master server on one of the machines in the cluster -- is that actually the case? I suppose I wouldn't be surprised if that were the case, but I don't remember seeing that documented anywhere, either.
The second (ClusterDoesNotExist), J-VM gets registered in DNS and I can see the computer object for it in AD, so I'm assuming it's correctly registered in AD and the like.
I think that covers most everything. I'll try moving my VMM server off of the cluster and see if that makes things happier, in the meantime. For me, this is somewhat sub-optimal (since I want clustering for quick migration more than redundancy), but if that's what is going on, at least I'll know.
Thanks much!