I do not like wiki's. Why did we need yet another markup language???
So Microsoft can now say that SharePoint supports wiki's but does that mean you should deploy them in your organization?
I have seen things like FAQ's built in wiki's and they drive me up the wall. Identifying what has changed in a wiki as the pages get bigger and bigger is not easy. If the information can be structured in any way then why not use a more universal format that allows the content to be better created, managed and consumed?
That is a lot of questions, but I'm going to try and use this wiki to ensure that my personal dislike for wiki's is not based on predujis.
So, this wiki is going to track my findings on the implications of an organization not upgrading the Office client and SharePoint servers at the same time.
In an ideal world you would update the client and server components of a system at the same time, but Microsoft has the Good, Better, Best approach to client version vs. server (thanks largely to the use of standards such as WebDAV and SOAP).
Customers will often have several SharePoint server deployments. Maybe a central Portal Server and several distributed WSS servers so there could be many combinations of client and server versions in use during a migration period which could take weeks, months or years.
Here are the scenarios I will cover:
In each of these I will try and cover the changes in behavior that may not be obvious and suggest ways around any sticky situations.
Another page