Update | Citrix Workspace app for Mac

Looking for:

Updating citrix workspace 

Click here to download CITRIX

     

Updates to Citrix Workspace app for Windows Prerequisites.Citrix Workspace Updates

 

The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation. The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions. Citrix Workspace app for Windows. View PDF. This content has been machine translated dynamically.

Give feedback here. Thank you for the feedback. Citrix Workspace app for Windows Citrix Workspace app Translation failed! Update January 11, Contributed by: L C.

The official version of this content is in English. Some of the Citrix documentation content is machine translated for your convenience only. Citrix has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Citrix product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Citrix, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated.

Citrix will not be held responsible for any damage or issues that may arise from using machine-translated content. Instructions for Contributors. January 11, Contributed by: L C. Citrix Preview Documentation. Third party notices. Document History. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente.

You can upgrade certain deployments to newer versions without having to first set up new machines or sites. This is called an in-place upgrade. To start an upgrade, you run the installer from the new version to upgrade previously installed core components, VDAs, and certain other components. Then you upgrade the databases and the site. You can upgrade any component that can be installed with the full-product installer and the standalone VDA installers , if there is a newer version provided.

For host upgrades, see the appropriate documentation. The following diagram shows the steps the upgrade sequence. Upgrade procedure contains details of each step in the diagram. Hybrid Rights licenses are term-based subscription licenses that are provided, in addition to the cloud service subscription, when a customer transitions or trades up from a perpetual license to a cloud service subscription. You can also purchase a Hybrid Rights add-on with your DaaS subscriptions.

Before deploying the new license file, update your License Server to the most recent version. If you have access to a Hybrid Rights license with no SaaS attribute, follow these steps to get access to the new Hybrid Rights license with SaaS attribute:.

Go to citrix. For more information, see Download licenses. The following image shows the Hybrid Rights license file with SaaS attribute in the Increments section. Most of the main product components can be upgraded by running the product installer on the machine containing the component. If one machine contains more than one component for example, Studio and License Server , all components on that machine are upgraded, if the product media contains newer versions of their software.

If the installation has a new version of the Citrix License Server software, upgrade this component first before any other components. If you have not yet determined whether your License Server is compatible with the new version , it is essential that you run the installer on the License Server before upgrading any other core components.

If the installation media contains a new version of the StoreFront software, run the installer on the machine containing the StoreFront server. If the installation media contains a new version of the Director software, run the installer on the machine containing Director. The Citrix Provisioning installation media is available separately from the Citrix Virtual Apps and Desktops installation media.

To learn how to install and upgrade Citrix Provisioning server and target device software, see the Citrix Provisioning product documentation. Leaving half of the Controllers active allows users to access the site.

VDAs can register with the remaining Controllers. There might be times when the site has reduced capacity because fewer Controllers are available. The upgrade causes only a brief interruption in establishing new client connections during the final database upgrade steps. The upgraded Controllers cannot process requests until the entire site is upgraded.

Preliminary site tests run on the first Controller, before the actual upgrade starts. For details, see Preliminary site tests. After you upgrade Web Studio, the version information might not update immediately. Citrix strongly recommends that you back up the database before upgrading. See CTX During a database upgrade, product services are disabled. During that time, Controllers cannot broker new connections for the site, so plan carefully.

The wizard generates and displays the scripts and a checklist of upgrade steps. For example, if the logging database schema does not change, the UpgradeLoggingDatabase. After the database upgrade completes and product services are enabled, Studio automatically tests the environment and configuration, and then generates an HTML report.

If problems are identified, you can restore the database backup. After resolving issues, you can upgrade the database again. From the newly upgraded Studio, select Citrix Studio site-name in the navigation pane.

To make Upgrade remaining Delivery Controllers available, create at least one machine catalog and one delivery group for the site. After completing the upgrade and confirming completion, close and then reopen Studio. If you used Machine Creation Services and a master image to create machines, go to your host and upgrade the VDA on the master image.

You can use any of the available VDA installers. If you used Citrix Provisioning to create machines, see the Citrix Provisioning product documentation for guidance about upgrading. After completing an upgrade, you can test the newly upgraded site. From Studio, select Citrix Studio site-name in the navigation pane.

On the Common Tasks tab, select Test Site. These tests run automatically after you upgrade the database, but you can run them again at any time. To avoid this:. Upgrade other components in your deployment.

For guidance, see the following product documentation:. When you update your deployment, several database schemas can be upgraded.

The following table lists which database schemas are upgraded in the process:. Additionally, Citrix has announced the deprecation of the PvD technology and recommends that customers start using Citrix App Layering going forward.

Citrix App Layering version 4. Also, PvD for Windows 10 continues to be excluded from 7. Therefore, customers should not use it with their 7. The following technologies and host types are not supported in Citrix Virtual Apps and Desktops 7 Current Release deployments:. If your current deployment uses PvDs or AppDisks, or has connections to unsupported host types for example, Microsoft Azure Classic , you can upgrade to version or later supported versions only after removing items that use those technologies.

If your current deployment uses public cloud host connections for example, AWS , ensure that you have Hybrid Rights License before upgrading. When the installer detects one or more of the unsupported technologies or host connections without Hybrid Rights License, the upgrade pauses or stops, and an explanatory message appears. The installer logs contain details. To help ensure a successful upgrade, review and follow the applicable guidance for removing the unsupported items.

Before you can upgrade your VDAs to version or a later supported version , you must remove that software, even if you never used it. When using the graphical interface, that removal can be done for you, or you can include removal options when using the CLI. A deployment upgrade cannot succeed until you remove all machines that are configured to use PvD. This affects catalogs and Delivery Groups. However, the VDA installers do. A deployment upgrade cannot proceed until you remove AppDisks from all Delivery Groups that use them, and then remove the AppDisks themselves.

A deployment upgrade to version or later supported version cannot proceed if the site has connections to unsupported host types, such as Citrix CloudPlatform or Microsoft Azure Classic. Complete the following tasks before attempting an upgrade. Selective component install: If you install or upgrade any components to the new version but choose not to upgrade other components on different machines that require upgrade, Studio reminds you. You upgrade the Controller but you do not run the installer on the machine where Studio is installed.

Studio will not let you continue to manage the site until you upgrade Studio. Components on earlier operating systems: You cannot install current VDAs on operating systems that are no longer supported by Microsoft or Citrix.

For more information, see Earlier operating systems. When you upgrade, Citrix recommends that you upgrade all components and VDAs so that you can access all the new and enhanced features in your edition and version. For example, although you can use current VDAs in deployments containing earlier Controller versions, new features in the current release might not be available. VDA registration issues can also occur when using non-current versions.

In some environments, you might not be able to upgrade all VDAs to the most current version. In that case, when you create a machine catalog, you can specify the VDA version installed on the machines. This is called the functional level. By default, this setting specifies the minimum recommended VDA version. The default value is sufficient for most deployments.

Consider changing the setting to an earlier version only if the catalog contains VDAs earlier than the default. Mixing VDA versions in a machine catalog is not recommended. If a catalog is created with the default minimum VDA version setting, and one or more machines has a VDA earlier than the default version, those machines cannot register with the Controller, and will not work.

For more information, see VDA versions and functional levels. When your environment contains sites with different product versions for example, a XenDesktop 7.

For details, see the StoreFront documentation. In a mixed environment, continue using the Studio and Director versions for each release, but ensure that different versions are installed on separate machines. Now, you want to use a newer component version, but that OS is no longer supported for the current version of the component. It indicates the latest valid component version supported for each listed OS, and the component version when installation and upgrade became invalid. These methods are feasible for VDAs.

If you want to continue using machines with the earlier OS, you can choose one of the following:. To manually download and install the required version of the.

NET Framework, see the related Microsoft article. For additional information about. Was this page helpful? Thank you! Sorry to hear that. Name Name is required. Email Email address is required. Close Submit. Featured Products. Need more help?

Product issues. Open or view cases Chat live. Other support options.