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 2013
April 08
Slipstreaming Patches into SharePoint 2013

Now that the March 2013 PU is out we have a patch to play with. And this isn’t a normal patch. This patch is important. It will have to be installed in order to install any future patches. You should consider this the base version of SharePoint 2013, especially for new farms. One of the first things I wanted to test was slipstreaming the patch. The news was good, it’s the same process we used with SharePoint 2010. Just extract the update files into the Updates directory before you install SharePoint 2013. Nothing to it.

Let’s see how it looked when I did it. Here is what my directory structure looked like:

 

Kurgan 3-29-2013 8-22-05 AM

I copied the files from the SharePoint 2013 ISO into a folder in C:\Install. On a production system you would put this on a non C drive. After I copied the files over I peeked into the updates folder to see what’s in there. This is what I found:

 

Kurgan 3-29-2013 8-22-56 AM

That sounds delightful, let’s drop a patch in there and see what happens.

Extracting SharePoint 2013 patches follows the same process as SharePoint 2010, which you can find outlined in this brilliant blog post. Those are the instructions I used when writing this blog post. First I verified the March 2013 PU supported this.

 

Kurgan 3-29-2013 8-24-23 AM

Looks like it does. Let’s go ahead and extract it to our updates folder. After we accept the license terms our updates folder gets full of patch files.

Kurgan 3-29-2013 9-15-03 AM

Then install SharePoint 2013 the same way you normally would.

Let me know if you have any problems.

tk

ShortURL: http://www.toddklindt.com/sp2013slipstream

Comments

definitely install new farm from slipstream source

Because updating RTM farm takes forever (2hours in my case) with very little content.
 on 4/9/2013 1:24 AM

What about non-english versions?

Hi Todd

Thanks for the post.

The March 2013 PU can be downloaded in various language versions. So how would a Dane like me prepare a slipstreamed istallation image that includes a Danish language pack?

Thanks Again,
Jakob Rohde
 on 4/9/2013 1:40 AM

What about non-english versions?

Hi Todd

Thanks for the post.

The March 2013 PU can be downloaded in various language versions. So how would a Dane like me prepare a slipstreamed istallation image that includes a Danish language pack?

Thanks Again,
Jakob Rohde
 on 4/9/2013 1:57 AM

Service Bus and Workflow Manager update

I'm glad to see nothing changed here.  During March, they also released a Service Bus and Workflow Manager update.  Can those be slipstreamed?  I'm guessing no since they are picky about the order.
 on 4/9/2013 11:26 AM

Or use a script

AutoSPSourceBuilder is your friend:
https://autospsourcebuilder.codeplex.com/
 on 4/15/2013 12:30 AM

Re: Or use a script

Yup, that's a good idea, too.

tk
Todd O. KlindtNo presence information on 4/16/2013 8:38 PM

And ulterior CUs?

In my understanding, 2013 CU patches (post march) break this mechanic, so i currently use a 2013 march slipstream, then apply LP(s), then the latest CU.

I would be interested to know if there's a way to slipstream, say, the august CU with a french LP in one installation set, using either autoSPSource or good ol' extract :-)
 on 8/28/2013 7:48 AM

Re: And ulterior CUs?

The Language Pack patching is kind of a mess. They are separate products and are patched separately. Sort off. The Language Packs are installed separately. They are also patched separately at the Service Pack level. But at the CU level, each CU has all the patches for all the languages. That's why they're so much larger than Service Packs.  You can slipstream SPs into LPs. I've never tried to slipstream a CU into an LP.

You shoul try it and let me know. :)

tk
Todd O. KlindtNo presence information on 8/28/2013 8:36 AM

Let me rephrase that :)

i was wondering if you can extract a newer cu over the march slipstreamed cu and install sharepoint without collateral damage, which i think unlikely :-)

as for the language packs, that's a good question, as they can't be slipstreamed afaik. So as i said, i currently install the slipstreamed march, then LPs, then a more recent CU. It's long, but its the only way i found to be sure everything is patched :D

E.issaly
 on 8/28/2013 2:48 PM

Re: Let me rephrase that :)

E.issaly,
In theory you can slipstream newer CUs over top of older SPs and PUs and the installer should make it all work fine. In reality that started breaking around last August and slipstreaming might just be broken. :(

Language Packs are separate products from SharePoint. You can't slipstream Excel into SharePoint either. :) You can slipstream Language Pack SPs can be slipstreamed into the Language Pack install. There is an "Updates" folder. I _think_ you can also slipstream CUs there, but I don't think I've tried that.

Then run the Config Wizard at the end and Bob's your uncle! :)

tk
Todd O. KlindtNo presence information on 8/30/2013 9:16 AM
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.

Title


Body *


Today's date *

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

Twitter


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

Attachments

 

 SysKit