11/9/2022 0 Comments Citrix xenapp 6.5 features![]() ![]() And now that XenApp was suddenly a part of the FMA as well, some learning had to be done. ![]() This was around 2008.Īt that time (around the release of XenDesktop 7.0) if you were a diehard XenApp administrator who had nothing to do with XenDesktop, the FMA was unknown territory. It was quickly replaced by Citrix XenDesktop 2.0 (IMA-based technology), introducing Citrix’s PortICA technology, a huge leap forward. ![]() XenDesktop 4.0 (and previous versions) released earlier in 2009 was still primarily based on the IMA.Īs a side note, while the Citrix archives do not mention any of this–at least I wasn’t able to find any related information–the true birth of XenDesktop actually started with ‘Citrix Desktop Server’, which back then wasn’t considered to be enterprise-worthy by most and only provided some basic VDI features. As you might or might not know, the FMA originated with the second big XenDesktop release, which was version 5.0 back in December 2010, the 17 th, and stayed with XenDesktop until the 7.0 release – and forward – as mentioned. On the other hand, it did help in getting the FMA a lot more attention: suddenly Citrix-minded IT folks were aware that there was more than just the IMA, though they probably knew already. Of course, this announcement got a LOT of attention and unfortunately for Citrix not in a good way, I’m sure most of you can remember. As a final gesture, together with XenDesktop 7 they also released Feature Pack 2 for XenApp 6.5. This change also meant that any further developments around XenApp 6.5 (and the IMA) would stop as well: no more additional feature packs (with one exception) or other types of enhancements going forward. The idea behind this project? Before commenting, read the introduction blog post here And while in its early days the FMA was a VDI only platform it has slowly but surely evolved to now also support RDSH(hosted shared desktops) as well as hosted/published applications and tons of other enhancements and features. Although this might have come as a surprise to some, the FMA was always known to be the next generation architecture, providing enhanced scalability, robustness and manageability over the IMA. It marked the date that Citrix decided XenApp would no longer be sold as a separate product and would from then on be part of XenDesktop. XenApp became part of the FMA back in June 2013, the 26 thto be exact when Citrix launched XenDesktop 7.0 (previously known under the code name Excalibur). As it stands today, I think most of you know that both XenDesktop and XenApp are built on top of the FlexCast Management Architecture, or FMA in short. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |