Hyper-converged solution in Windows Server
  • Introduction
  • Intro
    • Introduction
    • Requirements
    • Topology
  • Preparing the servers
    • Server 1: The Domain Controller
    • Prepping the 2 HC servers
    • Server 2: HyperConvergence 1
    • Server 3: HyperConvergence 2
  • Set up the Fail over cluster with storage spaces direct
    • Test the cluster
    • Build the cluster
    • Add a cluster witness
    • Clean the disks
    • Enable storage spaces direct
    • Create cluster-volumes
  • Setup Hyper-V and test
    • The next steps
    • Edit Hyper-V Paths
    • Create a High Available VM
    • Test it
    • Where to go from here
  • Extra
    • Add a 3rd node
Powered by GitBook
On this page

Was this helpful?

  1. Set up the Fail over cluster with storage spaces direct

Build the cluster

PreviousTest the clusterNextAdd a cluster witness

Last updated 5 years ago

Was this helpful?

was a bit unclear in my opinion and so was the page. So anyway this is what I learned from this:

  • The "name" is a netbios name, so should be less than 15 characters long

  • The staticaddress is the adress you will give to the cluster.

So, execute this cmdlet.

New-Cluster –Name MyFirstCluster –Node HC1,HC2 –NoStorage -StaticAddress 192.168.1.15

You might get a warning:

All in all, if you check the logs and the clusterwitness is the cause of the error, there shouldn't be any concern:

Our next step will be to configure the cluster witness.

Also, when in doubt, just verify!

The original Microsoft guide
new-cluster cmdlet