Hello all.
We are currently running View 5.2.0 and will be upgrading to 5.3.2 this weekend. We have 250 32-bit Windows 7 VM's on our network divided up into 8 pools all being linked persistent clones using Persona Management. This being said, we have a huge network latency issue when users login the next day after a company-wide recompose of all vm's. The latency starts when everyone logs into their vm's at the same time around 9:00am and the issue finally subsides about 1 1/2 - 2 hours later. I'm pretty sure this is due to the fact that everyone is creating a new local profile on every VM at the same exact time putting a lot of stress on the DC's to get profile information. How does everyone get around this issue? The only way I have been able to get around this is to only recompose groups of 30-40 VM's in one night and this is fine until we come across a major upgrade like the one I will be performing this weekend.
A little side question: Is it "OK" to upgrade to View 5.3.2 and have a View Agent of 5.3.0? Only ask because I would like to slowly recompose all machines unless I can get the issue above fixed in time.
