SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Just finished installing SP2010. Is it good practice to install hot-fixes or sp1 before stating with the full configuration?

Is there an order I should deploy these hotfixes or sp? If yes, what all I should install and the order?

share|improve this question
up vote 5 down vote accepted

Typically my team doesn't just install the "latest" CU, but the latest one we are comfortable is stable. Currently we are going to August CU. We install all system patches, SP1 and the CU update before configuring the farm.

share|improve this answer

I suggest running Windows Update with the additional recommendations for Office enabled. This will get your updates installed and happy. If you're doing it manually, download SP1, then the latest CU, which I think is December

share|improve this answer

Always install the latest service pack but the CU is optional. Officially, Microsoft only recommends installing the CU if it contains a fix for an issue you are seeing.

Unofficially, whenever I build a new farm I always install the latest CU and haven't gotten bit yet.

share|improve this answer
Except if you want UPS to work, then you need at least the June CU as well as SP1 ;) – James Love Feb 9 '12 at 21:46

Don't forget CU for SQL Server, they are sometimes appreciate.

share|improve this answer
Is this supposed to be a comment instead of an answer? Let me know and I can convert it for you... – Kit Menke Feb 10 '12 at 19:18

In addition to what has already been said, you can slipstream the contents of CU's and/or service packs into the install itself.

share|improve this answer

Installing updates that only apply to a certain bug that fixes your environment sets a farm to multiple issues. As a PFE, I recommend picking a strategy of applying either current CU (N) or N-1 or N-2 at the most. Keeping a patched environment saves unneeded troubleshooting and a generally healthier platform. If you are concerned about a CU, test in a lower life cycle before deploying. Installing SP and then CU is a typical scenario.

share|improve this answer
I believe our answers and strategies are based on similar ideas. I guess the part that I would challenge is targeting CU (N) initially if it is very fresh with little community feedback. As a PFE you may have access to additional information, but you have to admit that some CUs have been more stable than others. In addition, how quickly can or should an existing environment deploy a CU? The planning often takes 2 months in many of the environments I work in and by then another CU is available. – Mike Oryszak Feb 10 '12 at 3:24

I'm deploying the August 2011 CU on nearly every deployment at the moment. There are some issues surrounding Audience compilation it seems there are some fixes in the Dec 2011 CU and we will be tested that soon.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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