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
+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
@@ -41,7 +41,7 @@ If you want to use a custom device image, you can add it into your Azure subscri
41
41
42
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
-
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.
44
+
1. For Azure AD join on-premises network connections (OPNC) without your own network, 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.
45
45
46
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
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,25 +47,25 @@ To create an OPNC, you must:
47
47
- Be an [Intune Administrator in Azure AD](/azure/active-directory/roles/permissions-reference).
48
48
- Have [Owner permissions on the Azure subscription](/azure/cost-management-billing/manage/add-change-subscription-administrator) that contains the virtual network.
49
49
50
-
## To create a Hybrid Azure Active Directory Join OPNC
51
-
52
-
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **On-premises network connection** > **Create connection**.
53
-
54
-
2. On the **Network details** page, enter a **Name** for the new connection. The connection name must be unique within the customer tenant.
55
-
56
-
3. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy OPNC](health-checks.md), you won't be able to proceed.
57
-
4. Select a **Virtual network** and **Subnet**.
58
-
5. Select **Next**.
59
-
6. On the **AD domain** page, provide the following information:
50
+
## Create an OPNC
51
+
52
+
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **On-premises network connection** > **Create**.
53
+
2. Depending on the type of OPNC you want to create, choose **Azure AD Join (preview)** or **Hybrid Azure AD Join**.
54
+
55
+
3. On the **Network details** page, enter a **Name** for the new connection. The connectionname must be unique within the customer tenant.
56
+
4. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy OPNC](health-checks.md), you won't be able to proceed.
57
+
5. Select a **Virtual network** and **Subnet**.
58
+
6. Select **Next**.
59
+
7. For hybrid Azure AD join OPNCs, 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
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
64
- AD domain password: The password for the user specified above.
65
65
- Confirm AD domain password: The password for the user specified above.
66
66
67
-
7. Select **Next**.
68
-
8. On the **Review + Create** page, select **Create**.
67
+
8. Select **Next**.
68
+
9. On the **Review + Create** page, select **Create**.
Copy file name to clipboardExpand all lines: windows-365/enterprise/manage-rdp-device-redirections.md
+1-29Lines changed: 1 addition & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,35 +87,7 @@ For more help using the settings catalog to create a device configuration policy
87
87
88
88
## Use a GPO to manage RDP device redirections
89
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) :
91
-
92
-
## Redirection support
93
-
94
-
The following table lists which peripherals are supported for redirection based on which platform is used to access the Cloud PC.
95
-
96
-
| Peripheral | Windows Remote Desktop client | Microsoft Store Remote Desktop client | Android | iOS/iPadOS | macOS | Web |
| Serial port |||||||
| Start menu integration |||||||
116
-
| Teams AV |||||||
| USB |||||||
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).
0 commit comments