Docs update tracker

Updates from: 09/02/2023 03:10:05

Service	Microsoft Docs article	Related commit history on GitHub	Change details
SharePoint	Export A Site List Or Document Library	https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/export-a-site-list-or-document-library.md	Previously updated : 03/13/2018 Last updated : 08/31/2023 Title: "Export sites, lists, or document libraries in SharePoint Server"-+ description: "Learn how to export a site, list, or document library in SharePoin [!INCLUDE[appliesto-2013-2016-2019-SUB-xxx-md](../includes/appliesto-2013-2016-2019-SUB-xxx-md.md)] You can export a site, list, or document library in SharePoint Server by using the SharePoint Central Administration website or Microsoft PowerShell. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have made with your organization. - - + ## Before you begin -<a name="begin"> </a> -We recommend that you regularly back up the complete farm. However, business or IT requirements might require you to export a site, list, or document library. Regularly exporting sites, lists, and document libraries reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps make sure that data is available for recovery, if that is required. You can only export one site, list, or document library at a time. +We recommend that you regularly back up the complete farm. However, business or IT requirements might require you to export a site, list, or document library. Regularly exporting sites, lists, and document libraries reduces data losses that might occur from hardware failures, power outages, or other problems. It's a simple process and helps ensure that the data is available for recovery when required. You can only export one site, list, or document library at a time. For information about what to back up and which tools to use, see [Plan for backup and recovery in SharePoint Server](backup-and-recovery-planning.md). -Before you begin this operation, review the following information about prerequisites: +Before you begin this operation, review the following information: -- Before you begin, you must create a folder on the local computer or the network in which to store the export file. For better performance, we recommend that you export to the local computer and then move the export file to a network folder. - -- You cannot use SQL Server tools or Data Protection Manager to export a site, list or document library. - +- Create a folder on the local computer or the network to store the export file. For better performance, we recommend that you export to the local computer and then move the export file to a network folder. +- You can't use SQL Server tools or Data Protection Manager to export a site, list or document library. + ## Use PowerShell to export a site, list, or document library in SharePoint Server -<a name="proc1"> </a> You can use PowerShell to export a site, list, or document library manually or as part of a script that can be run at scheduled intervals. - To export a site, list or document library by using PowerShell +To export a site, list or document library by using PowerShell: 1. Verify that you have the following memberships: - - - securityadmin fixed server role on the SQL Server instance. - - - db_owner fixed database role on all databases that are to be updated. - - - Administrators group on the server on which you are running the PowerShell cmdlets. - - An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint Server cmdlets. - + + - securityadmin fixed server role on the SQL Server instance + - db_owner fixed database role on all databases that are to be updated + - Administrators group on the server on which you're running the PowerShell cmdlets + + An administrator can use the `Add-SPShellAdmin` cmdlet to grant permissions to use SharePoint Server cmdlets. + > [!NOTE] - > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true). + > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true). 2. Start the SharePoint Management Shell. - 3. At the PowerShell command prompt, type the following command: - - ```powershell - Export-SPWeb -Identity <SiteURL> -Path <Path and File Name> [-ItemUrl <URL of Site, List, or Library>] [-IncludeUserSecurity] [-IncludeVersions] [-NoFileCompression] [-GradualDelete] [-Verbose] - ``` + + ```powershell + Export-SPWeb -Identity <SiteURL> -Path <Path and File Name> [-ItemUrl <URL of Site, List, or Library>] [-IncludeUserSecurity] [-IncludeVersions] [-NoFileCompression] [-UseSqlSnapshot] [-Verbose] + ``` Where: - - - _\<SiteURL\>_ is URL for the site, list, or library that you are exporting. - - - _\<Path and FileName\>_ is path and name for the site, list, or library that you are exporting. - - - _\<URL of Site, List, or Library\>_ is the URL for the site, list, or library where you are exporting. - - If you are exporting a large site, list, or document library, you can use the `GradualDelete` parameter. When this parameter is used, the site collection is marked as deleted, which immediately prevents any further access to its content. The data in the deleted site collection is then deleted gradually over time by a timer job instead of at one time, which reduces its effect on the performance of farm servers and SQL Server. - - To specify which version of the site, list, or document library to include, use the `IncludeVersions` parameter and specify "LastMajor" (default), "CurrentVersion", "LastMajorandMinor", or "All". To include the user security settings with the list or document library, use the `IncludeUserSecurity` parameter. If you want to overwrite the file that you specified, use the `Force` parameter. To view the progress of the backup operation, use the `Verbose` parameter. - - The `NoFileCompression` parameter lets you specify that no file compression is performed during the export process. Using this parameter can lower resource usage up to 30% during the export process. Using this parameter will result in a backup folder being created instead of a compressed file. If you use the `NoFileCompression` parameter in the `Export-SPWeb` command, you must also use it when you import the content by using the `Import-SPWeb` command. - + - _\<SiteURL\>_ is the URL of the site you're exporting. + - _\<Path and FileName\>_ is the path and name of the file that will contain the exported data. + - _\<URL of Site, List, or Library\>_ is the relative URL of the list or library you're exporting and should start with a forward slash (/). You should only specify this parameter if you want to export an individual list or library instead of the entire site. + + The `UseSqlSnapshot` parameter lets SharePoint create a snapshot of the content database before starting the export, then export the siteΓÇÖs content from that snapshot instead of the live database. This allows users to continue to interact with the site without impacting the data integrity of the export. Once the export is finished, it will automatically remove the snapshot. Database snapshots require the Enterprise Edition of SQL Server. + + To specify which version of the site, list, or document library to include, use the `IncludeVersions` parameter and specify "LastMajor" (default), "CurrentVersion", "LastMajorandMinor", or "All". To include the user security settings with the list or document library, use the `IncludeUserSecurity` parameter. If you want to overwrite the file that you specified, use the `Force` parameter. To view the progress of the backup operation, use the `Verbose` parameter. + + The `NoFileCompression` parameter lets you specify that no file compression is performed during the export process. Using this parameter can lower resource usage up to 30% during the export process. Using this parameter results in a backup folder being created instead of a compressed file. If you use the `NoFileCompression` parameter in the `Export-SPWeb` command, you must also use it when you import the content by using the `Import-SPWeb` command. + For more information, see [Export-SPWeb](/powershell/module/sharepoint-server/Export-SPWeb?view=sharepoint-ps&preserve-view=true). > [!NOTE] -> We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. +> We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. ## Use Central Administration to export a site, list, or document library in SharePoint Server -<a name="proc2"> </a> You can use Central Administration to export a site, list, or document library. You can only export one site, list, or document library at a time. - To export a site, list, or document library by using Central Administration +To export a site, list, or document library by using Central Administration: 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. - 2. Start Central Administration. - 3. In Central Administration, on the home page, click Backup and Restore. - 4. On the Backup and Restore page, in the Granular Backup section, click Export a site or list. - 5. On the Site or List Export page, in the Site Collection section, select the site collection from the Site Collection list, and then select the site from the Site list. - -6. If you are exporting a site, skip this step, Select the list or document library from the List list. - +6. If you're exporting a site, skip this step, Select the list or document library from the List list. 7. In the File Location section, in the Filename box, type the UNC path of the shared folder and the file to which you want to export the list or document library. The file name must use the .cmp extension. - 8. If the file already exists and you want to use this file, select the Overwrite existing files check box. Otherwise, specify a different file name. - 9. If you want to export all the security and permissions settings with the list or library, in the Export Full Security section, select the Export full security check box. - 10. If you want to specify which version of the list or library to export, select one of the following versions from the Export versions list: - - - All Versions - - - Last Major - - - Current Version - - - Last Major and Last Minor - + + - All Versions + - Last Major + - Current Version + - Last Major and Last Minor + 11. When you have specified the settings that you want, click Start Export. - + 12. You can view the status of all backup jobs at the top of the Granular Backup Job Status page. You can view the status of the current backup job in the Content Export section of the page. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. - + If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the \<file name>\.export.log file at the UNC path that you specified in step 6. - + ## See also -<a name="proc2"> </a> -#### Concepts +### Concepts [Plan for backup and recovery in SharePoint Server](backup-and-recovery-planning.md) -#### Other Resources - -[Use Windows PowerShell to administer SharePoint Server](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true) +### Other Resources +[Use Windows PowerShell to administer SharePoint Server](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true)
SharePoint	Add A Server To A Sharepoint Server 2016 Farm	https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/add-a-server-to-a-sharepoint-server-2016-farm.md	Before you can install SharePoint Server and add a server to the farm, you must For download locations, see [Links to applicable software](hardware-and-software-requirements.md#section5) in "Hardware and software requirements (SharePoint Server 2016)." -For download locations, see [Links to applicable software](hardware-and-software-requirements-2019.md#section5) in "Hardware and software requirements (SharePoint Server 2019)." +For download locations, see [Links to applicable software](hardware-and-software-requirements-2019.md#links-to-applicable-software) in "Hardware and software requirements (SharePoint Server 2019)." > [!TIP] > After you obtain a copy of the required software, we recommend that you create an installation point that you can use to store the images. You can use this installation point to install future software updates.
SharePoint	Hardware And Software Requirements 2019	https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/hardware-and-software-requirements-2019.md	Title: Hardware and software requirements for SharePoint Server 2019-+ Previously updated : 7/24/2018 Last updated : 08/31/2023 audience: ITPro f1.keywords: - NOCSH description: Find out the minimum hardware and software requirements you need to [!INCLUDE[appliesto-xxx-xxx-2019-xxx-xxx-md](../includes/appliesto-xxx-xxx-2019-xxx-xxx-md.md)] > [!IMPORTANT] -> If you contact Microsoft Customer Support Services about a production system that does not meet the minimum hardware specifications described in this article, support will be limited until the system is upgraded to the minimum requirements. - - -## Hardware requirements: Location of physical servers -<a name="hwLocServers"> </a> +> If you contact Microsoft Customer Support Services about a production system that does not meet the minimum hardware specifications described in this article, support will be limited until the system is upgraded to the minimum requirements. + +## Hardware requirements + +### Location of physical servers Some enterprises have datacenters that are in close proximity to one another and connected by high-bandwidth fiber optic links. In this environment, you can configure the two datacenters as a single farm. This distributed farm topology is called a stretched farm. Stretched farms are supported for SharePoint Server 2019. For a stretched farm architecture to work as a supported high-availability solution, the following prerequisites must be met: -- There is a highly consistent intra-farm latency of \<1 ms one way, 99.9% of the time over a period of ten minutes. (Intra-farm latency is commonly defined as the latency between the front-end web servers and the database servers.) - +- A highly consistent intra-farm latency of \<1 ms one way and 99.9% of the time over a period of ten minutes. (Intra-farm latency is commonly defined as the latency between the front-end web servers and the database servers.) - The bandwidth speed must be at least 1 gigabit per second. - + To provide fault tolerance in a stretched farm, use the standard best practice guidance to configure redundant service applications and databases. > [!NOTE] > The intra-farm latency of \<1 ms one way, 99.9% of the time over a period of ten minutes is also required for SharePoint environments with servers that are located in the same datacenter. The bandwidth speed should also be in this case at least 1 gigabit per second. -## Hardware requirements: SharePoint Servers and MinRole installations -<a name="hwforwebserver"> </a> +### SharePoint Servers and MinRole installations The values in the following table are minimum values for installations on servers that are running SharePoint Server 2019 in a multiple server farm installation. For information about hardware and software requirements for Microsoft SQL Serve \|Installation scenario\|Deployment type and scale\|RAM\|Processor\|Hard disk space\| \|:--\|:--\|:--\|:--\|:--\| -\|Single server role that uses SQL Server <br/> \|Development or evaluation installation of SharePoint Server 2019 with the minimum recommended services for development environments. Use the Single-Server farm role that will let you choose which service applications to provision. For additional information on Single-Server farm role, see [Overview of MinRole Server Roles in SharePoint Server](overview-of-minrole-server-roles-in-sharepoint-server.md) <br/> \|16 GB <br/> \|64-bit, 4 cores <br/> \|80 GB for system drive <br/> 100 GB for second drive <br/> \| +\|Single server role that uses SQL Server <br/> \|Development or evaluation installation of SharePoint Server 2019 with the minimum recommended services for development environments. Use the Single-Server Farm role and choose which service applications to provision. For more information on the Single-Server Farm role, see [Overview of MinRole Server Roles in SharePoint Server](overview-of-minrole-server-roles-in-sharepoint-server.md). <br/> \|16 GB <br/> \|64-bit, 4 cores <br/> \|80 GB for system drive <br/> 100 GB for second drive <br/> \| \|Single server role that uses SQL Server <br/> \|Pilot or user acceptance test installation of SharePoint Server 2019 running all available services for development environments. <br/> \|24 GB <br/> \|64-bit, 4 cores <br/> \|80 GB for system drive <br/> 100 GB for second drive and additional drives <br/> \| \|Web server or application server in a three-tier farm <br/> \|Development or evaluation installation of SharePoint Server 2019 with a minimum number of services. <br/> \|12 GB <br/> \|64-bit, 4 cores <br/> \|80 GB for system drive <br/> 80 GB for second drive <br/> \| \|Web server or application server in a three-tier farm <br/> \|Pilot, user acceptance test, or production deployment of SharePoint Server 2019 running all available services. <br/> \|16 GB <br/> \|64-bit, 4 cores <br/> \|80 GB for system drive <br/> 80 GB for second drive and additional drives <br/> \| - + ## Deployment requirements: Farm Topology -<a name="hwforwebserver"> </a> For information about how to plan for a server deployment, see [Planning for a MinRole server deployment in SharePoint Server 2019](planning-for-a-minrole-server-deployment-in-sharepoint-server.md). ## Software requirements for SharePoint Server 2019 -<a name="section4"> </a> The requirements in the following section apply to the following installations: - Server farm with a single server in the farm - - Server farm with multiple servers in the farm - - + > [!NOTE] -> SharePoint Server 2019 supports drives that are formatted with the Resilient File System (ReFS). For additional information about ReFs, see [Resilient File System Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831724(v=ws.11)) and [Resilient File System](/windows/win32/w8cookbook/resilient-file-system--refs-) +> SharePoint Server 2019 supports drives that are formatted with the Resilient File System (ReFS). For more information about ReFs, see [Resilient File System Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831724(v=ws.11)) and [Resilient File System](/windows/win32/w8cookbook/resilient-file-system--refs-) > [!IMPORTANT] > SharePoint Server 2019 requires a minimum Active Directory domain and forest functional level of Windows Server 2003 (native). For more information about Active Directory functional levels, see [Forest and Domain Functional Levels](/windows-server/identity/ad-ds/active-directory-functional-levels). This section provides minimum software requirements for each server in the farm. #### Minimum requirements for a database server in a farm -One of the following: +Ensure at least one of the following requirements is met: - A Standard or Enterprise Edition of SQL Server for Windows that supports database compatibility level 130. This includes SQL Server 2016, SQL Server 2017, SQL Server 2019, SQL Server 2022, and any future version of SQL Server for Windows that supports database compatibility level 130. For more information about database compatibility levels, see [Compatibility Certification](/sql/database-engine/install-windows/compatibility-certification) and [ALTER DATABASE (Transact-SQL) Compatibility Level](/sql/t-sql/statements/alter-database-transact-sql-compatibility-level). - Microsoft Azure SQL Managed Instance (MI). This is only supported if your SharePoint Server farm is hosted in Microsoft Azure. For more information, see [Deploy Azure SQL Managed Instance with SharePoint Servers 2016 and 2019](../administration/deploy-azure-sql-managed-instance-with-sharepoint-servers-2016-2019.md). - -> [!NOTE] -> SQL Server products and all future public updates are supported through the SQL Server product lifecycle. - -> [!NOTE] -> SQL Server Express is not supported. Azure SQL Database (the non-Managed Instance DBaaS service) is also not supported for any SharePoint databases. - -One of the following server operating systems: - -- Windows Server 2016 Standard or Datacenter - -- Windows Server 2019 Standard or Datacenter + > [!NOTE] + > SQL Server products and all future public updates are supported through the SQL Server product lifecycle. -- Windows Server 2022 Standard or Datacenter - -#### Minimum requirements for SharePoint servers in a farm + > [!NOTE] + > SQL Server Express is not supported. Azure SQL Database (the non-Managed Instance DBaaS service) is also not supported for any SharePoint databases. -One of the following server operating systems: - -- Windows Server 2016 Standard or Datacenter (Desktop Experience) - -- Windows Server 2019 Standard or Datacenter (Desktop Experience) +- One of the following server operating systems: + - Windows Server 2016 Standard or Datacenter (Desktop Experience) + - Windows Server 2019 Standard or Datacenter (Desktop Experience) + - Windows Server 2022 Standard or Datacenter (Desktop Experience) -- Windows Server 2022 Standard or Datacenter (Desktop Experience) +#### Minimum requirements for SharePoint servers in a farm > [!NOTE] > We don't support installing or upgrading SharePoint 2019 RTM on a server that previously hosted a prerelease version of SharePoint. A new server build is required to host SharePoint 2019 RTM. One of the following server operating systems: The Microsoft SharePoint Products Preparation Tool installs the following prerequisites on SharePoint servers in a farm: - Web Server (IIS) role- - Windows Process Activation Service feature - - Microsoft .NET Framework version 3.5 - - Microsoft .NET Framework version 4.7.2 - - Microsoft SQL Server 2012 Service Pack 4 Native Client- + >[!NOTE] + > If you have the November 2022 Public Update for SharePoint Server 2019 or a newer Public Update, then you can remove the Microsoft SQL Server 2012 Service Pack 4 Native Client as it is no longer required. For more information, see [Description of the security update for SharePoint Server 2019: November 8, 2022 (KB5002294)](https://support.microsoft.com/kb/5002294). - Microsoft WCF Data Services 5.6 - - Microsoft Identity Extensions - - Microsoft Information Protection and Control Client 2.1 (MSIPC) - - Microsoft Sync Framework Runtime v1.0 SP1 (x64) - - Windows Server AppFabric 1.1 - - Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB 3092423)- - Visual C++ Redistributable Package for Visual Studio 2012 - - Visual C++ Redistributable Package for Visual Studio 2017 - - >[!NOTE] - >The required software above will be supported when used by SharePoint via the SharePoint Product Lifecycle. - + >[!NOTE] + >The required software above will be supported when used by SharePoint via the SharePoint Product Lifecycle. + #### Minimum requirements for client computers -- A supported browser. For more information, see [Plan browser support in SharePoint Server 2019](browser-support-planning-2016-2019.md). +A supported browser is required for client computers. For more information, see [Plan browser support in SharePoint Server 2019](browser-support-planning-2016-2019.md). ## Manually configure Windows Server Roles and Features -To manually configure the required Windows Server Roles and Features, you can use one of two methods: 1. Server Manager 2. Microsoft PowerShell -To configure by using Server Manager, see [Install or Uninstall Roles, Role Services, or Features](/windows-server/administration/server-manager/install-or-uninstall-roles-role-services-or-features) +To manually configure the required Windows Server Roles and Features, you can use one of two methods: + +1. Server Manager +2. Microsoft PowerShell +To configure by using Server Manager, see [Install or Uninstall Roles, Role Services, or Features](/windows-server/administration/server-manager/install-or-uninstall-roles-role-services-or-features) -To configure by using PowerShell: +To configure by using PowerShell: From a PowerShell command prompt window, type: -```Install-WindowsFeature NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-Pipe-Activation45,NET-WCF-HTTP-Activation45,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-Asp-Net45,Web-Net-Ext,Web-Net-Ext45,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-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Windows-Identity-Foundation,Xps-Viewer -IncludeManagementTools -Verbose``` +```powershell +Install-WindowsFeature NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-Pipe-Activation45,NET-WCF-HTTP-Activation45,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-Asp-Net45,Web-Net-Ext,Web-Net-Ext45,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-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Windows-Identity-Foundation,Xps-Viewer -IncludeManagementTools -Verbose +``` > [!NOTE] -> Some Windows features being installed are ΓÇ£Features On Demand (FOD)ΓÇ¥, which are downloaded from Windows Update. If the computer doesnΓÇÖt have access to Windows Update, you can specify local installation files by adding the Source parameter and pointing to the \sources\sxs folder on the Windows Server installation media. +> Some Windows features being installed are "Features On Demand (FOD)", which are downloaded from Windows Update. If the computer doesn't have access to Windows Update, you can specify local installation files by adding the Source parameter and pointing to the `\sources\sxs` folder on the Windows Server installation media. > > For example: -Source D:\sources\sxs - ## Optional software supported in SharePoint Server 2019 -<a name="OptionalSoftware"> </a> -The optional software in this section is supported but is not required to install or use SharePoint Server 2019. This software might be required by capabilities such as business intelligence. +The optional software in this section is supported but isn't required to install or use SharePoint Server 2019. This software might be required by capabilities such as business intelligence. \|Environment\|Optional software\| \|:--\|:--\| \|Single server farm, front-end web servers, and application servers in a farm <br/> \| .NET Framework Data Provider for SQL Server (part of Microsoft .NET Framework) <br/> .NET Framework Data Provider for OLE DB (part of Microsoft .NET Framework) <br/> SharePoint Workflow Manager <br/> You can install SharePoint Workflow Manager on a dedicated computer. <br/> Microsoft SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint Technologies <br/> This add-in is used by Access Services for SharePoint Server 2019. <br/> Microsoft SQL Server 2012 Data-Tier Application (DAC) Framework 64-bit edition <br/> Microsoft SQL Server 2012 Transact-SQL ScriptDom 64-bit edition <br/> Microsoft System CLR Types for Microsoft SQL Server 2012 64-bit edition <br/> Microsoft SQL Server 2012 with SP1 LocalDB 64-bit edition <br/> Microsoft Data Services for the .NET Framework 4 and Silverlight 4 (formerly ADO.NET Data Services) <br/> Exchange Web Services Managed API, version 1.2 <br/> \| - + ## Links to applicable software -<a name="section5"> </a> To install Windows Server 2016 or higher, SQL Server 2016 or higher, or SharePoint Server 2019, you can go to the websites that are listed in this section. You can install most software prerequisites through the SharePoint Server 2019 Start page. The software prerequisites are also available from websites that are listed in this section. You can enable the Web Server (IIS) role in Server Manager. -In scenarios where installing prerequisites directly from the Internet is not possible, you can download the prerequisites and then install them from a network share. For more information, see [Install prerequisites for SharePoint Server from a network share](install-prerequisites-from-network-share.md). +In scenarios where installing prerequisites directly from the Internet isn't possible, you can download the prerequisites and then install them from a network share. For more information, see [Install prerequisites for SharePoint Server from a network share](install-prerequisites-from-network-share.md). - [SharePoint Server 2019](https://go.microsoft.com/fwlink/?LinkId=2006095) - - [Language Packs for SharePoint Server 2019](https://go.microsoft.com/fwlink/?LinkId=2006096) - - [Microsoft .NET Framework version 4.7.2](https://www.microsoft.com/net/download/dotnet-framework-runtime)- - [Microsoft WCF Data Services 5.6](https://go.microsoft.com/fwlink/p/?LinkId=320724)--- [Microsoft Information Protection and Control Client (MSIPC)](https://go.microsoft.com/fwlink/p/?LinkId=544913) - -- [Microsoft SQL Server 2012 SP4 Feature Pack - Native Client \x64\sqlncli.msi](https://www.microsoft.com/download/details.aspx?id=56041) - -- [Microsoft Sync Framework Runtime v1.0 SP1 (x64)](https://go.microsoft.com/fwlink/p/?LinkId=618411) - -- [Windows Server AppFabric 1.1](https://go.microsoft.com/fwlink/p/?LinkId=618412) - +- [Microsoft Information Protection and Control Client (MSIPC)](https://go.microsoft.com/fwlink/p/?LinkId=544913) +- [Microsoft SQL Server 2012 SP4 Feature Pack - Native Client \x64\sqlncli.msi](https://www.microsoft.com/download/details.aspx?id=56041) +- [Microsoft Sync Framework Runtime v1.0 SP1 (x64)](https://go.microsoft.com/fwlink/p/?LinkId=618411) +- [Windows Server AppFabric 1.1](https://go.microsoft.com/fwlink/p/?LinkId=618412) - [Cumulative Update Package 7 for AppFabric 1.1 for Windows Server](https://support.microsoft.com/kb/3092423)--- [Visual C++ Redistributable Package for Visual Studio 2012](https://go.microsoft.com/fwlink/?LinkId=627156) - -- [Visual C++ Redistributable Package for Visual Studio 2017](https://go.microsoft.com/fwlink/?LinkId=848299) - -- [Exchange Web Services Managed API, version 1.2](https://www.nuget.org/packages/Microsoft.Exchange.WebServices/1.2.0) - +- [Visual C++ Redistributable Package for Visual Studio 2012](https://go.microsoft.com/fwlink/?LinkId=627156) +- [Visual C++ Redistributable Package for Visual Studio 2017](https://go.microsoft.com/fwlink/?LinkId=848299) +- [Exchange Web Services Managed API, version 1.2](https://www.nuget.org/packages/Microsoft.Exchange.WebServices/1.2.0) - [Microsoft Identity Extensions](https://go.microsoft.com/fwlink/?LinkId=252368) - + ## Prerequisite installer operations and command-line options -<a name="section7"> </a> -The SharePoint Server 2019 prerequisite installer (prerequisiteinstaller.exe) installs the following software, if it has not already been installed on the target server, in the following order: +The SharePoint Server 2019 prerequisite installer (`prerequisiteinstaller.exe`) installs the following software, if it hasn't already been installed on the target server, in the following order: 1. Web Server (IIS) Role - 2. Microsoft SQL Server 2012 SP4 Native Client - 3. Microsoft Sync Framework Runtime v1.0 SP1 (x64) - 4. Windows Server AppFabric 1.1 - 5. Microsoft Identity Extensions - 6. Microsoft Information Protection and Control Client 2.1\- 7. Microsoft WCF Data Services 5.6 - 8. Microsoft .NET Framework 4.7.2 - 9. Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB 3092423)- 10. Visual C++ Redistributable Package for Visual Studio 2012 - 11. Visual C++ Redistributable Package for Visual Studio 2017 -You can run prerequisiteinstaller.exe at a command prompt with the following options. When you run prerequisiteinstaller.exe at a command prompt, you might be asked to restart the server one or more times during the installation process. After restarting, you should continue the prerequisite installation by running prerequisiteinstaller.exe with the `/continue` option. +You can run `prerequisiteinstaller.exe` at a command prompt with the following options. When you run `prerequisiteinstaller.exe` at a command prompt, you might be asked to restart the server one or more times during the installation process. After restarting, you should continue the prerequisite installation by running `prerequisiteinstaller.exe` with the `/continue` option. - `/?` displays command-line options. - -- `/continue` is used to tell the installer that it is continuing from being restarted. - +- `/continue` is used to tell the installer that it's continuing from being restarted. - `/unattended` indicates no user interaction. - -The installer installs from the file that you specify in the command-line options described in the following list. In this list, < _file_> signifies the file from which you want to install. If you do not specify the < _file_> option, the installer downloads the file from the Internet and installs it. If the option does not apply to the current operating system, it is ignored. + +The installer installs from the file that you specify in the command-line options described in the following list. In this list, <_file_> signifies the file from which you want to install. If you don't specify the <_file_> option, the installer downloads the file from the Internet and installs it. If the option doesn't apply to the current operating system, it's ignored. - /SQLNCli:<_file_> Install Microsoft SQL Server 2012 SP4 Native Client from <_file_>. - - /Sync:<_file_> Install Microsoft Sync Framework Runtime SP1 v1.0 (x64) from <_file_>. - - /AppFabric:<_file_> Install Windows Server AppFabric from <_file_> (AppFabric must be installed with the options /i CacheClient,CachingService,CacheAdmin /gac).- - /IDFX11:<_file_> Install Microsoft Identity Extensions from <_file_>. - - /MSIPCClient:<_file_> Install Microsoft Information Protection and Control Client from <_file_>.- - /KB3092423:<_file_> Install Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB3092423) from <_file_>.- - /WCFDataServices56:<_file_> Install Microsoft WCF Data Services 5.6 from <_file_>. - - /DotNet472:<_file_> Install Microsoft .NET Framework 4.7.2 from <_file_>. - - /MSVCRT11:<_file_> Install Visual C++ Redistributable Package for Visual Studio 2012 from <_file_>.- - /MSVCRT141:<_file_> Install Visual C++ Redistributable Package for Visual Studio 2017 from <_file_>. - - + ### Installation options Certain prerequisites are installed by the prerequisite installer with specific options. Those prerequisites with specific installation options are listed below with the options that are used by the prerequisite installer. -- Windows AppFabric - - /i CacheClient,CachingService,CacheAdmin /gac - -- Microsoft WCF Data Services - - /quiet - -The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller.\<date\>.\<time\>.log. You can check these log files for specific details about all changes the installer makes to the target computer. +- Windows AppFabric: /i CacheClient,CachingService,CacheAdmin /gac + +- Microsoft WCF Data + +The prerequisite installer creates log files at `%TEMP%\prerequisiteinstaller.\<date\>.\<time\>.log`. You can check these log files for specific details about all changes the installer makes to the target computer.
SharePoint	Install Sharepoint Server 2016 On One Server	https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/install-sharepoint-server-2016-on-one-server.md	Title: "Install SharePoint Servers 2016 or 2019 on one server"-+ Previously updated : 07/24/2018 Last updated : 08/31/2023 audience: ITPro f1.keywords: - NOCSH description: "Learn how to install SharePoint Server on a single server." [!INCLUDE[appliesto-xxx-2016-2019-xxx-xxx-md](../includes/appliesto-xxx-2016-2019-xxx-xxx-md.md)] - You can install and configure SharePoint Servers 2016 or 2019 on a single server if you are 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. +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. > [!NOTE] > 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. - ## Overview -<a name="section1"> </a> 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. -## Before you install SharePoint Servers 2016 or 2019 on a single server -<a name="section2"> </a> +## Prerequisites -Before you begin to install and configure SharePoint Servers 2016 or 2019, do the following: +Before you begin to install and configure SharePoint Servers 2016 or 2019 on a single server, do the following: -- For SharePoint Server 2016, ensure that you have met all hardware and software requirements. You must have a 64-bit version of Windows Server 2012 R2. To host SharePoint databases, you must also have a 64-bit version of SQL Server 2014 SP1. For more information about these requirements, such as specific updates that you must install, see [Hardware and software requirements for SharePoint Server 2016](hardware-and-software-requirements.md). +- For SharePoint Server 2016, ensure that you've met all hardware and software requirements. You must have a 64-bit version of Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019. To host SharePoint databases, you must also have a 64-bit version of SQL Server 2014 SP1, 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 2016](hardware-and-software-requirements.md). + +- 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](hardware-and-software-requirements-2019.md). -- For SharePoint Server 2019, ensure that you have met all hardware and software requirements. You must have a 64-bit version of Windows Server 2016. To host SharePoint databases, you must also have a 64-bit version of SQL Server 2016 or 2017. For more information about these requirements, such as specific updates that you must install, see [Hardware and software requirements for SharePoint Server 2019](hardware-and-software-requirements-2019.md). - - Ensure that you perform a clean installation of SharePoint Servers 2016 or 2019. - -- Ensure that you are prepared to set up the required accounts by using appropriate permissions. For detailed information, see [Initial deployment administrative and service accounts in SharePoint Server](initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). - -- Ensure the Max degree of parallelism is set to 1. For additional information about max degree of parallelism see, [Configure the max degree of parallelism Server Configuration Option](/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option). - - Security note: As a security best practice, we recommend that you install SharePoint Servers 2016 or 2019 by using least-privilege administration. + +- 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](initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). + +- Ensure the Max degree of parallelism is set to 1. For more information about max degree of parallelism, see, [Configure the max degree of parallelism Server Configuration Option](/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option). + +> [!NOTE] +> As a security best practice, we recommend that you install SharePoint Servers 2016 or 2019 by using least-privilege administration. > [!TIP] -> If you decide to install prerequisites manually, you can still run the Microsoft SharePoint Products Preparation Tool to verify which prerequisites are required on each server. +> If you decide to install prerequisites manually, you can still run the Microsoft SharePoint Products Preparation Tool to verify which prerequisites are required on each server. ## Install SharePoint Servers 2016 or 2019 on a single server -<a name="section3"> </a> -To install and configure SharePoint Server 2016 or 2019 on a single server, you will follow these steps: +To install and configure SharePoint Server 2016 or 2019 on a single server, follow these steps: -1. Run the Microsoft SharePoint Products and Technologies Preparation Tool, which installs all prerequisites to use SharePoint Server. - -2. Run Setup, which installs binaries, configures security permissions, and edits registry settings for SharePoint Servers 2016 or 2019. - -3. Run SharePoint Products Configuration Wizard, which installs and configures the configuration database, installs and configures the content database, and installs the SharePoint Central Administration web site. - +1. Run the [Microsoft SharePoint Products and Technologies Preparation Tool](#run-the-microsoft-sharepoint-products-preparation-tool), which installs all prerequisites to use SharePoint Server. +2. Run [Setup](#run-setup), which installs binaries, configures security permissions, and edits registry settings for SharePoint Servers 2016 or 2019. +3. Run [SharePoint Products Configuration Wizard](#run-the-sharepoint-products-configuration-wizard), which installs and configures the configuration database, installs and configures the content database, and installs the SharePoint Central Administration web site. 4. Configure browser settings. - -5. Run the Farm Configuration Wizard, which configures the farm, creates the first site collection, and selects the services that you want to use in the farm. - +5. Run the [Farm Configuration Wizard,](#run-the-farm-configuration-wizard) which configures the farm, creates the first site collection, and selects the services that you want to use in the farm. 6. Perform post-installation steps. - + > [!IMPORTANT] > 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](initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). ### Run the Microsoft SharePoint Products Preparation Tool -Because the prerequisite installer downloads components from the Microsoft Download Center, you must have Internet access on the computer on which you are running the installer. Use the following procedure to install software prerequisites for SharePoint Servers 2016 or 2019. +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. - To run the Microsoft SharePoint Products Preparation Tool +To run the Microsoft SharePoint Products Preparation Tool: 1. 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](initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). - 2. In the SharePoint Server installation disc image software, mount the ISO file, and click the splash.hta file. The SharePoint Server splash screen is displayed. - -3. Click Install software prerequisites. - +3. Click Install software prerequisites. 4. On the Welcome to the SharePoint Products Preparation Tool page, click Next. - 5. On the License Terms for software products page, review the terms, select the I accept the terms of the License Agreement(s) check box, and then click Next. - -6. On the Your system needs to restart to continue page, click Finish to restart the computer. - +6. On the Your system needs to restart to continue page, click Finish to restart the computer. 7. Repeat steps 2-4. - 8. On the Installation Complete page, click Finish. - + ### Run Setup 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. - To run Setup +To run Setup: 1. 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](initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). - 2. On the SharePoint Server Start page, click Install SharePoint Server. - 3. On the Enter Your Product Key page, enter your product key, and then click Continue. - 4. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue. - -5. Optional: To install SharePoint Server at a custom location, or to store search index files at a custom location, click the File Location tab, and then either type the custom location or click Browse to find the custom location. - +5. Optional: To install SharePoint Server at a custom location, or to store search index files at a custom location, click the File Location tab, and then either type the custom location or click Browse to find the custom location. > [!NOTE] - > 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 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. 6. Click Install Now. - -7. When Setup finishes, a dialog prompts you to complete the configuration of your server. Ensure that the Run the SharePoint Products Configuration Wizard now check box is selected. - -8. Click Close to start the configuration wizard. - +7. When Setup finishes, a dialog prompts you to complete the configuration of your server. Ensure that the Run the SharePoint Products Configuration Wizard now check box is selected. +8. Click Close to start the configuration wizard. + > [!NOTE] -> 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 (< _time stamp_>). - +> 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 (<time stamp>)`. + ### Run the SharePoint Products Configuration Wizard Use the following procedure to install and configure the configuration database and the content database, and to install the SharePoint Central Administration website. - To run the SharePoint Products Configuration Wizard +To run the SharePoint Products Configuration Wizard: 1. 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](initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). - 2. If you have closed the SharePoint Products Configuration Wizard, you can access it by clicking Start, point to All Apps, click Microsoft SharePoint Products, and then click SharePoint Products Configuration Wizard. If the User Account Control dialog appears, click Continue. - 3. On the Welcome to SharePoint Products page, click Next. - 4. In the dialog that notifies you that some services might have to be restarted during configuration, click Yes. - 5. On the Connect to a server farm page, click Create a new server farm, and then click Next. - 6. On the Specify Configuration Database Settings page, do the following: - -1. In the Database server box, type the name of the computer that is running SQL Server. - -2. In the Database name box, type a name for your configuration database or use the default database name. The default name is SharePoint_Config. - -3. In the Username box, type the user name of the farm administrator service account. Ensure that you type the user name in the format DOMAIN\username. - - Security note: The farm administrator 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 administrator 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. - -4. In the Password box, type the user password. - -7. Click Next. - -8. On the Specify Farm Security Settings page, type a passphrase, and then click Next. - - Although a passphrase resembles a password, it is usually longer to improve security. It is used to encrypt credentials of accounts that are registered in SharePoint Server. For example, the SharePoint Server server farm administrator 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: - - - Contains at least eight characters - - - Contains at least three of the following four character groups: - - - English uppercase characters (from A through Z) - - - English lowercase characters (from a through z) - - - Numerals (from 0 through 9) - - - Nonalphabetic characters (such as !, $, #, %) - -9. On the Specify Server Role page, choose the appropriate role, click Next. - + 1. In the Database server box, type the name of the computer that is running SQL Server. + 2. In the Database name box, type a name for your configuration database or use the default database name. The default name is SharePoint_Config. + 3. In the Username box, type the user name of the farm service account. Ensure that you type the user name in the format DOMAIN\username. + > [!NOTE] + > 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. + 4. In the Password box, type the user password. + 5. Click Next. + 6. On the Specify Farm Security Settings page, type a passphrase, and then click Next. + + 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: + - Contains at least eight characters + - Contains at least three of the following four character groups: + - English uppercase characters (from A through Z) + - English lowercase characters (from a through z) + - Numerals (from 0 through 9) + - Nonalphabetic characters (such as, !, $, #, %) +7. On the Specify Server Role page, choose the appropriate role, click Next. > [!NOTE] > 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. - -10. On the Configure SharePoint Central Administration Web Application page, do the following: - - - Either select the Specify port number check box and type the port number that you want the SharePoint Central Administration web application to use, or leave the Specify port number check box cleared if you want to use the default port number. - - - Click either NTLM or Negotiate (Kerberos). - -11. Click Next. - -12. On the Completing the SharePoint Products Configuration Wizard page, review your configuration settings to verify that they are correct, and then click Next. - +8. On the Configure SharePoint Central Administration Web Application page, do the following: + - Either select the Specify port number check box and type the port number that you want the SharePoint Central Administration web application to use, or leave the Specify port number check box cleared if you want to use the default port number. + - Click either NTLM or Negotiate (Kerberos). +9. Click Next. +10. On the Completing the SharePoint Products Configuration Wizard page, review your configuration settings to verify that they're correct, and then click Next. > [!NOTE] > The Advanced Settings option is not available in SharePoint Servers 2016 and 2019. - -13. On the Configuration Successful page, click Finish. When the wizard closes, setup opens the web browser and connects to Central Administration. - - 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 are 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](install-sharepoint-server-2016-on-one-server.md#configurebrowser). - +11. On the Configuration Successful page, click Finish. When the wizard closes, setup opens the web browser and connects to Central Administration. + + 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](#configure-browser-settings). + ### Configure browser settings -<a name="configurebrowser"> </a> -After you run the SharePoint Products Configuration Wizard, you should confirm that SharePoint Server works correctly by configuring additional settings in Internet Explorer. +After you run the SharePoint Products Configuration Wizard, you should confirm that SharePoint Server works correctly by configuring additional settings in your web browser. -If you are not using Internet Explorer, you might have to configure additional settings for your browser. For information about supported browsers, see [Plan browser support in SharePoint Servers 2016 and 2019](browser-support-planning-2016-2019.md). +If you're using Internet Explorer, confirm that you have configured the browser settings correctly by logging on to the server, see [Plan browser support in SharePoint Servers 2016 and 2019](browser-support-planning-2016-2019.md). -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 are prompted for your user name and password when you connect, perform the following procedures: +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: - Add the SharePoint Central Administration website to the list of trusted sites - - Disable Internet Explorer Enhanced Security settings - + If you receive a proxy server error message, perform the following procedure: - Configure proxy server settings to bypass the proxy server for local addresses - - To add the SharePoint Central Administration website to the list of trusted sites + +To add the SharePoint Central Administration website to the list of trusted sites: -1. Verify that the user account that completes this procedure has the following credentials: - - - The user account is a member of the Administrators group on the computer on which you are performing the procedure. - +1. Verify that the user account that completes this procedure is a member of the Administrators group on the computer in which you're performing the procedure. 2. In Internet Explorer, on the Tools menu, click Internet Options. - 3. On the Security tab, in the Select a zone to view or change security settings area, click Trusted Sites, and then click Sites. - 4. Clear the Require server verification (https:) for all sites in this zone check box. - 5. In the Add this web site to the zone box, type the URL to your site, and then click Add. - 6. Click Close to close the Trusted Sites dialog. - 7. Click OK to close the Internet Options dialog. - - To disable Internet Explorer Enhanced Security settings + +To disable Internet Explorer Enhanced Security settings: -1. Verify that the user account that completes this procedure has the following credentials: - - - The user account is a member of the Administrators group on the computer on which you are performing the procedure. - +1. Verify that the user account that completes this procedure is a member of the Administrators group on the computer in which you're performing the procedure. 2. Click Start, point to All Apps, point to Administrative Tools, and then click Server Manager. - 3. In Server Manager, select the root of Server Manager. - -4. In the Security Information section, click Configure IE ESC. - - The Internet Explorer Enhanced Security Configuration dialog appears. - +4. In the Security Information section, click Configure IE ESC. The Internet Explorer Enhanced Security Configuration dialog appears. 5. In the Administrators section, click Off to disable the Internet Explorer Enhanced Security settings, and then click OK. - - To configure proxy server settings to bypass the proxy server for local addresses + +To configure proxy server settings to bypass the proxy server for local addresses: 1. Verify that the user account that completes this procedure has the following credentials: - - - The user account is a member of the Administrators group on the computer on which you are performing the procedure. - + - The user account is a member of the Administrators group on the computer on which you're performing the procedure. 2. In Internet Explorer, on the Tools menu, click Internet Options. - 3. On the Connections tab, in the Local Area Network (LAN) settings area, click LAN Settings. - 4. In the Automatic configuration area, clear the Automatically detect settings check box. - 5. In the Proxy Server area, click the Use a proxy server for your LAN check box. - -6. Type the address of the proxy server in the Address box. - -7. Type the port number of the proxy server in the Port box. - -8. Select the Bypass proxy server for local addresses check box. - -9. Click OK to close the Local Area Network (LAN) Settings dialog. - +6. Type the address of the proxy server in the Address box. +7. Type the port number of the proxy server in the Port box. +8. Select the Bypass proxy server for local addresses check box. +9. Click OK to close the Local Area Network (LAN) Settings dialog. 10. Click OK to close the Internet Options dialog. - + ### Run the Farm Configuration Wizard -<a name="configurebrowser"> </a> -You have now completed setup and the initial configuration of SharePoint Server. You 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. +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. - To run the Farm Configuration Wizard +To run the Farm Configuration Wizard: 1. 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](initial-deployment-administrative-and-service-accounts-in-sharepoint-server.md). - 2. On the SharePoint Central Administration home page, on the Quick Launch, click Configuration Wizards, and then click Launch the Farm Configuration Wizard. - 3. On the Help Make SharePoint Better page, click one of the following options, and then click OK: - - - Yes, I am willing to participate (Recommended.) - - - No, I don't want to participate. - + - Yes, I am willing to participate (Recommended.) + - No, I don't want to participate. 4. On the Configure your SharePoint farm page, next to Yes, walk me through the configuration of my farm using this wizard, click Start the Wizard. - 5. On the Service Applications and Services page, in the Service Account section, click the service account option that you want to use to configure your services. - - Security note: 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 2016 is aware ΓÇö make sure that you click that option before you continue. - + >[!NOTE] + > 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. 6. In the Services section, review the services that you want to use in the farm, and then click Next. - 7. On the Create Site Collection page, do the following: - -1. In the Title and Description section, in the Title box, type the name of your new site. - -2. Optional: In the Description box, type a description of what the site contains. - -3. In the Web Site Address section, select a URL path for the site. - -4. In the Template Selection section, in the Select a template list, select the template that you want to use for the top-level site in the site collection. - - > [!NOTE] - > To view a template or a description of a template, click any template in the Select a template list. - + 1. In the Title and Description section, in the Title box, type the name of your new site. + 2. Optional: In the Description box, type a description of what the site contains. + 3. In the Web Site Address section, select a URL path for the site. + 4. In the Template Selection section, in the Select a template list, select the template that you want to use for the top-level site in the site collection. + > [!NOTE] + > To view a template or a description of a template, click any template in the Select a template list. 8. Click OK. - 9. On the Configure your SharePoint farm page, review the summary of the farm configuration, and then click Finish. - + ## Post-installation steps -<a name="section4"> </a> 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. -- Configure usage and health data collection You can configure usage and health data collection in your server farm. The system writes usage and health data to the logging folder and to the logging database. - -- Configure diagnostic logging You can configure diagnostic logging that might be required after initial installation or upgrade. The default settings are sufficient for most situations. Depending upon the business needs and life-cycle of the farm, you might want to change these settings. - -- Configure incoming e-mail You can configure incoming e-mail so that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail so that SharePoint sites can archive e-mail discussions as they occur, save e-mailed documents, and show e-mailed meetings on site calendars. In addition, you can configure the SharePoint Directory Management Service to provide support for e-mail distribution list creation and administration. - -- Configure outgoing email You can configure outgoing email so that your Simple Mail Transfer Protocol (SMTP) server sends email alerts to site users and notifications to site administrators. You can configure both the "From" email address and the "Reply" email address that appear in outgoing alerts. - -- Configure Search settings You can configure Search settings to crawl the content in SharePoint Server. +- Configure usage and health data collection You can configure usage and health data collection in your server farm. The system writes usage and health data to the logging folder and to the logging database. +- Configure diagnostic logging You can configure diagnostic logging that might be required after initial installation or upgrade. The default settings are sufficient for most situations. Depending upon the business needs and life-cycle of the farm, you might want to change these settings. +- Configure incoming e-mail You can configure incoming e-mail so that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail so that SharePoint sites can archive e-mail discussions as they occur, save e-mailed documents, and show e-mailed meetings on site calendars. In addition, you can configure the SharePoint Directory Management Service to provide support for e-mail distribution list creation and administration. +- Configure outgoing email You can configure outgoing email so that your Simple Mail Transfer Protocol (SMTP) server sends email alerts to site users and notifications to site administrators. You can configure both the "From" email address and the "Reply" email address that appear in outgoing alerts. +- Configure Search settings You can configure Search settings to crawl the content in SharePoint Server.
SharePoint	Installing Sharepoint Subscription Edition On One Server	https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/installing-sharepoint-subscription-edition-on-one-server.md	Title: "Installing SharePoint Server Subscription Edition on one server" --++ Last updated 06/23/2021 audience: ITPro Use the following procedure to install and configure the configuration database If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint Server Subscription Edition are installed, in the`%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\LOGS` folder. - If you are prompted for your user name and password, you might have to add the SharePoint Central Administration website 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](install-sharepoint-server-2016-on-one-server.md#configurebrowser). + If you are prompted for your user name and password, you might have to add the SharePoint Central Administration website 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](install-sharepoint-server-2016-on-one-server.md#configure-browser-settings). ### Configure browser settings <a name="configurebrowser"> </a>
SharePoint	Single Server With Sql Server	https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/single-server-with-sql-server.md	Use the following procedure to install and configure the configuration database If the SharePoint Products Configuration Wizard fails, check the PSCDiagnostics log files, which are located on the drive on which SharePoint 2013 is installed, in the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\15\LOGS folder. - If you are 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](install-sharepoint-server-2016-on-one-server.md#configurebrowser). + If you are 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](install-sharepoint-server-2016-on-one-server.md#configure-browser-settings). ### Configure browser settings <a name="configurebrowser"> </a>
SharePoint	New And Improved Features In Sharepoint Server Subscription Edition	https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition.md	description: "Learn about the new features and updates to existing features in S [!INCLUDE[appliesto-xxx-xxx-xxx-SUB-xxx-md](../includes/appliesto-xxx-xxx-xxx-SUB-xxx-md.md)] -Learn about the new features and updates to existing features in SharePoint Server Subscription Edition. +Learn about the new features and updates to existing features that were introduced during the initial release of SharePoint Server Subscription Edition. + +For information on new and updated features that were introduced after the initial release of SharePoint Server Subscription Edition, see [SharePoint Server Subscription Edition Version 22H2](new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release.md) and [SharePoint Server Subscription Edition Version 23H1](new-and-improved-features-in-sharepoint-server-subscription-edition-23h1-release.md). ## List of new features and updates to existing features -The following table provides the list of new features and updates to existing features in SharePoint Server Subscription Edition. +The following table provides the list of new features and updates to existing features, introduced during the initial release of SharePoint Server Subscription Edition. \|Feature Group\|Features\|More info\| \|:--\|:--\|:--\| SharePoint Server Subscription Edition supports additional security features whe <a name="core"> </a> ### Windows Server Core -Windows Server Core is a leaner Windows Server deployment type compared to the classic Windows Server with Desktop Experience. Server Core minimizes the number of OS features and services that are installed and running to only those that are truly needed for a server. This reduces the demand on system resources (CPU, RAM, and disk space) and the potential attack surface for security vulnerabilities. +Windows Server Core is a leaner Windows Server deployment type compared to the classic Windows Server with Desktop Experience. Server Core minimizes the number of OS features and services that are installed and running to only those that are essential for a server. This reduces the demand on system resources (CPU, RAM, and disk space) and the potential attack surface for security vulnerabilities. SharePoint Server Subscription Edition adds support for the Windows Server Core deployment type with both Windows Server 2019 and Windows Server 2022. The Windows Server Desktop Experience deployment type remains supported with both Windows Server 2019 and Windows Server 2022.