My company is looking to upgrade to Office 2010 from 2007 and so far the project has been without major issues aside from one thing. About half of our test cases have Outlook 2010 freeze on the splash screen during "Processing..." after upgrade. This is resolved by clearing the OST file and relaunching in all cases.
We want to push this out to our company without user intervention and minimal helpdesk involvement so wiping *.ost from the local drive during the SCCM push and letting them repopulate on first launch would seem logical. Unfortunately a large number of our sites are fairly remote and have low-bandwidth connections, so a large amount of OST pulls simultaneuosly will effectively kill the internet at those site for long periods.
I haven't be able to find any mention of this issue around the forums and Google, does anyone have any suggestions for a coverserion of the in-place OST that can be run, a way to clear the OST and push a replacement during the overall Office push, or anything else that might help eliminate/mitigate this issue?