Windows 10 Enterprise multi-session FAQ

Windows 10 Enterprise multi-session, formerly known as Windows 10 Enterprise for Virtual Desktops (EVD), is a new Remote Desktop Session Host that allows multiple concurrent interactive sessions. Previously, only Windows Server could do this. This capability gives users a familiar Windows 10 experience while IT can benefit from the cost advantages of multi-session and use existing per-user Windows licensing instead of RDS Client Access Licenses (CALs). For more information about licenses and pricing, see Azure Virtual Desktop pricing.

How many interactive sessions that can be active at the same time relies on your system's hardware resources (vCPU, memory, disk, and vGPU), how your users use their apps while signed in to a session, and how heavy your system's workload is. We suggest you validate your system's performance to understand how many users you can have on Windows 10 Enterprise multi-session. To learn more, see Azure Virtual Desktop pricing.

Windows 10 Enterprise multi-session is a virtual edition of Windows 10 Enterprise. One of the differences is that this operating system (OS) reports the ProductType as having a value of 3, the same value as Windows Server. This property keeps the OS compatible with existing RDSH management tooling, RDSH multi-session-aware applications, and mostly low-level system performance optimizations for RDSH environments. Some application installers can block installation on Windows 10 multi-session depending on whether they detect the ProductType is set to Client. If your app won't install, contact your application vendor for an updated version.

We don't allow customers to run Windows 10 or 11 Enterprise multi-session in production environments outside of the Azure Virtual Desktop service. Only Microsoft or the Azure Virtual Desktop Approved Providers, Citrix and VMware, can provide access to the Azure Virtual Desktop service. It's against the licensing agreement to run Windows 10 or 11 multi-session outside of the Azure Virtual Desktop service for production purposes. Windows 10 and 11 multi-session also won’t activate against on-premises Key Management Services (KMS).

No. It's not currently possible to upgrade an existing virtual machine (VM) that's running Windows 10 Professional or Enterprise to Windows 10 Enterprise multi-session. Also, if you deploy a Windows 10 Enterprise multi-session VM and then update the product key to another edition, you won't be able to switch the VM back to Windows 10 Enterprise multi-session and will need to redeploy the VM. Changing your Azure Virtual Desktop VM SKU to another edition is not supported.

No. Azure Virtual Desktop supported virtual machine OS images do not support Remote Desktop IP Virtualization.

You can start a VM in Azure with Windows 10 Enterprise multi-session and customize it by installing LOB applications, sysprep/generalize, and then create an image using the Azure portal.

To get started, create a VM in Azure with Windows 10 Enterprise multi-session. Instead of starting the VM in Azure, you can download the VHD directly. After that, you'll be able to use the VHD you downloaded to create a new Generation 1 VM on a Windows 10 PC with Hyper-V enabled.

Customize the image to your needs by installing LOB applications and sysprep the image. When you're done customizing, upload the image to Azure with the VHD inside. After that, get Azure Virtual Desktop from the Azure Marketplace and use it to deploy a new host pool with the customized image.

You can use any supported configuration tool, but we recommend Configuration Manager version 1906 because it supports Windows 10 Enterprise multi-session or Microsoft Intune for Azure AD-joined or Hybrid Azure AD-joined session hosts.

Windows 10 Enterprise multi-session can be Azure AD-joined. To get started, follow the steps to Deploy Azure AD-joined virtual machines.

Windows 10 Enterprise multi-session is in the Azure gallery. To find it, navigate to the Azure portal and search for the Windows 10 Enterprise for Virtual Desktops release. For an image integrated with Microsoft 365 Apps for enterprise, go to the Azure portal and search for Microsoft Windows 10 + Microsoft 365 Apps for enterprise.

The Azure gallery has several releases, including Windows 10 Enterprise multi-session, version 1909, and Windows 10 Enterprise multi-session, version 1903. We recommend using the latest version for improved performance and reliability.

Windows 10 Enterprise multi-session, versions 1909 and later are supported and are available in the Azure gallery. These releases follow the same support lifecycle policy as Windows 10 Enterprise, which means the March release is supported for 18 months and the September release for 30 months.

We recommend you use FSLogix profile containers when you configure Windows 10 Enterprise in non-persistent environments or other scenarios that need a centrally stored profile. FSLogix ensures the user profile is available and up-to-date for every user session. We also recommend you use your FSLogix profile container to store a user profile in any SMB share with appropriate permissions, but you can store user profiles in Azure page blob storage if necessary. Azure Virtual Desktop users can use FSLogix at no additional cost. FSLogix comes pre-installed on all Windows 10 Enterprise multi-session images, but the IT admin is still responsible for configuring the FSLogix profile container.

For more information about how to configure an FSLogix profile container, see Configure the FSLogix profile container.

For a full list of applicable licenses, see Azure Virtual Desktop pricing.

This happens because you're using Windows 10 Enterprise multi-session with a profile management solution like FSLogix. Your admin or profile solution configured your system to delete user profiles when users sign out. This configuration means that when your system deletes your user profile after you sign out, it also removes any apps you installed during your session. If you want to keep the apps you installed, you'll need to ask your admin to provision these apps for all users in your Azure Virtual Desktop environment.

Most virtualized environments are configured by default to prevent users from installing additional apps to their profiles. If you want to make sure an app doesn't disappear when your user signs out of Azure Virtual Desktop, you have to provision that app for all user profiles in your environment. For more information about provisioning apps, check out these resources:

• Publish built-in apps in Azure Virtual Desktop
• DISM app package servicing command-line options
• Add-AppxProvisionedPackage

You can disable the Microsoft Store app to make sure users don't download extra apps beyond the apps you've already provisioned for them.

To disable the Store app:

1. Create and edit a new Group Policy Object.
2. Select Computer Configuration > Policies > Administrative Templates > Windows Components > Store.
3. Open the Turn off the Store Application setting.
4. Select the Enabled option.
5. Click the Apply button.
6. Click the OK button.

Yes. You can update Windows 10 Enterprise multi-session and Windows 11 Enterprise multi-session with the appropriate feature updates published to WSUS.

Next steps

To learn more about Azure Virtual Desktop and Windows 10 Enterprise multi-session:

• Read our Azure Virtual Desktop documentation
• Visit our Azure Virtual Desktop TechCommunity
• Set up your Azure Virtual Desktop deployment with the Azure Virtual Desktop tutorials