We have a peculiar problem. Where we are at:We have started to test Windows 7 and have 3 Windows 7 PCs among 300 Vista PCs. We run roaming user profiles and have redirected my documents to a Windows Server 2003 file share.We run AppV 4.5.What we have noticed is that anyone who has logged on to a Windows 7 PC appears to be experiencing delays when the log off and later log onto aVista PC. The delay appears to occur at the same time as the synchronisation bubble appears. The problem is cleared by deleting the users roaming profile. The delay affects the start menu and task bar, but not the desktop or running applications (if you start them before the moment the freeze occurs.) Other symptoms include the task bar dissappearing from view, leaving only the round start button, if you click the synchronisation bubble. The freeze lasts about 1-2 minutes and leaves no trace in event logs. Does anyone know what the profile compatibility is between Win7and has anyone else come across this problem.Anthony Sheehy - .net

Hello Anthony, The structure of user profiles are same between Windows 7 and Windows Vista, however my advice to you is to keep Windows 7 and pre-Windows 7 user profiles completely separate. In my company, when a user gets a new machine with Windows 7, I rename their roaming profile and manually move all of the documents where they need to be. (You could use Vista's "Windows Easy Transfer" program to migrate settings.) Users with 7 on their primary machine may only use Vista machines if those machines have Group Policies that are disallowing roaming profiles and offline files.Thomas Lin

Thank you Thomas, Alas, in the environment we work in, the relationship between PCs and Users is dynamic and it is therefore not possible to tie a person to either version. For that reason it is also not possible to disable roaming. We may have a time of migration where Vista and Windows 7 will run side by side during the transition. At the moment it is 3 Win7 against 300 Vista (and those 3 are in the IT Department.) As far as I can tell (and please correct me if I am wrong) it is not possible to Policy where the profile is stored. If it was, we would use a reflective policy with a WMI filter on the PC version and all would be solved. So I would rather find the cause before we reach transition (which, thankfully is about 9 months away...) Anthony Sheehy - .net

Hello Anthony,The problems can also arise from user profiles not being properly unloaded during logoff. This can happen when poorly-designed applications try and keep registry hives open after the user logs off from the network. An easy way to tell that this is occurring is to scan the Application log on the user's machine for event IDs 1517 and 1524, which indicate that the user profile is not unloading successfully during logoff. To resolve this problem, obtain the User Profile Hive Cleanup Service add-on from the Microsoft Download Center. This service runs in the background and looks for users who have logged off but still have their user profile hives loaded. When it finds such users, it determines which applications have open handles to the registry and forces these handles to be released. You can download this utility here. Thomas Lin

Hi Thomas,Triple checked and this is not the problem. Interesting development though; we have spotted exactly when this occurs:If you log into a Windows 7 PC (profile and redirection in place) then go and log into a Vista PC while remaining logged into the Windows 7 PC, the start menu and taskbar freezes. If you log out of the Windows 7 PC and log into the Vista PC, the Start Menu and Taskbar behaves normal. If you log into the Vista PC and then log into another Vista PC, the Start Menu and Taskbar behave normal.There are no errors in the Vista PC log relating to this. Windows 7 appears to be holding on to something that Vista needs, and is a change of behaviour from Vista.Anthony Sheehy - .net