The Citrix Servers should have an installation of Tableau Desktop or Tableau Prep Builder with the Authority to Run (ATR ) option set (Virtual Desktop Support) but no activation performed.
Tableau Desktop and Tableau Prep must be able to communicate with either your Tableau Server or Tableau Cloud site to use LBLM in a virtual deployment. If license keys are still being used, Tableau Desktop and Tableau Prep Builder need to access the Tableau license server via Internet access. No offline activations are possible with this model.
When installing Tableau Desktop or Tableau Prep, be sure to set the activation duration to a value applicable to your use case. More information on the activation duration is available in this Tableau Community Blog. There are two installer flags that will improve the end user experience for a non-persistent delivery system, SYNCHROUNOUSLICENSECHECK and SILENTLYREGISTERUSER. Information on these settings is available in the "Additional configuration for virtual deployments" section of the LBLM Help Guide.
For more information on how to setup Tableau Desktop or Tableau Prep Builder in a virtual deployment, please see Configure Virtual Desktop Support.
A user will be entering a key or signing into a server (LBLM) with each new VM delivered. If LBLM is implemented, no product keys need to be entered but the end user will log into Tableau Server or Tableau Cloud.
If the end user opens Tableau Desktop and is delivered to the same Citrix Server before the ATR activation lease has expired, there will be no prompt to activate.
If still leveraging license keys and using Virtual Desktop, there is no need to deactivate the product key before returning the VM. The ATR license server will handle the activation management for you.
If the activation duration is not set properly, you might see a "max extra activations" error. For more information, see Error "max extra activations exceeded".
If the Virtual Desktop option (ATR) is not set for a non-persistent environment, a maximum activation error will occur.
001458049

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.