thibaut blanchin

Hello,

I'm trying to remotly register a VM into a windows 2008 R2 cluster with
Add-ClusterVirtualMachineRole powershell commandlet.
It always fails except in one case : if I connect to the first node of the
cluster - I mean first in alphabetical order - and the VM is on this node.

It's easy to reproduce, if you have a Cluster with Hyper-V role :
- Create a virtual machine within hyper-V managment console on one node
(not the "first" one...).
- From a Windows 7 computer, open Powershell command line and connect to
this node:

- Import system modules in order to have system cmdlets :

- try to register the VM into the cluster :

VirtualMachineName

=> Add-ClusterVirtualMachineRole : Unable to connect to node1 via WMI ...

It sounds like Add-ClusterVirtualMachineRole is checking each node of the
cluster to find the virtual machine and faces some delegation issue as it is
launched remotly.
It seems also that, instead of looking for the VM localy first, it checks
the node in alphabetical order.
Of course Add-ClusterVirtualMachineRole is working fine if executed localy
on any node. My problem is that I need to use it from a remote server inside
a script.

I've been looking for a workaround but I'm missing new ideas now...
Any help would be greatly appreciated.
--
Thibaut Blanchin
DT - Plate formes & Systèmes
CEGID

elden

You might be running into the double hop problem, check out this blog and see
if it addresses your issue:
http://blogs.msdn.com/clustering/arc...5/9803001.aspx

thibaut blanchin

Thanks !
It sounds to be exaclty what I'm facing. I'm going to test it.

--
Thibaut Blanchin
DT - Plate formes & Systèmes
CEGID