Search
The Best Hyperconverged Infrastructure (HCI) for Enterprise ROBO, SMB & Edge

Should Windows Server where StarWind VSAN is installed be included into a domain?

Explanation

A Windows domain is a form of a computer network in which all user accounts, computers, printers and other security principals, are registered with a central database.

https://msdn.microsoft.com/en-us/library/aa746492(v=vs.85).aspx

StarWind VSAN  itself doesn’t require domain, however in hyper-converged scenario with Hyper-V environments the servers require to be the part of it in order to create the failover cluster.

The domain itself can be configured on physical or virtual machine. Please follow the recommendation in KB article on how to place a DC in case of StarWind Virtual SAN usage.

Request a Product Feature

To request a new product feature or to provide feedback on a StarWind product, please email to our support at support@starwind.com and put “Request a Product Feature” as the subject.

Hey! Looking for a reliable, high-performance, and cost-effective shared storage solution for your production cluster?
Dmytro Malynka
Dmytro MalynkaStarWind Virtual SAN Product Manager
We’ve got you covered! StarWind Virtual SAN (VSAN) is specifically designed to provide highly-available shared storage for Hyper-V, vSphere, and KVM clusters. With StarWind VSAN, simplicity is key: utilize the local disks of your hypervisor hosts and create shared HA storage for your VMs. Interested in learning more? Book a short StarWind VSAN demo now and see it in action!