Unable to create new Hyper-V VM after successful vsan setup

[jhemphi]

I have a new 2 node hyperconverged StarWind Virtual SAN setup that I am trying to get running. All initial setup steps, HA Device creation and sync, Failover cluster test and creation, SOFS creation, Disk creation, initialization, partition/format, and folder/share creation all completed without error. However, every time I try to create a new VM, it fails with permission errors. Can't seem to figure out where I have gone wrong.
Any help would be greatly appreciated.
Thanks,

[Boris (staff)]

What privileges have you got in the environment? What type of account do you use? Can you reproduce the steps?

[jhemphi]

Thanks for your reply.
I am a system administrator on the domain and I am using an account with full administrator privileges (member of both 'domain admins' and 'enterprise admins') however I am not using the actual "administrator" account.
I am using the VSan Free and StarwindX library with Powershell for administration of Starwind and a separate Win 10 Pro machine that is domain joined for other administration. Hyper-V servers are Server 2016 Core.

[Boris (staff)]

Any information on the steps you make to reproduce this permission issue?

[jhemphi]

I used the guide "Hyperconverged 2-Node Scenario with Hyper-V Server 2016". Where the guide starts with Starwind Management Console, I used Powershell commands and the guidance from the samples in CreateHA(two nodes).ps1.

[Boris (staff)]

I am generally interested in the Hyper-V part, as you've got the StarWind part of the environment up and running just fine.
In what way do you create VMs? What are the steps that you follow? This is the information I initially meant to request.