question

MiroslavHavranec-3463 avatar image
0 Votes"
MiroslavHavranec-3463 asked ElevenYu-MSFT commented

Hyper-V cluster using external SOFS (S2D - 2node - without AD) - permission error

Hello dear friends,
i have problem with permissions on external SOFS S2D storage.

////SERVER PART/////

I have 2 node SOFS with SMB multi share. On both node is failover cluster with SOFS roles and SMB share with multi nic support. RDMA working.

This boot servers is not in active directory, only in workgroup ! and all is based on "hosts" file and regular external DNS server with static entries.

This node are marked as STOR1 and STOR2.

All working well.


////CLIENT PART/////

On client part i have multiple blades, all with same os, win2019 dc and on this blades MARKED as BLADE1, BLADE2 there is HYPER-V (compute). This Hyper-V hypervisor use 40GB network for connection to STOR1 and STOR2. All working well, Blades has network drive Z: mapped to SOFS (STOR1+STOR2) share. In windows Explorer is possible copy file to this share without problem, but if i run Hyper-V, use this share (example : Z:/VMDATA and Z:/VMCONFIG i have problem with permissions. ERROR 0x80070005.

I USE ONLY WORKGROUP

How to resolve this problem ?
It is possible without domain ?
(i know that in AD i add BLADE1 to ACL on STOR1 and STOR2 - but in no AD ?)

I test set permission on shared folder on STOR1 and STOR2 to Everyone - full access, i try it same on Client part but with no success still same problem

Any idea ?

Thank you much for answer !

Mirek




windows-server-hyper-vwindows-server-clusteringwindows-server-management
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Have you checked if the answer helps?

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

0 Votes 0 ·

1 Answer

ElevenYu-MSFT avatar image
0 Votes"
ElevenYu-MSFT answered

Hi,

Thank you for posting question to Microsoft Q&A forum.

After researching, I found an article that describe a similar issue as yours.

The issue happened because the Hyper-V host does not have permission on the network share. You need to ensure the permissions allow the Computer account of the Hyper-V host to access this share.

Please try the solution in below link to see if it helps to resolve your issue.
https://docs.microsoft.com/en-us/troubleshoot/windows-server/virtualization/error-0x80070005-export-vms

Best regards,


If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.