Installing SharePoint 2010 and SQL Server 2012 on Windows Server 2012 Release Preview

As an update to my previous blog post, this installation guide will cover installing SharePoint 2010 with Service Pack 1 and SQL Server 2012 on Windows Server 2012 Release Preview.

As with Windows Server 8 Beta, you will need the following in order to install SharePoint:

ServerManagerCmd.exe

Slipstreamed install of SP1 for SharePoint 2010 (http://blogs.msdn.com/b/ronalg/archive/2011/07/11/slipstream-sharepoint-2010-sp1-and-language-packs-w-sp1-into-rtm.aspx and http://toddklindt.com/blog/Lists/Posts/Post.aspx?List=56f96349-3bb6-4087-94f4-7f95ff4ca81f&ID;=295&Web;=48e6fdd1-17db-4543-b2f9-6fc7185484fc)

Microsoft Chart Controls for Microsoft .NET Framework 3.5

Microsoft Filter Pack 2.0 (also available in PrerequisiteInstallerFilesFilterPack)

Microsoft SQL Server 2008 Native Client

Microsoft SQL Server 2008 R2 ADOMD.NET

Microsoft Sync Framework 1.0

From Server Manager, go to Manage –> Add Roles and Features.

Add the Application Server and Web Server (IIS) roles:

image[53]

Next, add the Windows Identity Foundation 3.5 feature:

image[54]

Install the following Web Server (IIS) role features:

image[55]

image[56]

image[57]

image[58]

Install the following Application Server role features:

image[59]

First, installing SQL 2012:

Fortunately, with SQL 2012, there is nothing more that needs to be done for the SQL Database Engine, Integration Services, and SQL Management Studio.  During installation, it will enable .NET 3.5.1 which is also required for SharePoint 2010.

Next, slipstream SP1 into SharePoint 2010 if you haven’t done so already.  Copy ServerManagerCmd.exe from the above download into C:\Windows\System32.

Proceed with the SharePoint 2010 installation using setup.exe from the extracted SharePoint installation.

Run the following command from an elevated PowerShell command prompt:

When SharePoint creates application pools, they will be set to v2.0 which is currently required for SharePoint 2010.

After the installation is complete, run the SharePoint Configuration Wizard.  If you get the below error, you did not correctly run the above command to set the default Application Pool creation to v2.0.  Instead, you will need to go to IIS and set the SharePoint-related Application Pools from v4.0 to v2.0, then go and run the above PowerShell command, otherwise you’ll continue to face these types of errors.

image[40]

SharePoint 2010 PowerShell Management Shell:

In Windows Server 2012, PowerShell is version 3 by default, using the .NET 4 Framework.  This will not work for the SharePoint .NET assemblies.

In the Start screen, right click the SharePoint 2010 Management Shell link, then click Open File Location at the bottom of the screen:

image[51]

Go to Properties on the Management Shell and on the Shortcut tab add “-version 2.0” after PowerShell.exe, for example, the Target should look like:

The Management Shell will now function as expected.

And yes, the User Profile Synchronization Service still functions as expected!

20 Comments

  1. Still stuck on the ServerManagerCmd.exe problem.
    I grabbed the ServerManagerCmd.exe from my 2008 R2 server instead of making my own and stuck it in System32, but it won't work.
    Any idea why?

  2. You'll need to grab the one from the link in order to return exit code 1003. The ServerManagerCmd.exe from previous versions of Windows will not work.

  3. Great walk through. I can't get the filter pack to install. I have server 2012 running on an intel box with a 6core 980x cpu but it looks like maybe the filter pack install is having issues with it. Any ideas?

    Product: Microsoft Filter Pack 2.0 — Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.CRT,version="9.0.30729.4148",type="win32",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b"'. Please refer to Help and Support for more information. HRESULT: 0x80070BC9. assembly interface: IAssemblyCacheItem, function: Commit, component: {3FA0170E-227C-37C7-BAC0-64691A992C81}

  4. Disregard my last message. Just needed a reboot.

    Should we be installing sharepoint using he standalone option or the 'stand alone or farm' option?

  5. For this guide, use the Farm option. I have not tested a Stand alone installation.

  6. Are you using local accounts with the farm option? There are comments out there to use the sharepoint powershell to create the dbs; however that doesn't appear to be compatible with the version of .net runtime

  7. I'm only using domain accounts. You need to change the .NET version that the SharePoint Management Shell runs as; see the above article for now to do that.

  8. "And yes, the User Profile Synchronization Service still functions as expected!"

    Expected…. does that mean it works or it fails?

  9. Great run on my Azure Virtual Machine 2012

  10. For the SharePoint powershell to work you need to add the “-version 2.0″ switch to the SharePoint Powershell shortcut. Therefore the new command should be –C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -version 2.0 -NoExit ” & ‘ C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ‘ “–

  11. Excellent article. Followed to the letter, works perfectly! Thanks Trevor.

  12. thanks man, worked like a charm :-)

  13. Me Greatest Thanks and Respect. Wow! This is coolest thing and it works.

  14. So I’ve followed the instructions above and succesfully installed a Sharepoint 2010 Foundation on a Windows Server 2012. The configuration wizard signaled OK. But when I try to access the Management Studio I get a HTTP 404 error. What is wrong?

  15. Great article, thnx!
    SharePoint works fine on Server 2012 :)

  16. Thank you,

    you did that, what Microsoft can’t or won’t do in more than 2 years… SharePoint 2010 SP2 is out and still no support for Server 2012 – shame.

  17. Pingback: SharePoint 2010 Service Pack 2 – Server 2012 Support | Andrew J Billings

Leave a Reply