Been reading quite a bit about user profiles and stuff lately. I’ve always imagined profiles as this blob of user settings + data under the
C:\Users\<username> location. And every time we need to reset a profile there’s this arduous task of backing up the user data too and restoring it. Silly.
But turns out it’s just easier to use folder redirection and redirect all your data folders to a common place. Advantage of this is that roaming profile users can login any place and have the latest up-to-date data. None of the hassle of requiring a logoff-login for the profile to sync etc.
- https://serverfault.com/questions/465511/roaming-profile-vs-folder-redirection – Difference between roaming profile & folder redirection
- https://blogs.technet.microsoft.com/askds/2010/09/01/microsofts-support-statement-around-replicated-user-profile-data/ – You should not use DFSR for user profile data
- DFSN is a good choice for the profile path (as long as you don’t have multiple targets per folder). Here’s a good Citrix page with info and how one might do this.
- While reading the above I came across the top 10 common causes of slow DFSR replication. Might be useful some day …
- Useful: pre-seeding DFSR via Robocopy etc. (a more “official” TechNet version of the same info)
- Common DFSR configuration mistakes and oversights
- Good to know when folder redirecting. If network latency from client to server is larger than 80ms it switches to offline mode.
- http://www.htguk.com/everything-you-wanted-to-know-about_23/ – an ammazing post on roaming profiles and such
- Citrix recommends using the Windows folder redirection than their own.