SharePoint 2013 Service Pack 1 Pulled

Update

The KB article for SP1 (KB2817429) has been updated with the following:

We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.

SharePoint Server 2013 Service Pack 1 appears to have been pulled from the Microsoft Download Center.

The timing is slightly off, as clients have been requesting this patch lately as its been available for a bit now. I’ve had a few quibbles with Service Pack 1, particularly the poor implementation of registry permissions and general provisioning problems with Service Applications. Its nothing that can’t be overcome, but hopefully the Product Group can clean it up when the patch reappears.

Thanks to Anders Rask for pointing it out and tweeting it up.

User groups, kangaroos, and SharePoint Migrations

I had the pleasure of presenting at not one, but two (!!) user groups in Australia this past week to discuss the pitfalls of migrating to SharePoint 2013 and all the things that go wrong along the way.

First up, the Sydney SharePoint User Group located in the heart of the CBD. Sydney is my home away from home for the next few years, and I’m very grateful to the organisers for giving me the opportunity to come out.

The following day, after a quick train ride and some kangaroo sightings, it was off to Canberra for the Canberra SharePoint User Group. There were some projector issues, but I do hope that everyone that attended got something out of the session.

Ignite SharePoint 2013 Search Session

I particularly like Slide 22 (Search Scale Out and Optimization) aka The Cheat Sheet.

Inconvenient Settings Loss With Dismount-SPContentDatabase

Are you someone that likes to go through your web applications and dismount your databases prior to patching? Or maybe you’re just moving a content database from one web application to another. Or maybe, just maybe, you want to dismount a content database for the fun of it!

Well, if that’s you, you might have noticed (or maybe not), that when the content database is remounted, a few properties get reset to their default values such as MaximumSiteCount and WarningSiteCount (2,000 and 5,000 respectively). This can be pretty inconvenient (to say the least!) if you’ve modified these settings in any way and even more inconvenient if you didn’t document them before running Dismount-SPContentDatabase.

Once again, it’s our friend PowerShell to the rescue. The following functions allow you to dismount all of the content databases in a given web application (Dismount-SPContentDatabases) while retaining the pertinent settings in CSV file. The function helpfully titled Mount-SPContentDatabases will remount the content databases (using Mount-SPContentDatabase) to the supplied web application using the previous settings (including the original DatabaseServer), thus saving you at least 5 minutes to enjoy an additional cup of coffee.

Example Use

Imagine you have a web application with the name ContosoIntranet.

SharePoint 2013 Additional Prerequisites Unavailable for Download

As you’re all aware, SharePoint 2013 has some additional prerequisites that are required for a proper installation that aren’t included in the Prerequisite Installer. Todd Klindt just had a great post on this (so go there for the extra details), but he forgot to mention that 2 of the required hotfixes don’t currently have publicly available request forms. Todd was also nice enough to include some download links, so I’m posting them here as well for posterity.

  • KB 2759112 - A hotfix is available for the .NET Framework 4.5 that resolves an ASP.NET race condition issue in Windows Server 2008 R2 – Download
  • KB 2765317 - A hotfix is available for the .NET Framework 4.5 that resolves an ASP.NET race condition issue in Windows Server 2012 – Download

Shredded Bits. It’s What’s For Breakfast

Dan Usher (@usher) and I were given the opportunity to head down and present at the Richmond SharePoint User Group (@RichmondSUG). It was a great crowd and we had a great time. Now, for your viewing pleasure…

The Slides