feat(win): update documentation for win 2022 (#5191)

* feat(win): update documentation for win 2022

* feat(em): win 2022

* Update pages/elastic-metal/how-to/use-private-networks.mdx

Co-authored-by: Néda <[email protected]>

---------

Co-authored-by: Néda <[email protected]>

Author: bene2k1

pages/elastic-metal/how-to/use-private-networks.mdx

@@ -155,17 +155,61 @@ You must configure the virtual network interface on each Elastic Metal server yo
     <Message type="important">
       Two network interfaces display: Your VLAN and `default`. Make sure to keep the default network, otherwise you will lose access to your server via the public internet.
     </Message>
-7. Click **Start** > **Execute** and type `ncpa.cpl`. Then click **OK** to open the network connection manager.
-8. Click on your VLAN network connection and right-click on it to open the menu. Click **Properties** to display the connection properties.
-9. Select **Internet Protocol version 4 (TCP/IPv4)** and click **Properties**. A pop-up displays.
-10. Click **Use the following IP address** and configure the IPv4 configuration of your Private Network. Then click **OK** to save your configuration.
-11. Click **Close** to close the network interface properties.
 
-    You completed the configuration of your Private Network on Windows Server 2019.
+### Static IP configuration (optional)
+
+<Message type="important">
+  If you are running multiple virtual machines on an Elastic Metal server, our managed DHCP is not currently able to distribute IP addresses to your virtual machines. We recommend that you use the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/) to book IP addresses for your virtual machines, and assign them manually.
+</Message>
+
+1. Click **Start** > **Run** and type `ncpa.cpl`. Then click **OK** to open the network connection manager.
+2. Click on your VLAN network connection and right-click on it to open the menu. Click **Properties** to display the connection properties.
+3. Select **Internet Protocol version 4 (TCP/IPv4)** and click **Properties**. A pop-up displays.
+4. Click **Use the following IP address** and configure the IPv4 configuration of your Private Network. Then click **OK** to save your configuration.
+    <Message type="tip">
+      To know what netmask and IP address to configure, refer to the **Private Network** menu for your Elastic Metal server in the Scaleway console.
+    </Message>
+5. Click **Close** to close the network interface properties.
+
     <Message type="tip">
       You can use the `ipconfig` command to verify your IP configuration from a command prompt.
     </Message>
 
+### Additional configuration for virtual machines running on Hyper-V
+
+If you are running virtual machines with Hyper-V, refer to the Microsoft documentation regarding [Hyper-V and VLANs](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/configure-virtual-local-area-networks-for-hyper-v).
+
+<Message type="note">
+  Since Windows Server 2022 came out, the procedure differs from Windows 2019. LBFO (a Hyper-V switch related to NIC teaming) has been deprecated and replaced by SET (Switch Embedded Teaming).
+  This change may introduce limitations regarding VLAN assignment for multiple VMs on clusters of Elastic Metal servers.
+</Message>
+
+Below is an example of how to connect one Private Network to a virtual machine created by Hyper-V on a Windows Server 2022 host (the Elastic Metal server's operating system).
+
+1. Open a PowerShell terminal and run the following command:
+    ```powershell
+    Get-NetAdapter
+    ```
+    <Message type="important">
+      Do not enable NIC Teaming on the host.
+    </Message>
+    This command will display the network interface names. Copy the name of the interface that is "Up".
+
+2. Create a new VMSwitch:
+    ```powershell
+    New-VMSwitch -Name "SET Team" -NetAdapterName "<NAME OF THE NETWORK INTERFACE>" -EnableEmbeddedTeaming $true
+    ```
+
+3. Create a "custom" resource in the [Private Network](/vpc/how-to/attach-resources-to-pn/).
+
+4. When creating the VM, select the SET switch in the networking creation menu.
+
+5. Copy the MAC address of the VM from the **Network adapter** section of the VM settings, under the **Advanced features** subsection.
+
+6. Change the Virtual Machine settings:
+   - Go to the "Network adapter" section of the VM in Hyper-V.
+   - Set the VLAN ID (copy it from the **Private Network** menu in the Elastic Metal server console).
+
 ## How to delete a Private Network
 
 <Message type="note">