Hey everyone! I'm setting up a RDS farm with Windows Server 2025 that has multiple session host servers. I'm trying to figure out the best way to get user profiles to roam smoothly between these servers. I've noticed that apps like OneDrive, Teams, and Outlook don't seem to work well in this setup. I've tried several methods including appdata redirection, user profile disks, and FSLogix profile containers, but it always works only on the first logon. When a user logs in on one server, they can authenticate just fine in OneDrive, Teams, and Outlook. But when they log off and log back on to another server, they have to set everything up again. This back-and-forth is really frustrating—I've spent a ton of time trying to sort this out. Any suggestions would be really appreciated! Thanks!
6 Answers
Make sure to check the C:Users folder on each server for any leftover local user profile folders. If there are profiles, that might block the user profile disks from attaching, which could cause your issues. You might need to clean up those entries from the registry as well to prevent temporary profile issues.
Don’t forget about the registry key for 'roamidentity'! Also, activating device sync to Azure AD and setting up SSO should be key parts of your setup.
At a previous job, I used UPDs along with FSLogix, and it worked flawlessly for roaming profiles. OneDrive and Teams worked without any issues.
That's good to hear! I might give UPDs with FSLogix a shot again.
Used UPDs at my last gig and it worked great for roaming users—just something to consider. Although we didn't use Teams or OneDrive, so not sure how they would handle it.
I agree with FSLogix! Additionally, make sure you have SSO properly configured with Azure AD. That can really smooth out the user experience across different servers.
You should definitely go with FSLogix. It's specifically designed for this kind of scenario and handles OneDrive and Teams really well.
I hadn't considered that! I'll definitely check the profiles on each server.