From 782f4e8c842c5e83088626c04f622153ede63ede Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Tue, 2 Sep 2025 14:12:01 +0200
Subject: [PATCH 01/10] Update deployment-virtual.md

1. consolidating virtual disks which was partly 6 and partly 4.

2. the new requirements allow deployments with only 2 disks.
---
 azure-local/deploy/deployment-virtual.md | 12 +++---------
 1 file changed, 3 insertions(+), 9 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index d0cbec43d9..aaa7669727 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -187,26 +187,20 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
     Set-VmProcessor -VMName "Node1" -Count 8
     ```
 
-1. Create extra drives to be used as the boot disk and hard disks for Storage Spaces Direct. After these commands are executed, six new VHDXs will be created in the `C:\vms\Node1` directory as shown in this example:
+1. Create extra drives to be used as the boot disk and hard disks for Storage Spaces Direct. After these commands are executed, two new VHDXs will be created in the `C:\vms\Node1` directory as shown in this example:
 
    ```PowerShell
     new-VHD -Path "C:\vms\Node1\s2d1.vhdx" -SizeBytes 1024GB
     new-VHD -Path "C:\vms\Node1\s2d2.vhdx" -SizeBytes 1024GB
-    new-VHD -Path "C:\vms\Node1\s2d3.vhdx" -SizeBytes 1024GB
-    new-VHD -Path "C:\vms\Node1\s2d4.vhdx" -SizeBytes 1024GB
-    new-VHD -Path "C:\vms\Node1\s2d5.vhdx" -SizeBytes 1024GB
-    new-VHD -Path "C:\vms\Node1\s2d6.vhdx" -SizeBytes 1024GB
-    ```
+   ```
 
-1. Attach drives to the newly created VHDXs for the VM. In these commands, six VHDs located in the `C:\vms\Node1` directory and named `s2d1.vhdx` through `s2d6.vhdx` are added to `Node1`. Each `Add-VMHardDiskDrive` command adds one VHD to the VM, so the command is repeated six times with different `-Path` parameter values.
+1. Attach drives to the newly created VHDXs for the VM. In these commands, two VHDs located in the `C:\vms\Node1` directory and named `s2d1.vhdx` through `s2d6.vhdx` are added to `Node1`. Each `Add-VMHardDiskDrive` command adds one VHD to the VM, so the command is repeated six times with different `-Path` parameter values.
 
     Afterwards, the `Node1` VM has four VHDs attached to it. These VHDXs are used to enable Storage Spaces Direct on the VM, which are required for Azure Stack HCI deployments:
 
    ```PowerShell
     Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\s2d1.vhdx"
     Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\s2d2.vhdx"
-    Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\s2d3.vhdx"
-    Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\s2d4.vhdx"
     ```
 
 1. Disable time synchronization:

From 30405020cb67ed4fc0da32dbe96340f015089bc2 Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Tue, 2 Sep 2025 14:14:50 +0200
Subject: [PATCH 02/10] Update deployment-virtual.md

added OS disks
---
 azure-local/deploy/deployment-virtual.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index aaa7669727..5ed3e8cae1 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -190,15 +190,17 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
 1. Create extra drives to be used as the boot disk and hard disks for Storage Spaces Direct. After these commands are executed, two new VHDXs will be created in the `C:\vms\Node1` directory as shown in this example:
 
    ```PowerShell
+    new-VHD -Path "C:\vms\Node1\OS.vhdx" -SizeBytes 127GB
     new-VHD -Path "C:\vms\Node1\s2d1.vhdx" -SizeBytes 1024GB
     new-VHD -Path "C:\vms\Node1\s2d2.vhdx" -SizeBytes 1024GB
    ```
 
-1. Attach drives to the newly created VHDXs for the VM. In these commands, two VHDs located in the `C:\vms\Node1` directory and named `s2d1.vhdx` through `s2d6.vhdx` are added to `Node1`. Each `Add-VMHardDiskDrive` command adds one VHD to the VM, so the command is repeated six times with different `-Path` parameter values.
+1. Attach drives to the newly created VHDXs for the VM. In these commands, two VHDs located in the `C:\vms\Node1` directory and named `s2d1.vhdx` through `s2d2.vhdx` are added to `Node1`. Each `Add-VMHardDiskDrive` command adds one VHD to the VM, so the command is repeated six times with different `-Path` parameter values.
 
-    Afterwards, the `Node1` VM has four VHDs attached to it. These VHDXs are used to enable Storage Spaces Direct on the VM, which are required for Azure Stack HCI deployments:
+    Afterwards, the `Node1` VM has two VHDs attached to it. These VHDXs are used to enable Storage Spaces Direct on the VM, which are required for Azure Stack HCI deployments:
 
    ```PowerShell
+    Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\OS.vhdx"
     Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\s2d1.vhdx"
     Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\s2d2.vhdx"
     ```

From be9f8cd340c0b7873d630b553231290abe334ce2 Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Tue, 2 Sep 2025 14:23:28 +0200
Subject: [PATCH 03/10] Update deployment-virtual.md

rename Azure Stack HCI to Azure Local (even though the OS is not renamed but it is so confusing)
corrected information about number of disks as I forgot to mention and count OS disk in previous PR.
---
 azure-local/deploy/deployment-virtual.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index 5ed3e8cae1..1b94e44ed1 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -1,5 +1,5 @@
 ---
-title: Deploy a virtual Azure Local, version 23H2 system
+title: Deploy a virtual Azure Local, version 23H2 / 24H2 system
 description: Describes how to perform an Azure Local, version 23H2 virtualized deployment.
 author: alkohli
 ms.author: alkohli
@@ -52,10 +52,10 @@ Before you begin, make sure that each virtual host system can dedicate the follo
 | ----------| ------- |
 | Virtual machine (VM) type | Secure Boot and Trusted Platform Module (TPM) enabled. |
 | vCPUs | Four cores. |
-| Memory | A minimum of 24 GB. |
+| Memory | A minimum of 32 GB. |
 | Networking | At least two network adapters connected to internal network. MAC spoofing must be enabled. |
-| Boot disk | One disk to install the Azure Stack HCI operating system from ISO. At least 200 GB. |
-| Hard disks for Storage Spaces Direct | Four dynamic expanding disks. Maximum disk size is 1024 GB. |
+| Boot disk | One disk to install the Azure Local operating system from ISO. At least 127 GB. |
+| Hard disks for Storage Spaces Direct | Two dynamic expanding disks. Maximum disk size is 1024 GB. |
 | Data disks | At least 127 GB each. The size must be the same for each disk. |
 | Time synchronization in integration  | Disabled. |
 
@@ -117,7 +117,7 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
 
     ```PowerShell
     New-VHD -Path "your_VHDX_path" -SizeBytes 127GB
-    New-VM -Name Node1 -MemoryStartupBytes 20GB -VHDPath "your_VHDX_path" -Generation 2 -Path "VM_config_files_path"
+    New-VM -Name Node1 -MemoryStartupBytes 32GB -VHDPath "your_VHDX_path" -Generation 2 -Path "VM_config_files_path"
     ```
 
 1. Disable dynamic memory:
@@ -187,7 +187,7 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
     Set-VmProcessor -VMName "Node1" -Count 8
     ```
 
-1. Create extra drives to be used as the boot disk and hard disks for Storage Spaces Direct. After these commands are executed, two new VHDXs will be created in the `C:\vms\Node1` directory as shown in this example:
+1. Create extra drives to be used as one for boot disk and two hard disks for Storage Spaces Direct. After these commands are executed, three new VHDXs will be created in the `C:\vms\Node1` directory as shown in this example:
 
    ```PowerShell
     new-VHD -Path "C:\vms\Node1\OS.vhdx" -SizeBytes 127GB
@@ -197,7 +197,7 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
 
 1. Attach drives to the newly created VHDXs for the VM. In these commands, two VHDs located in the `C:\vms\Node1` directory and named `s2d1.vhdx` through `s2d2.vhdx` are added to `Node1`. Each `Add-VMHardDiskDrive` command adds one VHD to the VM, so the command is repeated six times with different `-Path` parameter values.
 
-    Afterwards, the `Node1` VM has two VHDs attached to it. These VHDXs are used to enable Storage Spaces Direct on the VM, which are required for Azure Stack HCI deployments:
+    Afterwards, the `Node1` VM has two VHDs attached to it. These VHDXs are used to enable Storage Spaces Direct on the VM, which are required for Azure Local deployments:
 
    ```PowerShell
     Add-VMHardDiskDrive -VMName "Node1" -Path "C:\vms\Node1\OS.vhdx"
@@ -225,7 +225,7 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
 
 ## Install the OS on the virtual host VMs
 
-Complete the following steps to install and configure the Azure Stack HCI OS on the virtual host VMs:
+Complete the following steps to install and configure the Azure Local OS on the virtual host VMs:
 
 1. [Download version 23H2 operating system for Azure Local deployment](./download-23h2-software.md) and [Install the Azure Stack HCI operating system](deployment-install-os.md).
 

From 5ee0e4af45b425a354d72cd874b02e6fdc503ebc Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Mon, 22 Sep 2025 16:28:28 +0200
Subject: [PATCH 04/10] Aktualisieren von deployment-virtual.md

Bold text,because validation will fail when not set. The idea was that it's only necessary on adapters when teamed but that's not the case.
---
 azure-local/deploy/deployment-virtual.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index 1b94e44ed1..e07fbfdf8c 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -153,7 +153,7 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
     Get-VmNetworkAdapter -VmName "Node1" |Connect-VmNetworkAdapter -SwitchName "virtual_switch_name"
     ```
 
-1. Enable MAC spoofing on all network adapters on VM `Node1`. MAC address spoofing is a technique that allows a network adapter to masquerade as another by changing its Media Access Control (MAC) address. This is required in scenarios where you're planning to use nested virtualization:
+1. Enable MAC spoofing *on all network adapters* on VM `Node1`. MAC address spoofing is a technique that allows a network adapter to masquerade as another by changing its Media Access Control (MAC) address. This is required in scenarios where you're planning to use nested virtualization:
 
     ```PowerShell
     Get-VmNetworkAdapter -VmName "Node1" |Set-VmNetworkAdapter -MacAddressSpoofing On

From 995c1a6411c9768959e6f2e9920cca661e6ebbb1 Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Mon, 22 Sep 2025 16:37:48 +0200
Subject: [PATCH 05/10] Aktualisieren von deployment-virtual.md

Added teaming
---
 azure-local/deploy/deployment-virtual.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index e07fbfdf8c..6c97478134 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -153,10 +153,12 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
     Get-VmNetworkAdapter -VmName "Node1" |Connect-VmNetworkAdapter -SwitchName "virtual_switch_name"
     ```
 
-1. Enable MAC spoofing *on all network adapters* on VM `Node1`. MAC address spoofing is a technique that allows a network adapter to masquerade as another by changing its Media Access Control (MAC) address. This is required in scenarios where you're planning to use nested virtualization:
+1. Enable MAC spoofing *on all network adapters* on VM `Node1`. MAC address spoofing is a technique that allows a network adapter to masquerade as another by changing its Media Access Control (MAC) address. 
+In addition we need to enable teaming *on all network adapters*, because NetworkATC will team vNICs for the management / compute intent, and depending on the configuration (storage switched) aswell on the storage vNICs.
+This is required in scenarios where you're planning to use nested virtualization:
 
     ```PowerShell
-    Get-VmNetworkAdapter -VmName "Node1" |Set-VmNetworkAdapter -MacAddressSpoofing On
+    Get-VmNetworkAdapter -VmName "Node1" |Set-VmNetworkAdapter -MacAddressSpoofing On -Allow Teaming On
     ```
 
 1. Enable trunk port (for multi-node deployments only) for all network adapters on VM `Node1`. This script configures the network adapter of a specific VM to operate in trunk mode. This is typically used in multi-node deployments where you want to allow multiple Virtual Local Area Networks (VLANs) to communicate through a single network adapter:

From 1c3b57fa6201c7c8da5f09e08aee146a29fbcd15 Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Mon, 22 Sep 2025 16:44:11 +0200
Subject: [PATCH 06/10] Aktualisieren von deployment-virtual.md

---
 azure-local/deploy/deployment-virtual.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index 6c97478134..b690ba3f35 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -19,7 +19,10 @@ This article describes how to deploy a virtualized Azure Local instance on a hos
 You need administrator privileges for the Azure Local virtual deployment and should be familiar with the existing Azure Local solution. The deployment can take around 2.5 hours to complete.
 
 > [!IMPORTANT]
-> A virtual deployment of Azure Local is intended for educational and demonstration purposes only. Microsoft Support doesn't support virtual deployments.
+> A virtual deployment of Azure Local is intended for educational and demonstration purposes only. 
+
+>NOTE
+>Microsoft Support doesn't support virtual >deployments.
 
 ## Prerequisites
 
@@ -227,7 +230,7 @@ This is required in scenarios where you're planning to use nested virtualization
 
 ## Install the OS on the virtual host VMs
 
-Complete the following steps to install and configure the Azure Local OS on the virtual host VMs:
+Complete the following steps to install and configure the Azure Stack HCI OS on the virtual host VMs:
 
 1. [Download version 23H2 operating system for Azure Local deployment](./download-23h2-software.md) and [Install the Azure Stack HCI operating system](deployment-install-os.md).
 

From 765bd02cd38d4a1847eeca17f7112272310b72df Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Mon, 22 Sep 2025 16:45:44 +0200
Subject: [PATCH 07/10] Aktualisieren von deployment-virtual.md

---
 azure-local/deploy/deployment-virtual.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index b690ba3f35..f5fd5d1745 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -57,7 +57,7 @@ Before you begin, make sure that each virtual host system can dedicate the follo
 | vCPUs | Four cores. |
 | Memory | A minimum of 32 GB. |
 | Networking | At least two network adapters connected to internal network. MAC spoofing must be enabled. |
-| Boot disk | One disk to install the Azure Local operating system from ISO. At least 127 GB. |
+| Boot disk | One disk to install the Azure Stack HCI operating system from ISO. At least 127 GB. |
 | Hard disks for Storage Spaces Direct | Two dynamic expanding disks. Maximum disk size is 1024 GB. |
 | Data disks | At least 127 GB each. The size must be the same for each disk. |
 | Time synchronization in integration  | Disabled. |

From 7ba1c1a4524e048cc8b342d0601fe6e7cf707f58 Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Mon, 22 Sep 2025 16:47:43 +0200
Subject: [PATCH 08/10] Aktualisieren von deployment-virtual.md

---
 azure-local/deploy/deployment-virtual.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index f5fd5d1745..9822124d0b 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -21,8 +21,8 @@ You need administrator privileges for the Azure Local virtual deployment and sho
 > [!IMPORTANT]
 > A virtual deployment of Azure Local is intended for educational and demonstration purposes only. 
 
->NOTE
->Microsoft Support doesn't support virtual >deployments.
+>[!NOTE]
+>Microsoft Support doesn't support virtual deployments.
 
 ## Prerequisites
 

From bbbf593fcbfcbde24bb1e30d90023c6063c28b9b Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Mon, 22 Sep 2025 16:52:00 +0200
Subject: [PATCH 09/10] Aktualisieren von deployment-virtual.md

Changes to system requirements table
---
 azure-local/deploy/deployment-virtual.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index 9822124d0b..32d3761b27 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -43,9 +43,9 @@ Before you begin, make sure that:
     | Component | Minimum |
     | ------------- | -------- |
     | Processor| Intel VT-x or AMD-V, with support for nested virtualization. For more information, see [Does My Processor Support Intel&reg; virtualization technology?](https://www.intel.com/content/www/us/en/support/articles/000005486/processors.html)
-    | Memory| The physical host must have a minimum of 32 GB RAM for single virtual node deployments. The virtual host VM should have at least 24 GB RAM.<br><br>The physical host must have a minimum of 64 GB RAM for two virtual node deployments. Each virtual host VM should have at least 24 GB RAM for deployment and 32 GB for applying updates.|
-    | Host network adapters| A single network adapter.|
-    | Storage| 1 TB Solid state drive (SSD). |
+    | Memory| The physical host must have a minimum of 48 GB RAM for single virtual node deployments. The virtual host VM should have at least 32 GB RAM.<br><br>The physical host must have a minimum of 72 GB RAM for two virtual node deployments. Each virtual host VM should have at least 32 GB RAM for deployment and for applying updates.|
+    | Host network adapters | A single network adapter. |
+    | Storage | 1 TB Solid state drive (SSD). |
 
 ### Virtual host requirements
 
@@ -60,7 +60,7 @@ Before you begin, make sure that each virtual host system can dedicate the follo
 | Boot disk | One disk to install the Azure Stack HCI operating system from ISO. At least 127 GB. |
 | Hard disks for Storage Spaces Direct | Two dynamic expanding disks. Maximum disk size is 1024 GB. |
 | Data disks | At least 127 GB each. The size must be the same for each disk. |
-| Time synchronization in integration  | Disabled. |
+| Time synchronization in integration | Disabled. |
 
 > [!NOTE]
 > These are the minimum requirements to successfully deploy Azure Local. Increase the capacity like virtual cores and memory when running actual workloads like virtual machines or containers.

From 10533cd62c5eb6c5fd89e4e9ae19665750d263e7 Mon Sep 17 00:00:00 2001
From: Karl Wester-Ebbinghaus <45657752+Karl-WE@users.noreply.github.com>
Date: Thu, 16 Oct 2025 22:14:24 +0200
Subject: [PATCH 10/10] Revise deployment instructions for Azure Local

Updated the title and improved clarity in the instructions regarding MAC address spoofing and teaming for network adapters.

added space after pipes |
---
 azure-local/deploy/deployment-virtual.md | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/azure-local/deploy/deployment-virtual.md b/azure-local/deploy/deployment-virtual.md
index 32d3761b27..0d05394d23 100644
--- a/azure-local/deploy/deployment-virtual.md
+++ b/azure-local/deploy/deployment-virtual.md
@@ -1,5 +1,5 @@
 ---
-title: Deploy a virtual Azure Local, version 23H2 / 24H2 system
+title: Deploy a virtual Azure Local, version 23H2 and 24H2 system
 description: Describes how to perform an Azure Local, version 23H2 virtualized deployment.
 author: alkohli
 ms.author: alkohli
@@ -19,9 +19,12 @@ This article describes how to deploy a virtualized Azure Local instance on a hos
 You need administrator privileges for the Azure Local virtual deployment and should be familiar with the existing Azure Local solution. The deployment can take around 2.5 hours to complete.
 
 > [!IMPORTANT]
+>
 > A virtual deployment of Azure Local is intended for educational and demonstration purposes only. 
 
+
 >[!NOTE]
+>
 >Microsoft Support doesn't support virtual deployments.
 
 ## Prerequisites
@@ -153,21 +156,22 @@ Follow these steps to create an example VM named `Node1` using PowerShell cmdlet
 1. Attach all network adapters to the virtual switch. Specify the name of the virtual switch you created, whether it was external without NAT, or internal with NAT:
 
     ```PowerShell
-    Get-VmNetworkAdapter -VmName "Node1" |Connect-VmNetworkAdapter -SwitchName "virtual_switch_name"
+    Get-VmNetworkAdapter -VmName "Node1" | Connect-VmNetworkAdapter -SwitchName "virtual_switch_name"
     ```
 
-1. Enable MAC spoofing *on all network adapters* on VM `Node1`. MAC address spoofing is a technique that allows a network adapter to masquerade as another by changing its Media Access Control (MAC) address. 
-In addition we need to enable teaming *on all network adapters*, because NetworkATC will team vNICs for the management / compute intent, and depending on the configuration (storage switched) aswell on the storage vNICs.
-This is required in scenarios where you're planning to use nested virtualization:
+1. Enable MAC address spoofing and teaming on all network adapters on VM Node1 if you plan to use nested virtualization.
+
+* MAC address spoofing lets a network adapter appear as another by changing its Media Access Control (MAC) address.
+* NetworkATC teams vNICs for management and compute intent, and, depending on the configuration, for storage vNICs.
 
     ```PowerShell
-    Get-VmNetworkAdapter -VmName "Node1" |Set-VmNetworkAdapter -MacAddressSpoofing On -Allow Teaming On
+    Get-VmNetworkAdapter -VmName "Node1" | Set-VmNetworkAdapter -MacAddressSpoofing On -Allow Teaming On
     ```
 
 1. Enable trunk port (for multi-node deployments only) for all network adapters on VM `Node1`. This script configures the network adapter of a specific VM to operate in trunk mode. This is typically used in multi-node deployments where you want to allow multiple Virtual Local Area Networks (VLANs) to communicate through a single network adapter:
 
     ```PowerShell
-    Get-VmNetworkAdapter -VmName "Node1" |Set-VMNetworkAdapterVlan -Trunk -NativeVlanId 0 -AllowedVlanIdList 0-1000
+    Get-VmNetworkAdapter -VmName "Node1" | Set-VMNetworkAdapterVlan -Trunk -NativeVlanId 0 -AllowedVlanIdList 0-1000
     ```
 
 1. Create a new key protector and assign it to `Node1`. This is typically done in the context of setting up a guarded fabric in Hyper-V, a security feature that protects VMs from unauthorized access or tampering.