How to create a SharePoint slipstream using the latest updates(referred)

With the announcement of the December 2008 Cumulative Update and the changes in the software update model it brings, we felt it was a good time to revisit the topic of slipstreaming. This post provides the process for creating a slipstream installation source that uses the December 2008 CU as an example. You can simply replace the December 2008 CU with the February 2009 CU, April 2009 CU, and so on going forward because the process will be the same.

Here are the steps to create a slipstream to the latest bits:

1. Copy the RTM (release) media into a new local folder such as C:\SPSlipstream
2. Extract SP1 and copy the extracted contents into the C:\SPSlipstream\UPDATES folder that was copied when you performed step 1.
3. Extract the December 2008 CU and copy the contents into the C:\SPSlipstream\UPDATES folder.
4. If you are not using Windows SharePoint Services only, delete the wsssetup.dll file from C:\SPSlipstream\UPDATES folder.

A few notes:

1. Use the following command to extract a software package to a folder: /extract:C:\myfolder to extract to C:\myfolder. If you already agree to the EULA, use the /quiet switch to suppress the EULA.
2. If you have a Windows SharePoint Services-only deployment, SP1 above is defined as Windows SharePoint Services SP1 while December 2008 CU is defined as the December 2008 Windows SharePoint Services CU package.
3. If you have a Microsoft Office SharePoint Server 2007 deployment, SP1 above is defined as both Windows SharePoint Services SP1 and Microsoft Office SharePoint Server 2007 SP1 while December 2008 CU is defined as the December 2008 Windows SharePoint Services CU package and the December 2008 Microsoft Office SharePoint Server 2007 CU package.
4. If you have a Project Server deployment, first pick either A or B, and for SP1 add Project Server SP1 to the slipstream source. For the December 2008 CU you can simply install the Microsoft Office SharePoint Server 2007 CU package (even if Microsoft Office SharePoint Server 2007 is not deployed).
5. If you follow this process with the December 2008 CU and want to use it again for the next cumulative update, you can either
1. Choose to start over the process from scratch.
2. Repeat steps 3-4 and add the next CU to your existing slipstream.

FAQ [Updated on 01/13/09]:

Q1. What about Infrastructure Update? Is it included in December CU?
A: Yes, it is included.

Q2. How do you include language packs?
A: The original Language Packs included wsslpk.msi and wssmui.msi. These are in the specific locale of the language pack itself. We updated both of these at SP1. The WSSMUI package specifically has been updated through hotfixes (including the December Cumulative Update), and is commonly referred to as the "localized patch". As mentioned in the prior post at, the local patches are included in the December CU packages 960010 and 960011. Therefore, applying the December CU to Language Packs is as simple as ensuring the Language Pack is installed, as with the product we also suggest installing the SP1 version of the language pack, and then the latest Cumulative Update such as 960010 or 960011.

Q3. Thanks for nice post. i have a confusion with it. I already installed the Sp1 and infrastructure updates. So still i need to download and extract the sp1. I am using MOSS then you say no need of wss updates, what its mean?
A: For MOSS installation, WSS updates are recommended, but not a requirement.

Q4. If I'm starting with the single download of WSS 3.0 with SP1, do I just do note a and skip step 2?
A: Yes. To start with WSS 3.0 with SP1, you don't need to do step 2 since it is already included in the package.

Q5. Where is wsssetup.dll? I cannnot find it.
A: If you start with MOSS 2007 with SP1, step 4 is not necessary because the file wsssetup.dll is already removed. You won't find it in the directory.

Q6. Thanks for the info - v.useful. Just to be clear though, is the logic below right? "4. If you are not using Windows SharePoint Services only" If that is literally what is meant - perhaps it would be clearer to say "If you are using MOSS...."
A: Yes, if you are using MOSS RTM you should delete this file.

Q7. Do you confirm that you are talking about "svrsetup.dll" instead of "Servicessetup.dll" as mentionned?
A: This is a replacement mistake when do the posting, the correct one is "wsssetup.dll". It is corrected now.

Dan Winter

SharePoint Program Manager

Jie Li

SharePoint Technical Product Manager
referred from