HyperV

Overview Switch Embedded Teaming (SET) is technology used for network interface card (NIC) teaming in Windows Server with utilizing the HyperV networking stack. Here is the comparataion of the Switch Embedded Teaming (SET) with LBFO (Load Balance and Failover) mode. Switch Embedded Teaming (SET) Introduced in: Windows Server 2016. Purpose: Designed specifically for use with Hyper-V and Software Defined Networking (SDN) environments. Features: Integration with Hyper-V: SET is deeply integrated with the Hyper-V Virtual Switch, allowing virtual NICs (vNICs) for VMs to directly use the teaming capabilities....

If you want to check the Block Size / Allocation Unit on Windows, you can use the following powershell command: Check volumes blocksize. Get-CimInstance -ClassName Win32_Volume | Select-Object Name,Filesystem,Label,Blocksize | Sort-Object Name | Format-Table -AutoSize Get-WmiObject -Class Win32_Volume -ComputerName $env:COMPUTERNAME | Select BlockSize,Name,FileSystem | Format-Table -AutoSize Check partitions blocksize and StartingOffset. Get-WmiObject -Class Win32_DiskPartition -ComputerName $env:COMPUTERNAME | select Name, NumberOfBlocks, Size, StartingOffset, Blocksize | Format-Table -AutoSize Check only the CSV (Cluster shared volume) on the Hyper-V Cluster Get-CimInstance -ClassName Win32_Volume | where {$_....

Network Design And IP Plan Management: 10.0.10.0/24 -> For comunication between Servers. Heartbeat: 10.0.11.0/24-> For comunication between cluster nodes. SAN: 10.0.8.0/27 or /24 -> For comunication to the SAN storage. Server Name Management IP SAN1 IP SAN2 IP HeartBeat IP SAN Storage 10.0.10.8 10.0.8.5 10.0.8.6 10.0.8.7 10.0.8.8 CA-HVC0 10.0.10.10 - - - CA-HVC01 10.0.10.11 10.0.8.11 10.0.8.21 10.0.11.11 CA-HVC02 10.0.10.12 10.0.8.12 10.0.8.22 10.0.11.12 CA-HVC03 10.0.10.13 10.0.8.14 10.0.8.23 10.0.11.13 Requirement You need at least 3 servers with the same hardware specification with 64 bit processors supports a virtualization Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology....

Overview Windows 2019/2022 has builtin iSCSI target server role, which allows Windows to host storage for other devices over a network. Here’s a step-by-step guide to set up a Windows Server 2022 machine as an iSCSI target server: Step 1: Install the iSCSI Target Server Role Install-WindowsFeature FS-iSCSITarget-Server -IncludeManagementTools Restart the server to apply the changes. Step 2: Create and Configure an iSCSI Virtual Disk Create iscsi target name New-IscsiServerTarget -TargetName "iSCSITarget01" -InitiatorId @("IPAddress:10....

Case When encountering a storage, or server issue, you may observe VMs in the Hyper-V management console that lack configuration files, and its associated VM disk. However, the VMs remain logged and visible in the HyperV Manager console. Attempts to remove these VMs might fail due to no Delete option. In the Hyper-V management console, these VMs typically appear in a Saved state with the error message: Cannot connect to virtual machine configuration storage...

Get-VM | select -ExpandProperty NetworkAdapters | select VMname, IPAddresses

A command to get the VM list detail that includes the following: Get-VM: This command gets the virtual machines from one or more Hyper-V hosts Get-ClusterNode: This command to gets information about one or more nodes, or servers, in a failover cluster Get-VMProcessor: This command to get the CPU count on the Virtual Machine Get-VMNetworkAdapterVlan: This command gets the virtual LAN settings configured on a virtual network adapter. Get-VMNetworkAdapter: This command to gets the Virtual Network Adapter on the VM...

If you have the need to move multiple VM disks on a stand-alone Hyper-V server or Hyper-V cluster server, this script may help you move them. If you perform manually VM disk migration for multiple VM, you will need to finish the one VM first before you can proceed to the next VM. Hence, this can prevent you from waiting as the script will handle it and move to the next VM disks....

Get VHD location: Get-VM -VMName $vmname | Select-Object VMId | Get-VHD Get VM Size Get-VM -VMName vmname | Select-Object VMId | Get-VHD | select vhdtype,path,@{label='Size(GB)';expression={$_.filesize/1gb -as [int]}} Get-VM | Select-Object VMId | Get-VHD | select vhdtype,path,@{label='Size(GB)';expression={$_.filesize/1gb -as [int]}} On Cluster Get-VM -ComputerName (Get-ClusterNode) | ForEach-Object {Get-VHD -ComputerName $_.ComputerName -VMId $_.VMId} | Select -Property path,computername,vhdtype,@{label='Size(GB)';expression={$_.filesize/1gb -as [int]}}