I'm having an issue with roaming profiles not pulling down on new Windows 10 desktops.
Created the username.V5 folder
Copied data from V2 to V5
Gave full control and ownership to the user
Made the user a local admin on the W10 workstation
Still getting errors that the profile is not synched. Nothing pulling down at all from the 2008 server.
Has anyone successfully used roaming profiles between 2008R2 and Windows 10?
I deleted the V5 and local, deleted the users SID out of registry and rebooted.
I created a test file on her desktop, rebooted, browsed out to the V5 share and it was there.
This is where it went south...
I had to change ownership on the V5 so I could access it (With a domain admin account). Gave the user and admin full control, then gave her ownership again.
Now I'm getting the temporary profile error again. I can't win with this thing.
Cliff Galiher
Changing permissions will break profiles absolutely. That is by design. Delete and restart and let the system work as it is supposed to.
RISLA
ASKER
I need domain admins to have full access to the profiles for backup, restore, or even just placing new icons on their desktops. How can I accomplish this? Off the bat the V5's read 0 bytes and empty because I (ADmin) don't have permission to the folder.
When I upgrade someone from W7 to 10, how am I moving their desktop icons? The only thing I can think of is logging in as the user on their new PC, browsing to their old V2, and copying to the desktop. Having access was always a convenient way to just copy and paste.
I do go into roaming profiles regularly to see who's using the server space with anything that's not work related. Is there a way to give the user and domain admins full control over the profiles as we've always done up until this upgrade to W10?