When Microsoft released Microsoft Office Sharepoint Server (MOSS) 2007, it was touted as The Next Big Thing™ for enterprises. And that’s where the good news ends…
This piece of software has so many issues I don’t even know where to start. My first encounter with it was when I had to evaluate the web content management features of the product. That evaluation period lasted about a week, but was stretched to a month just for the sake of it. When coming from something like eZ Publish, it felt like I had done some time travelling all the way back to the Stone Age .
A remarkable feat that Microsoft managed to pull was to release an anti-developer product. My career is still pretty short, but it was the first time that I encountered a piece of software that was set on making a developer’s life as hard as possible.
After the dust had settled and a couple of holidays had joined other historical facts, it was time for the second encounter. The idea was to give the collaboration features of MOSS 2007 a test run. So my colleagues and I clicked around when we suddenly noticed the “My site” link. A harmless link  to a personal site… until we (= 3 persons at that time) managed to click at the same time: one arrived at the personal site, one got an error but managed to proceed and the other one got an error and another one when trying to proceed. Guess which one was me… I was told it was caused by the speed of the network connection. Makes sense? Not to me.
The security settings regularly start leading their own life causing all sites to go down, file uploads went wrong and blocked all edit actions on document lists, etc. These are just a couple of things, but I could go on for quite a while. It’s at a point where I don’t know whether to laugh when it goes wrong or to cry with the fact Microsoft managed to produce such a nightmare.
: I know there were no computers back then, but let’s forget that little detail so I can make my point 😉
: Or so it seemed…