For the past 5 months since moving to Office 2010, all our Outlook users who connect to our IMAP mail server will get the dreaded "0x8004010F: Outlook data file cannot be accessed" message every time they logon to a different workstation with our roaming profiles. We only have Windows 7 clients now, as we initially put the fault down to a bug with Windows XP.
We can get the users to continually reset their Outlook profile but this does not help get to the underlying issue, but mearly provides a band-aid solution in the short term.
Their main PST file is held on their network share. Their temp PST was held on the local station user appdata folder. We have tried reloating it to a network share via both the registry ForcePSTPath and the Outlook 2010 GPO PST setting. The files are happily created and work the first time the profile is reset, but any subsequent login's create a second or third temp pst file and srs file and the "0x8004010F: Outlook data file cannot be accessed" reoccurs.
We are tempted to migrate to an Exchange 2010 or @Live solution if it is the only way to resolve the issue, but would rather keep our current mail server solution (MDaemon), and be certain that if we move that the issue will still not exist.
