We have three pools that are built from the same base image and this occurs in all three pools. We recompose atleast once a month. When we do recompose, I recompose only one pool at a time and spread it over three nights. The next morning, when my user base arrives and starts logging in, my help desk starts getting calls, pretty steady throughout the morning from users that cannot login. Approximatly 20% of each pool will have this issue.
Users log in through zero clients. We use smartcard authentication. Almost never does a user have an issure authenticating into the zero client. All users have only one machine assigned and we have our zero clients configured to direct the user directly to their view client. Once the users has passed through the zero client and into the Windows 7 View client, they have to aggree<Click OK> to our compamies policies inorder to login. At this point one of three things can happen. 1) Single sign on works and users loads to their desktop. 2) Presented with "Other User" or "VMware SSO User" and cannot login with out the system being rebooted by the help desk. 3) Single sign on seems to work, but instead of loading the users profile, the system hangs, as our users say "Hanging on the blue screen", not to be confused with the BSOD. This is the default Windows 7 under water background that usually displays while the " O Welcome" (Windows 7 spinning doughnut preceding welcome). At this point the help desk will need to reboot that system to allow the user to log in. Once the system has been rebooted, either "restart guest" in vSphere or "Reset" from View Manager will work for this. (Reset from View sometimes take more then one try).
Both 2 and 3 can only be recovered by a reboot of the View client. In both cases, when the user tries to self-fix, by reinitiating the login sequence, they loop with the same results.
Things we have tried:
>Reset view clients shortly after they report as available in View manager after the recompose
>Normal Shut down/Restart initiated in vSphere once systems have become available in View after the recompose
>The above two twice, even tried a combination of the above, twice
>Nothing
>Reviewed Windows event logs after the recompose
Some machines indicate there is another PC on the network with the same name, but the time stamps are during the recompose and the event does not return subsequenctly
Machines that required a reboot to allow the user to login do not have any events recorded prior to the reboot.
>Reviewed this link: http://communities.vmware.com/message/1874507#1874507 and checked our settings in Zero client and View
>Still working on this one: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2005210. Our orginization does not allow me to see above my OU
My users are starting to get a little frustrated when it comes to recompose time. If anyone has any ideas on what I could be missing, or has other suggestions on how to resolve that, your help would be greatly appriacated. Thank you for taking the time to read this far 
and thank you for any assistance.