Installing SharePoint 2010 Service Pack 2 beta on Windows Server 2012

The SharePoint Server 2010 Service Pack 2 beta has been released on Connect today. With this public beta comes ability to install SharePoint 2010 (including Office Web Apps and Project Server 2010) on Windows Server 2012 (and Windows 8) in a supported manner. Installing SharePoint Server 2010 SP2 (beta) must be done with newly released media as slipstreaming SP2 into a pre-SP2 installation of SharePoint media will not work.

Installation for SharePoint is similar to what every administrator is used to. Run the pre-req installer, which will configure Windows Server roles and features, as well as install any necessary binaries for SharePoint 2010.


Once completed, run setup.exe from the new media per the normal process, and install SharePoint. This server will be installed in Farm Complete mode.


Configuration has not changed, either…


Our farm ends up at version 14.0.7011.1000.

PowerShell is still an issue. The shortcut included with the installation package does not affix “-Version 2.0” to the command line, hence the SharePoint Management Shell shortcut must still be manually edited to support using the Management Shell on Windows Server 2012.


Unlike installing pre-SP2 on Windows Server 2012, however, is that the IIS Application Pools are correctly configured to run under the .NET Framework 2.0.


One new feature that IIS8 brings is SNI (Server Name Indicator) support. With this support, you can leverage multiple SSL certificates against a single IP address. For example, you can have and, using two separate SSL certificates on two separate IIS sites assigned to the same IP address.



This could potentially eliminate the use of Wildcard Certificates in some environments while eliminating multiple IP addresses for a farm in others.

I was unable to install SharePoint + Project Server with Office Web Apps due to an issue with the WAC install indicating that trial bits (which SharePoint and Project Server SP2 Beta are) with licensed editions (which WAC SP2 beta should not be).

As I find more changes, I’ll write them up here, however SP2 is meant as a cumulation of updates and security fixes that are, for the most part, already available via CUs/CODs and security hotfixes.

Trevor Seward is a Microsoft Office Apps and Services MVP who specializes in SharePoint Server administration, hybrid scenarios, and SharePoint Online. He has been working with SharePoint for 16 years from SharePoint 2003 on up, managing environments with terabytes of content for 150,000+ user organizations. Trevor is an author of Deploying SharePoint 2016 and Deploying SharePoint 2019. You can find him on Twitter and in /r/sharepoint.