![]() Optionally it can also be configured to communicate with AppController as part of a XenMobile deployment, VDI-in-a-Box is also an option. StoreFront communicates with Receiver, the Delivery Controllers and NetScaler (STA) with regards to external access. ![]() Within a XenDesktop Site you basically have two points of authentication, one of which is StoreFront and the other being the NetScaler Gateway. Both API’s act as a bridge between the StoreFront services, with the authentication service and the store service being the most important ones. Receiver for HTML 5, it provides access to applications and desktops using just a HTML 5 capable web browser, no locally installed Receiver is needed. There is also a so-called StoreFront Web API a.k.a. This API is primarily responsible for operations like, user authentication, enumeration, reconnecting, disconnecting, launching applications and desktops, power control and more. It talks to StoreFront using the StoreFront Service API, again using ports 80 and/or 443. This can either be a VDI or HSD orientated architecture. We’ll start with Receiver it’s installed on the end user device and communicates with NetScaler, StoreFront and the virtual and/or physical machines in the data center over port 80 or 443. Just as a pre-appetizer, let’s have a look at some of the main components that make up the Flexcast Management Architecture (FMA) today and, from a bird’s eye view, how they interact and rely on each other before we get into some more detail on this. A look at the main services that make up XenDesktop, or FMA if you will.ICA protocol stack breakdown, not really me taking but still.More specific, what happens inside the VDA during launch time.What happens when a resource, desktop or application, is launched.The application, or resource, enumeration process.Internal & external (NetScaler Gateway) user authentication steps.Compact overview on the main components that make up the FMA.Below you’ll find what I want to cover during some of the next (mini) chapters. It goes without saying that what applies to XenDesktop applies to XenApp as well since they are both part of the same Flexcast Management Architecture. I’ll try and break it down phase by phase, starting with a brief FMA overview, followed by the user authentication/enumeration process and take it from there. ![]() Make sure to check out one of my previous articles as well: Troubleshooting Citrix XenDesktop & XenApp 7.x? Read this! since I feel it’s closely related, enjoy! If you find any typo’s, and I’m absolutely positive that you will, just ignore them! So that’s what I tried to achieve here as well, hopefully you’ll find it detailed (and well written) enough, and next to this blog post I also included the option to download the information in. PDF and/or Word document for future reference. ![]() Whenever I am on the lookout for new information, whether it is for troubleshooting purposes or just to learn something new, I always hope to find two things… First of all, I hope to find detailed and well written information, and secondly, a way to download the information as a. Also, and even if it’s only for me, I think it’s nice to have all related information in one place and not scattered over multiple blog posts, which might be considered bad marketing by some, I know :-) However, I still feel that I’ll be able to provide you with some new insights on some of the topics covered. I am aware that most of the topics, not all though, that I’m going to discuss are very popular and as such are well documented, either by fellow community members or, in some cases, by Citrix. Throughout this guide I’d like to zoom in on the FMA, some of its main components and talk about what happens during some of the most common day-to-day operations and processes, so common that in most cases we don’t even think about what’s going on under the hood until… it breaks down! In fact, I guess it’s safe to state that, that goes for all problems in life, if you don’t know or understand the basics of what you are dealing with than you’re bound to get lost, fast. When troubleshooting a XenDesktop environment/architecture it’s important to know which components and services are involved, how they interact and what is supposed to happen during normal operations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |