Browsed by
Tag: SharePoint 2007

SharePoint/Office 2007 Service Pack 3 coming Q4 2011

SharePoint/Office 2007 Service Pack 3 coming Q4 2011

The Office Sustained Engineering Team has announced that Service Pack 3 (SP3) for Office 2007 & SharePoint 2007 will be coming some time during 2011 Q4.  This appears to be the last major update to the 2007 client & server stack as the team states:

“We are offering this release in preparation for the April 2012 end of mainstream support for the 2007 client and server products. The October 2011 release provides a 6-month window to test and deploy the release prior to exiting mainstream support.”

The Service Pack will be a roll-up of all prior 2007 Cumulative and Public updates since Service Pack 2 plus some new hotfixes.  As always with the SharePoint 2007 world, you will need to install the WSS update before the MOSS update.  There is not a planned or expected CU requirement following the SP3 installation. 

To quote the article directly:

“SP3 will include changes in the following areas:

Office Client 2007 Suites
Office SharePoint 2007 Servers
Office SharePoint Search Server 2007
Office SharePoint Designer 2007
Office Project 2007
Office Visio 2007
Office Proofing tools 2007
Calendar Printing Assistant for Outlook 2007
Office InterConnect 2007
Office Compatibility Pack
PowerPoint Viewer
Visio Viewer
Office Servers Language Pack
Windows SharePoint Services 3.0
Office Access Runtime and Data Connectivity Components”

Soapbox time!!!!


As always, please plan to test your upgrade plan in your Development/Test/QA environment prior to ever consider installing in Production. 

Keep in mind that if you only have a Production environment, you really only have a testing environment.  Now is a good time to start updating your resume if you haven’t and you are even thinking about heading down an upgrade path. 

Consider spending as little as $50 a month with a company like CloudShare to get a testing environment.  They have a great pre-production hosting option that will allow you to validate your scenarios without having to invest a ton of capital to do it.

NOTE: Best Practices for installing SharePoint 2010 Service Packs and updates changed as of August 31, 2011 according to the Update for SharePoint 2010 Products page

“As a result of the new packaging, it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update.”

Keep an eye on this, the story has now changed and then changed back since RTM.

How SharePoint Governance is like a moose in a swimming pool

How SharePoint Governance is like a moose in a swimming pool

I was watching the news last night and a story came on about a man in Manchester, NH (about 30 minutes from my house) who heard a noise that was coming from his backyard, and when he turned on this lights he found a Moose in his backyard.  The moose was spooked by the sudden flood of light and charged through his fence and directly into the man’s swimming pool.


The man from didn’t have many options going in to the situation, it just descended upon him from nature and he was forced to simply deal with the situation.  He went from having a nice quiet evening at home to needing help from 12 people to get a moose out of his pool, having a shredded pool cover, and ending up with his saga documented on the evening news.

How this relates to SharePoint

Lying in bed after fasting all day for Yom Kippur, the Jewish day of Atonement, all I could think was how similar this man’s scenario was to all too many deployments of SharePoint: Someone hears something, starts to investigate, the next thing they know they have a 2000 pound angry animal on their hands.

In our many cases we have the ability to hold off the animal and redirect its efforts into something more productive and healthy with governance and proper planning, however many times the beast barrels through our defenses and we are dealing with a world of trouble that we didn’t intend on.

The man in the story had many options:

  1. ignore the situation and hope it clears itself up
  2. grab a gun and shoot it himself
  3. call a local hunter to deal with it for him
  4. calmly call the police and figure out how best to deal with the situation with expert assistance

I sincerely hope that when faced with situations like this we deal with things as well as the man from the news story did because in the end, all that was really lost was part of a fence, a $200 pool cover, and some time.

Here are a couple of things to keep in mind, whether you are dealing with an angry moose, or an impending SharePoint deployment:

  1. Find out what you don’t know
  2. Stop and determine the correct plan of action before proceeding
  3. Understand what the drivers of your situation are
  4. Get control over an out of control situation

When it comes to SharePoint deployments, whether properly conceived or not, it is always best to stop and examine your options.  It is always going to be best to take a bit of time up front to save a complete rebuild later.

The moral of the story

When cooler heads prevail, everyone comes out alive, and with a reasonably interesting story to share.  Think before you act, and in our world, before you implement.