Living in SharePoint “Mixed Mode”
It was 3 years ago this month that I configured and deployed my first SharePoint 2007 solution (running on beta software). At the time, I told myself that for some short amount of time I needed to live in SharePoint “mixed mode” (term stolen from the SQL Server authentication option). To me, “mixed mode” meant having to support customers who were running SharePoint 2003 or 2007. The challenge with it, of course, is differences in functionality, administration and general configuration. Do you know what? I’m still living in “mixed mode” (supporting several organizations that are still running SharePoint 2003).
Here’s the deal… very shortly, I’ll fall deeper into this “mixed mode”, most likely supporting 3 flavors of SharePoint. No problem; I’m ready. BUT… this time (wait for the bold statement) I think more customers will find themselves in “mixed mode”. Here’s why:
· SharePoint 2007 was/is widely popular and many organizations have rogue instances (small SharePoint environments started by IT or some other department or some satellite office). An organization may choose to not upgrade all of these environments immediately.
· Windows SharePoint Services sites may have come from various parent products… MOSS (obviously), Project Server, Team Foundation Server, etc. Again, these sites may continue to exist as SharePoint 2007 for some time until the parent product is upgraded.
· SharePoint 2007 usage spilled outside the firewall to include extranet and intranet sites. These sites may be on different schedules for migration than a core intranet portal.
What does this mean? IT (and I’ll argue the business side as well) must be prepared to support and maintain two versions of SharePoint. This means more core skills, more planning and more time. Think this through and get prepared. Here are some questions to ponder:
Will support come from the same team members?
Will your users understand the difference when you stop referring to it as ‘SharePoint’ and must distinguish between 2007 and 2010?
Will your 3rd party products support both versions, inclusively or exclusively?
Will you be able to identify the signs that will indicate the critical moment to consider an upgrade?
Do you understand the Microsoft technology roadmap well enough to help plan upgrades for those SharePoint touch points (like PS and TFS)?
Do you have a strategy for new SharePoint activity to help determine which environment to build in?
These are just a few of the several questions I have had to deal with over the last 3 years. It is not always easy but, with the proper education and investment, the right choice shows itself. Remember, it’s budget season – time to start thinking about 2010 – make sure you think this through and plan/budget accordingly.