Profiles are compatible only between the following client and server operating system pairs:
|Client operating system version||Server operating system version||Profile extension|
|Windows XP||Windows Server 2003 |
Windows Server 2003 R2
|Windows Server 2008|
Windows Server 2008 R2
|Windows 8||Windows Server 2012||v3|
|Windows 8.1||Windows Server 2012 R2||v4|
|Windows 10||Windows Server Technical Preview||v5|
For example, if you try to deploy Windows 10 in an environment that uses roaming, mandatory, super-mandatory, or domain default profiles in Windows 7, you experience the following behavior:
After you use a user account that has an existing Windows 7, Windows 8, or Windows 8.1 profile to log on to a Windows 10-based computer for the first time, a "v5" version of the profile is created.
By default, this feature is enabled in Windows 10 clients and uses a .V5 profile folder extension unless the feature is specially disabled. On older operating systems, the default was "v2" unless the hotfixes that are described in the following articles are applied and the steps that are mentioned in the articles are followed.
- Roaming, mandatory, super-mandatory, and domain default user profiles that were created in one version of Windows must be kept isolated from those that were created in another version of Windows.
- For more information about this issue in Windows 8, click the following article number to view the article in the Microsoft Knowledge Base:2887239 Incompatibility between Windows 8 roaming user profiles and roaming profiles in other versions of Windows
- For more information about this issue in Windows 8.1, click the following article number to view the article in the Microsoft Knowledge Base: 2890783 Incompatibility between Windows 8.1 roaming user profiles and those in earlier versions of Windows
Article ID: 3056198 - Last Review: Aug 5, 2016 - Revision: 1