- #CITRIX XENAPP 6.5 DIAGRAM OF LOGON PROCESS CHART LICENSE#
- #CITRIX XENAPP 6.5 DIAGRAM OF LOGON PROCESS CHART PLUS#
In XenDesktop 7 the FMA now combines provisioning and personalization tools for both desktops and applications. XenDesktop has been doing it this way for a while now so it should be ok.
![citrix xenapp 6.5 diagram of logon process chart citrix xenapp 6.5 diagram of logon process chart](https://els-jbs-prod-cdn.jbs.elsevierhealth.com/cms/attachment/98840cd6-d072-429a-8361-7624a406059b/fx1_lrg.jpg)
#CITRIX XENAPP 6.5 DIAGRAM OF LOGON PROCESS CHART PLUS#
XD7 Delivery Controllers don’t have a Local Host Cache (LHC) this means that user authentication, application enumeration (and requests) and user connection requests, plus a few more ? all need to come from the central SQL DB, including server Load Balance information. Data flow has changed and in some designs different rules now apply. Since Data Collectors (and thus Zones) are no longer part of the overall architecture and all virtual and or physical servers in XD7 basically function as ‘Workers’ or ‘Session only Mode’ (as far as the former XenApp servers are concerned anyway) this also means that most of our old XenApp designs don’t apply anymore and it might be time to re-think and re-design them. No more IMA protocol and Service, these are replaced by the XD7 Virtual Agents that get installed on all Virtual and or Physical machines provisioned through XenDesktop 7. With the introduction of XenDesktop 7 IMA is gone! But what does this tell us? Well… It basically means that Zones together with their Zone Data Collectors are gone (it’s now one big Site) so no more Zone preference policies and Load Balance policies are now applied at Site level instead of Zones. However, these workers still consist of the same bits and bytes as installed on a Data Collector compared to ‘just’ a Delivery Agent which are lighter weight, as Citrix puts it. As they only host user sessions and will (or can) never be ‘elected’ as an Data Collector for their zone they won’t get all the IMA store (database) information pushed into their LHC enhancing overall performance.
#CITRIX XENAPP 6.5 DIAGRAM OF LOGON PROCESS CHART LICENSE#
The picture below, owned by Citrix, isn’t new but it does still provides us with a clear overview on the overall XD7 architecture.Ī quote from Citrix: “Unlike XenApp, the Delivery Agent communicates only with the controllers in the site and does not need to access the site database or license server directly” Having quoted that, XenApp workers (session host only servers) offer the same sort of benefit. More on the overall architecture and its components in a minute. If the database isn’t reachable for some reason running sessions will keep working but new sessions cannot be established and configuration changes aren’t possible, keep that in mind. Make sure you implement some kind of database redundancy like SQL replication or clustering of some sort.
![citrix xenapp 6.5 diagram of logon process chart citrix xenapp 6.5 diagram of logon process chart](https://i2.wp.com/robbeekmans.net/wp-content/uploads/2017/02/logonsimcontol.png)
This database is very important, next to things like XenDesktop Site policies, Machine Catalogs, Delivery Groups and published applications and or (hosted) desktops, it also contains all live dynamic ’runtime’ data like: who is connected to which resource, on which server, server load and connection statuses used to make load balance decisions and so forth. The Controllers on their turn communicate with a central (SQL) database. Delivery Agents are installed on all virtual and or physical machines provisioned by XenDesktop 7, they communicate (and register themselves) with the Delivery Controller(s) and the license server. The FMA is primarily made up out of Delivery Controllers and Agents. Although they’re partly based on the Excalibur Tech Preview the information is still valid as it applies to basic infrastructure components and concepts which were already announced and ‘known’ a few months ago and haven’t changed since and probably won’t for years to come. Is it improved? Definitely! Detailed overview? Scroll down!ĭuring this Blog I will primarily focus on the FMA, for more information on the other components and technologies used in XenDesktop 7 check out some of my other Blogs. I thought it might be a good idea (and time) to have a closer look at FMA.
![citrix xenapp 6.5 diagram of logon process chart citrix xenapp 6.5 diagram of logon process chart](https://blog.citrix24.com/wp-content/uploads/2019/06/LB2.png)
Although it seems that the Independent Management Architecture (IMA) will probably be around for many more years to come, it’s all FMA from now on when it comes to future developments. One of the biggest releases in years! Of-course I’m just kidding, who could have missed that?! Citrix also announced XenApp 6.5 FP 2 which will be released in June, once again enhancing and extending XenApp’s life, a good thing if you ask me. Did you hear? Citrix officially launched XenDesktop 7 just a few weeks ago.