I like, no wait, I love lists… there, I’ve said it. But no, really, I think (bulleted) lists are one of the best ways to share facts and knowledge. That’s also why I used multiple lists in my book, dozens of them containing hundreds of bulleted (FMA) facts. Throughout the various chapters I highlight multiple so-called ‘FMA facts’, 116 in total to be exact and I conclude each chapter with a list of key takeaways. This post is meant to share with you most of the FMA Facts that I came up while writing The FlexCast Management Architecture, though I did slightly alter quite a few of them.
Citrix IMA vs. FMA… XenDesktop components and terminology cheat sheet
This post is meant to provide you with a quick comparison, a cheat sheet if you will, between the two architectures. As you all (should) know by now, with the introduction of XenDesktop 7.x XenApp became part of the Flexcast Management Architecture, or FMA in short, and with this came certain terminology and conceptual changes. Here I would like to show you how each former 6.5 (IMA) XenApp component has its equivalent in the FMA world. Although technically there are some differences, on the functional side of things there is not much between them. To be clear, I’m not focusing on features that are in IMA and (still) not in FMA.
Connection Leasing vs. Local Host Cache. Conclusion? CL doesn’t stand a chance!
When Citrix re-released their XenApp and XenDesktop products not that long ago, things changed. XenApp’s Independent Management Architecture, IMA, was no more and got replaced by XenDesktop’s Flexcast Management Architecture, or FMA. With it some of the functionality and features loved and used by many disappeared as well. Features like Sessions Lingering, Anonymous Users, Pre-Launch and a few more, were missed, and for some this even became one of the main reasons not to migrate at that time. Luckily Citrix has again reinstated some of the most popular features known to XenApp 6.5, again, not all, but some, in its latest XenApp release, version 7.6.