Regardless of which have XenApp or XenDesktop version currently in use, there is a simple upgrade or migrating to the current or latest version.
This post will help you to learn:
- , the available options for updating and migration
- has made five ways Citrix to the latest version, easier to move
- What the upgrade and migration process takes and where to find information
shows on the chart of the available paths. For example, a customer with XenDesktop 7.0 can currently be updated at a later 7.x version.
is a frequently asked question: "If I have 7.0 XenDesktop 7.1 or 7.5, I can directly upgrade to XenDesktop 7.8 without first to 7.6 or 7.7 upgrade? "
The answer is yes, update 7.8 directly on XenApp or XenDesktop.
The same applies to XenApp 6.5 directly to the migration to 7.8 XenApp: there is a migration. This simplifies the upgrade / migration experience; Customers have several upgrade / migration not go through cycles, thereby reducing the complexity, cost and risk of failures .
to define Upgrading and migrating strategy, you should also take into account the newly introduced long -term service release and current release service options.
Whether you choose LTSR or the current version, the following section 5 ways Citrix has easily latest version to move made.
5 Ways Citrix move made modern new technologies easier to stay on recent versions
ahead of the curve with new features
Each version with innovative features offers so that customers make the extraordinary possible. For example, include the new features in XenApp and XenDesktop 7.8 AppDisk Layering technology and App-V and AppDNA integration and much more.
support new OS and platform support
XenApp and XenDesktop to new Windows versions immediately. For example, support the latest XenApp and XenDesktop versions of Windows 10. So you can align your OS / platform migration strategy with the current XenApp or XenDesktop release.
Improved Quality set a new bar
Each version has an exponential reduction in the problems internally during the test, as well as externally in the field.
Each version also includes updates from previous versions seen so that it reported a better quality release. There are dedicated engineering resources to upgrade, increasing Upgrade Test and Automation cover 100% of the upgrade path table above have helped that much added to the confidence in the quality upgrade.
upgrade improves stability
has reduced the number of intermittent problems with upgrades, both internally and externally. to reproduce a number of race conditions, exceptions and tough problems that have appeared in customer environments has been fixed.
Low maintenance and management costs with direct upgrade
The inclusion of hotfixes, plus full end-to-end tests during communications, reduces the risk of errors. The ability to update directly (for example, 7.1 to 7.8), with no intermediate upgrades, reduced administrative costs and reduces the likelihood and the risk of unknown errors.
process and documentation for upgrade and migration
MIGRATION XenDesktop 4.x to XenDesktop 7.x
Migrate XenDesktop 4
If you are considering XenDesktop 4.x migration to a newer XenApp or XenDesktop release will be the migration tool useful.
to XenApp or XenDesktop 7.x
There are a few things I'd like to highlight
- to new operating systems and to get new features, customers have the Update option only VDA components , in contrast to other products / solutions in the market. Customers do not need to update the entire site and all of its components.
- Citrix also supports mixed VDAS while customers complete the upgrade process in phases. This helps to update a number of user groups / resources to the newer VDAS. After reviewing the customer can use the changes to the remaining groups / resources apply. With this approach, if there are problems, then can those be solved affect without the other groups / resources.
- As a best practice, you should "Test Site" in the Studio UI or console as checkpoints , to ensure that the site before and during the upgrade sequence is in good health. We recommend the following:
- Before upgrading start - Ensure that the report of "Test Site" produced without problems is green. Should problems arise, solve them first, before you start the upgrade. The upgrade workflow can not resolve problems that already exists in the application, and the modernization can make problems more complex, affecting the functionality of the website
- During the upgrade using checkpoints -. This ensures that the upgrade successfully advanced. Should problems arise, they dissolve before go in the upgrade sequence to the next step. You can run tests on the following checkpoints:
-
- updated
- test as each controller Updating
- Test as a location with Studio
- test be taken before the backup (s) [upgraded
- test as a series of VDAs and other components
further information, see the following:
the above diagram shows the sequence for XenApp and XenDesktop update. A few things I would like to highlight:
- to
- obtain new operating systems and new features, customers have the option VDA components only upgrade , in contrast to other products / solutions on the market. Customers do not need to update the entire site and all of its components.
- Citrix also supports mixed VDAS while customers complete the upgrade process in phases. This helps to update a number of user groups / resources to the newer VDAS. After reviewing the customer can use the changes to the remaining groups / resources apply. With this approach, if there are problems, then can those be solved affect without the other groups / resources.
- As a best practice should "Test Site" in the Studio UI or console as checkpoints , to ensure that the site before and during the upgrade sequence is in good health. We recommend the following:
- Before upgrading start - Ensure that the report of "Test Site" produced without problems is green. Should problems arise, solve them first, before you start the upgrade. The upgrade workflow can not resolve problems that already exists in the application, and the modernization can make problems more complex, affecting the functionality of the website
- During the upgrade using checkpoints -. This ensures that the upgrade successfully advanced. Should problems arise, they dissolve before go in the upgrade sequence to the next step. You can run tests on the following checkpoints:
- test how each controller will be updated Studio
- test is updated
- Test as the site taken before the backup (s) to be [upgraded
- test as a series of VDAs and other components
for further details, see:
- upgrade to XenApp or XenDesktop 7.6
- upgrade to XenApp or XenDesktop 7.7
- upgrade to XenApp or XenDesktop 7.8
I hope this was helpful. I appreciate any feedback about this or other topics you would like me to cover. You can leave a comment here, or tweet me at @ManbinderSingh.
0 Komentar