Forum Discussion
FSLogix with O365 Container on RDS 2019 Server, some users Intermittently get "The information store
https://learn.microsoft.com/en-us/office/troubleshoot/activation/shared-computer-activation#FSLogix%20issues%20with%20shared%20computer%20activation
- we have already played with this. It hasn't helped. In addition, when the outlook connectivity to exchange online breaks, office is still activated. Word excel etc, still works fine, you are still licensed. You just can't connect to exchange online.
We are not sure why going into word, going file account, and the signing out and back in, in word, fixes the connection to exchange online, but I imagine that the authentication token that is used for syncing settings in word, and for connecting to oulook to exchange online is probably shared, and outlook is trying to use an invalid token, it fails, and it is not asking to renew it. In word, when you sign out and in, it renews it, so outlook functions again. This is just an assumption though.
We also played with Hybrid joining the RDS hosts, but it seems to have no impact.We're having the same problems, and have been for the last few months.
It's actually good to see there are others out there with the same problem.
We don't use FSLogix though - our user profile disks are stored on a separate VM, so I don't believe the issue is specific to FSLogix.
I'm coming round to the conclusion that there is a fault/incompatibility between M365 apps and Remote Desktop Services/Multiple RDS Session Hosts/User Profile Disks.
Our setup:
- Windows Server 2019 Standard - Remote Desktop Services.
- Three RDS Session Hosts.
- User Profile Disks.
- 60 users.
- Windows and Office always kept up to date with latest updates.
Things tried so far:- Signing out of Microsoft account via Word or Excel, then signing back in.
- Steps on this site: https://www.matrix7.com.au/microsoft-365/o365-outlook-logon-error-something-went-wrong-1001/
- Completely recreating the users' RDS profile.
Usually one or a combination of the above will sort the problem, although often it won't sort it for good. We've got one user in particular that we've recreated the RDS profile for and it still won't work.
I think WihanHerbst is on to something with the authentication token - I've wondered the exact same thing, given that we have multiple RDS session hosts.
