Skip Ribbon Commands
Skip to main content

Quick Launch

Todd Klindt's home page > Todd Klindt's Office 365 Admin Blog > Posts > Slipstreaming patches into SharePoint 2010
September 19
Slipstreaming patches into SharePoint 2010

I was cruising around the Ars Technica forums and saw a question about SharePoint 2010. The poster wanted to do a fresh install with the August 2010 CUs and wanted to know if he could just run the Config Wizard once after the SharePoint 2010 install and installing the subsequent CUs. I told him that should work, but I also mentioned he could slipsteam the CU into the install and save himself some time. I realized that I hadn't actually done that with SharePoint 2010 yet, so I decided to give it a go. Here's how you slipstream CUs (and eventually service packs, I assume) into SharePoint 2010.

First, let's agree on a definition of slipstreaming. Slipstreaming is adding patches or service packs to the installation of a product, in this case, SharePoint 2010. When patches are slipstreamed they don't require any extra steps to install. The install process installs them as part of its normal activities.

Second, let's be clear about when you should install CUs. CUs are the new hotfixes. You shouldn't install them just because they're out. You shouldn't install them just because your buddies did. You should only install them because you're having a problem with SharePoint 2010 and said problem is fixed in a CU. The CUs will patch discrete parts of SharePoint 2010, so you should also only install the CUs that fix your particular problem.

Okay, now that we've got all that out of the way, how do you do it?

You need to extract your SharePoint installation into its directories. For SharePoint server you do that like this:


I typed the following:

Md SharePoint 2010

OfficeServer.exe /extract:.\sp2010

If everything went well, you should get a dialog box telling you it was extracted successfully. It should look like this in the file system:


I've highlighted the part that makes this magic all possible, the Updates folder. To slipstream CUs, just drop their MSP files into that directory. At the end of the install process the installer will check for MSPs there, and install them. Below is how I slipstreamed both the June and August CUs into my new installation:

The stuff highlighted in red is the June CUs, the stuff in green is the August CUs. This demonstrates how to stack them. Since the patches are discrete, something that's patched in June (like filterpack-x-none.msp and wasrvwfe-x-none.msp), might not be updated in August. In that case, if you want the all, you have to extract all the CUs and copy them over in order. The bottom line shows that both June and August patch osrchwfe-x-none, so when we copy over the August CUs we have to make sure we overwrite the older version. You end up with an Updates folder that looks like this:

Now run Setup.exe like you normally would and install SharePoint 2010. Towards the end of the install process, the MSPs in the Updates folder will be installed automatically. You can verify they were installed by checking in Central Admin. Go to Upgrades and Migration > Check Product and patch installation status. This lists all the products that make up SharePoint, as well as their patch numbers.

I think Microsoft did a fabulous job with this. Not only does it show you the current version, but it lists all the previously versions as well. And, AAAND, there's a link to every patch you've installed. Now, this might seem dumb, why would you need a link to a patch you've already installed? If you add another server to your farm, that's why. Now there's no more fumbling around for an EXE you know you have, but you just can't find. Pretty slick. I've also got links to all the CUs downloads in my SharePoint 2010 Build Numbers blog post.

That's all there is to it. Again, be careful with CUs. Only install them if you need them.



Doesn't the C in Cumulative mean Cumulative?

You've never needed to load anything but the latest CU before... is this new to 2010?
 on 9/20/2010 6:59 AM

Slipstreaming Question

If I am doing a fresh install stall do you think I should slipstream?  I think I should.

I agree with you about adding CUs to environments which already exist.
 on 9/20/2010 7:12 PM

Re: Doesn't the C in Cumulative mean Cumulative?

It does, but it means the patches have all the patches for that product up to that point. The August CU has all the fixes from the June CU plus new ones. You don't need to install June then August.

It does not mean the CU patches every product in SharePoint. That's not what the word "Cumulative" means.

Todd O. KlindtNo presence information on 9/23/2010 9:39 AM

Re: Slipstreaming Question

You should only install a CU if it fixes a problem you have, regardless of where in your install process you are. For instance you should slipstream the June CU for the User Profile Service if you're using a SQL named instance. If you're not, you shouldn't slipstream the CU. If you want to install a CU you should be able to explain what product it's fixing. "Because it's the latest" it's good enough for CUs. They are tested as thoroughly as service packs and RTMs. You're risking the stability and performance of your farm in the new of being "the latest" if you install a CU that isn't addressing a problem you're having.

Todd O. KlindtNo presence information on 9/23/2010 9:41 AM

No mention of SharePoint Foundation 2010 patches ?


Thank you very much for the article. However, I am still unclear whether SP Foundation patches should be added on top of SP Server 2010. In the "Updates for SharePoint 2010 Products" page :

The Best Practices section says "We recommend that you always install SharePoint Foundation 2010 patches before you install SharePoint Server 2010 patches. This best practice ensures that you will be successful when installing updates"

So let's say I want to slipstream the CU Dec 2010, I assume I should extract the CU of SPF 2010 and SP2010 in the Updates subfolder ?

Thanks in advance for any help.
 on 2/7/2011 12:40 PM

Re: September 19 Slipstreaming patches into SharePoint 2010 Edit

I've got a blog post coming on this, but from my very short investigation it looks like the SharePoint Server CUs include everything from the SharePoint Foundation CUs.

Todd O. KlindtNo presence information on 2/15/2011 10:38 PM

Re: Doesn't the C in Cumulative mean Cumulative?

Cumulative updates do include updates from all previous CU's. There is no need to install each one of them:

"We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous update package. We recommend that you consider applying the most recent fix release that contains the hotfix that you need."
 on 3/7/2011 2:17 AM

How about Service Packs and Cumulative Updates?

Now that there is service pack 1 as well as cumulative updates, will I still be able to use this process to slipstream the updates? Will SharePoint Setup know in what order to apply the SP and CU patches?
 on 11/20/2011 1:42 PM

Re: How about Service Packs and Cumulative Updates?

I see that this scenario is covered in this post:
 on 11/21/2011 12:49 PM

You may not want to slip stream CU if Language Packs need to be installed

If you are installing Language Packs in the environment you should not slip stream CU, CU will only update components that are installed, which would mean when language packs are installed later you would need to reapply the CU just to get hotfixes for language packs on environment, otherwise there could be missing hotfixes
 on 2/7/2012 11:38 PM
1 - 10Next

Add Comment

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.


Body *

Today's date *

Select a date from the calendar.
Please enter today's date so I know you are a real person


Want a message when I reply to your comment? Put your Twitter handle here.