***Updated 7/10/2014 for Windows Server 2012 R2 and SharePoint 2013 SP1


This will be a basic walkthrough on installing SharePoint 2013 SP1.  The TechNet documentation for the process is here:  http://technet.microsoft.com/en-us/library/cc262957.aspx

Windows Server 2012 R2 and SQL 2012 SP1 will be used.  We already have an existing remote SQL 2012 SP1 server we will be using in this scenario for database services.


  • OPSMGR\ShptSetup  (user account that will log in and install or update SharePoint)
  • OPSMGR\ShptSvc      (service account for the farm, database access account)
  • OPSMGR\SharePoint Admins (Group)

Add all the SharePoint accounts to the SharePoint Admins group.  Technically for lowest priv the ShptSvc account does not need to be a SharePoint admin – as setup will grant necessary permissions to the SharePoint servers and Databases, however this is done for simplicity in a lab environment.


Install a new Windows Server 2012 R2 computer.  Join it to a domain.  Add the DOMAIN\SharePoint Admins global group to the Local Administrators group.

Log on to the SharePoint server as DOMAIN\shptsetup

ShptSetup account must have the following rights:   http://technet.microsoft.com/en-us/library/ee662513.aspx

  • local admin on all SharePoint servers
  • SQL Server login on the computer that runs SQL Server.
  • Member of the following SQL Server roles:
    • securityadmin fixed server role
    • dbcreator fixed server role
  • If you run Windows PowerShell cmdlets that affect a database, this account must be a member of the db_owner fixed database role for the database.
  • To make this process simple – if possible, just grant the shptsetup account to have SysAdmin role over the SQL instance for installation.


The prerequisite installer in SharePoint 2013 SP1 is not fully compatible with Server 2012 R2.  Therefore – it will bomb out trying to install the IIS role.  Similar to http://support.microsoft.com/kb/2765260

We will get around this by proactively installing the needed roles and features using powershell.  (open an ELEVATED powershell)

Import-Module ServerManager

Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 -Source %SXSFOLDER%

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 %SXSFOLDER%

%SXSFOLDER% is your location where you have a copy of the SXS folder from the Server 2012 R2 media.  Make sure your elevated Powershell session can reach this location.  I ended up having to use a UNC path as my mapped drive would not work and kept bombing out on finding the source.


Next, run prerequisiteinstaller.exe from the SharePoint 2013 SP1 media:


This will install all the necessary pre-reqs needed for SharePoint 2013 SP1 on a Windows Server 2012 R2 OS:


Once the prereqs are installed, reboot the server.  When you log back in as DOMAIN\shptsetup, the installation of prereqs will complete.  Click Finish.



Next up, run setup.exe from the SharePoint 2013 SP1 media.

Input your product key.

Accept the license agreement

Choose Complete:


Click Install Now.

When complete – we can run the config wizard:




We want to create a new farm:



Provide a SQL server, and a SharePoint farm database access account:


The user account running setup needs access to the SQL server in order to create the SharePoint databases.  The provided SharePoint Farm Account/Database Access account will get the required permissions automatically by setup.

Provide a passphrase:


Specify a port or accept the default:



Complete the wizard:



When complete – you should see:



This will kick off the central administration sire farm configuration wizard.



Answer the questions in the wizard, and create the first site collection.