How to force profile to use outlook.ost instead of creating new (outlook0.ost) file?
Posted on 2009-04-14
A couple of weeks ago, I deployed a CMW to all machines and in that CMW, I enforced/enabled the cached exchange mode on existing profiles.
Though in my tests everything worked great, during deployment I came across a very bad behavior: upon starting outlook, profiles were re-creating a new OST file (outlook0.ost) and pointing to it, rather than continuing the point to existing outlook.ost files. This caused major traffic and thus downtime and I had to redeploy a new CMW to disable cached exchange mode.
I now need to once again re-enable cached exchange mode, but I DON'T want the profiles to create a new OST file... I want them to point to the existing and already-built outlook.ost.
How do I do this?
PS. I realize I can rename outlook.ost to outlook0.ost and this avoid re-creating a new ost. But I feel like it would be a cleaner solution avoiding this workaround and forcing profiles automatically point to outlook.ost, both for this time and for future reference, if possible.