edits

Author: mburke5678

modules/creating-the-vsphere-windows-vm-golden-image.adoc

@@ -19,7 +19,9 @@ You must use link:https://docs.microsoft.com/en-us/powershell/scripting/install/
 
 .Procedure
 
-. Create a new VM in the vSphere client using the Windows Server Semi-Annual Channel (SAC): Windows Server 20H2 ISO image that includes the link:https://support.microsoft.com/en-us/help/4565351/windows-10-update-kb4565351[Microsoft patch KB4565351]. This patch is required to set the VXLAN UDP port, which is required for clusters installed on vSphere. See the link:https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html[VMware documentation] for more information.
+.  Select a compatible Windows Server version. Currently, the Windows Machine Config Operator (WMCO) stable version supports Windows Server 2022 Long-Term Servicing Channel with the OS-level container networking patch link:https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d[KB5012637].
+
+. Create a new VM in the vSphere client using the VM golden image with a compatible Windows Server version. For more information about compatible versions, see the "Windows Machine Config Operator prerequisites" section of the "Red Hat OpenShift support for Windows Containers release notes."
 +
 [IMPORTANT]
 ====

modules/windows-machineset-aws.adoc

@@ -80,7 +80,7 @@ $ oc get -o jsonpath='{.status.infrastructureName}{"\n"}' infrastructure cluster
 <2> Specify the infrastructure ID, worker label, and zone.
 <3> Configure the machine set as a Windows machine.
 <4> Configure the Windows node as a compute machine.
-<5> Specify the AMI ID of a Windows image with a container runtime installed. You must use Windows Server 2019.
+<5> Specify the AMI ID of a supported Windows image with a container runtime installed.
 <6> Specify the AWS zone, like `us-east-1a`.
 <7> Specify the AWS region, like `us-east-1`.
 <8> Created by the WMCO when it is configuring the first Windows machine. After that, the `windows-user-data` is available for all subsequent machine sets to consume.

modules/wmco-prerequisites.adoc

@@ -18,22 +18,25 @@ The following table lists the link:https://docs.microsoft.com/en-us/windows/rele
 |Supported Windows Server version
 
 |Amazon Web Services (AWS)
-|Windows Server 2019
+|Windows Server 2019, version 1809 Long-Term Servicing Channel (LTSC)
 
 |Microsoft Azure
-|Windows Server 2019
+a|* Windows Server 2022 Long-Term Servicing Channel (LTSC)
+* Windows Server 2019, version 1809 Long-Term Servicing Channel (LTSC)
 
 |VMware vSphere
-|Windows Server 20H2 
+|Windows Server 2022 Long-Term Servicing Channel (LTSC)
 
 |Bare metal or provider agnostic
-|Windows Server 2019
+|Windows Server 2022 Long-Term Servicing Channel (LTSC)
+
 |===
 
 == Supported networking
 
 Hybrid networking with OVN-Kubernetes is the only supported networking configuration. See the additional resources below for more information on this functionality. The following tables outline the type of networking configuration and Windows Server versions to use based on your platform. You must specify the network configuration when you install the cluster. Be aware that OpenShift SDN networking is the default network for {product-title} clusters. However, OpenShift SDN is not supported by WMCO.
 
+
 .Platform networking support
 [cols="2",options="header"]
 |===
@@ -60,8 +63,9 @@ Hybrid networking with OVN-Kubernetes is the only supported networking configura
 |Supported Windows Server version
 
 |Default VXLAN port
-|Windows Server Long-Term Servicing Channel (LTSC): Windows Server 2019
+|Windows Server 2019, version 1809 Long-Term Servicing Channel (LTSC)
 
 |Custom VXLAN port
-|Windows Server Semi-Annual Channel (SAC): Windows Server 20H2
+|Windows Server 2022 Long-Term Servicing Channel (LTSC)
+
 |===