Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, September 7, 2015 8:57 AM
Does Windows 10 handle roaming profiles in the same way as Windows 7 in a Domain environment? One of my users reports she is not seeing the correct desktop after upgrading to 10. Not sure if there are other issues.
All replies (3)
Tuesday, September 8, 2015 2:09 PM
Ah.. .no.
Just like Win7 <> Win8.1 there are issues when using the same roaming profile.
There really ought to be a .v5 profile for win10....
Monday, September 14, 2015 2:23 AM
Hi,
Yes, Windows 10 roaming profile has changed a little bit, it uses new version of user profile called 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.
And some users reported the previous start screen under Windows 7 or 8.1 won’t sync to Windows 10 so seems like Windows 10 doesn’t support Start menu layouts of Windows 8.1 in present stage.
Regarding to desktop, we have not receive any report or similar issue yet, I’d suggest we looking into server for the answer. Did anything else synced without problem except desktop?
And make sure you didn’t disjoin the machine from domain before upgrade, it might cause similar issues.
Read this thread for more reference.
Regards,
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Sunday, October 25, 2015 2:27 PM
Hi,
More information on this. It is not roaming profiles that is the problem, but folder redirection; it seems that folders are not being redirected. My server software is Windows Server 2008 R2. I have seen posts for similar problems with other server software versions and am asking if there is a fix?