Troubleshoot

Introduction

Resource locations contain the machines that deliver desktops and apps. Those machines are created in catalogs, so the catalogs are considered part of the resource location, too. Each resource location also contains Cloud Connectors. Cloud Connectors enable Citrix Cloud to communicate with the resource location. Citrix installs and updates the Cloud Connectors.

Optionally, you can initiate several Cloud Connector and resource location actions in the Citrix-managed Azure subscription. For details, see:

The Citrix Managed Desktop service also offers access to troubleshooting and supportability tools that can help resolve configuration and communication issues with the machines that deliver desktops and apps (the VDAs). For example, creating a catalog might fail, or users might be unable to start their desktop or apps.

This troubleshooting includes gaining access to your dedicated Citrix-managed Azure subscription through a bastion machine or direct RDP. After gaining access to the subscription, Citrix supportability tools are used to locate and resolve issues. For details, see:

Resource location actions from the Manage dashboard

  1. From the Manage dashboard, expand Subscriptions on the right.
  2. Click the Citrix-managed subscription.

The Resource Locations tab on the subscription card lists each resource location, plus the status of each Cloud Connector in the resource location.

Each resource location’s entry contains an ellipsis menu. From this menu, you can select the following actions.

  • Run Health Check: Selecting this action in the menu starts the connectivity check immediately. If the check fails, the Cloud Connector’s state is unknown, because it is not communicating with Citrix Cloud. You might want to restart the Cloud Connector.
  • Restart Connectors: Citrix recommends restarting only one Cloud Connector at a time. Restarting takes the Cloud Connector offline, and disrupts user access and machine connectivity. After selecting this action in the menu, select the check box for the Cloud Connector you want to restart. Click Restart.
  • Add Connectors: Adding a Cloud Connector typically takes 20 minutes to complete.

    After selecting this action in the menu, provide the following information.

    • How many Cloud Connectors to add.
    • The OU for the Cloud Connectors. By default, the resource locations’ OU is used.
    • Whether your network requires a proxy server for internet connectivity. If it does, enter the proxy server’s FQDN or IP address, including the port number.
    • The domain service account name and password. These credentials are used to domain-join the Cloud Connector machines.

    Click Add Connectors.

  • Delete Connectors: If a Cloud Connector cannot communicate with Citrix Cloud, and a restart does not resolve the issue, Citrix Support might recommend deleting that Cloud Connector.

    After selecting this action in the menu, select the check box for the Cloud Connector you want to delete. Then click Delete.

    (You can also delete an available Cloud Connector. However, if deleting the selected available Cloud Connector will result in fewer than two available Cloud Connectors in the resource location, you cannot delete the selected Cloud Connector.)

  • Select Update Time: Citrix automatically provides software updates for the Cloud Connectors. During an update, one Cloud Connector is taken offline and updated, while other Cloud Connectors remain in service. When the first update completes, another Cloud Connector is taken offline and updated, and so on until all Cloud Connectors in the resource location are updated. The best time to start updates is usually outside your typical business hours.

    After selecting this action in the menu, choose the time to begin updates, or indicate that updates should start as soon as an update is available. Click Save.

  • Rename: After selecting this action in the menu, enter the new name for the resource location. Click Save.
  • Configure Connectivity: After selecting this action in the menu, indicate whether users can access desktops and apps through the Citrix Gateway service, or only from within your corporate network.

VDA troubleshooting using a bastion or direct RDP

The supportability features are for people who have experience troubleshooting Citrix issues. This includes:

  • Citrix Service Providers (CSPs) and others who have the technical knowledge and troubleshooting experience with Citrix Virtual Apps and Desktops products.
  • Citrix Support personnel.

If you’re not familiar or comfortable with troubleshooting Citrix components, you can request help from Citrix Support. Citrix Support representatives might ask you to set up one of the access methods described in the remainder of this section. However, the Citrix representatives do the actual troubleshooting, using Citrix tools and technologies.

Important:

These supportability features are valid only for domain-joined machines. If the machines in your catalogs are not domain joined, you’re guided to request troubleshooting help from Citrix Support.

Access methods

These access methods are valid only for the Citrix-managed Azure subscription For more information, see About Azure subscriptions.

Two supportability access methods are provided.

  • Access your resources through a bastion machine in the Citrix-managed dedicated customer Azure subscription. The bastion is a single point of entry that allows access to the machines in the subscription. It provides a secure connection to those resources by allowing remote traffic from IP addresses in a specified range.

    The steps in this method include:

    • Create the bastion machine
    • Download an RDP agent
    • RDP to the bastion machine
    • Connect from the bastion machine to the other Citrix machines in your subscription

    The bastion machine is intended for short-term use. This method is intended for issues involving the creation of catalogs or master image machines.

  • Direct RDP access to the machines in the Citrix-managed dedicated customer Azure subscription. To permit RDP traffic, port 3389 must be defined in the Network Security Group.

    This method is intended for catalog issues other than creation, such as users unable to start their desktops.

Remember: As an alternative to these two access methods, contact Citrix Support for help.

Bastion access

  1. From the Manage dashboard, expand Troubleshoot & Support on the right.
  2. Click View troubleshooting options.
  3. On the Troubleshoot page, select either of the first two issue types, and then click Use our troubleshooting machine.
  4. On the Troubleshoot with Bastion Machine page, select the catalog.

    • If the machines in the selected catalog are not domain joined, you’re instructed to contact Citrix Support.
    • If a bastion machine has already been created with RDP access to the selected catalog’s network connection, skip to step 8.
  5. The RDP access range is displayed. If you want to restrict RDP access to a smaller range than allowed by the network connection, select the Restrict RDP access to only computers in IP address range check box and then enter the desired range.
  6. Type a username and password that you’ll use to log in when you RDP to the bastion machine. Password requirements.

    Do not use unicode characters in the username.

  7. Click Create Bastion Machine.

    When the bastion machine is successfully created, the page title changes to Bastion – connection.

    If the bastion machine creation fails (or if it fails during operation), click Delete at the bottom of the failure notification page. Try to create the bastion machine again.

    You can change the RDP range restriction after the bastion machine is created. Click Edit. Enter the new value and then click the check mark to save the change. (Click X to cancel the change.)

  8. Click Download RDP File.
  9. RDP to the bastion, using the credentials you specified when creating the bastion. (The bastion machine’s address is embedded in the RDP file you downloaded.)
  10. Connect from the bastion machine to the other Citrix machines in the subscription. You can then collect logs and run diagnostics.

Bastion machines are powered on when they are created. To save costs, they are powered off automatically if they remain idle after startup. The machines are deleted automatically after several hours.

You can power manage or delete a bastion machine, using the buttons at the bottom of the page. If you choose to delete a bastion machine, you must acknowledge that any active sessions on the machine will end automatically. Also, any data and files that were saved on the machine will be deleted.

Direct RDP access

  1. From the Manage dashboard, expand Troubleshoot & Support on the right.
  2. Click View troubleshooting options.
  3. On the Troubleshoot page, select Other catalog issue.
  4. On the Troubleshoot with RDP Access page, select the catalog.

    If RDP has already been enabled to the selected catalog’s network connection, skip to step 7.

  5. The RDP access range is displayed. If you want to restrict RDP access to a smaller range than permitted by the network connection, select the Restrict RDP access to only computers in IP address range check box and then enter the desired range.
  6. Click Enable RDP Access.

    When RDP access is successfully enabled, the page title changes to RDP Access – connection.

    If RDP access is not successfully enabled, click Retry Enabling RDP at the bottom of the failure notification page.

  7. Connect to machines using your Active Directory administrator credentials. You can then collect logs and run diagnostics.

Get help

If you still have problems with Citrix Managed Desktops, open a ticket by following the instructions in How to Get Help and Support.