The idea behind this project? Before commenting, read the introduction blog post here 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, then 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.
Use Keywords: auto with the application and/or desktop of choice. When using so called Keywords, Administrators can pre-subscribe users to certain core resources so that their home screen won’t be completely empty when logging in for the first time. Let’s put the two together and see what happens, I’ll only use StoreFront in my examples.ĭue note that when using StoreFront users will first have to select and subscribe to resources (applications and/or desktops) from the store before they show up on their main home screen and can be launched. That’s why the user authentication process and resource enumeration basically go hand in hand. When a user logs in for the first time, meaning that there are no active and/or disconnected sessions lingering around somewhere, right after the user is authenticated the resource enumeration process kicks in and will eventually show the user its assigned resources. What happens when a user logs in, authenticates and so on. Now that we have looked at the various individual FMA components and services involved, let’s have a closer look to see how everything works together.
0 kommentar(er)
