Merge pull request #207333 from Heidilohr/work-update-server

Updating Windows Server image article

Author: Stacyrch140

articles/virtual-desktop/TOC.yml

@@ -191,7 +191,7 @@
         href: deploy-azure-ad-joined-vm.md
       - name: Deploy a Windows 7 virtual machine
         href: deploy-windows-7-virtual-machine.md
-      - name: Deploy Windows Server based machine
+      - name: Deploy a Windows Server-based virtual machine
         href: deploy-windows-server-virtual-machine.md
       - name: Deploy a GPU-based session host
         href: configure-vm-gpu.md

articles/virtual-desktop/deploy-windows-server-virtual-machine.md

@@ -4,56 +4,78 @@ description: How to deploy and configure Windows Server edition virtual machines
 author: ravibak
 ms.author: ravibak
 ms.service: virtual-desktop
-ms.topic: how-to #Required; leave this attribute/value as-is.
-ms.date: 03/18/2022
-ms.custom: template-how-to #Required; leave this attribute/value as-is.
+ms.topic: how-to
+ms.date: 08/18/2022
+ms.custom: how-to
 ---
 
-# Deploy Windows Server based virtual machines on Azure Virtual Desktop
+# Deploy Windows Server-based virtual machines on Azure Virtual Desktop
 
 >[!IMPORTANT]
 >This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects. If you're using Azure Virtual Desktop (classic) without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/deploy-windows-7-virtual-machine.md).
 
-The process to deploy Windows Server based Virtual Machines (VM) on Azure Virtual Desktop is slightly different than for VMs running other versions of Windows such as Windows 10 or Windows 11. This guide will walk you through the steps.
-
-Azure Virtual Desktop Host pool supports running Windows Server 2012 R2 and above editions.
+The process for deploying Windows Server-based virtual machines (VMs) on Azure Virtual Desktop is slightly different than the one for VMs running other versions of Windows, such as Windows 10 or Windows 11. This guide will walk you through the process.
 
 > [!NOTE]
-> - Azure AD Join session host scenario is not supported with Windows Server editions.
+> Windows Server scenarios support the following versions of Azure Active Directory (AD)-joined session hosts:
+> 
+> - Windows Server 2019
+> - Windows Server 2022
+> 
+> However, Windows Server scenarios don't support the following versions of Azure AD-joined session hosts:
+> 
+> - Windows Server 2012
+> - Windows Server 2016
 
 ## Prerequisites
 
-Running Windows Server based host virtual machines on Azure Virtual Desktop requires Remote Desktop Services (RDS) Licensing Server.
+Before you get started, you'll need to make sure you have the following things:
+
+- Azure Virtual Desktop host pools support running Windows Server 2012 R2 and later.
+
+- Running Windows Server-based host VMs on Azure Virtual Desktop requires a Remote Desktop Services (RDS) Licensing Server. This server should be a separate server or remote VM in your environment that you've assigned the Remote Desktop Licensing Server role to.
+  
+  For more information about licensing, see the following articles:
+
+  - [Operating systems and licenses](prerequisites.md)
+  - [License your RDS deployment with client access licenses](/windows-server/remote/remote-desktop-services/rds-client-access-license)
 
-For more information, refer [Operating systems and licenses](prerequisites.md)
+  If you're already using Windows Server-based Remote Desktop Services, you probably already have a licensing server set up in your environment. If you do, you can continue using the same license server as long as the Azure Virtual Desktop hosts have line-of-sight with the server.
 
-Use the following information to learn about how licensing works in Remote Desktop Services and to deploy and manage your licenses.
+- Your Windows Server VM should already be assigned the Remote Desktop Session Host role. Without that role, the Azure Virtual Desktop Agent won't install and the deployment won't work.
 
-[License your RDS deployment with client access licenses](/windows-server/remote/remote-desktop-services/rds-client-access-license)
+## Configure Windows Server-based VMs
 
-If you're already using Windows Server based Remote Desktop Services, you'll likely have Licensing Server setup in your environment. You can continue using the same provided Azure Virtual Desktop hosts has line of sight to the Server. 
+Now that you've fulfilled the requirements, you're ready to configure Windows Server-based VMs for deployment on Azure Virtual Desktop.
 
-## Configure Windows Server based Virtual Machines
+To configure your VM:
 
-Once you've done the prerequisites, you're ready to configure Windows Server based VMs for deployment on Azure Virtual Desktop.
+1. Follow the instructions from [Create a host pool using the Azure portal](create-host-pools-azure-marketplace.md) until you reach step 6 in [Virtual machine details](create-host-pools-azure-marketplace.md#virtual-machine-details). When it's time to select an image in the **Virtual machine details** field, either select a relevant Windows Server image or upload your own customized Windows Server image.
 
-1. Follow the instructions from [Create a host pool using the Azure portal](create-host-pools-azure-marketplace.md).
+2. For the **Domain to join** field, you can select either **Active Directory** or **Azure Active Directory**.
+   
+   >[!NOTE]
+   >If you select **Azure Active Directory**, you should not select the **Enroll VM with Intune** option, as Intune doesn't support Windows Server.
 
-1. Select relevant Windows Server image or upload your own customized image based on Windows Server edition at **Step 6** under **Virtual machine details** section.
+3. Connect to the newly deployed VM using an account with local administrator privileges.
 
-1. Select **Active Directory** as an option under **Domain to Join** at **Step 12** of **Virtual machine details** section.
+4. Next, open the **Start** menu on your VM Desktop and enter **gpedit.msc** to open the Group Policy Editor.
 
-1. Connect to the newly deployed VM using an account with local administrator privileges.
-1. Open the Start menu and type "gpedit.msc" to open the Group Policy Editor.
-1. Navigate the tree to **Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing**
-1. Select policy **Use the specified Remote Desktop license servers** and set the policy to point to the Remote Desktop Licensing Servers FQDN/IP Address.
-2. Select policy **Specify the licensing mode for the Remote Desktop Session Host server** and set the policy to Per Device or Per User, as appropriate for your licensing eligibility. 
+5. Go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Remote Desktop Services** > **Remote Desktop Session Host** > **Licensing**.
+
+6. Once you're at **Licensing**, select **Use the specified Remote Desktop license servers**, then set the policy to point to the Remote Desktop Licensing Servers FQDN/IP Address.
+
+7. Finally, select **Specify the licensing mode for the Remote Desktop Session Host server** and set the policy to **Per device** or **Per user**, depending on your licensing eligibility. 
 
 > [!NOTE]
-> - You can also use and apply Domain based GPO and scope it to OU where Azure Virtual Desktop Hosts resides in Active Directory.
+> You can also use and apply a domain-based group policy object (GPO) and scope it to the Organizational Unit (OU) where the Azure Virtual Desktop hosts are located in your Active Directory.
 
 ## Next steps
-Now that you've deployed Windows Server based Host VMs, you can sign in to a supported Azure Virtual Desktop client to test it as part of a user session. If you want to learn how to connect to a session, check out these articles:
 
-- [Connect with the Windows Desktop client](user-documentation/connect-windows-7-10.md)
-- [Connect with the web client](user-documentation/connect-web.md)
+Now that you've deployed Windows Server-based Host VMs, you can sign in to a supported Azure Virtual Desktop client to test it as part of a user session. If you want to learn how to connect to a session using Remote Desktop Services for Windows Server, check out our [list of available clients](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients).
+
+If you'd like to learn about other ways to create VMs for Azure Virtual Desktop, check out these articles:
+
+- To set up a VM automatically as part of the host pool setup process, see [Tutorial: Create a host pool](create-host-pools-azure-marketplace.md).
+- If you'd like to manually create VMs in the Azure portal after setting up a host pool, see [Expand an existing host pool with new session hosts](expand-existing-host-pool.md).
+- You can also manually create a VM with [Azure CLI, PowerShell](create-host-pools-powershell.md), or [REST API](/rest/api/desktopvirtualization/).