Just wondering if any of you with more experience with Roaming Profiles can explain this behaviour.
There's an old Roaming Profiles set-up that's been dragged along through the years and we're wanting to senset it.
One thing we're seeing is that for users who's roaming Profiles write-back haven't been working, (maybe permission error on some files) if we do something that might trigger it to star working again (like add folder exclusion), their local profile gets nuked.
It seems like this is only an issue with roaming Profiles that haven't been working, if they've been working, any changes we've made hadn't had the affect off killing the local profile and starting fresh.
I've check for any GPO settings that might be asking for the local profile to be deleted, but I haven't found anything. From what I understand, the profiles should only be merging.
Has anyone else seen behaviour like this before where a roaming profile goes from not working to working and it kills the local copy?
It's been a long, long time since I touched anything with roaming profiles. Just about everyone uses redirected folders now if they need that sort of functionality, and this is one of the reasons. Roaming profiles just proved very buggy historically.
man, I dislike redirecting things like the desktop... it's no longer a local folder and makes using it as a scratch pad super slow...
Ever since I embraced using OneDrive and Nextcloud, I would use junctions points. Folders like Desktop, Documents and so on would be stored in the OneDrive or Nextcloud folder and then I would use junction points. The user shell folders paths will still stay the same.
This is what I do.