Operating system compatibility of SharePoint 2010/2013 has evolved

Mar 11, 2014


Service pack 2 for SharePoint 2010 and Service pack 1 for SharePoint 2013 recently came out.

A support of 2012R2 at last !

Both service packs bring support for Windows Server 2012R2. This is a recurrent problematic for IT services. How to reduce the number of different versions of an operating system in order to make maintenance cheaper and easier?

Warning: “in place” upgrade of operating system for SharePoint 2013 is not supported by Microsoft. You need to reinstall the farm and migrate the content. See section “overview of improvements” in this article https://support.microsoft.com/kb/2817429

I won’t be surprised if it was the same for SharePoint 2010, even if it’s not indicated (see https://support.microsoft.com/kb/2724471/ )

Therefore I decline any responsibility in damages you may cause using following instructions.

Migration of my dev vm’s

However I tried to migrate my development machines to WS2012. Again, if I break those, no big deal. (plus I had some snapshots)

Starting migration from:

  • SP2010: windows server 2008R2

  • SP2013: windows server 2012

I began by installing sp2 on the 2010 machine and sp1 on the 2013 one. Once it was installed, I updated system to 2012R2. I was surprised to see that SharePoint was working pretty well on both machines after the installation. I only had a couple of log entries

Encountered (and solved) problems after migrating

Secure Token Service

On both machines I had this error:

Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/62476613

Exception: System.ServiceModel.ServiceActivationException: The service ‘/SecurityTokenServiceApplication/securitytoken.svc’ cannot be activated due to an exception during compilation. The exception message is: Exception has been thrown by the target of an invocation.. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.ArgumentNullException: Value cannot be null.

Just in case I re-ran the psconfig in order to register again SharePoint services. But it didn’t solve the issue. Solution came from this msdn forum thread, the author indicated that we only need to re-provision services to solve the problem. He also provides us the powershell script to do so.


SharePoint management Shell not working

The second problem I had due to the upgrade is related to powershell 3 which runs on .net 4. (problem I had only on the 2010 machine). Solution is pretty simple, you only have to edit the shortcut to management shell as documented in this article.



Migrating my dev vm’s went well. I’ve done it a week ago and I had no other problem at this time. Bu again these are developments machines, beware on your environments where the consequences could be bigger.

Last edited May 27, 2021 by Vincent Biret