Updating at t roaming
Before Windows Vista the only way you could configure the roaming profiles path for a users was by configuring it on the users account via Active Directory Users and Computers.
While configuring the roaming profile path on the users account is now far easier with the multiple user attribute update feature this still left the setting configured for each individual users and unless you do an audit of all the user account it is possible that some path’s could be setup incorrectly.
Explanation: I have added “\profile” onto the end of what would normally be the profile path so that when the profile is created it is placed at the same level as all the other redirected folders. If you are still running Windows XP this policy works very well if you have used a geographical OU structure (see Best Practice: Active Directory Structure Guidelines – Part 1 ) for your workstations as you will be able to send the users roaming profile path for each user to a local file server.
This would allow you to point users in the local site to the closest/quickest roaming profile server to reduce the time it takes to logon and logoff.
Below is the view of a users roaming profile configured to \server04.contoso.local\users$\%username%\profile .
If you are a Windows XP user this will translate to \server04.contoso.local\users$\sam\profile and if you are a Windows Vista/7 users this will translate to \server04.contoso.local\users$\sam\profile.v2 and if you are a Windows 8.1 with the “ registrey key enabled it will be \server04.contoso.local\users$\sam\profile.v3 Explanation: I have added “\profile” onto the end of what would normally be the profile path so that when the profile is created it is placed at the same level as all the other redirected folders. Reference: you setup the optional Profiles$ share for Windows XP then you will need to make sure the share you use is profiles$ (not users$) and there is no need for the additional \Profiles folder to be specified.
Error Message you will get if you do not add you file servers into the Intranet Zone.
As of the November 2013 Windows 8.1 update there is now a registry key you can set to spawn a .v3 profile to avoid conflicts with older versions of the profile.
In case you still wondering what User State Virtualization is then check out the overview video from Microsoft below: You have always been able to configured a users roaming profile patch by configuring the Profile Path on the users account (see image below).
This method allows you to granularly configure a users roaming profile path location however it is a lot more laborious process to ensure that they are consistent with the folder redirection policy that is also applied to the users.
However in ever since Windows Vista there is now a group policy setting you can apply to computers that configured the roaming profile path for anyone who logs onto that computer called “Set roaming profile path for all users logging onto this computer”.
Warning: The biggest problem with the Per Computer roaming profile configuration is that there is no way to exclude you administrator accounts from also getting this policy as it is a per computer policy.