Using Classic Outlook on Windows for personal email, calendar, and contact management
I've just been reading through the details on the Microsoft support article for this issue (link).
The details they give under Scenario 2 could be an issue if roaming of the %localappdata% folder is no longer supported:
- For those of us that use User Profile Disks (not FSLogix) with multiple RDS session hosts, how do we prevent the %localappdata% from being roamed between session hosts?
- If roaming of the %localappdata% is no longer supported, does this effectively mean that using M365 apps inside a multi-session host RDS environment is no longer supported as well?
Scenario 2:
In the second scenario the error "Something went wrong [1001]" is caused by user profile management issues.
In this category of issues, we find that on both VDI and physical devices the user profile data is being roamed and that can cause identity and authentication data components to be in a bad state.
Roaming any data under the path %localappdata% is not supported. If you choose to move content under %localappdata%, make sure that the content of the following folders and registry keys never leaves the device under any condition.
- %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
- %localappdata%\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy
- %localappdata%\Packages<any app package>\AC\TokenBroker
- %localappdata%\Microsoft\TokenBroker
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\IdentityCRL
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\AAD
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WorkplaceJoin
Roaming of the work account's device certificate is not supported.