SharePoint 2013 Public Update March 2013

Today is available a PU – Public Update - (march 2013) for SharePoint 2013.

You need to install it if you plan to update your farm in the future. ;)

Here you are the links to official KB article and the links to direct download.

• KB 2768000 - SharePoint Foundation 2013
• KB 2767999 - SharePoint Server 2013
• KB 2768001 - Project Server 2013

• Download SharePoint Foundation 2013 March 2013 PU
• Download SharePoint Server 2013 March 2013 PU
• Download Project Server 2013 March 2013 PU

Server package (about 1.6GB!!!! in english version) contains Foundation Package.
Project package contains Server Package.

Enjoy!

Create Self Signed Certificate for IIS 6 - SelfSSL.exe

In order to create a Self Signed certificate for a web application running on a IIS 6.0 web server, we can use SELFSSL.exe utility.

This exe can be normally found on this directory:

C:\Program Files\IIS Resources\SelfSSL

Issue this command:

selfssl /S:<site ID of web application> /V:999999

Confirm eventually the replacement of the existing SSL Certificate and you are done.

This was usefull for me because self signed certificate of my "Office Server Web Service" web application of MOSS 2007 was Expired.

The error logged in trace log accessing User Profile page of SharedService Provider was:

Fail to obtain crawl status. System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

The aspx page exception was:

An error has occurred while accessing the SQL Server database or the Office SharePoint Search service.

This is the screenshot.

SharePoint - Upgrade Classic Content DB 2010 to Claims Web Application 2013

Just as reminder for me, when you need to attach a content database that come from a SharePoint 2010 web application with Classic Mode Authentication Schema to a SharePoint 2013 web application that use claims (default) authentication, after the attach (that can be done either with powershell or the oldstyle (ed) stsadm.exe) you need to convert users from classic to claims.

This can be done with this PS command:

Convert-SPWebApplication -Identity  http://webappurl.with.fqdn -To Claims -RetainPermissions -Force

even if the web app is already in claims auth.