|
| 1 | +--- |
| 2 | +# required metadata |
| 3 | +title: Troubleshoot Citrix HDX Plus for Windows 365 |
| 4 | +titleSuffix: |
| 5 | +description: Troubleshoot Citrix HDX Plus for Windows 365. |
| 6 | +keywords: |
| 7 | +author: ErikjeMS |
| 8 | +ms.author: erikje |
| 9 | +manager: dougeby |
| 10 | +ms.date: 10/12/2022 |
| 11 | +ms.topic: troubleshooting |
| 12 | +ms.service: cloudpc |
| 13 | +ms.subservice: |
| 14 | +ms.localizationpriority: high |
| 15 | +ms.technology: |
| 16 | +ms.assetid: |
| 17 | + |
| 18 | +# optional metadata |
| 19 | + |
| 20 | +#ROBOTS: |
| 21 | +#audience: |
| 22 | + |
| 23 | +ms.reviewer: aradinger |
| 24 | +ms.suite: ems |
| 25 | +search.appverid: MET150 |
| 26 | +#ms.tgt_pltfrm: |
| 27 | +ms.custom: intune-azure; get-started |
| 28 | +ms.collection: M365-identity-device-management |
| 29 | +--- |
| 30 | + |
| 31 | +# Troubleshoot Citrix HDX Plus for Windows 365 |
| 32 | + |
| 33 | +When you turn on Citrix HDX Plus for a user, the Citrix Virtual Delivery Agent is automatically installed on that user's Cloud PCs. The agent enables the HDX protocol. If this installation runs into a problem, you'll receive an error message in the All Cloud PC list. The description of the error includes advice on how to troubleshoot the error. |
| 34 | + |
| 35 | +If the Citrix HDX Plus agent installation fails, the user can still connect to their Cloud PC by using Remote Desktop. |
| 36 | + |
| 37 | +While troubleshooting errors, make sure that the following steps have all been successful: |
| 38 | + |
| 39 | +- The users license state is synchronized from Citrix to Microsoft Endpoint Manager, including the users Azure Active Directory (Azure AD) user ID. |
| 40 | + - The prerequisites have been met. |
| 41 | + - The Citrix connector is enabled and healthy in Microsoft Endpoint Manager. |
| 42 | + - The correct permissions have been set for the Citrix third-party apps in Azure AD. For more information on required permissions, see [Requirements for using Citrix HDX Plus for Windows 365 Enterprise](requirements-citrix.md). |
| 43 | + - The Azure AD user is added and discoverable in the Citrix console. |
| 44 | +- The Citrix agent is downloaded on the Cloud PC. |
| 45 | + - The Cloud PC can access Citrix download URL. |
| 46 | + - No security policy is blocking PowerShell or any app/agent installation as System. |
| 47 | +- The Citrix Virtual Delivery Agent is installed. |
| 48 | + - Check **Apps & Features** to see if the Citrix Virtual Apps and Desktops Virtual Delivery Agent is installed on the Cloud PC. |
| 49 | + - Check Windows event viewer (eventvwr.msc) logs to make sure that the agent installation is executed. |
| 50 | + - Check Citrix installation logs for any failures: %TEMPsystemdrive%\Windows\Temp\Citrix\XenDesktop Installer. |
| 51 | +- The Cloud PC is registered into the Citrix cloud tenant. |
| 52 | + - Check the Cloud PC registration status in the Citrix configuration console. |
| 53 | + - If the Cloud PC is unregistered, check the Application sign-in Windows event viewer (eventvwr.msc) for Citrix Desktop Service errors and warnings. |
| 54 | + |
| 55 | +After you find the root cause, remove the assigned license from the Citrix console and re-add the license. This should trigger a reinstallation of the Citrix Virtual Delivery Agent. |
| 56 | + |
| 57 | +If no other solution works, you can [reprovision](reprovision-cloud-pc.md) the Cloud PC to reattempt the Citrix HDX plus enablement. Reprovisioning will delete the Cloud PC and create a brand new one. All data on the original Cloud PC will be lost. Therefore, reprovisioning should be the last resort to resolve the issue. |
| 58 | + |
| 59 | +## Troubleshoot connection issues |
| 60 | + |
| 61 | +If you’re having connectivity issues with your Citrix HDX Plus Cloud PC, you may want to test the default RDP-based connectivity. This process is a handy troubleshooting technique to determine if the issue is with the Cloud PC or the HDX connectivity. |
| 62 | + |
| 63 | +### Turn on the RDP protocol |
| 64 | + |
| 65 | +When the Citrix HDX Plus protocol is turned on, the Windows 365 remoting protocol remains enabled but inactive. This inactivity means that users trying to connect with the Windows 365 supported Remote Desktop clients (including the HTML5 browser) are blocked by default. Users can only connect by using HDX. Users trying to connect with non-HDX clients will get a generic error message. |
| 66 | + |
| 67 | +You can turn on the RDP protocol so users can sign in with RDP to test the Cloud PC connectivity. You can do either of the following to turn on the RDP protocol: |
| 68 | + |
| 69 | +- [Make a user a local admin](assign-users-as-local-admin.md) on the Cloud PC. |
| 70 | +- [Add the user to the Direct Access Users group on the Cloud PC](/windows/client-management/mdm/policy-csp-localusersandgroups?WT.mc_id=Portal-fx). |
| 71 | + |
| 72 | +After taking either of these steps, you might have to reboot the Cloud PC for the group membership updates to take effect. Afterwards, the user will be able to connect by using either RDP or Citrix HDX. |
| 73 | + |
| 74 | +You can now test the connectivity by using RDP, and raise a support case with the relevant support team if problems persist. |
| 75 | + |
| 76 | +<!-- ########################## --> |
| 77 | +## Next steps |
| 78 | + |
| 79 | +[Learn about Citrix HDX Plus for Windows 365](set-up-citrix.md). |
0 commit comments