Uredi

Deli z drugimi prek

Windows 10 or Windows 11 Enterprise multi-session remote desktops

  • Članek

Azure Virtual Desktop multi-session with Microsoft Intune is now generally available.

You can now use Microsoft Intune to manage Windows 10 or Windows 11 Enterprise multi-session remote desktops in the Microsoft Intune admin center just as you can manage a shared Windows 10 or Windows 11 client device. When managing such virtual machines (VMs), you'll be able to use both device-based configuration targeted to devices or user-based configuration targeted to users.

Windows 10 or Windows 11 Enterprise multi-session is a new Remote Desktop Session Host exclusive to Azure Virtual Desktop on Azure. It provides the following benefits:

  • Allows multiple concurrent user sessions.
  • Gives users a familiar Windows 10 or Windows 11 experience.
  • Supports use of existing per-user Microsoft 365 licensing.

You can manage Windows 10 and Windows 11 Enterprise multi-session VMs created in Azure Government Cloud in US Government Community (GCC), GCC High, and DoD.

Important

Microsoft Intune support for Azure Virtual Desktop multi-session is not currently available for Citrix DaaS and VMware Horizon Cloud.

Overview

Device configuration support in Microsoft Intune for Windows 10 or Windows 11 Enterprise multi-session is generally available (GA). This means policies defined in the OS scope and apps configured to install in the system context can be applied to Azure Virtual Desktop multi-session VMs when assigned to device groups.

Note

Device-based configuration cannot be assigned to users and user-based configuration cannot be assigned to devices. It will be reported as Error or Not applicable.

User configuration support in Microsoft Intune for Windows 10 or Windows 11 multi-session VMs is generally available. With this you are able to:

  • Configure user scope policies using Settings catalog and assign to groups of users. You can use the search bar to search all configurations with scope set to "user".

  • Configure user certificates and assign to users.

  • Configure PowerShell scripts to install in the user context and assign to users.

Prerequisites

This feature supports Windows 10 or Windows 11 Enterprise multi-session VMs, which are:

  • Running Windows 10 multi-session, version 1903 or later, or running Windows 11 multi-session.
  • Set up as remote desktops in pooled host pools that have been deployed through Azure Resource Manager.
  • Under the same tenant as Intune.
  • Running an Azure Virtual Desktop agent version of 1.0.2944.1400 or later.
  • Microsoft Entra hybrid joined and enrolled in Microsoft Intune using one of the following methods:
  • Microsoft Entra joined and enrolled in Microsoft Intune by enabling Enroll the VM with Intune in the Azure portal.
  • Licensing: The appropriate Azure Virtual Desktop and Microsoft Intune license is required if a user or device benefits directly or indirectly from the Microsoft Intune service, including access to the Microsoft Intune service through a Microsoft API. For more information, go to Microsoft Intune licensing.
  • See What is Azure Virtual Desktop? for more information about Azure Virtual Desktop licensing requirements.

Limitations

Intune does not support using a cloned image of a computer that is already enrolled. This includes both physical and virtual devices such as Azure Virtual Desktop (AVD). When device enrollment or identity tokens are replicated between devices, Intune device enrollment or synchronization failures will occur.

Note

If you're joining session hosts to Microsoft Entra Domain Services, you can't manage them using Intune.

Important

  • If you're using Windows 10, versions 2004, 20H2, or 21H1 builds, make sure that you install the July 2021 Windows Update or a later Windows update. Otherwise, remote actions in the Microsoft Intune admin center, like remote sync, won't work correctly. As a result, pending policies assigned to devices might take up to 8 hours to be applied.
  • Intune does not currently support token roaming functionality between devices. If FSLogix, or a similar technology, is used to manage Windows user profiles and settings, you must ensure that tokens are not unexpectedly roamed or duplicated across devices. To confirm that you are running a supported version and configuration of FSLogix with token roaming disabled, please see the FSLogix RoamIdentity Configuration Settings Reference.

Windows 10 or Windows 11 Enterprise multi-session VMs are treated as a separate OS edition and some Windows 10 or Windows 11 Enterprise configurations won't be supported for this edition. Using Microsoft Intune doesn't depend on or interfere with Azure Virtual Desktop management of the same VM.

Create the configuration profile

To configure configuration policies for Windows 10 or Windows 11 Enterprise multi-session VMs, you'll need to use the Settings catalog in the Microsoft Intune admin center.

The existing device configuration profile templates aren't supported for Windows 10 or Windows 11 Enterprise multi-session VMs, except for the following templates:

  • Trusted certificate - Device (machine) when targeting devices and User when targeting users
  • SCEP certificate - Device (machine) when targeting devices and User when targeting users
  • PKCS certificate - Device (machine) when targeting devices and User when targeting users
  • VPN - Device Tunnel only

Microsoft Intune won't deliver unsupported templates to multi-session devices, and those policies appear as Not applicable in reports.

Note

If you use co-management for Intune and Configuration Manager, in Configuration Manager, set the workload slider for Resource Access Policies to Intune or Pilot Intune. This setting allows Windows 10 and Windows 11 clients to start the process of requesting the certificate.

To configure policies

  1. Sign in to the Microsoft Intune admin center and choose Devices > By platform > Windows > Manage devices > Configuration > Create > New Policy.
  2. For Platform, select Windows 10 and later.
  3. For Profile type, select Settings catalog, or when deploy settings by using a Template, select Templates and then the name of the supported Template.
  4. Select Create.
  5. On the Basics page, provide a Name and (optionally) Description > Next.
  6. On the Configuration settings page, select Add settings.
  7. Under Settings picker, select Add filter and select the following options:
    • Key: OS edition
    • Operator: ==
    • Value: Enterprise multi-session
    • Select Apply. The filtered list now shows all configuration profile categories that support Windows 10 or Windows 11 Enterprise multi-session. The scope for a policy is shown in parentheses. For user scope it shows as (User) and all the rest are policies with device scope.
  8. From the filtered list, pick the categories that you want.
    • For each category you pick, select the settings that you want to apply to your new configuration profile.
    • For each setting, select the value that you want for this configuration profile.
  9. Select Next when you're done adding settings.
  10. On the Assignments page, choose the Microsoft Entra groups containing the devices to which you want this profile assigned > Next.
  11. On the Scope tags page, optionally add the scope tags you want to apply to this profile > Next. For more information about scope tags, see Use role-based access control and scope tags for distributed IT.
  12. On the Review + create page, choose Create to create the profile.

Administrative templates

Windows 10 or Windows 11 Administrative Templates are supported for Windows 10 or Windows 11 Enterprise multi-session via the Settings catalog with some limitations:

  • ADMX-backed policies are supported. Some policies aren't yet available in the Settings catalog.
  • ADMX-ingested policies are supported, including Office and Microsoft Edge settings available in Office administrative template files and Microsoft Edge administrative template files. For a complete list of ADMX-ingested policy categories, see Win32 and Desktop Bridge app policy configuration. Some ADMX ingested settings won't be applicable to Windows 10 or Windows 11 Enterprise multi-session.

To list supported Administrative Templates, you'll need to use the filter in Settings catalog.

Compliance and Conditional access

You can secure your Windows 10 or Windows 11 Enterprise multi-session VMs by configuring compliance policies and Conditional Access policies in the Microsoft Intune admin center. The following compliance policies are supported on Windows 10 or Windows 11 Enterprise multi-session VMs:

  • Minimum OS version
  • Maximum OS version
  • Valid operating system builds
  • Simple passwords
  • Password type
  • Minimum password length
  • Password Complexity
  • Password expiration (days)
  • Number of previous passwords to prevent reuse
  • Microsoft Defender Antimalware
  • Microsoft Defender Antimalware security intelligence up-to-date
  • Firewall
  • Antivirus
  • Antispyware
  • Real-time protection
  • Microsoft Defender Antimalware minimum version
  • Defender ATP Risk score

All other policies report as Not applicable.

Important

You'll need to create a new compliance policy and target it to the device group containing your multi-session VMs. User-targeted compliance configurations aren't supported.

Conditional Access policies support both user and device based configurations for Windows 10 or Windows 11 Enterprise multi-session.

Note

Conditional Access for Exchange on-premises isn't supported for Windows 10 or Windows 11 Enterprise multi-session VMs.

Note

Configuration and compliance policies for BitLocker, Secure Boot, and features leveraging vTPM (Virtual Trusted Platform Module) are not supported at this time for Azure Virtual Desktop VMs.

Endpoint security

You can configure profiles under Endpoint security for multi-session VMs by selecting Platform Windows 10, Windows 11, and Windows Server. If that Platform is not available, the profile is not supported on multi-session VMs.

For more information, see Manage device security with endpoint security policies in Microsoft Intune

Application deployment

All Windows 10 or Windows 11 apps can be deployed to Windows 10 or Windows 11 Enterprise multi-session with the following restrictions:

  • All apps must be configured to install in the system/device context and be targeted to devices. Web apps are always applied in the user context by default so they won't apply to multi-session VMs.
  • All apps must be configured with Required or Uninstall app assignment intent. The Available apps deployment intent isn't supported on multi-session VMs.
  • If a Win32 app configured to install in the system context has dependencies or supersedence relationship on any apps configured to install in the user context, the app won't be installed. To apply to a Windows 10 or Windows 11 Enterprise multi-session VM, create a separate instance of the system context app or make sure all app dependencies are configured to install in the system context.
  • Azure Virtual Desktop RemoteApp and MSIX app attach aren't currently supported in Microsoft Intune.

Script deployment

Scripts configured to run in the system context and assigned to devices are supported on Windows 10 or Windows 11 Enterprise multi-session. This can be configured under Script settings by setting Run this script using the logged on credentials to No.

Scripts configured to run in the user context and assigned to users are supported on Windows 10 and Windows 11 Enterprise multi-session. This can be configured under Script settings by setting Run this script using the logged on credentials to Yes.

Windows Update for Business

You can use the settings catalog to manage Windows Update settings for quality (security) updates for Windows 10 or Windows 11 Enterprise multi-session VMs. To find the supported settings in the catalog, configure a settings filter for Enterprise multi-session and then expand the Windows Update for Business category.

The following settings are available in the catalog, with the links opening the Windows CSP documentation:

Remote actions

The following Windows 10 or Windows 11 desktop device remote actions aren't supported and will be grayed out in the UI and disabled in Graph for Windows 10 or Windows 11 Enterprise multi-session VMs:

  • Autopilot reset
  • BitLocker key rotation
  • Fresh Start
  • Remote lock
  • Reset password
  • Wipe

Retirement

Deleting VMs from Azure will leave orphaned device records in the Microsoft Intune admin center. They'll be automatically cleaned up according to the cleanup rules configured for the tenant.

Security baselines

Security baselines aren't available for Windows 10 or Windows 11 Enterprise multi-session at this time. We recommend that you review the Available security baselines and configure the recommended policies and values in the Settings catalog.

Additional configurations that aren't supported on Windows 10 or Windows 11 Enterprise multi-session VMs

Out of Box Experience (OOBE) enrollment isn't supported for Window 10 or Windows 11 Enterprise multi-session. This restriction means that:

  • Windows Autopilot and Commercial OOBE aren't supported.
  • Enrollment status page isn't supported.

Windows 10 or Windows 11 Enterprise multi-session managed by Microsoft Intune isn't currently supported for China Sovereign Cloud.

Troubleshooting

The following sections provide troubleshooting guidance for common issues.

Enrollment issues

Issue Detail
Enrollment of Microsoft Entra hybrid joined virtual machine fails
  • Auto-enrollment is configured to use user credentials. Windows 10 or Windows 11 Enterprise multi-session virtual machines must be enrolled using device credentials.
  • The Azure Virtual Desktop agent you're using must be version 1.0.2944.1400 or later.
  • You've more than one MDM provider, which isn't supported.
  • Windows 10 or Windows 11 Enterprise multi-session VM is configured outside of a host pool. Microsoft Intune only supports VMs provisioned as part of a host pool.
  • The Azure Virtual Desktop host pool wasn't created through the Azure Resource Manager template.
Enrollment of Microsoft Entra joined virtual machine fails
  • The Azure Virtual Desktop agent you're using isn't updated. The agent must be version 1.0.2944.1400 or above.
  • Azure Virtual Desktop host pool wasn't created through the Azure Resource Manager template.

Configuration issues

Issue Detail
Settings catalog policy fails Confirm the VM is enrolled using device credentials. Enrollment with user credentials isn't currently supported for Windows 10 or Windows 11 Enterprise multi-session.
Configuration policy didn't apply Templates (except for Certificates) aren't supported on Windows 10 or Windows 11 Enterprise multi-session. All policies must be created via the settings catalog.
Configuration policy reports as Not applicable Some policies aren't applicable to Azure Virtual Desktop VMs.
Microsoft Edge/Microsoft Office ADMX policy doesn't show up when I apply the filter for Windows 10 or Windows 11 Enterprise multi-session edition Applicability for these settings isn't based on the Windows version or edition but on whether those apps have been installed on the device. To add these settings to your policy, you may have to remove any filters applied in the settings picker.
App configured to install in system context didn't apply Confirm the app doesn't have a dependency or supersedence relationship on any apps configured to install in user context. User context apps aren't currently supported on Windows 10 or Windows 11 Enterprise multi-session.
Update rings for Windows 10 and later policy didn't apply Windows update rings policies aren't currently supported. Quality updates can be managed via settings available in the settings catalog.

Next steps

Learn more about Azure Virtual Desktops.