About two and a half years ago I published the ultimate Citrix XenDesktop 7.x internals cheat sheet, version 1.0 and it turned out to be a big hit. In the meantime, it has been viewed over 80.000 times already. All the more reason to start working on version 2.0. Since I have been writing about Citrix technologies for the last couple of years I have built up a broad archive, which I can now partly (re) use and re-write to come up with an even more detailed edition, version 2.0 of the Citrix XenDesktop 7.x internals cheat sheet. I would strongly advice you to download a .PDF copy – If you like the blogpost, you’ll love the .PDF, trust me! It includes a full Table of Contents making it easier to navigate.
For your convenience – 100+ Citrix XenApp & XenDesktop FMA facts listed!
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.
Installing and configuring Citrix StoreFront, the web.config file!
Not to long ago StoreFront replaced WebInterface (yes, it’s still officially supported till June 2015) and with it came a bunch of cool new and (very) useful features like Receiver for web and StoreFront multi site configurations for example, offering load balancing and HA capabilities, user mapping, application subscription synchronisation, optimal NetScaler Gateway routing and a few more. Also, we are no longer bound to an external database, this is now taken care of by the build-in Windows Extensible Storage Engine. The downside, at least for me, is that most, but not all, of these features need to be configured and or modified in the web.config file, comparable to the WebInterface.conf file we have with WebInterface.