Install Sharepoint 2013 On Windows Server 2016

4 views

Skip to first unread message

Danny Hosford

unread,

Aug 3, 2024, 11:35:55 AM8/3/24

to stananrystha

You can install and configure SharePoint Servers 2016 or 2019 on a single server if you're hosting only a few sites for a limited number of users or if you want to create a trial or development environment. This configuration is also useful if you want to configure a farm to meet your needs first, and then add servers to the farm at a later stage.

In previous versions of SharePoint, a single server installation automatically installed SQL Server Express. In SharePoint Servers 2016 and 2019, a single server installation contains only SharePoint. SQL Server can be installed on the same server or on a separate server; both scenarios are supported. For better performance we recommend installing SQL Server on a separate server.

After you have completed setup and the SharePoint Products Configuration Wizard, you will have installed binaries, configured security permissions, configured registry settings, configured the configuration database, configured the content database, and installed the SharePoint Central Administration web site. Next, you can choose to run the Farm Configuration Wizard to configure the farm, select the services that you want to use in the farm, and create the first site collection, or you can manually perform the farm configuration at your own pace.

For SharePoint Server 2019, ensure that you've met all hardware and software requirements. You must have a 64-bit version of Windows Server 2016, Windows Server 2019, or Windows Server 2022. To host SharePoint databases, you must also have a 64-bit version of SQL Server 2016, SQL Server 2017, SQL Server 2019, or SQL Server 2022. For more information about these requirements, such as specific updates that you must install, see Hardware and software requirements for SharePoint Server 2019.

Ensure that you're prepared to set up the required accounts by using appropriate permissions. For detailed information, see Initial deployment administrative and service accounts in SharePoint Server.

To complete the following procedures, the account that you use must be a member of the Administrators group on the computer on which you are installing SharePoint Server. For information about user accounts, see Initial deployment administrative and service accounts in SharePoint Server.

Because the prerequisite installer downloads components from the Microsoft Download Center, it's highly recommended that you have Internet access on the computer on which you're running the installer. Use the following procedure to install software prerequisites for SharePoint Servers 2016 or 2019.

The following procedure installs binaries, configures security permissions, and edits registry settings for SharePoint Server. At the end of Setup, you can choose to start the SharePoint Products Configuration Wizard, which is described later in this section.

If you intend to use this computer as a search server, we recommend that you store the search index files on a separate storage volume or partition. Any other search data that needs to be stored is stored in the same location as the search index files. You can only set this location at installation time.

If Setup fails, check log files in the Temp folder of the user account you used to run Setup. Ensure that you are logged in using the same user account and then type %temp% in the location bar in Windows Explorer. If the path in Windows Explorer resolves to a location that ends in a "1" or "2", you have to navigate up one level to view the log files. The log file name is SharePoint Server Setup ().

Verify that the user account that is performing this procedure is the farm administrator user account. For information about the farm administrator user account, see Initial deployment administrative and service accounts in SharePoint Server.

The farm service account is used to access your configuration database. It also acts as the application pool identity account for the SharePoint Central Administration application pool, and it is the account under which the Microsoft SharePoint Foundation Timer service runs. The SharePoint Products Configuration Wizard adds this account to the SQL Server Login accounts, the SQL Server dbcreator server role, and the SQL Server securityadmin server role. The user account that you specify as the farm service account has to be a domain user account. However, it does not have to be a member of any specific security group on your SharePoint servers or your database servers. We recommend that you follow the principle of least-privilege and specify a user account that is not a member of the Administrators group on your SharePoint servers or your database servers.

Although a passphrase resembles a password, it is longer to improve security. It's used to encrypt credentials of accounts that are registered in SharePoint Server. For example, the SharePoint Server server farm service account that you provide when you run the SharePoint Products Configuration Wizard. Ensure that you remember the passphrase, because you must use it every time that you add a server to the farm. Ensure that the passphrase meets the following criteria:

For a single server farm, we recommend choosing the Single Server Farm role, although you can select a Custom role if you want to individually manage the services instances that run on the server. You can change the role of a server later if you change your mind or want to expand your farm by adding additional servers.

If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint Servers 2016 and 2019 are installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS folder.

If you're prompted for your user name and password, you might have to add the SharePoint Central Administration web site to the list of trusted sites and configure user authentication settings in Internet Explorer. You might also want to disable the Internet Explorer Enhanced Security settings. If you see a proxy server error message, you might have to configure proxy server settings so that local addresses bypass the proxy server. Instructions for configuring proxy server settings are provided in the following section. For more information about how to configure browser and proxy settings, see Configure browser settings.

To confirm that you have configured browser settings correctly, log on to the server by using an account that has local administrative credentials. Next, connect to the SharePoint Central Administration web site. If you're prompted for your user name and password when you connect, perform the following procedures:

You have now completed setup and the initial configuration of SharePoint Server and have created the SharePoint Central Administration web site. You can now configure your farm and sites, and you can select services by using the Farm Configuration Wizard.

For security reasons, we recommend that you use a different account from the farm administrator account to configure services in the farm.If you decide to use an existing managed account, that is, an account of which SharePoint Server is aware, then ensure you click that option before you continue.

After you install and configure SharePoint Server, your browser window opens to the Central Administration web site of your new SharePoint site. Although you can start adding content to the site or customizing the site, we recommend that you first perform the following administrative tasks.

Don't try to mess with hardware and software requirements and don't try to run a SharePoint server at the most minimal requirements. Of course it costs money and it doesn't matter if it's their hardware or your time: It has to be paid. But believe me if you need to change things later it takes way more time and resources than you would have invested at the beginning.

Installing SharePoint can't be compared to installing a tool or application. It includes way more effort than a Windows Server or SQL Server since it's based on different types of servers and a working infrastructure. Usually you will get challenges if you put a system on top combining different servers and services.

SharePoint has specific hardware, software, domain and account requirements before you can successfully install it. You need to meet them before you can start your installation to minimize waiting time and mistakes.

Usually I like to know which Windows Server 2016 role services and features are enabled: If you run the SharePoint 2019 prerequisites installer you won't see the exact configuration steps. Anyway it's sufficient for this scenario.

The prerequisites installer also downloads required patches and hotfixes for Windows Server 2016. In case you want to download them manually please read: SharePoint 2019 hardware and software requirements.

I suspect that SP2013 is not officially supported on top of Windows Server 2016, but I'm interested to install it in such scenario for testing purposes. It seems that prerequisites installer fails specifically because Application Server role has been deprecated in Windows Server 2016 (see this question on serverfault.com). Anyone with positive experience of getting SP2013 to work on top of Server 2016? Is it possible at all? NOTE: I'm not asking about official supportability (I guess it is not supported configuration), but about practical feasibility of doing this.

Has anyone been able to install Sharepoint 2016 on a fresh Server 2016? The prerequisiteinstaller fails to do anything. Downloading and Installing all the prerequisites also fails to satisfy the Setup.exe.

I have made multiple attempts to install SharePoint 2016 on a fresh Server 2016. The preprequsite installer fails but I was able to manually install all of the prerequisites using the many helpful resources listing these and their links. I did the registry edits and Powershell system environment modifications for AppFabric and manually configured AppFabric caching coping the settings from an existing SharePoint 2013 on Server 2012 system I have been running. This satisfies the prerequisite installer, but the SharePoint installer won't start. It tells me AppFabric is incorrectly installed and to uninstall it and rerun the prerequisite installer. An endless loop. Verified on two completely fresh server 2016 builds.