SharePoint 2010 Service Pack 2 was released this month.
I’ve seen a few posts on blogs, but none so far were complete.
Here’s a list, I gathered this from: http://support.microsoft.com/kb/2687524
Note: This page took forever to load – in fact I almost closed it since it didn’t seem to have any relative information, then data showed up – they must build the page with an AJAX callback – it has quite a lot of detail!
I’ve organized the list below by product configurations so a few items are repeated (ie you’ll see the language packs in both the SP standard and Project server section)
Foundation / Free:
Standard and Higher:
“Other” servers/connectors etc:
Microsoft Search Server 2010 SP2: sserversp2010-kb2687461-fullfile-x64-en-us.exe KB article: 2687461
(Note: Search Server 2010 SP2 was a separate offering by MS to allow search without needing sharepoint – if you are using the search features of SharePoint, you’ll just use either the foundation or server versions of SP2 above)
Much has been written about this, and I’ve seen some conflicting advice. I don’t have a “right answer” here – but I will say it’s a good idea to be prepared:
- Practice on a test environment first.
- take a backup of your IIS directory, especially the web.config files on your web front ends
- Take a backup of your “hive” (c:\program files\common files\microsoft shared\web server extensions\14\*) there may be customization here.
- Take backups of every DB, especially the content DB’s
- Don’t forget about 3rd party DB’s like newsgator, K2, etc.
- If your SharePoint infrastructure is Virtualized, you can get a fool proof backup by doing this:
- Shut down all your VM’s and then take a snapshot in the powered off state.
- Take SQL backups while the VM’s are off.
The above steps might be a bit extreme, and maybe aren’t necessary, but they do give the best option of pain free recovery if you have to roll back. The logic being you can restore it to the exact same state (that of a shutdown system) – Every other backup method involves backing up (and subsequently restoring) a moving target…
This might be a good technique to follow when patching – basically it proposes shutting down the IISAdmin and SPTimerServces, and stopping or pausing the Search Services prior to patching then starting them back up afterwards.