I ended up rebuilding all user profiles by deleting them one at a time on the Remote Desktop Server user list, changing the storage location for Roaming Profiles for each user to a different name and then re-login and rebuild anything required (mainly the users folders including, App Data, settings, views, logins to apps etc from flat file backups). Took over 14hrs - thanks Microsoft Azure for your in-place recovery for Remote Desktop Server user profiles being absolutely useless, including useless support from any Microsoft Azure, Windows Server and 365 staff member on the issue itself and also on how to recover from backups without the error returning immediately. I am reminded of how 'in-the-wild' we are as techs for Microsoft products. If you want the job d9ne properly, you must do it yourself......
Unable to get Cached Exchange to Sync
We had a server crash for our Windows Server 2022 RDH (Desktop Experience) with Roaming Profiles copied from another Domain Controller Server Data Drive.
After the crash and restart of the RDH, staff advised that emails were not arriving (no new emails since the crash. Emails are being received in Outlook 365 on the RDH for around 15 users. Each user is experiencing the same symptoms. We tried at least the following to fix the errors and NOTHING has worked:
- Quick and Online Repairs to Office 365
- Uninstall and Reinstall to Change from Office 365 (64-bit) to Office 365 (32-bit)
- Removing the User Outlook Profile and re-adding
- Removing
- Outlook.exe /safe
- Clearing all add-ins
- Outlook.exe /cleanips
- Renaming a file in C:\Program Files{x86)\Microsoft Office\root\Office16 (in fact all files on the uninstall too).
- Restoring the Servers back to VM Backups from days before crash (both servers - only 2 in the network)
- Restarting Modems and Networking Equipment
- Cleared Filters for Synchronisation
- Cleared Offline Items (not that there are any once we delete/rename the .OST file)
- Removing User Profile from RDH and re-login to recreate
And yet this all results in sync errors showing in the mailbox (original problem) and no emails download (NONE) to catch up an old .OST or even from creating a new .OST file.
We tried the following to see the extent of the damage:
- Checking all Server Hardware and software is in healthy state
- Trying to use a different email mailbox from another 365 Tenant on these users and same error
- Trying to access these users mailbox from Online login (works fine)
- Trying to access a 365 mailbox from a different 365 Tenant and same error
- Trying to connect one of the user mailboxes from another PC on another site (works fine - both no caching and cached exchange mode)
- Trying to connect a user mailbox on the domain admin login (works fine)
- Almost all the resolutions we could find in Google Searches
This seems from the symptoms to be an issue with the user profiles, but I would have thought a VM restore to a time before the error would have resolved it if this was the case?
Really frustrating as I don't know why the restored Servers from backups before the crash would still yield the same issue??
The only thing that has seemingly fixed it for anyone online is to rebuild the user profiles from scratch - not ideal for 15 users......
Below are the error messages received for every folder or sync item in exchange many times while trying to sync a faulting mailbox on the server (users mailbox name redacted):
20:36:17 Synchroniser Version 16.0.17328
20:36:17 Synchronising Mailbox ’Mailbox Name’
20:36:17 Synchronising server changes in folder ’Inbox’
20:36:17 Downloading from server ’https://outlook.office365.com/mapi/emsmdb/?MailboxId=68411927-40’
20:36:18 Error synchronising folder
20:36:18 [8000FFFF-3EE-8000FFFF-560]
20:36:18 Unknown Error.
20:36:18 Microsoft Exchange Information Store
20:36:18 For more information on this failure, click the URL below:
20:36:18 https://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=8000ffff-3ee-8000ffff-560
20:36:18 Additional Info:
Failed while syncing item:
EntryID: No current item
Item:
ErrCtx: 0x09010801
Hresult: 0x8000FFFF
FnCall: 0x09010602