I currently have two Remote desktop Collections that consist of the following:
2 Desktop Session hosts with User Profile disk share, lets call them Desktop1, Desktop2 and \\share\desktop
2 Remote app Session hosts with User Profile disk share, lets call them Remote1, Remote2 and \\share\remote
In both collections i am having issues with the Office document cache becoming corrupted.
this happens mostly when the user are logged on to a diffrent node then the one they were on previously.
For the Desktop users they recieve the error message and is able to correct the issue using the repair document cache, this creates a new folder after renaming the old one.
however they are frustrated that they have to go threw all the error messages.
But for my Remote app users the problem is worse:
They are using Dynamics AX and from there they can start a mail merge that wants to open Word.
If their document cache is corrupted they are never prompted with the error message and Dynamics AX becomes unresponsive.
how can i provide my users with a better experience
I previously created this case in the Office forums,
https://social.technet.microsoft.com/Forums/office/en-US/b9d377f4-0eb3-49aa-aec9-8a7895d1ab04/session-hosts-remote-app-hosts-and-office-document-upload-center?forum=officesetupdeploy
but they suggested that my terminal servers were at fault and that i create a new post here.
My current work around:
I have Created a Group Policy user preference that deletes the Document cache folder upon login.
This prevents the document cache from being corrupted as the folder is created at launch of an office program.
This is not a permanent solution, but my users are no longer bothered by the issue.
