Cerulean
[H]F Junkie
- Joined
- Jul 27, 2006
- Messages
- 9,476
Greetings,
Right now with the current set of GPOs (like three dozen or so) and configuration it takes approximately 1-3 minutes for users to login. Our old computer system with terminal servers would take 2-3 minutes for users to login, or if about the same time -- there were other issues such as horribly under-specced and overloaded servers with 40 users per terminal server.
With a brand new set of GPOs (about a dozen or less) and OU structure that I carefully made and designed after spending several hours analyzing the existing GPOs and OU structure, it takes on average 16 seconds to login (best being 12 seconds, worst being 22 seconds). This uses VMware View Persona management storing profiles at \\srv-persona1\EXP_Profiles$\%username%. This is currently not being used by our North American environment.
If we use a persistent local profile through VMware View, login time is 2 seconds flat. Our Asian environment of at least 100 users uses this + the brand new set of GPOs and OU structure I created, but without VMware View Persona management (again -- persistent local profile).
At minimum, my supervisor is wanting to get the login time below 10 seconds -- aiming for 2 seconds, while using Persona management. He told me he would like to get rid of all of the GPOs (or as much as possible). I responded saying this is unrealistic and wrong, defeating the purpose of why GPOs as a feature exists and would also result in higher maintenance time and more frequent reprovisioning of hundreds of automated floating pools (something that from my understand is a pain in the butt and takes a very long time to do).
I don't think 2 seconds is a realistic goal. I think 10-20 seconds is fine. By industry standards / typical login times "at best" -- what is actually reasonable, why, and what company (or what is the size of the company)?
Right now with the current set of GPOs (like three dozen or so) and configuration it takes approximately 1-3 minutes for users to login. Our old computer system with terminal servers would take 2-3 minutes for users to login, or if about the same time -- there were other issues such as horribly under-specced and overloaded servers with 40 users per terminal server.
With a brand new set of GPOs (about a dozen or less) and OU structure that I carefully made and designed after spending several hours analyzing the existing GPOs and OU structure, it takes on average 16 seconds to login (best being 12 seconds, worst being 22 seconds). This uses VMware View Persona management storing profiles at \\srv-persona1\EXP_Profiles$\%username%. This is currently not being used by our North American environment.
If we use a persistent local profile through VMware View, login time is 2 seconds flat. Our Asian environment of at least 100 users uses this + the brand new set of GPOs and OU structure I created, but without VMware View Persona management (again -- persistent local profile).
At minimum, my supervisor is wanting to get the login time below 10 seconds -- aiming for 2 seconds, while using Persona management. He told me he would like to get rid of all of the GPOs (or as much as possible). I responded saying this is unrealistic and wrong, defeating the purpose of why GPOs as a feature exists and would also result in higher maintenance time and more frequent reprovisioning of hundreds of automated floating pools (something that from my understand is a pain in the butt and takes a very long time to do).
I don't think 2 seconds is a realistic goal. I think 10-20 seconds is fine. By industry standards / typical login times "at best" -- what is actually reasonable, why, and what company (or what is the size of the company)?