Switch branches/tags
Nothing to show
Find file History
Latest commit ab4c7fe Oct 6, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
MultiNodeConfig.psd1 SDNExpress Scenario Added Aug 28, 2018
Scenario.ps1 RDMA naming Oct 6, 2018
readme.md Big cleanup - removed 1709, serverVHDs var, client creation... Oct 4, 2018


About Scenario

Author: Andreas Sobczyk / CloudMechanic.net / Twitter /

Description and requirements

  • In this scenario SDNv2 without VMM can be created and deployed from scratch nested in one Hyper-V host

  • Script is tested only for this specific nested scenario

  • Works with Windows Server 2016 and 2019

  • Require around 100GB memory and 300GB disk space



$LabConfig=@{ DomainAdminName='LabAdmin'; AdminPassword='LS1setup!'; Prefix = 'SDNExpress2019-'; SecureBoot=$false; SwitchName = 'LabSwitch'; DCEdition='4'; VMs=@();InstallSCVMM='No'; PullServerDC=$false;  Internet=$true;AllowedVLANs="1-400"; AdditionalNetworksInDC=$true; AdditionalNetworksConfig=@(); EnableGuestServiceInterface=$true}
$LABConfig.AdditionalNetworksConfig += @{ 
        NetName = 'HNV';

1..4 | % { 
    $LABConfig.VMs += @{
        VMName = "$VMNames$_" ;
        Configuration = 'S2D' ;
        ParentVHD = 'Win2016Core_G2.vhdx';
        SSDNumber = 2;
        SSDSize=800GB ;
        HDDNumber = 4;
        HDDSize=4TB ;
        MemoryStartupBytes= 20GB;
        VMProcessorCount = 6

$LABConfig.VMs += @{
        VMName = "Management" ;
        Configuration = 'S2D' ;
        ParentVHD = 'Win2016_G2.vhdx';
        SSDNumber = 1;
        SSDSize=50GB ;
        MemoryStartupBytes= 2GB;
        VMProcessorCount = 2


Tip: When prompt for the VHDX, select the same as you used for the hosts

The script is devided in two parts, first part should be run from the Hyper-V host, second part should be run from the DC

For detailed guidance go to: https://cloudmechanic.net/2018/08/29/deploying-a-sdnv2-lab-on-a-single-host-using-nested-hyper-v/

Part 1

  • Select the VHDX to be used for the SDN VMs
  • Select the MultiNodeConfig.psd1 file
  • Select the Windows Admin Center MSI file (1806+)

Part 2

Copy the second part of the script to the Management VM and execute it.

Known Issues

  • SDN VMs not join to the domain, especially the gateway VMs seems to have problems, if this happens use the Hyper-V Manager console on the Management VM to connect to HV1 or HV2 or HV3 and domain join the VMs manually with SCONFIG to corp.contoso.com.
  • Doing deployment the SLB MUXs is timing out on WinRM, if this happens just rerun the SDNExpress deployment script again and it should continue, the SDNExpress script is made to be rerun if any errors occur.
  • Gateways needs to be rebooted after RemoteAccess is installed, if this happens use the Hyper-V Manager console on the Management VM to connect to HV1 or HV2 and restart the related Contoso-GW VM, then rerun the SDNExpress deployment script.