Virtual Desktop Vr Download

[Ben Hollinbeck]

Virtualdesktop support is an opt-in feature of Tableau Desktop 10.5 and later and Tableau Prep Builder 2018.2.1 and later that gives you the ability to optimize your installations of Tableau for non-persistent virtual desktops, or for computers that are regularly reimaged. The authorization-to-run (ATR) service enables the Tableau license server to manage the activation limits and deactivations of the virtual machines (VMs).

Starting with version 2020.1, virtual desktop can be configured for login-based license management (no product keys needed). This is the preferred, and often the required, method to implement a virtual deployment of Tableau Desktop when end users are not issued product keys. For more information, see Activate Tableau using Login-based License Management(Link opens in a new window).

With virtual desktop support enabled, Tableau login-based license management license capacity or key leases are automatically returned when not in use after a predetermined amount of time. This means that you do not need to manually refresh or deactivate the login-based license management lease or any product key. Tableau must communicate with Tableau Server or Tableau Cloud for login-based license management. If you are still using product keys, Tableau Desktop clients must periodically connect to the Internet to communicate with the hosted license service.

Without virtual desktop support, an activated Tableau license or login-based license management license lease remains in use until the license term expires or the license is deactivated, causing a maximum activation error. Using virtual desktop support with frequently recycled VMs or regularly reimaged computers means that the VM is returned and the activation is added back to login-based license management for a future activation request. Virtual Desktop manages the login-based license management activation or product key activation, which prevents the maximum activation error from occurring when configured with the correct activation duration.

When virtual desktop support is enabled, Tableau Desktop or Tableau Prep Builder periodically contacts a Tableau-hosted authorization-to-run (ATR) service to verify that Tableau is authorized to run, based on its license. When virtual desktop is configured to also use login-based license management, Tableau Cloud and Tableau Server work as a proxy to the ATR service to verify that Tableau is authorized to run with a valid Tableau Cloud or Tableau Server Creator user.

The ATR service verifies the license or whether the user is a valid Creator user, and the length of the authorization window. As long as this communication is successful, Tableau runs without any impact to the user. The diagrams below show the communication process between the client and licensing components.

By default, an instance of Tableau Desktop or Tableau Prep Builder is given a 14 day authorization window during which it is authorized to run. This means that after the initial authorization, you could use Tableau without any network connection for 14 days before the activation expired. The authorization checks are attempted regularly, and each time a check is successful, the authorization window is reset to its full length. This happens without any impact to you, unless there have been no successful checks and the window is nearing its expiration, in which case a warning message lets you know that you need to connect Tableau to the network so the authorization can be confirmed. The 14 day default is typically not a good value for deploying virtual desktop where you receive a new VM with every use. For more information, see Requested duration settings.

The length of the authorization window is determined by the value of the requested duration. By default, the requested duration is 14 days (1,209,600 seconds), but you can configure this to fit your environment depending on how often a user will be receiving a new VM or if the Tableau Desktop is of a persistent nature.

You set the requested duration in seconds. The minimum requested duration you can set is 4 hours (14,400 seconds) and the maximum is six months (15,552,000 seconds). Use the following guidelines to determine how to set the requested duration setting for your users:

For virtual desktops that are recycled nightly, set the requested duration to the minimum of 4 hours (14,400 seconds). This will allow you to reuse your product activations (either login-based license management or a product key) each morning and eliminates the need to remember to deactivate them each evening before the virtual desktops are recycled.

The benefit of using virtual desktop support is that for environments that regularly recycle their VMs, you can set a duration short enough to expire the license activation before the desktop is reused. This means that you do not use up all your activations. You will still need to enter the product key to run Tableau after the desktop is recycled. Login-based license management can improve the end-user experience in this scenario by requesting a sign in to Tableau Cloud or Tableau Server to activate Tableau Desktop or Tableau Prep Builder instead of entering a product key.

Virtual desktop support is an opt-in feature if you're not using login-based license management, so you need to enable the feature in order to use it (it is disabled by default). If you're using login-based license management, the Tableau-managed license service (ATR) is on by default, but the ATR duration and additional installer flags need to be set for Virtual Desktop support. The ways to enable virtual desktop when not using login-based license management depend on whether you are running Tableau on Windows or on the Mac:

Include the ATRENABLED switch if login-based license management is not being used (version 2019.4 and earlier, or manually disabled). The ATRENABLED switch is not needed if login-based license management is configured on Tableau Desktop.

You must run the command from the directory where the .exe file is located or specify a full path to the location of the .exe file on the computer. Do not run the setup program from a shared directory on your network. Instead, download the .exe file to a directory on the computer where you're installing.

The ATRREQUESTEDDURATIONSECONDS has a minimum setting of 4 hours (14,400 seconds). The following example shows the Windows installer command that enables automatic license deactivation and set the duration to 12 hours (43,200 seconds):

When creating a primary image for a large virtual deployment, the above settings are appropriate and no product key activation should be completed. When using a new VM, each end user will enter the product key or sign in to Tableau Desktop or Tableau Prep Builder if login-based license management is enabled.

If Tableau Desktop or Tableau Prep Builder is already installed, you can still enable virtual desktop support by editing the Windows registry to add an entry for ATREnabled. To change the default duration a license activation is authorized for, you can add an entry for ATRREQUESTEDDURATIONSECONDS.

If Tableau Desktop or Tableau Prep Builder is already installed, you can still enable virtual desktop support from the Windows command prompt. The atrdiag.exe program resides in the \bin directory for Windows and is a tool specific to the virtual desktop and login-based license management settings. The atrdiag.exe program can report on the values selected, change virtual desktop configuration settings, and initially configure virtual desktop. If Tableau Technical Support is needed, providing the output from the atr tool is often helpful.

If you encounter issues when configuring or using virtual desktop, you can collect diagnostic information about the computer that is running Tableau Prep Builder or Tableau Desktop using the virtual desktop diagnostic tool (atrdiag).

You can verify that virtual desktop is enabled and view the value set for the requested duration seconds in use for Tableau Desktop activation. The TTL Start and TTL End values reflect the current lease being used on the virtual machine (VM) running Tableau Desktop. The commands provided below will capture the state of your virtual desktop support installation, regardless of whether you have installed Tableau Desktop or Tableau Prep Builder.

To learn more about resolving issues with Tableau Desktop installation, see Troubleshoot Your Tableau Desktop or Tableau Prep Builder Installation or Troubleshoot Tableau Desktop or Tableau Prep Builder Licensing.

The Azure Virtual Desktop Store app for Windows is currently in PREVIEW.See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

The Microsoft Remote Desktop client is used to connect to Azure Virtual Desktop to access your desktops and applications. This article shows you how to connect to Azure Virtual Desktop with the Remote Desktop client for Windows, which only allows you to subscribe to a feed made available to you by your organization administrators.

You can also connect to Azure Virtual Desktop with Windows App, a single app to securely connect you to Windows devices and apps from Azure Virtual Desktop, Windows 365, Microsoft Dev Box, Remote Desktop Services, and remote PCs. For more information, see What is Windows App?

Here's how to install the Remote Desktop client for Windows using the MSI installer. If you want to deploy the Remote Desktop client in an enterprise, you can use msiexec from the command line to install the MSI file. For more information, see Enterprise deployment.

If you left the box for Launch Remote Desktop when setup exits selected, the Remote Desktop client will automatically open. Alternatively to launch the client after installation, use the Start menu to search for and select Remote Desktop.

If you have the Remote Desktop client (MSI) and the Azure Virtual Desktop app from the Microsoft Store installed on the same device, you may see the message that begins A version of this application called Azure Virtual Desktop was installed from the Microsoft Store. Both apps are supported, and you have the option to choose Continue anyway, however it could be confusing to use the same remote resource across both apps. We recommend using only one version of the app at a time.

3a8082e126