User State Virtualisation

Sounds great! But what is it really?

Microsoft describes user state virtualisation (USV) as “a collection of Microsoft technologies that enables synchronisation of user state information from individual computers to a central location. Centralised management and storage of user state is desirable because it provides users with mobility and flexibility while helping IT departments manage costs and compliance.”

USV is comprised of four main components; local data, Offline Files, Folder Redirection and Roaming Profiles.  Although none of these are new features in Windows 7, all have instead been improved to provide not only a seamless transition between desktops, but also when using laptops offline and online.

Roaming User Profiles

Network profiles can be used to allow users to roam between different computers on the network and access their personalised desktop. Such profiles are known as Roaming User Profiles. Roaming User Profiles (RUP) enables user profiles to be stored in a folder share from a network server and then downloaded to the user’s computer whenever the user logs on using their domain credentials. After the profile has been downloaded and applied to the user’s computer, the user will see their personalised desktop with all its application settings and operating system preferences, such as network drive mappings, printer connections, and wallpaper selections. When the user logs off, any updated profile information is uploaded to the network server. RUP thus replicates user profiles that contain both user data files and user settings (registry–based information) to the server, and synchronises it to users’ computers.

Folder Redirection

Folder Redirection (FR) enables specific folders within user profiles to be redirected to locations on network. Windows 7 supports the redirection of the following 13 folders found within user profiles: AppData\Roaming, Desktop, Start Menu, Documents, Pictures, Music, Videos, Favorites, Contacts, Downloads, Links, Searches, and Saved Games. These folders are referred to as known folders.  FR can also be used to significantly reduce the size of RUP, which results in faster logon/logoff times.

Offline Files

Offline Files (OF) provides users with the ability to work with local copies of files that are stored in shared folders on network servers, even when they don’t have network connectivity. Any changes to these local files are then automatically synchronised with the server when network connectivity is re-established.

Interoperability

Windows 7 introduces considerable differences against RUPs in Windows XP, and these changes cause incompatibilities between the two operating systems.  Microsoft has taken this into account by ensuring all Windows 7 RUPs end with “.v2”.  This does though mean that is it not possible to roam between Windows XP and Windows 7 environments, say during a migration; although by using FR we can provide a fairly seemless transition between the two.

Real worldy stuff

• If your support teams are used to deleting/renaming local user profiles in Windows XP, please be aware that this process has changed.  A registry under ProfileList will need modifying or deleting (I may discuss this in later post).

• Before you start anything, take the time to understand the requirements.  It may not provide any benefit in your organisation.  Mobile users for example?

• To allow users to traverse between environments (XP <-> Win 7) ensure that either; you don’t use RUPs or you have a RUP for each.

• Fully utilise FR, as not only can it speed up logon/logoff processes it ensures users data is available from everywhere.  I see a lot of companies redirecting the Desktop, Favorites, Documents and Start Menu to the users home folder, and by also implementing RPs it means that there is hardly any data lost if the user roams or if a client heaven forbid; dies.

• Ensure your roaming or folder redirected data is held on a load balanced /  DR happy solution.  Usually works well using DFS namespaces, although for smaller implementations a simply folder share does work….but not recommended.  If you have tiered storage capabilties, store your roaming profiles on the fast tier 1 disk, and leave the FR data on tier 2 slower disks.

• Ensure you have all the support tools in place before the migration begins.  Obvious, but Support Teams need the necessary tools to manage local and roaming profile, and understand the full spread of where individual parts of the users profile is located.

• The migration to Windows 7 could be a good opportunity to clean up user’s data footprint, and start a fresh profile / home directory.  By doing this you will isolate user’s data from each operating system preventing users from traversing seemlessly.

• Ensure your permissions are correct on the central folder for the roaming profiles, else you could end up in a whole world of pain.

• If you implement RUPs, ensure that you stop it from bloating by either limiting the profile size (User Configuration\Administrative Templates\System\User Profiles\Limit profile size) or by excluding folders (User Configuration\Administrative Templates\System\User Profiles\Exclude directories in roaming profile).  Both are very important in their own ways!

• Some additional GPO settings l like to implement on the clients that RUPs are going to be used on:

"System\User Profiles\Do not check for user ownership of Roaming Profile Folders"
"System\User Profiles\Add the Administrators security group to roaming user profiles"

Hope this gives a little insight.  Planning is key, understand the requirements and take your time to testing the different variation and underlining technologies.  User State Virtualisation touches many IT areas such as Active Directory Group Policies (very important), Standard Operating Environment / Windows 7 Build ,Central Storage (SAN / iSCSI / File Servers)(also very important), and even Service Desk Support Teams.  Be nice, be prepared; discuss the ‘proposed’ changes with them before its too late!