There are often people who ask me, now that Citrix Xenapp/xendesktop product updates so quickly, what version should I choose. Before answering this question, you actually have to start with Citrix's current product release and update strategy.
If the use of Citrix products older students must know, as a very historical it software company, its products in the past is basically a yearly update, every May through the technical conference to make a notice, local September around the official release of products. And the released products are rarely cross-generational, typically SP (Service pack) or FP (Feature pack). If you want to cross-generational basic 2-3 years will be one time. This type of update, which seems slow at the moment, is normal 5-10 years ago.
So in a time of rapid it change, everyone is emphasizing agile development, which becomes less applicable. So Citrix at the end of 2015 proposed product life cycle planning such as LTSR and Cr.
LTSR: Long-term stable support version
CR: Current Version
https://www.citrix.com/support/programs/software-maintenance/xenapp-and-xendesktop-servicing-options.html
#在这里Citrix Cloud is a Citrix-owned SaaS service that has the opportunity to introduce the Citrix Cloud, a new business model that Citrix is promoting globally from North America, to drive users to the pure SaaS desktop cloud.
650) this.width=650; "src=" Https://s4.51cto.com/wyfs02/M01/9C/15/wKiom1lsIfjwYulZAACJQ30Jb6k146.png "style=" width : 800px;height:272px; "title=" Cr.png "width=" "height=" 272 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiom1lsifjwyulzaacjq30jb6k146.png "/>
650) this.width=650; "src=" Https://s3.51cto.com/wyfs02/M01/9C/14/wKioL1lsIfninrQXAACL6lWZIic145.png "style=" width : 800px;height:383px; "title=" Ltsr.png "width=" "height=" 383 "border=" 0 "hspace=" 0 "vspace=" 0 "alt=" Wkiol1lsifninrqxaacl6lwziic145.png "/>
, we can see. In this system, LTSR and CR are not completely fragmented two products, all CR is the average one quarter for the period (not more than 3 quarters) release a new version, it is characterized that each version will be added to new features (objectively speaking, almost every version has a very substantial content inside) personal suggestions if the new function, You can update for one cycle in half a year, or 2 versions. LTSR is 18-24 months of consolidation.
The biggest benefit of the CR version is the addition of the new features mentioned earlier, such as the recent release of Io Optimization,full CLONE in NVENC,MCS Preparation in Hdx3d, the new transport protocol EDT, and so on. However, as with any new product, new features will easily bring about the same problem, relatively speaking, its problem is commonly known as a relatively more bugs. (although each new version also fixes some known issues in the old version)
Therefore, for those who do not have special new feature requirements, more attention to stability of the user LTSR this long-term stable support version is more valuable.
LTSR is to choose a CR version as a blueprint, or a basic version, and then on this basis do not do any new features development and support, only one thing is to fix the bug. So LTSR we also commonly known as stable version, the reason is here. It collects various internal tests, customer feedback issues, and fixes the problem through Cu (cumulative Update) for all users.
Some of the benefits of this approach are:
- https://www.citrix.com/support/ product-lifecycle/product-matrix.html
-
#I also want to remind you to use the earlier version of 7. X students note that before the 7.11 version of 7. The life cycle of X is only June 18
-
The CU is a patch pack and also a full installation package. This means that if you are a 7.6 ltsr version, the CU can be upgraded to its latest version. If you are a new user, the new environment, you can also directly install the CU, directly deploy the latest version, without the need to first install 7.6 LTSR, and then install the CU. By the time the document was written, the latest version of 7.6 LTSR is the latest 7.6 LTSR CU4. https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-6-long-term-service-release/xad-whats-new/ Cumulative-update-4.html
There are a few things to note when using LTSR:
- LTSR is a generic term that has strict restrictions on many of the components in Citrix Xenapp/xendesktop, so in a production environment, do not assemble individual components at will, unless necessary. http://docs.citrix.com/en-us/xenapp-and-xendesktop/7-6-long-term-service-release/xad-whats-new/ long-term-service-release.html
-
Some of the components in the LTSR are not, such as personal vDisk, which are not included in the VDA. If you need to use the personal vdisk feature, you need to use the CR version.
- Each new version of CU needs to identify the SA-Citrix Product service expiration date, such as the latest 7.6 LTSR CU4 SA is valid for June 14, 2017.
From my personal point of view:
-
If it is a purely VDI project, without some new features such as the 7.6, it is highly recommended to use the LTSR and its latest CU version.
-
If it is an application virtualization, 3D-based projects are recommended to use the CR version, currently the latest version is 7.14.
Of course there will be many friends said, the current LTSR and the latest CR between the functional gap is too big, it is difficult to choose AH. Objectively speaking, this is indeed the case. The current 7.6 ltsr with the latest 7.14, the difference between 7 versions, the functional gap that is quite obvious drops.
But this problem will soon be resolved, according to the Citrix update cycle, a LTSR version is updated every 18-24 months, so as shown earlier in this year Q3 (expected in mid-August) Citrix will release the next version of LTSR, with the expected version number 7.15 LTSR. He will be modelled on 7.13/7.14, when the new LTSR version will meet your needs for functionality and stability for a long time.
Please look forward to it.
This article is from the "Citrix in the Cloud" blog, be sure to keep this source http://kaiqian.blog.51cto.com/236001/1948164
Citrix xenapp/xendesktop version is selected correctly