Apparently the hourly close-open ritual was too much of a hassle and I've gotten a call almost religiously on the hour for last 2 days. She only got new emails when she closed and re-opened outlook, but they showed instantly on mobile device and OWA. moved user over last Friday and inbox just stopped synching. Was having similar problems with Cached outlook 2010 and brand spanking new Exchange2010 server.
![cached exchange mode outlook 2010 not updating cached exchange mode outlook 2010 not updating](https://www.remosoftware.com/info/wp-content/uploads/2016/12/b1.jpg)
In fact, when the inbox is finished processing and Outlook proceeds to check the subfolders, emails will start to come in.
![cached exchange mode outlook 2010 not updating cached exchange mode outlook 2010 not updating](https://www.systoolsgroup.com/updates/wp-content/uploads/2018/06/outlook-rules-not-working-automatically-1280x720.png)
He does have an inbox of 700mb with several subfolders, but moving them doesn't seem to resolve the problem. I've not found this problem with any of our other remote users.
#Cached exchange mode outlook 2010 not updating install
I was able to reproduce this problem using a clean install of Windows 7/Office 2010 on a different laptop with a Verizon mifi to test outside our ISP. Apparently, when he's using the same ISP, the problem goes away. His emails would appear in his inbox within 1-2 minutes. He recently visited our area and his hotel uses the same ISP as our offices. When cached mode is disabled, he immediately receives his emails. When he first opens Outlook, the message 'Updating Folder" remains for 10-15 minutes before the first email shows up in his inbox. Outlook 2010 is configured in cached mode. Our user is located in the UK and he connects to our servers in Virginia either by VPN or via RPC.
![cached exchange mode outlook 2010 not updating cached exchange mode outlook 2010 not updating](https://www.usatechblog.com/wp-content/uploads/2020/06/increase-size.png)
To give you some background, We are currently using Exchange 2003 Enterprise with a front end server. I have an odd situation with one of our remote users.