S2D Hyperconverged

• Scenario Description
• Scenario requirements
• Screenshots
  • Howto
  • Result
• How it looks like end-to-end (when you just paste the script).

Scenario Description

Note: Scenario is bit obsolete. Use AzSHCI Deployment Scenario for deployment instead (just skip Azure Registration)

• In this scenario 2-16 node S2D cluster can be created.
• It is just simulation "how it would look like". Performance is not a subject here - it is just to test look and feel
• Script is well tested, on both real and simulated environments. However if you need assist, ask your Premier Field Engineer
• you can also use Nano Servers (its eating less resources). However as communicated here, our focus is Core Server for physical infrastructure servers
• Deploy script finishes in ~5 minutes. Scenario script finishes in ~37 minutes.
• S2D Cluster Validation Report

Scenario requirements

• Windows 10 1511 with enabled Hyper-V or Windows 10 1607+ (if nested virtualization is enabled)
• 8GB Memory or 20GB if nested virtualization is used (for 4 node configuration)
• SSD (with HDD it is really slow)

Screenshots

Howto

Deploy.ps1 result

Collapsed scenario script in DC (ctrl+m)

Script configuring the scenario (copied to PowerShell script just by right-clicking into the window)

Result

Scenario script finished in 37minutes

Server Manager (you need to add servers manually)

Failover Cluster Manager Summary

Failover Cluster Manager Roles

Failover Cluster Manager Nodes

Failover Cluster Manager Disks

Failover Cluster Manager Pool

Failover Cluster Manager Networks

How it looks like end-to-end (when you just paste the script).

Note, there are small differences as I did it a while ago.