Home
%3CLINGO-SUB%20id%3D%22lingo-sub-333295%22%20slang%3D%22en-US%22%3ESharePoint%202010%2C%20Service%20Pack%202%20and%20the%20Cumulative%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333295%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Sep%2019%2C%202013%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EEach%20time%20when%20a%20service%20pack%20comes%20out%20for%20SharePoint%2C%20there's%20always%20a%20bit%20of%20confusion%20around%20how%20the%20Service%20Pack%20affects%20cumulative%20updates.%20Let%20me%20explain%20the%20state%20of%20SP2%20with%20the%20June%20and%20August%20CUs.%20Although%20the%20June%20CU%20and%20SP2%20came%20out%20at%20the%20same%20time%2C%20the%20June%20CU%20has%20a%20lower%20build%20number(14.0.7102.5000)%20than%20SP2(14.0.7015.1000).%20In%20order%20to%20build%20SP2%2C%20which%20is%20a%20longer%20process%20than%20building%20a%20CU%2C%20the%20SharePoint%20code%20base%20branches.%20SP2%20and%20the%20June%20CU%20are%20in%20development%20at%20the%20same%20time.%20What%20this%20means%20is%20that%20in%20order%20for%20the%20later%20release(SP2)%20to%20include%20the%20changes%20from%20the%20earlier%20release(June%20CU)%2C%20the%20code%20branches%20must%20be%20merged.%20Unfortunately%20this%20rarely%20happens%20when%20SharePoint%20Service%20Packs%20are%20released%2C%20due%20to%20tight%20deadlines.%20What%20this%20means%20is%20that%20Service%20Pack%202%20does%20not%20include%20the%20changes%20that%20are%20in%20the%20June%20CU.%20If%20you%20install%20the%20June%20CU%20and%20SP2%2C%20you%20will%20get%20none%20of%20the%20changes%20that%20are%20included%20in%20the%20June%20CU.%20Since%20SP2%20has%20a%20higher%20build%20number%2C%20it's%20version%20of%20SharePoint%20files%20overwrite%20the%20June%20CU's%20versions.%20Since%20Cumulative%20Updates%20are%20indeed%20cumulative%2C%20you'll%20need%20to%20install%20the%20August%20CU(14.0.7106.5000)%20to%20get%20the%20chances%20that%20were%20included%20in%20the%20June%20CU.%20I%20hope%20this%20helps%20folks%20understand%20a%20confusion%20situation.%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-333295%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Sep%2019%2C%202013%20Each%20time%20when%20a%20service%20pack%20comes%20out%20for%20SharePoint%2C%20there's%20always%20a%20bit%20of%20confusion%20around%20how%20the%20Service%20Pack%20affects%20cumulative%20updates.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-333295%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Epatching%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eservice%20pack%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharepoint%202010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharepoint%20Server%202010%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on MSDN on Sep 19, 2013

Each time when a service pack comes out for SharePoint, there's always a bit of confusion around how the Service Pack affects cumulative updates. Let me explain the state of SP2 with the June and August CUs. Although the June CU and SP2 came out at the same time, the June CU has a lower build number(14.0.7102.5000) than SP2(14.0.7015.1000). In order to build SP2, which is a longer process than building a CU, the SharePoint code base branches. SP2 and the June CU are in development at the same time. What this means is that in order for the later release(SP2) to include the changes from the earlier release(June CU), the code branches must be merged. Unfortunately this rarely happens when SharePoint Service Packs are released, due to tight deadlines. What this means is that Service Pack 2 does not include the changes that are in the June CU. If you install the June CU and SP2, you will get none of the changes that are included in the June CU. Since SP2 has a higher build number, it's version of SharePoint files overwrite the June CU's versions. Since Cumulative Updates are indeed cumulative, you'll need to install the August CU(14.0.7106.5000) to get the chances that were included in the June CU. I hope this helps folks understand a confusion situation.