• What we are going to set up – Total 5 Servers as minimum setup.
    • Inernet Accessible network connected over 1GbE LAN.
    • x1 – Windows Server 2022 AD Server
      • Install AD.
      • Install DNS with integration mode.
      • Install DHCP (If the DHCP server does not exist in Service network.)
      • Option: MDT for Auto build
    • x1- Windows Server 2022 iSCSI / RDS Server (Broker / Session Tunnel / RD Web)
      • Install iSCSI Target to provide the iSCSI virtual SAN disk over dedicated TCP/IP LAN.
      • Windows RDS service core controller as Broker / Session Tunnel Server and RD Web Server.
      • iSCSI Server role server is to be expanded per the demand of Storage Capacity.
      • Or Internal Disk may need to be added/upgrade with more sufficient capacity Disk.
    • x3 – Windows Server 2022 Failover Cluster via 3 Node Hyper-V / RDS session host.
      • Hyper-V virtualization Platform Server for VDI and Test lab Servers.
      • Connect to iSCSI Virtual SAN Disk via Failover Cluster shared volume to store HA VDI/VM Servers.
      • RDS Session host to allow the VDI Service via Windows Remote Desktop Service.
      • Node for Failover can be expanded as per the demand capacity.
      • For setting up the internal network zone A/B for enclosed area so that you can test anything in segregated environment, add additional NIC to these machines and connect these machines in Switch.
    • Logical Diagram

    • Physical Setup Diagram

    • Network parameter (example)
      • Lab Service Network
        • IP Segment – 192.168.100.0/24
        • DNS Server – 192.168.100.10 (This IP address is to be assigned to AD Role Server)
        • Gateway – 192.168.100.254 (This IP address is to be assigned to Internet GW router LAN Address)
        • DNS Suffix – in this example: “examplekawasakilab.net”
      • iSCSI Virtual SAN Network
        • IP Segment – 172.17.0.0/24
        • DN Server – To be Empty
        • Gateway – To be Empty

Steps 1

  • Build 5 Windows 2022 Servers with Laptop
    • Example – DELL Lattitude 5300.
      • 2 ~ 3 USB 3.0 (3.2 gen1 or greater) ports (A or C)
      • Working battery (For flexibility of hardware handling)
      • Display – At least the recognizable what is in screen.
      • Working 1GB internal NIC
      • CPU – Gen 8 or greater with up to 8 CPU (When Hyperthreading turned on)
      • Memory – can be up to 32GB or more.
        Example: Set of 16GB x 2 modules = total 32GB.
      • Keyboard – to be working but, external keyboard can help if broken.
      • Internal SSD (M.2 SSD, 2,5inch SSD or PCIE SSD) capacity to be more than 100GB.
        The machine already has enough SSD disk.

        “One machine” will be used as Storage Server – to be upgraded to 1 TB or greater capacity.
        Example:

      • USB high speed 2nd NIC is to be added and connected to the GbE switch (2.5GbE switch preferred). The machine has 2 USB port and USB-C port. In total, it can have at least 3 NICs as additional. (If you use the USB-C high speed HUB, you can extend more.)
        • Example
        • Preferred: USB 3.2 Gen1接続 2.5GbE LANアダプター ETQG-US3
        • 1GbE: TP-Link USB to Ethernet Adapter (UE306)
        • Even USB-C compatible NIC is fine.
      • Site for purchase the best price Reused Machine.
        中古パソコン通販専門店 Be-Stock
        Example:

        *Obtain the Switch accordingly. 1GB home hub is very cheap in market. 2.5GB hub started available in these days. Consider 2.5GB switch for iSCSI. Other network can go with 1GB.
    • Installation Spec
      • C drive to be set up with 100GB of internal Disk.
      • Set the initial password properly.
      • License activation is NOT mandatory
    • Post installation
      • Install Driver properly.
      • Upgrade all drivers especially NIC which is Realtech chip.
      • Assign IP address tentatively so that Machine can access to internet.
      • Apply all Windows Update.
      • Virtual memory (Page file) size has to be properly adjusted.
      • At initial step, turn off the Firewall.
      • To make the later adjustment easy, Remote Desktop is turned on for any level of protocol security.
      • Disable unnecessary any restrictions as much as possible.
      • Adjust timezone and time.
  • Configure IP network on All Machines
    • Internal NIC
      • Disable IPv6.
      • Configure IP address.
        • AD Server – 192.168.100.10
        • iSCSI Server – 192.168.100.5
        • Hyper-V node 1~3 – 192.168.100.21,22,23
      • Configure DNS Suffix
        • examplekawasakilab.net
    • USB NIC
      • Disable all services except TCP/IPv4
      • Configure IP address.
        • iSCSI Server – 172.17.0.254
        • Hyper-V node 1~3 – 172.17.0.1,2,3
  • Name to all servers
    • AD Server – KSWSAD0001
    • iSCSI Server – KSWSIS0002
    • Hyper-V node 1~3 – KSWSHV0001,0002,0003

Step 2

  • Install Active Directory Services and DNS server role into AD Server
    • Configure the AD via the following parameters
      • Domain name: examplekawasakilab.net
      • NT Domain name: EXAMPLEKAWASAKI

    • Configure DNS as AD integrated mode.
      • Create reverse lookup zone for 192.168.100.0/24 segment.
      • Confirm the AD DNS can support IP lookup against the Internet Access.
        >nslookup
        #Server 192.168.100.10
        #www.dell.com
        #<exmpected outcome will be displayed>
    • Optionally – Install DHCP server and activate new scope for Service Network IP management.
      • Scope name – 192.168.100.0/24
      • lease range – 192.168.100.100 to 192.168.100.200
      • DNS server – 192.168.100.10
      • Default Gateway – 192.168.100.254
  • Create AD OU (OrganizationalUnit) Structure, operator account and delegate the operation roles accordingly.
    • At the top, create “Resources”.
    • Under “Resources”, create “Users”, “Computers” and “Groups”.
    • Under “Users”, create “HumanAccounts” and “NonHumanAccounts”.
      • Place any normal user account such as Lab user into “HumanAccounts”.
      • Any other type of non-human account is placed into “NonHumanAccounts”
    • Under “Computers”, create “Workstations”, “VirtualNode” and “Servers”.
      • VDI, Client Type PC Computer object will be placed into “Workstations”.
      • Servers are to be placed into “Servers”.
      • Virtual node object such as Cluster Virtual computer object should be placed into “Virtual Node”
    • Under Groups, create “Access Control”, “Distribution Lists” and “Generic”.
      • File Permission and similar Access Control group is placed into “Access Control”.
      • Email Distribution List is to be created into “Distribution Lists”. (Mail enabled group).
      • Any other purpose group can be stored into Generic.
  • Getting all member servers joined into Domain.
    • Make sure all member servers (iSCSI Server, Hyper-V node servers) have DNS configured properly.
    • Join to domain and restart. Confirm you can log into the member nodes via domain administrator account.
    • At the AD OU, relocate all Computer objects from Computers into “OU=Resources,OU=Computers,OU=Servers”

Step 3

  • Configure Storage and Enable iSCSI Target role in iSCSI Server
    • Assign the 1 simple NTFS volume to unused Disk space (900GB expected).
    • Install iSCSI target role.
    • Create virtual disk file (you can use Dynamic expansion mode) into iSCSI storage volume and publish it to iSCSI target over 172.17.0.0 network for 172.17.0.1~3 iSCSI consumer.
  • Enable Hyper-V Role, Failover Cluster feature in all Hyper-V node servers
  • Enable iSCSI initiator on all Hyper-V node servers.
    • Connected to iSCSI target server.
    • Check disk is visible.
    • Make the iSCSI target brought up on line at 1 node.
    • From Computer management -> Disk management, get it initialized and format via NTFS.
    • Bring it to offline for now.
  • Start creating the cluster virtual node.
    • name – hypervCluster01
    • IP address- 192.168.100.15
    • Make sure Add all eligible storage to the cluster is turned off.
    • Complete the setup.
    • Add remaining node to Cluster.
    • Add storage strage to Available Storage, click storage and “Add to Cluster Shared Volumes“.
    • Confirm the storage is mounted into c:\clusterStorage\Volume1
    • Test creating the virtual machine empty box from Failover Cluster -> Roles.
  • Adjust “Host Guradian” via article.
    “HostGuradianService” issue in Hyper-V Live migration? – Avalon Lab Infrastructure Tech Forum (toshitoshi.net)

Step 4

Step5

  • Setup your external connection
    • DNS
    • Router setup for NAPT forwarding the traffic from outside to your Internal RDS Server.
  • Provide the Certificate to the Client PC accessing to VDI via RDS from External.