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: windows-365/enterprise/add-device-images.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,22 +39,21 @@ If you want to use a custom device image, you can add it into your Azure subscri
39
39
40
40
## Add a custom device image
41
41
42
-
You can upload the custom image to the Windows 365 service by following these steps:
42
+
For both hybrid Azure Active Directory (Azure AD) join and Azure AD join connections, you can upload the custom image to the Windows 365 service by following these steps:
43
43
44
-
> [!NOTE]
45
-
> For Azure AD Join on-premises network connections (OPNC) without your own network, you can upload custom images from your Azure subscription. You must first [create an on-premises network connection](create-on-premises-network-connection.md) with the Azure subscription associated with the targeted custom images.
44
+
1. For Azure AD join on-premises network connections (OPNC) without your own network, you can upload custom images from your Azure subscription. You must first [create an on-premises network connection](create-on-premises-network-connection.md) with the Azure subscription associated with the targeted custom images.
46
45
47
-
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
46
+
2. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
Copy file name to clipboardExpand all lines: windows-365/enterprise/create-on-premises-network-connection.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,8 @@ To create an OPNC, you must:
59
59
6. On the **AD domain** page, provide the following information:
60
60
-**AD domain name**: The DNS name of the Active Directory domain that you want to use for connecting and provisioning Cloud PCs. For example, corp.contoso.com.
61
61
-**Organizational unit**: (Optional.) An organizational unit (OU) is a container within an Active Directory domain, which can hold users, groups, and computers. Make sure that this OU is enabled to sync with Azure AD Connect. Provisioning will fail if this OU isn't syncing.
62
-
-**AD domain username**: The username, in user principal name (UPN) format, that you want to use for connecting the Cloud PCs to your Active Directory domain. For example, [email protected]. This service account must have permission to join computers to the domain and, if set, the target OU.
62
+
-**AD domain username**: The username, in user principal name (UPN) format, that you want to use for connecting the Cloud PCs to your Active Directory domain. For example, [email protected]. This service account must have permission to join computers to the domain and, if set, the target OU.
63
+
63
64
- AD domain password: The password for the user specified above.
64
65
- Confirm AD domain password: The password for the user specified above.
Copy file name to clipboardExpand all lines: windows-365/enterprise/manage-rdp-device-redirections.md
+51-10Lines changed: 51 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,21 +32,62 @@ ms.collection:
32
32
33
33
Remote Desktop Protocol (RDP) can be used to create redirections that let users connect to peripherals (like cameras, USB drives, and printers) from remote devices like Cloud PCs. By default, these redirections are enabled for Cloud PCs. For security reasons, you might want to override the default and block these redirections.
34
34
35
-
## Use GPO to manage RDP device redirections
35
+
To understand which redirections are supported based on which platform is used to access the Cloud PC, see [Compare the clients: redirections](/windows-server/remote/remote-desktop-services/clients/remote-desktop-app-compare).
36
36
37
-
To block any of the redirections, create and assign a Group Policy Object with the corresponding policies as shown in the table below. To learn more about the policies, download the [Group Policy Settings Reference Spreadsheet](https://www.microsoft.com/download/101451) :
37
+
## RDP device redirection settings
38
+
39
+
The following redirections can be managed by using the appropriate setting:
| USB drives| Don't allow supported Plug and Play device redirection |
52
+
53
+
There are two ways to manage these redirections:
54
+
55
+
- Settings Catalog: Use a device configuration policy in Microsoft Endpoint Manager. Supports both Azure Active Directory (Azure AD) join and hybrid Azure AD join Cloud PCs.
56
+
- Group Policy Object (GPO): Use GPOs in Windows Server Active Directory. Supports hybrid Azure AD join Cloud PCs only.
57
+
58
+
Follow the appropriate guidance to manage RDP device redirections.
59
+
60
+
## Use the Settings Catalog to manage RDP device redirections
61
+
62
+
To manage any of the redirections by using the Settings Catalog, create and assign a device configuration policy:
63
+
64
+
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Configuration profiles** > **Create profile**.
65
+
66
+
2. Select the **Windows 10 and later** platform, the **Settings catalog (preview)** profile type, then **Create**.
67
+
68
+
3. On the **Basics** page, enter a **Name** and **Description** (optional) for the new policy.
69
+
70
+
4. On the **Configuration settings** page, select **+ Add settings** to list and select settings to manage.
71
+
72
+
- To manage printer redirection settings, search for “Printer Redirection”, select the resulting category, and select the settings you want to manage.
73
+
- To manage other redirection settings, search for “Device and Resource Redirection”, select the resulting category, and select the settings you want to manage.
74
+
75
+
5. After you've selected all the redirection settings that you want to manage, close the **Settings picker** view, configure the settings on the **Configuration settings** page, then select **Next**.
76
+
77
+
6. On the **Assignments** page, select the users or groups that will receive the redirection policy, then select **Next**.
78
+
79
+
7. On the **Scope tags** page, select any desired scope tags to apply, then select **Next**.
80
+
81
+
8. On the *Review + create** page, select **Create**.
82
+
83
+
For more help using the settings catalog to create a device configuration policy, see [Use the settings catalog to configure settings on Windows and macOS devices](/mem/intune/configuration/settings-catalog).
84
+
85
+
> [!Note]
86
+
> The settings catalog configures policies by using the Policy CSP. To make sure that these settings take precedence over a conflicting GPO, you can also configure the [ControlPolicyConflict CSP](/windows/client-management/mdm/policy-csp-controlpolicyconflict#controlpolicyconflict-policies).
87
+
88
+
## Use a GPO to manage RDP device redirections
89
+
90
+
To manage any of the redirections by using GPO, create and assign a GPO in your Windows Server Active Directory domain. Make sure to use the corresponding policies as shown in the (RDP device redirection settings table)(#rdp-device-redirection-settings). To learn more about the policies, download the [Group Policy Settings Reference Spreadsheet](https://www.microsoft.com/download/101451) :
50
91
51
92
## Redirection support
52
93
@@ -69,7 +110,7 @@ The following table lists which peripherals are supported for redirection based
| Serial port |||||||
| Start menu integration |||||||
75
116
| Teams AV |||||||
0 commit comments