OST Redirection On Terminal Servers
Posted on 2014-08-19
We have a client with three (3) Win2008R2 terminal servers that users connect through via an RDSH Gateway server. We do not use roaming profiles. Up to now, Outlook has been configured in non-cache mode on the terminal servers. The client also utilizes MS Dynamics CRM with the Outlook CRM add-in. I recently migrated them from Exchange 2007 to Exchange 2013. A side-effect of this is that the CRM add-in now causes Outlook slowness when replying or forwarding messages - sometimes it takes 5-10 seconds for the reply/forward window to come up. We determined the issue went away if we put Outlook in cache mode, but this was undesirable because of the space that would be used on the terminal servers because of OST files that would generate for all users. We had a ticket open with Microsoft on the issue and they said the CRM add-in is only supported in an Exchange 2013 environment with Outlook in cached mode. Or rather, they changed their support matrix for CRM to that end in real time because of our call.
So now we're back to turning on cache mode in Outlook. We've purchased hard drives for a new volume on each TS. We want to redirect OST files there with minimal administrative effort. In other words, without logging in as every user and recreating their Outlook profile. What would be the best way to accomplish this?
Thanks for any suggestions.