Office 365 deployment issues

When you are, like me, in the middle of a Office 365 deployment after a extensive period of testing, you don't expect serious issues to arise anymore. Well, it will happen, bet on it!

Which issues came up, you ask? Ok, let's start:

• First we had some Active Directory Federation Services authentication issues, like described in this article. Those issues were, to be honost, a configuration issue which should have been tackled by Microsoft itself in the first place!


• A second issue is that not all messages Office 365 generates makes sense. Like when trying to mount a corrupted .PST file. It starts with a message that the Outlook profile cannot be loaded and a end with a message that not enough system resources are available? The solution for this is to rename all of the .PST files, start Outlook, remove all the archives mounted within Outlook, rename the .PST files to their original name and mount them one by one to find out which one is corrupt.. A time-consuming way if you ask me!


• A third issue we were running into is that you can test days, weeks or even months, but somehow suddenly a program pops up, according to the user a critical application, which cannot be started, cannot spawn Word 365 or cannot print. And all of the problems are due to the Office 365 installation!? Even when the application is from the stoneage, like 2006 er earlier?

Don't misunderstand me, 95% of the deployment process is running smoothly with no issues whatsoever. Only, that last 5% takes so much time to please, solve, convince and migrate..