Hello,

We have a storage spaces (non-clustered for now) installation and get errors when we create a VM from VMM. VMM sees everything - including the share that is the destination for the VHD until we click "create". The job instantly fails with 2904 "cannot find the path".

Things we have done/checked:

1. The share is registered to VMM

2. We cannot register the share to a host - it finds the share but does not save the share in the host config

3. We are at Rollup 6 updates.

4. We have (for testing) given Everyone Full Control of the share - no change in result.

5. If we create the VM from Hyper-V manager it is created, but VMM shows it as Unsupported.

Thanks in advance for anyone that can help!

• Moved by BrianEhMVP, Moderator Wednesday, May 20, 2015 2:45 PM

We have found the answer. We created a new VMMRunAs Domain Account, configured the host access to use it, gave it full control of the shares and we were able to register the share with the host and create VMs on the storage spaces share.

The old RunAs account had these same rights, but creating the new account made this work...don't know why.

• Marked as answer by Kristian NeseMicrosoft contingent staff, Moderator 13 hours 45 minutes ago

We have found the answer. We created a new VMMRunAs Domain Account, configured the host access to use it, gave it full control of the shares and we were able to register the share with the host and create VMs on the storage spaces share.

The old RunAs account had these same rights, but creating the new account made this work...don't know why.

• Marked as answer by Kristian NeseMicrosoft contingent staff, Moderator Thursday, May 21, 2015 5:30 PM

Did the 'Run As account' used to register the share in VMM have local admin permissions on the File Server  (Not only the share) ?

Yes, it did. It was a local admin.