-
-
Cloud Connector Standalone Citrix Secure Ticketing Authority (STA) service
-
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Upgrade a deployment
Upgrading changes your deployment to a newer version of Citrix Virtual Apps and Desktops™ 7 without having to set up new machines or sites. The approach is known as an in-place upgrade.
Upgrading gives you access to the latest features and technologies that you’re eligible for. Upgrades can also contain fixes, clarifications, and enhancements from earlier versions.
To start an upgrade, you run the installer from the new version. The installer upgrades previously installed core components, VDAs, and certain other components. You then upgrade the database and the site.
Upgrade overview
- Review the information in this article before beginning the upgrade. The article is the primary information source for learning how to prepare for and implement an upgrade.
- Ensure that your current Customer Success Services dates are valid and have not expired. For more information, see the Customer Success Services renewal licenses article.
- Complete the preparation guidance.
- Run installers to upgrade core components.
- Upgrade the system databases and the site.
- Upgrade VDAs on images (or directly on machines).
- Upgrade other components.
Each preparation and upgrade step is detailed in the articles listed in In this section.
Before you upgrade
Complete these checks before you start the upgrade:
- Confirm which versions you can upgrade. See Versions you can upgrade.
- Make sure your current Customer Success Services dates are valid and have not expired. For more information, see the Customer Success Services renewal licenses article.
- Review all the information in this article before you begin.
Versions you can upgrade
You can upgrade to Citrix Virtual Apps and Desktops™ 2507 LTSR from:
- Virtual Apps and Desktops 2402 LTSR with or without CUs, up to and including CU2
- Virtual Apps and Desktops 2203 LTSR with or without CUs, up to and including CU6
- Currently supported CR versions of Citrix Virtual Apps and Desktops
Note:
- Before initiating the upgrade process, Citrix® recommends that customers test the upgrade in a controlled environment and verify that it meets their specific requirements. Additionally, we advise reviewing all relevant product documentation, including the deprecation list and known issues, to ensure a seamless transition. This approach helps mitigate potential disruptions to production systems and enhances the overall upgrade experience. For more information on the list of supported versions, see Product Matrix.
What you can upgrade
Use these guidelines to determine what you can upgrade and where to find guidance:
- Any component that the full-product installer or the standalone VDA installers can install, when a newer version is provided.
- For components not installed with the full-product installer (such as Citrix Provisioning™ and Profile Management), see that component’s documentation for guidance.
- For host upgrades, see the appropriate documentation.
What to expect during the upgrade
Plan for reduced capacity and a short service interruption. Understand the impact before you schedule the upgrade:
- Site availability: If you upgrade half of the Delivery Controllers first, users can still access the site. VDAs register with the remaining Controllers. The site might run at reduced capacity while fewer Controllers are available.
- Single-Controller sites: If your site has only one Controller, the site is inoperable during the upgrade.
- Database upgrade: During the database upgrade, product services are disabled. While services are disabled, Controllers cannot broker new connections for the site.
- New connections: Expect a brief interruption in establishing new client connections during the final database upgrade steps. Upgraded Controllers cannot process requests until the entire site is upgraded.
Back up the databases before you start. See Back up the databases.
In this section
Start with the upgrade procedure for the end-to-end sequence. Step 1 of the procedure directs you to the preparation tasks that you must complete first. The following articles support the upgrade:
- Upgrade procedure: Follow the step-by-step sequence to upgrade your components, database, and site. Start here.
- Considerations and limitations: Review limitations, mixed-environment guidance, and operating system support.
- Preparation: Complete the pre-upgrade checklist and preparation tasks, including the SQL Server version check, preliminary site tests, and removing PvD, AppDisks, and unsupported hosts. Preparation is Step 1 of the upgrade procedure.
- Upgrade the database and site: Complete the detailed database and site upgrade, either automatically or manually.
- Frequently asked questions: Find answers to common questions about upgrade order, versions, licensing, and permissions.
More information
Long Term Service Release (LTSR)
Long Term Service Release (LTSR) deployment updates use Cumulative Updates (CUs). A CU updates baseline components of the LTSR, and each CU includes its own metainstaller.
Each CU has dedicated documentation. For example, for the 2203 LTSR, check the link on that LTSR’s What’s new page for the latest CU. Each CU page includes supported version information, instructions, and a link to the CU download package.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
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.
If you do not agree, select I DO NOT AGREE to exit.