![]() Settings delivered by group policies may cause connection problems. ![]() On-premises Group Policy Objects (GPO) may affect a Cloud PC's provisioning or behavior To test this possible cause, you can move the Cloud PC to a separate OU that’s blocked from receiving group policies. Other troubleshooting steps Move the Cloud PC to a new organizational unit (OU) with no group policiesĬonnection problems may be caused by settings delivered by group policies. Using a KDC proxy isn't currently available for Windows 365. This connection is only possible using a VPN solution. Possible solution: Remote Credential Guard requires connectivity to the on-premises Active Directory Domain Controller on the client PC used to access the Cloud PC. Using a client PC with Remote Credential Guard enabled Possible solution: Windows 365 is currently a Hybrid Azure Active Directory (Azure AD) Join device, requiring users to sign in with their on-premises Active Directory account. Signing in to the Cloud PC with Azure Active Directory-only user accounts Possible solution: Update VPN clients to the most up-to-date versions. Some other possible causes for Cloud PC connection failures include: Out-of-date third-party VPN client versions Possible solution: If the issue persists, sign in to > select the cog icon next to the Cloud PC > Restart. Potential cause: This error can occur when the Cloud PC’s processor is over-utilized. If this keeps happening, contact your network administrator for assistance. Possible solution: Review the settings and confirm that they aren’t interfering with connections. Potential cause: This error can be caused by network configuration settings, like: If this keeps happening, ask your admin or tech support for help. We couldn't connect to the gateway because of an error. Possible solution: Sign in to > select the cog icon next to the Cloud PC > Restart. Potential cause: There may be a resource issue on your Cloud PC. Specific connection errors We couldn't connect because there are currently no available resources Then, set an Azure AD conditional access policy and assign it to the appropriate users. Possible solution: Remove per-user multi-factor authentication for all users connecting to Cloud PCs. Because it blocks sign-in, per-user multi-factor authentication isn't supported for users connecting to Azure AD joined Cloud PCs. Potential cause #2: Per-user multi-factor authentication is turned on for the user account. If you only manage the user's physical device through Group Policy or you don't manage the user's physical device, you (or the user) can manage this setting through the allow PKU2U authentication requests to this computer to use online identities policy. Complete the creation of the device configuration policy.On the Assignments page, also select an Azure AD group containing the user or the user's physical device.On the Assignments page, select Add all devices > Edit filter > Include filtered devices in assignment > select the filter you created for all Cloud PCs.On the Configuration settings page, search for and select Network Security Allow PKU2U Authentication Requests > Allow.Create a device configuration policy using the settings catalog.Possible solution: Turn on PKU2U protocol requests on both the Cloud PC and the user's physical device: The user's physical device is Azure AD registered, Azure AD joined, or hybrid Azure AD joined to the same organization as the Cloud PC.The user is connecting from the Windows desktop client.The PKU2U protocol is only triggered in the following cases: Potential cause #1: Either the Cloud PC or the user's physical device denied PKU2U protocol requests. ![]() Errors when connecting to an Azure Active Directory (Azure AD) joined Cloud PC The logon attempt failed The following errors can occur when connecting to a Cloud PC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |