I just set up a View 5.0 enviroment the other day and I found my self discussing with the client where the user profiles should be stored and how important user experience in View deployments is.
So I thought it would help a lot creating a small list of pros and cons of user profiles in View deployments, based user assignment in pools versus Windows profile management.
Dedicated Pool with Persistent Disk:
No User Management: The persistent disk is used to store Application Data, Registry Entries, My Documents and all folders in C:Users/Documents and Setting/%username%. This is done using local GP.
With Windows Roaming Profile: The persistent disk take precedence. Nothing is roamed as Windows Roaming Profiles are applied as domain Group Policy.
With Windows Folder Redirection: The persistent disk takes precedence. Nothing is redirected. UPDATE* You can turn on Folder redirection. (Thx NetMedic 🙂 )
With View 5 Persona Management: Nothing is managed unless the Group policy is applied on the Image is self.
Dedicated without Persistent Disk:
No User Management: Everything is saved on the C: drive and will be deleted next time the pool is recomposed.
With Windows Roaming Profiles: The Profile is downloaded at first login to the VM, and when the pool is recomposed, the profile needs to be downloaded again. This will increase the size of the OS disk. Danger of profile corruption or the profile is not uploaded correctly at log-off.
With Windows Folder Redirection: Redirect folders to a network share rather than use the OS disk for data storage. Often used with Windows Roaming Profiles to streamline the login process. Used in all organizations that like to backup/control their user data J.
With View 5 Persona Management: A network share is used to store User Profiles and they are streamed to the View Desktop as needed. Data is synchronized every few minutes.
No User Management: Everything is saved on the C: drive and will be deleted next time the pool is recomposed or refreshed. Users gets a random VM from the pool and setting will never be the same.
With Windows Roaming Profiles: The profile is downloaded every time the user gets a new machine from the pool. Not a feasible choice with Floating Pools.
With Windows Folder Redirection: Folders are redirected but this is needs to be used with other user management tactics. Used with Windows Roaming profiles to decrease the size of the roaming profile.
With View 5 Persona Management: A network share is used to store User Profiles and they are streamed to the View Desktop as needed. If organizations are licensed for this feature this is the one that should be used instead of the slower Windows roaming profiles+folder redirection.
A small Excel chart for some overview of the user management: