You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md
+18-5Lines changed: 18 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ ms.collection:
33
33
34
34
Azure Virtual Desktop multi-session with Microsoft Intune is now generally available.
35
35
36
-
You can now use Microsoft Intune to manage Windows 10 or Windows 11 Enterprise multi-session remote desktops in the Microsoft Endpoint Manager admin center just as you can manage a shared Windows 10 or Windows 11 client device. When managing such virtual machines (VMs), you must use device-based configurations. Such configurations require user-less enrollments.
36
+
You can now use Microsoft Intune to manage Windows 10 or Windows 11 Enterprise multi-session remote desktops in the Microsoft Endpoint Manager 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 and user configuration.
37
37
38
38
Windows 10 or Windows 11 Enterprise multi-session is a new Remote Desktop Session Host exclusive to [Azure Virtual Desktop](/azure/virtual-desktop/) on Azure. It provides the following benefits:
39
39
@@ -45,8 +45,18 @@ You can manage **Windows 10** and **Windows 11 Enterprise multi-session** VMs cr
45
45
46
46
## Overview
47
47
48
-
Microsoft Intune only supports managing Windows 10 or Windows 11 Enterprise multi-session with device configurations. This means only [policies defined in the OS scope](/windows/client-management/mdm/policy-configuration-service-provider) and apps configured to install in the system context can be applied to Azure Virtual Desktop multi-session VMs. Additionally, all multi-session configurations must be targeted to devices or device groups. User scope policies aren't supported at this time.
48
+
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](/windows/client-management/mdm/policy-configuration-service-provider) and apps configured to install in the system context can be applied to Azure Virtual Desktop multi-session VMs. Additionally, multi-session configurations can be targeted to devices or device groups.
49
49
50
+
User configuration support in Microsoft Intune for Windows 11 multi-session VMs is in public preview. With this you'll be able to:
51
+
52
+
- 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".
53
+
54
+
- Configure user certificates and assign to users.
55
+
56
+
- Configure PowerShell scripts to install in the user context and assign to users.
57
+
58
+
> [!NOTE]
59
+
> User configuration support for Windows 10 multi-session builds will be available later this year.
50
60
51
61
## Prerequisites
52
62
@@ -70,7 +80,7 @@ See [What is Azure Virtual Desktop?](/azure/virtual-desktop/overview#requirement
70
80
71
81
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.
72
82
73
-
## Create the device configuration profile
83
+
## Create the configuration profile
74
84
75
85
To configure configuration policies for Windows 10 or Windows 11 Enterprise multi-session VMs, you'll need to use the [Settings catalog](../configuration/settings-catalog.md) in the Microsoft Endpoint Manager admin center.
76
86
@@ -95,7 +105,7 @@ Microsoft Intune won't deliver unsupported templates to multi-session devices, a
95
105
-**Key**: **OS edition**
96
106
-**Operator**: **==**
97
107
-**Value**: **Enterprise multi-session**
98
-
- Select **Apply**. The filtered list now shows all configuration profile categories that support Windows 10 or Windows 11 Enterprise multi-session. You can see the scope for the policy in parentheses (Device or User). Currently, only device settings are supported for multi-session.
108
+
- 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 parantheses. For user scope it shows as (User) and all the rest are policies with device scope.
99
109
8. From the filtered list, pick the categories that you want.
100
110
- For each category you pick, select the settings that you want to apply to your new configuration profile.
101
111
- For each setting, select the value that you want for this configuration profile.
@@ -110,6 +120,7 @@ Windows 10 or Windows 11 Administrative Templates are supported for Windows 10 o
110
120
111
121
- ADMX-backed policies are supported. Some policies aren't yet available in the Settings catalog.
112
122
- 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](/windows/client-management/mdm/win32-and-centennial-app-policy-configuration#overview). Some ADMX ingested settings won't be applicable to Windows 10 or Windows 11 Enterprise multi-session.
123
+
- ADMX - ingested policies are not supported for user targetting at this time.
113
124
114
125
## Compliance and Conditional access
115
126
@@ -163,7 +174,9 @@ All Windows 10 or Windows 11 apps can be deployed to Windows 10 or Windows 11 En
163
174
164
175
## Script deployment
165
176
166
-
Scripts configured to run in the system context 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**.
177
+
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**.
178
+
179
+
Scripts configured to run in the user context and assigned to users are supported on Windows 11 Enterprise multi-session. This can be configured under Script settings by setting **Run this script using the logged on credentials** to **Yes**.
0 commit comments