We've been having some weird issues with domain profiles and View Persona/Composer/etc. We have a persistent desktop pool using linked clones with View Persona and folder redirection enabled. However, when a user logs into the desktop for the first time, it pulls the default domain profile from \\domain.com\netlogon\Default User.v2which is what we want, but it doesn't copy all the contents correctly. For example, it will only copy portions of the AppData\Roaming profile, and most of the registry keys such as "Shell Folders" are not updated to the new profile location. Therefore, the profile is pretty much useless. If we login to a physical desktop, the profile copies with no issues and all the settings are in tact. We have no special group policies that would prevent this, so it has to be something with Persona or the fact that the user persistent disk is drive D. If we rename the profile, it will pull the local profile from C:\Users\Default with no issues. In fact, we copied this exact profile to the network so we had a consistent profile across our physical and virtual desktops. Has anyone else experienced this? I might put in a ticket with VMware support, but they have been worthless on issues that are Windows 7 related (I don't feel like explaining the issue ten times to someone I can't understand). Furthermore, "Everyone" has full control on this folder so security permissions aren't an issue.
This may not be an option for you, or may make management too difficult, but have you thought about making the View Persona GPO settings a Local policy and not a domain policy? You can configure the Local GPO settings on the template instead.