Consider the following scenario:
I have the following systems up and running:
A SCVMM Server (SCVMM 2012 R2 + RU2), fully patched (hostname: SCVMMSRV)
A NetApp NAS Storage correctly reached and managed using NetApp SMI-S Provider (DataONTAP 8.2P4, SMI-Provider 5.1)
(The CIFS Server if reachable at
\\NAS.domain.local)
A two-node Hyper-V Cluster (Windows Server 2012 R2 Update 1), fully patched (hostnames: HVSRV01A, HVSRV01B)
I also followed these configuration steps:
I created and registered a NAS Share to the SCVMM Library Role exposed by the SCVMM Server itself (\\NAS.domain.local\VMMLibrary);
I associated a new RunAs Account for the Library Management Credential (username: DOMAIN\scvmmLibrary);
I set on the NAS share full-control for both share and NTFS permissions to the following principals:
The SCVMM Service account (DOMAIN\scvmmService);
The SCVMM Library RunAsAccount (DOMAIN\scvmmLibrary);
The SCVMM Server Computer Account (DOMAIN\SCVMMSRV$);
The Hyper-V Cluster Nodes Computer Accounts (DOMAIN\HVSRV01A$,DOMAIN\HVSRV01B$)
Then I created a new VM (testvm2) and placed it on a cluster Node; then have run the New VM Template wizard starting from the VM itself, targeting the NetApp NAS share (path:\\NAS.domain.local\VMMLibrary\Templates).
During wizard execution the following error is raised:
"Error (20552)
VMM does not have appropriate permissions to access the resource \\NAS.domain.local\VMMLibrary\Templates\testvm2\Virtual Machines\3DEF07D0-86FA-4A81-869C-27A88673B847.xml
on the SCVMMSRV.domain.local server.
Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.
Also, verify that CredSSP authentication is currently enabled on the service configuration of the target computer SCVMMSRV.domain.local. To enable the CredSSP on the service configuration of the target computer, run the following command from an elevated command line: winrm set winrm/config/service/auth @{CredSSP="true"}"
Seems that SCVMMSRV lacks some kind of permission over the NAS share.
What kind of permissions are required on the share, the VMM Server, or Hyper-V Nodes to make sure that this scenario is working?