Activating Tableau Desktop in Citrix

Published: 11 Apr 2017
Last Modified Date: 18 Dec 2017


How to activate and set up Tableau Desktop in a Citrix virtual environment. 


  • Tableau Desktop
  • Citrix


Setting up and using Tableau Desktop in a virtual environment like Citrix is similar to using Tableau Desktop in a non-virtual environment. From a business standpoint, you will need to ensure that there is only one named user for each Tableau Desktop product key, and that the system is auditable. From an implementation standpoint, the Citrix environment must be a persistent virtual machine. Please review the following activation and registration considerations for additional requirements.


The installation process for Tableau Desktop in a Citrix environment is the same for a non-Citrix environment. During installation, you are prompted to enter the Tableau Desktop product key and then register the product.


After you install Tableau Desktop, you will need to activate the product using the product key. The Tableau activation process uses the internet to connect to the Tableau licensing service to track product usage. If the Citrix server is not connected to the internet, you might need to perform an offline activation. For more information, see the Activating Tableau Offline article.

Note: Because Tableau Desktop product operates on a named user licensing model, you need to have a product key for each person that uses Tableau Desktop.


Each user that opens the application for the first time is required to register.


Before reprovisioning a Citrix server, make sure to deactivate Tableau Desktop. For more information about deactivating Tableau Desktop, see the Move or Deactivate Tableau Desktop article. After reprovisioning the Citrix server, you must active and register Tableau Desktop again.

Additional Information

If you do not deactivate Tableau Desktop before reprovisioning the Citrix server, you might see a "max extra activations" error. For more information, see Error "max extra activations exceeded".
Did this article resolve the issue?