SharePoint server 2013 slipstreamed with SP1 is available via MSDN and VLSC, this supports Windows Server 2012 R2.
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
- 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/
Deep into SharePoint 