SHARE
Last night I needed to create a Outlook OST on a drive other than “C”. I thought it would be a simple process, but it wasnt. As always when something doesn’t work right I Googled away and there was a lot of people who were trying to do the same thing with limited results. I came across many posts that suggested editing the registry. Normally when you edit the registry, things work. Its the brain of the computer. Everything you do interacts in some way with the registry. This is a real good time to stress the importance of backing up your registry before making any changes. Just open up the registry and export the setting, save it to your desktop or thumb drive, done. Anyway, I’m not going to recreate the instructions there are plenty of them on Google. A good one is: https://www.slipstick.com/outlook/config/how-to-move-the-imap-personal-folder-pst/.
This is the bottom line — IMAP *.ost files honor the ForcePSTPath key, not ForceOSTPath even though the data file extension is *.ost. This is the part that got me. I edited the registry as ForceOST Path according to countless sources on Google. That doesn’t work even though Outlook 2010 – 2016 uses the OST file format. It wasnt until I used ForcePSTPath that it worked even though the software doesn’t use PST. Yea Microsoft, that cost me 2 hours I will NEVER get back.
Onward and Upward.
