mohegantribe
asked on
Receiving error 406 in SCVMM 2008 R2 adding host
Have SCVMM 2008 R2 installed on one node of a 2-node 2008 R2 failover cluster running Hyper-V.
I am receiving error 406 adding the cluster as a host in SCVMM. Added Administrators to Launch and Activation in DCOM application Virtual Machine Management (as advised in the error text), but this hasn't resolved.
If I choose the other node in the wizard first, it seems to go fine, and asks me to bring in both nodes of the cluster, which I do, then the wizard ultimately fails with error 406.
When I add the local server running SCVMM first in the wizard, I get the error 406 immediately.
I received the same error in PS using the Add-VMHostCluster specifying the local node running SCVMM, but the cluster added successfully by specifying the remote node.
I am concerned that SCVMM will not perform correctly since I received the error attempting to add the local node.
Is there any info on resolving the 406 error?
I am receiving error 406 adding the cluster as a host in SCVMM. Added Administrators to Launch and Activation in DCOM application Virtual Machine Management (as advised in the error text), but this hasn't resolved.
If I choose the other node in the wizard first, it seems to go fine, and asks me to bring in both nodes of the cluster, which I do, then the wizard ultimately fails with error 406.
When I add the local server running SCVMM first in the wizard, I get the error 406 immediately.
I received the same error in PS using the Add-VMHostCluster specifying the local node running SCVMM, but the cluster added successfully by specifying the remote node.
I am concerned that SCVMM will not perform correctly since I received the error attempting to add the local node.
Is there any info on resolving the 406 error?
Emptyone
Tried disabling the firewall on the Hyper-V nodes when doing the install?
ASKER
Firewalls disabled already for all but Public Networks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Node A runs the VMM, not a VM on Node A.
I hadn't tried editing Limits. Will try this if I need to remove and re-add the host.
I hadn't tried editing Limits. Will try this if I need to remove and re-add the host.
ASKER
Unable to verify at this time
You got the VMM installed on one of the Hyper-V nodes?
That will not work. You should have SCVMM installed on another physical server, or on a VM. Not on one of the physical nodes in the Hyper-V failover cluster