[ms office - 2013] Outlook OST Error

[networkmangler]

We have an annoying on going Outlook issue

 

We had this problem with Outlook 2010 and again with Outlook 2013. We have our own on site exchange 2010 server that outlook is connecting to

 

Users login open outlook and get the setup window appear. They press next, next, next finish with all the required settings getting pre populated and their outlook opens fine and everything works

 

Then if they login to a different computer they get the following error:

 

Your Outlook file cannot be configured

C:\users\%username%\AppData\Local\Outlook\%emailaddress%.ost

 

When I check that location there is indeed no file. I can manually create it and then if they re open outlook it works. The only other thing to do is reset their profile and they have to do the setup again

 

I found a Microsoft tech page that describes the issue but the fix doesn't fix the problem: https://support.microsoft.com/en-us/kb/3072598

 

Staff that have to cover a class that is in a different classroom to their own are getting a little miffed that when they go to another room they are unable to use outlook because of the issue

 

If anyone has any ideas on how to solve this I will be extremely grateful

[Norphy]

Turn off cached exchange mode in Outlook? It has a habit of causing more problems than it solves in my experience.

[john]

Turn off cached exchange mode in Outlook? It has a habit of causing more problems than it solves in my experience.

 

However you will increase load on exchange and could slow down performance for users and if your exchange server has a moment they will get no access to anything as its not online to access any mail. Cached mode was added for a reason just turning it off isn't the answer as it isn't actually a fix.

 

Do you have roaming profiles? If so the OST should roam with them assuming you've not blocked it from roaming and thus not be an issue or if you re-direct Appdata to somewhere else again it should follow and not be a big pain. If you don't do either of those things, perhaps users who are in another location could just use OWA instead.