First off, i have to say we are not really experiencing any problems with our Xendestop 7.6 configuration and systems. VDA's are registering without problems to the controllers and pretty quick as well.
However, it now seems that these speedy registrations are causing some side effects that result long logon times for users.
During the day users log on and off and desktops are restarted as a rsult so they are available again. Now we noticed that VM's that have just been restarted are also the first VM's to be assigned to a new user session again even tho there are 50 more VM's ready that have been ready for hours.
We suspect that these VM's, that have just been started, are still processing some configurations when a user session gets assigned to it.
So in order to prevent that we would like to know:
- is this working as intended? user sessions being assigned to the last VM that registered itself?
- is there any way to manupulate this? by example to delay the VDA registration or maybe a setting in the Desktop group?
It would be great if anybody could answer these question and even better if there is a solution!
If more info is needed please let me know.
We run a Xendesktop 7.6 configuration on a vSphere 5.1 hypervisor. And have a Windows 8.1 catalog with MCS random pooled vm's (about 550 desktops).
User personalisation is done with Appsense personalisation.
Question
Theo Portaal
Hello everybody,
First off, i have to say we are not really experiencing any problems with our Xendestop 7.6 configuration and systems. VDA's are registering without problems to the controllers and pretty quick as well.
However, it now seems that these speedy registrations are causing some side effects that result long logon times for users.
During the day users log on and off and desktops are restarted as a rsult so they are available again. Now we noticed that VM's that have just been restarted are also the first VM's to be assigned to a new user session again even tho there are 50 more VM's ready that have been ready for hours.
We suspect that these VM's, that have just been started, are still processing some configurations when a user session gets assigned to it.
So in order to prevent that we would like to know:
- is this working as intended? user sessions being assigned to the last VM that registered itself?
- is there any way to manupulate this? by example to delay the VDA registration or maybe a setting in the Desktop group?
It would be great if anybody could answer these question and even better if there is a solution!
If more info is needed please let me know.
We run a Xendesktop 7.6 configuration on a vSphere 5.1 hypervisor. And have a Windows 8.1 catalog with MCS random pooled vm's (about 550 desktops).
User personalisation is done with Appsense personalisation.
Thanks in advance!
Hans
Link to comment
18 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now