In the Manage Product Keys dialog box, select the product key and click Deactivate. Start the application on the computer where you originally installed it. Deactivate a product key on a computer with internet access
Tableau desktop releases license#
There are two ways to deactivate a license depending on whether the computer has internet access.
Tableau desktop releases how to#
Note: For information about how to deactivate a Tableau Desktop or Tableau Prep Builder product key from the command line, see "Deactivate the product key" in Install From the Command Line. If you are using a single TC key, then you only need to deactivate the key on one product and it will deactivate the key for both Tableau Desktop and Tableau Prep Builder.įor more information about the different license types, see User-based licenses (Link opens in a new window) in the Tableau Server online help. If you are using separate keys for Tableau Desktop and Tableau Prep Builder, you will need to deactivate both product keys. A product key that starts with TC can be used to activate or deactivate both Tableau Desktop and Tableau Prep Builder. If login-based license management is not being used in your enviroment, you may have one or more separate product keys that you can use to activate Tableau Desktop and Tableau Prep Builder.ĭepending on the type of product key you have, you may have a separate key for Tableau Desktop and Tableau Prep Builder or you may have one key that you can use to activate or deactivate both products.įor example a product key that starts with TD can be used to activate or deactivate Tableau Desktop only. If you get an error and can't activate Tableau Desktop or Tableau Prep Builder using your product key, contact Tableau Support (Link opens in a new window). Note: If the computer or virtual environment is no longer available to deactivate Tableau Desktop or Tableau Prep Builder (for example the computer was lost or stolen), you can activate by signing into Tableau Cloud or Tableau Server using login-based license management, or use the product key on a new computer. You can activate Tableau Desktop on up to two different computers if they are used by the same person and one computer per user for Tableau Prep Builder.
If you are using Tableau Desktop or Tableau Prep Builder in an environment with login-based license management, you do not need to deactivate any product keys if you want to move your installation to another computer. A file system repository can be placed in to any subdirectory of any directory specified here.If you no longer need Tableau Desktop or Tableau Prep Builder on a computer or you want to move it to another computer, deactivate the product key before you uninstall Tableau or you may not have the license available to activate on another computer. Each plugin will be contained in a subdirectory.
Canīe overridden by setting the ES_JAVA_HOME environment variable The bundled Java Development Kit used to run Elasticsearch. The location of the data files of each index / shard allocated Generated TLS keys and certificates for the transport and http layer. Path is to the auto-generated CA certificate for the HTTP layer.īinary scripts including elasticsearch to start a nodeĪnd elasticsearch-plugin to install pluginsĬonfiguration files including elasticsearch.ymlĮnvironment variables including heap size, file descriptors. Use the CA fingerprint editĬopy the fingerprint value that’s output to your terminal when Elasticsearch starts, andĬonfigure your client to use this fingerprint to establish trust when itįingerprint of the security certificate by running the following command. To your machine and configure your client to use it. If the auto-configuration process already completed, you can still obtain theįingerprint of the security certificate. Other clients can establish trust by using either the fingerprint of the CAĬertificate or the CA certificate itself. Fleet Server and Fleet-managedĮlastic Agents are automatically configured to trust the CA certificate. Any clients that connect to Elasticsearch,īeats, standalone Elastic Agents, and Logstash must validate that they trust theĬertificate that Elasticsearch uses for HTTPS. The hex-encoded SHA-256 fingerprint of thisĬertificate is also output to the terminal.
0 kommentar(er)
