2

Through my SharePoint career I've set it my policy to install:

  • Service Packs: Install as soon as they've come out. After evaluating on a test box, install to production
  • Cumulative Updates, Hot Fixes, etc: Install only if the need arises (for example we run into a problem one of them fixes).

The current person I'm with disagrees and likes to install everything the moment it comes out. I'm curious to see what everyone else here thinks of that policy and can point out times they had experienced when installing a Cumulative update for SharePoint was a lousy idea for them.

Long story short, how to you go about setting up patch rules for SharePoint? Specifically what steps do you take to implement a Service pack, Cumulative Update, etc. in your farm? How do you evaluate? What safeguards do you take against Service pack failure, etc?

Improve this question
1
  • +1 For having a policy and process. Many places still have the standard "Oh, updates. I should do those some day." policy.
    – Stu Pegg
    Commented May 12, 2011 at 19:22

2 Answers 2

Reset to default
2

From my experience:

  • Hot Fixes are to be applied IF and ONLY if the issue affects you. Hotfixes can go horribly wrong if applied in production without testing out in a staging environment first
  • CUs are usually pre-requisites for SP installs, so you can either do it in one shot before the SP Install or pace them out and do CU and then SP

We usually wait out a couple of months to 'review' upgrade stories before taking a dive into SPs. Also we tend to upgrade the Development VMs first before upgrading production.

Improve this answer
1

I agree with your stance and try to practice that as well. Even MS says only install this CU if you're being affected by something it fixes.

Improve this answer
2
  • I think this doesn't need to a be a wiki... especially if Microsoft specifically has documentation stating when a CU should or shouldn't be installed.
    – Kit Menke
    Commented May 12, 2011 at 20:15
  • It's asking for everyone's opinions though, irregardless of if there's a Microsoft recommendation or not. Meaning it's open ended and community wiki potential in my opinion.
    – Eric Alexander
    Commented May 12, 2011 at 20:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.