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/create-on-premises-network-connection.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ To create a connection, you must:
62
62
5. Select **Next**.
63
63
6. On the **AD domain** page, provide the following information:
64
64
-**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.
65
-
-**Organizational unit**: This is 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 is not syncing.
65
+
-**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.
66
66
-**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.
67
67
- AD domain password: The password for the user specified above.
68
68
- Confirm AD domain password: The password for the user specified above.
| USB drives|Don't allow supported Plug and Play device redirection |
52
52
53
-
There are two mechanisms to control these redirections:
53
+
There are two ways to manage these redirections:
54
54
55
-
- Settings Catalog: Available as a device configuration policy option in Microsoft Endpoint Manager and can be used to manage both Azure Active Directory (Azure AD) join and hybrid Azure AD join Cloud PCs.
56
-
- Group Policy Object (GPO): Available as part of Windows Server Active Directory and can be used to manage hybrid Azure AD join Cloud PCs only.
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
57
58
58
Follow the appropriate guidance to manage RDP device redirections.
59
59
@@ -80,7 +80,7 @@ To manage any of the redirections by using the Settings Catalog, create and assi
80
80
81
81
8. On the *Review + create** page, select **Create**.
82
82
83
-
See [settings catalog](/mem/intune/configuration/settings-catalog) for any additional guidance on creating a device configuration policy through the settings catalog.
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
84
85
85
> [!Note]
86
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).
@@ -110,7 +110,7 @@ The following table lists which peripherals are supported for redirection based
| Serial port |||||||
| Start menu integration |||||||
116
116
| Teams AV |||||||
0 commit comments