I have a 2012 R2 Hyper-V cluster. I have configured an EMC VNX array with SMB 3.0. I configured the shares with full access for each of teh cluster nodes and the cluster name. From a node of the cluster, I can select a VM, select Storage Migration, and then specify the EMC share as the destination.
I have a Windows 8.1 management workstation from which I perform most management functions. I want to be able to do the same thing using remote management. From the remote cluster management console, I select a VM, select Storage Migration, but I am unable to specify the EMC share as the destination.
I configured constrained delegation from the management workstation to the EMC array and to each of the nodes of the Hyper-V cluster, plus the cluster name itself, for cifs, just to see if that would change anything. I also configured the EMC shares with full access for the remote workstation. No change.
The remote workstation does not have network access to the EMC shares. I was hoping the constrained delegation would get me around that. My thinking on that was that constrained delegation would allow me to use the Cluster Console and that would then request one of the nodes to make the request to the share on behalf of the workstation. My guess is that is not how it is working.
Question. Is network access to the EMC array a requirement for remote management of the cluster to work? If so, is that something that should be? I know the cluster nodes have access to the storage. It seems like the idea of remote management is that you are talking to the remote machines and asking them to perform something. In this case, it seems like the management workstation has to make a connection before you can ask the cluster to perform the operation I know the cluster can perform.
Note: I will add network access to the workstation. It's a VM, so it won't take much to add the additional networks, but it doesn't seem like I should have to do this.
. : | : . : | : . tim