Installing SharePoint 2010 and SQL Server 2012 On Windows Server 2012 Release Preview
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
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.
Set-WebConfigurationProperty “
1 Set-WebConfigurationProperty
“/system.applicationHost/applicationPools/applicationPoolDefaults” –Name
managedRuntimeVersion –Value “v2.0” –PSPath IIS:\
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.
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:
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:
C:\Window s\System32\Window
1 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 ' "
The Management Shell will now function as expected.
And yes, the User Profile Synchronization Service still functions as expected!