Install SharePoint 2013 on Windows Server 2012 R2

SharePoint server 2013 slipstreamed with SP1 is available via MSDN and VLSC, this supports Windows Server 2012 R2.       

http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx

SharePoint Server 2013 SP 1 is released http://support.microsoft.com/kb/2817429, I havent personally tested this on Server 2012 R2 yet, but based on the KB article it is supported.

SharePoint 2013 is not supported on Windows Server 2012 R2, however according to MS SharePoint 2013 SP1 will be supported…

http://support.microsoft.com/kb/2891274.

However if you are a person who likes to work on bleeding edge and doesn’t want to wait till SP1 is release …then you are at the right place J.

For almost all of my SharePoint Installations (2010 and 2013) be it on a single server or a large farm of many servers, I use autospinstaller, an open source PowerShell script library for scripted SharePoint installs.

http://autospinstaller.codeplex.com/

However autospinstaller failed during the SP2013 prerequisites install on the R2 server with the following errors.

1. Error: Startup task doesn’t exist. This is not a continuation after a restart

2014-02-10 15:58:56 – C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\SharePointServerPreparationToolStartup_0FF1CE14-0000-0000-0000-000000000000.cmd
2014-02-10 15:58:56 – Error: Startup task doesn’t exist. This is not a continuation after a restart.
2014-02-10 15:58:56 – Locating the following command line arguments file:
2014-02-10 15:58:56 – E:\PrerequisiteInstaller.Arguments.txt

2. Error: [In HRESULT format] (-2147024894)

2013-10-02 15:59:02 – Created thread for installer
2013-10-02 15:59:02 – “C:\Windows\system32\ServerManagerCmd.exe” -inputpath “C:\Users\ADMINI~1\AppData\Local\Temp\PreB8C.tmp.XML”
2013-10-02 15:59:02 – Error: Unable to install (2)
2013-10-02 15:59:02 – Error: [In HRESULT format] (-2147024894)
2013-10-02 15:59:02 – Last return code (2)
2013-10-02 15:59:02 – Reading the following DWORD value/name…

Error: The tool was unable to install Application Server Role, Web Server (IIS) Role

SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
2013-10-02 15:59:02 – Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
2013-10-02 15:59:02 – Last return code (2)
2013-10-02 15:59:02 – Options for further diagnostics: 1. Look up the return code value 2. Download the prerequisite manually and verify size downloaded by the prerequisite installer. 3. Install the prerequisite manually from the given location without any command line options.
2013-10-02 15:59:02 – Cannot retry

The SharePoint 2013 prerequisite installer checks the OS version and detects it as unsupported as well as the AppFabric install requires special configurations. Due to these issues I decided to install the prerequisites manually but use autospinstaller for SharePoint install. Below is the order in which I performed the tasks.

Prerequisites Install

  1. Login to your R2 server as Administrator. You can as well perform this step under the Farm Administrator account, which should be also local administrator on the server. Run the PowerShell as administrator and execute the following

a. Import-Module ServerManager

b. Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 -Source E:\Sources\sxs

Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Scripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer -Source E:\Sources\sxs

-Source parameter should point to the windows installation media.

2. Download all the below prerequisites and save it locally.

SQL Server 2008 R2 SP1 Native Client
Microsoft WCF Data Services 5.0
Microsoft Information Protection and Control Client (MSIPC)
Microsoft Sync Framework Runtime v1.0 SP1 (x64)
Windows Identity Extensions

Windows Identity Foundation (KB974405) – This may fail and not required, as WIF is turned on as part of step 1. Make sure it’s turned on as a Windows feature. (Added for completeness of prerequisites)
Windows Server AppFabric
CU 1 for AppFabric 1.1 (KB2671763)

3. Install all the above prerequisites directly from the prerequisites folder in the sequence ordered above, EXCEPT the last two (AppFabric and CU 1 for AppFabric).

4. AppFabric requires special configuration and installing it in a usual way is not enough for SP 2013 and Win Srv 2012 R2. Run the following command

WindowsServerAppFabricSetup_x64.exe /i CacheClient,CachingService,CacheAdmin /gac

5. Install AppFabric1.1-RTM-KB2671763-x64-EN2013-with-sp1.aspx

U

6. Restart your server

 SharePoint 2013 Install

In order to make use of all the benefits of a scripted install, I still wanted to use autspinstaller but didn’t want the prerequisites install on it to run. Therefore I modified the autospinstaller script to bypass prerequisite install. Below is the change I did to the script AutoSPInstallerMain.ps1.

Navigate to the function, “Function Run-Install” and comment the below so that prerequisites install is bypassed.

#InstallPrerequisites $xmlinput

Save the file and run the autospinstaller in a standard way, please note that you need to configure autospinstallerinput.xml file in a standard way. Refer http://autospinstaller.codeplex.com/

Advertisements

4 comments on “Install SharePoint 2013 on Windows Server 2012 R2

  1. Bradley says:

    What can be done to run the script on a stand alone server with no Domain user account?

  2. Dave says:

    Wish I would have found your post a week ago when I was trying this. I eventually discovered the same thing – the reason the prerequisite installer doesn’t work is the deprecated command “servermanagercmd.exe”. It would have been a lot simpler if they had not removed the command from server 2012. Unfortunately the SharePoint 2013 Prerequisite installer is still expecting it to be there!
    Thanks for your post

  3. Grzesiek says:

    Great article, helped me a lot, thanks.

  4. Boyd says:

    Ugh, I am getting this error “Error: The tool was unable to install Application Server Role, Web Server (IIS) Role” in the logs. Using Windows Server 2012 r2. So looks like I will be following the intense list outlined on this blog tomorrow. Thanks for putting this list together; it is appreciated.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s