Updates from: 03/04/2022 02:20:54
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Authentication Context Example https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/authentication-context-example.md
Authentication contexts are used with sensitivity labels to connect [Azure AD co
## Requirements
-Some apps do not currently work with authentication contexts. If you have Office apps or third party apps, we recommend testing them on a site with authentication context enabled before broadly deploying this feature. Currently, the following apps do *not* work with authentication contexts:
+Some apps do not currently work with authentication contexts. If you have Office apps or third party apps, we recommend testing them on a site with authentication context enabled before broadly deploying this feature. Currently, the following apps and scenarios do *not* work with authentication contexts:
- Older version of Office apps (see the [list of supported versions](/microsoft-365/compliance/sensitivity-labels-teams-groups-sites#more-information-about-the-dependencies-for-the-authentication-context-option)) - Teams web app-- Workflows that use Power Apps or Power Automate
+- OneNote app can't be added to channel if the associated SharePoint site has an authentication context
+- Teams private channel won't provision a SharePoint if the main team site has an authentication context
+- Teams channel meeting recording upload fails on sites with an authentication context
+- SharePoint folder renaming in Teams fails if the site has an authentication context
+- Teams webinar scheduling fails if OneDrive has an authentication context
+- Workflows that use Power Apps or Power Automate fails to work for sites with an authentication context
- Third-party apps-- The OneDrive sync app won't sync sites with an authentication context.
+- The OneDrive sync app won't sync sites with an authentication context
+- Copy or Move files from Site-A(no policy) to Site-B(with policy) fails
Using authentication context with SharePoint sites requires at least one of the below licenses: - Office 365 E5
SharePoint Install And Configure Rbs https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/install-and-configure-rbs.md
- IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: 4cf30b48-f908-4774-920c-d2f2916f2c1b
-description: "Learn how use the FILESTREAM provider to enable Remote BLOB Storage (RBS) in a SharePoint Server farm."
+description: "Learn how to use the FILESTREAM provider to enable Remote BLOB Storage (RBS) in a SharePoint Server farm."
# Install and configure RBS with FILESTREAM in a SharePoint Server farm
SharePoint Server uses the RBS feature to store binary large objects (BLOBs) out
Unless otherwise specified, the information in this article is specific to RBS using the FILESTREAM provider. For guidance specific to another provider, contact the provider manufacturer. > [!TIP]
-> This solution uses the FILESTREAM RBS provider that is included with SQL Server 2014, Service Pack 1 SP1, SP2, SQL Server 2016, SQL Server 2016 SP1, and SQL Server 2008. If you want to install and configure RBS using a different provider, use the procedure in [Install and configure RBS with a 3rd party provider for SharePoint Server](install-and-configure-rbs-with-a-3rd-party-provider.md).
+> This solution uses the FILESTREAM RBS provider that is included with SQL Server 2019, SQL Server 2017, SQL Server 2016, SQL Server 2016 SP1, SQL Server 2014, Service Pack 1 SP1, SP2, and SQL Server 2008. If you want to install and configure RBS using a different provider, use the procedure in [Install and configure RBS with a 3rd party provider for SharePoint Server](install-and-configure-rbs-with-a-3rd-party-provider.md).
## Before you begin
After you have enabled and configured FILESTREAM, provision a BLOB store on the
> [!TIP] > For best performance, simplified troubleshooting, and as a general best practice, we recommend that you create the BLOB store on a volume that does not contain the operating system, paging files, database data, log files, or the tempdb file.
- ```sql
- use [WSS_Content]
- if not exists
- (select * from sys.symmetric_keys
- where name = N'##MS_DatabaseMasterKey##')
- create master key encryption by password = N'Admin Key Password !2#4'
- ```
-
- ```sql
- use [WSS_Content]
- if not exists
- (select groupname from sysfilegroups
- where groupname=N'RBSFilestreamProvider')
- alter database [WSS_Content]
- add filegroup RBSFilestreamProvider contains filestream
- ```
-
- ```sql
- use [WSS_Content]
- alter database [WSS_Content]
- add file (name = RBSFilestreamFile, filename = 'c:\Blobstore') to filegroup RBSFilestreamProvider
- ```
+ ```sql
+ use [WSS_Content]
+ if not exists
+ (select * from sys.symmetric_keys
+ where name = N'##MS_DatabaseMasterKey##')
+ create master key encryption by password = N'Admin Key Password !2#4'
+ ```
+
+ ```sql
+ use [WSS_Content]
+ if not exists
+ (select groupname from sysfilegroups
+ where groupname=N'RBSFilestreamProvider')
+ alter database [WSS_Content]
+ add filegroup RBSFilestreamProvider contains filestream
+ ```
+
+ ```sql
+ use [WSS_Content]
+ alter database [WSS_Content]
+ add file (name = RBSFilestreamFile, filename = 'c:\Blobstore') to filegroup RBSFilestreamProvider
+ ```
## Install the RBS client library on SQL Server and each Front-end or Application server <a name="library"> </a>
You must install RBS client library on the SQL Server node and all Front-end or
2. On SQL Server node, download the correct RBS client based on the SQL Server version and SharePoint level that you use.
- SharePoint Server 2016 supports the FILESTREAM provider that is included in the SQL Server 2014 and SQL Server 2016.
+ SharePoint Server Subscription Edition supports the FILESTREAM provider that is included in SQL Server 2019 and later versions of SQL Server.
+
+ SharePoint Server 2019 supports the FILESTREAM provider that is included in SQL Server 2016 and SQL Server 2017.
+
+ SharePoint Server 2016 supports the FILESTREAM provider that is included in SQL Server 2014 and SQL Server 2016.
SharePoint 2013 supports the FILESTREAM providers that are included in all versions of SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014. You only need to download the RSB.msi file from the Feature Pack but make sure you download the correct processor type for your server, either x86 or x64.
+ For SharePoint Server Subscription Edition, choose the correct install from the following list:
+
+ - [Microsoft SQL Server 2019 Integration Services Feature Pack](https://www.microsoft.com/download/details.aspx?id=100303)
+
+ For SharePoint Server 2019, choose the correct install from the following list:
+
+ - [Microsoft SQL Server 2016 SP1 Feature Pack](https://www.microsoft.com/download/details.aspx?id=54279)
+
+ - [Microsoft SQL Server 2016 SP2 Feature Pack](https://www.microsoft.com/download/details.aspx?id=56833)
+
+ - [Microsoft SQL Server 2016 SP3 Feature Pack](https://www.microsoft.com/download/details.aspx?id=103444)
+
+ - [Microsoft SQL Server 2017 Feature Pack](https://www.microsoft.com/download/details.aspx?id=55992)
+ For SharePoint Server 2016, choose the correct install from the following list: - [Microsoft SQL Server 2014 Feature Pack](https://go.microsoft.com/fwlink/p/?LinkID=733635)
You must install RBS client library on the SQL Server node and all Front-end or
- [Microsoft SQL Server 2014 SP2 Feature Pack](https://www.microsoft.com/download/details.aspx?id=53164) 3. Copy and paste the following command into the Command Prompt window. Replace _WSS_Content_ with the database name, and replace _DBInstanceName_ with the SQL Server instance name. You should run this command by using the specific database name and SQL Server instance name only one time. The action should finish within approximately one minute.
-
- ```
- msiexec /qn /lvx* rbs_install_log.txt /i RBS_amd64.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_Content" DBINSTANCE="DBInstanceName" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
- ```
+
+ ```sql
+ msiexec /qn /lvx* rbs_install_log.txt /i RBS_amd64.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_Content" DBINSTANCE="DBInstanceName" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1
+ ```
### To install the RBS client library on all SharePoint Front-end and Application servers
You must install RBS client library on the SQL Server node and all Front-end or
2. On any web server, download the correct RBS client based on the SQL Server version and SharePoint level that you use. Use one of the following lists to choose the correct install.
- SharePoint Server 2016 supports the FILESTREAM provider that is included in the SQL Server 2014 and SQL Server 2016.
+ SharePoint Server Subscription Edition supports the FILESTREAM provider that is included in SQL Server 2019 and later versions of SQL Server.
+
+ SharePoint Server 2019 supports the FILESTREAM provider that is included in SQL Server 2016 and SQL Server 2017.
+
+ SharePoint Server 2016 supports the FILESTREAM provider that is included in SQL Server 2014 and SQL Server 2016.
SharePoint 2013 supports the FILESTREAM providers that are included in all versions of SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014. You only need to download the RSB.msi file from the Feature Pack but make sure you download the x64 version.
+ For SharePoint Server Subscription Edition, choose the correct install from the following list:
+
+ - [Microsoft SQL Server 2019 Integration Services Feature Pack](https://www.microsoft.com/download/details.aspx?id=100303)
+
+ For SharePoint Server 2019, choose the correct install from the following list:
+
+ - [Microsoft SQL Server 2016 SP1 Feature Pack](https://www.microsoft.com/download/details.aspx?id=54279)
+
+ - [Microsoft SQL Server 2016 SP2 Feature Pack](https://www.microsoft.com/download/details.aspx?id=56833)
+
+ - [Microsoft SQL Server 2016 SP3 Feature Pack](https://www.microsoft.com/download/details.aspx?id=103444)
+
+ - [Microsoft SQL Server 2017 Feature Pack](https://www.microsoft.com/download/details.aspx?id=55992)
+ For SharePoint Server 2016, choose the correct install from the following list: - [Microsoft SQL Server 2014 Feature Pack](https://go.microsoft.com/fwlink/p/?LinkID=733635)
You must install RBS client library on the SQL Server node and all Front-end or
- [Microsoft SQL Server 2014 SP2 Feature Pack](https://www.microsoft.com/download/details.aspx?id=53164) 3. Copy and paste the following command into the Command Prompt window. Replace _WSS_Content_ with the database name, and replace _DBInstanceName_ with the name of the SQL Server instance. The action should finish within approximately one minute.
-
- ```
- msiexec /qn /lvx* rbs_install_log.txt /i RBS_amd64.msi DBNAME="WSS_Content" DBINSTANCE="DBInstanceName" ADDLOCAL=Client,Docs,Maintainer,ServerScript,FilestreamClient,FilestreamServer
- ```
- > [!NOTE]
- > If you attempt to install SQL Server 2012 Remote Blob Store for an additional database on the same instance of SQL Server, you will receive an error. For more information, see [KB2767183](https://support.microsoft.com/kb/2767183).
+ ```sql
+ msiexec /qn /lvx* rbs_install_log.txt /i RBS_amd64.msi DBNAME="WSS_Content" DBINSTANCE="DBInstanceName" ADDLOCAL=Client,Docs,Maintainer,ServerScript,FilestreamClient,FilestreamServer
+ ```
+
+ > [!NOTE]
+ > If you attempt to install SQL Server 2012 Remote Blob Store for an additional database on the same instance of SQL Server, you will receive an error. For more information, see [KB2767183](https://support.microsoft.com/kb/2767183).
-For subsequent content databases for which you want to enable RBS, change the `msiexec` command similar to below.
-
-```
-msiexec /qn /lvx* rbs_install_log_ContentDbName.txt /i RBS_amd64.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME="WSS_Content_2" ADDLOCAL="EnableRBS,FilestreamRunScript" DBINSTANCE="DBInstanceName"
-```
+ For subsequent content databases for which you want to enable RBS, change the `msiexec` command similar to below.
+
+ ```sql
+ msiexec /qn /lvx* rbs_install_log_ContentDbName.txt /i RBS_amd64.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME="WSS_Content_2" ADDLOCAL="EnableRBS,FilestreamRunScript" DBINSTANCE="DBInstanceName"
+ ```
4. Repeat this procedure for all Front-end servers and Application servers in the SharePoint farm.
You must enable RBS on one web server in the SharePoint farm. It is not importan
**To enable RBS by using Microsoft 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.
-
+
+ - **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.
+ 2. Start the SharePoint Management Shell. 3. At the Microsoft PowerShell command prompt, type the following command:
-
- ```
- $cdb = Get-SPContentDatabase <ContentDatabaseName>
- $rbss = $cdb.RemoteBlobStorageSettings
- $rbss.Installed()
- $rbss.Enable()
- $rbss.SetActiveProviderName($rbss.GetProviderNames()[0])
- $rbss
- ```
+
+ ```powershell
+ $cdb = Get-SPContentDatabase <ContentDatabaseName>
+ $rbss = $cdb.RemoteBlobStorageSettings
+ $rbss.Installed()
+ $rbss.Enable()
+ $rbss.SetActiveProviderName($rbss.GetProviderNames()[0])
+ $rbss
+ ```
Where _\<ContentDatabaseName\>_ is the name of the content database.
SharePoint Rbs Overview https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/rbs-overview.md
description: "Learn about how to use Remote BLOB Storage (RBS) in a SharePoint S
# Overview of RBS in SharePoint Server This article describes how to use SharePoint Server together with Remote BLOB Storage (RBS) and SQL Server to optimize database storage resources.
Before you implement RBS, we highly recommend that you evaluate its potential co
## Introduction to RBS <a name="Section2"> </a>
-In SharePoint Server, a binary large object (BLOB) is a large block of data stored in a database that is known by its size and location instead of by its structure ΓÇö for example a Office document or a video file. By default, these BLOBs, also known as unstructured data, are stored directly in the SharePoint content database together with the associated metadata, or structured data. Because these BLOBs can be very large, it might be better to store BLOBs outside the content database. BLOBs are immutable. Therefore, a new copy of the BLOB must be stored for each version of that BLOB. Because of this, as a database's usage increases, the total size of its BLOB data can expand quickly and grow larger than the total size of the document metadata and other structured data that is stored in the database. BLOB data can consume lots of space and uses server resources that are optimized for database access patterns. Therefore, it can be helpful to move BLOB data out of the SQL Server database, and onto commodity or content addressable storage. To do this, you can use RBS.
+In SharePoint Server, a binary large object (BLOB) is a large block of data stored in a database that is known by its size and location instead of by its structure ΓÇö for example an Office document or a video file. By default, these BLOBs, also known as unstructured data, are stored directly in the SharePoint content database together with the associated metadata, or structured data. Because these BLOBs can be very large, it might be better to store BLOBs outside the content database. BLOBs are immutable. Therefore, a new copy of the BLOB must be stored for each version of that BLOB. Because of this, as a database's usage increases, the total size of its BLOB data can expand quickly and grow larger than the total size of the document metadata and other structured data that is stored in the database. BLOB data can consume lots of space and uses server resources that are optimized for database access patterns. Therefore, it can be helpful to move BLOB data out of the SQL Server database, and onto commodity or content addressable storage. To do this, you can use RBS.
RBS is a SQL Server library API set that is incorporated as an add-in feature pack that you can install when you install the following:
+- SQL Server 2019
+
+- SQL Server 2017
+
+- SQL Server 2016
+ - SQL Server 2014 Service Pack 1 (SP1) - SQL Server 2014
RBS is composed of the following components:
An RBS provider consists of a managed library and, optionally, a set of native libraries that communicate with the BLOB store.
- An example of an RBS provider is the SQL FILESTREAM provider. The SQL FILESTREAM provider is an add-in feature of SQL Server 2014 Service Pack 1 (SP1) that enables storage of and efficient access to BLOB data by using a combination of SQL Server 2014 (SP1) and the NTFS file system. For more information about FILESTREAM, see [FILESTREAM (SQL Server)](/sql/relational-databases/blob/filestream-sql-server?viewFallbackFrom=sql-server-2014) For information about how to enable and configure FILESTREAM, see [Enable and Configure FILESTREAM](/sql/relational-databases/blob/enable-and-configure-filestream?viewFallbackFrom=sql-server-2014).
+ An example of an RBS provider is the SQL FILESTREAM provider. The SQL FILESTREAM provider is an add-in feature of SQL Server 2014 Service Pack 1 (SP1) or later versions of SQL Server that enables storage of and efficient access to BLOB data by using a combination of SQL Server 2014 (SP1) or later versions and the NTFS file system. For more information about FILESTREAM, see [FILESTREAM (SQL Server)](/sql/relational-databases/blob/filestream-sql-server?viewFallbackFrom=sql-server-2014) For information about how to enable and configure FILESTREAM, see [Enable and Configure FILESTREAM](/sql/relational-databases/blob/enable-and-configure-filestream?viewFallbackFrom=sql-server-2014).
- **BLOB store**
RBS is composed of the following components:
RBS uses a provider to connect to any dedicated BLOB store that uses the RBS APIs. SharePoint Server supports a BLOB storage implementation that accesses BLOB data by using the RBS APIs through such a provider. There are two kinds of RBS providers, local and remote.
-The location in which an RBS provider stores the BLOB data depends on the provider that you use. In the case of the FILESTREAM provider, the data is not stored in the .mdf file. Instead, it is stored in another folder that is associated with the database.
+The location in which an RBS provider stores the BLOB data depends on the provider that you use. In the case of the FILESTREAM provider, the data isn't stored in the .mdf file. Instead, it's stored in another folder that is associated with the database.
### Local RBS provider A local provider stores the BLOBS outside the database but on the same server that is running SQL Server. You can conserve resources by using the local RBS FILESTREAM provider to put the extracted BLOB data on a different (that is, less resource-intensive) local disk. Because the BLOBs are stored in the same Filegroup as the metadata, SharePoint Server features, such as backup and restore in Central Administration, can be used.
-The RBS FILESTREAM provider is available as an add-in when you install SQL Server 2014 Service Pack 1 (SP1). The RBS FILESTREAM provider uses the SQL Server FILESTREAM feature to store BLOBs in an additional resource that is attached to the same database and stored locally on the server. The FILESTREAM feature manages BLOBs in a SQL database by using the underlying NTFS file system.
+The RBS FILESTREAM provider is available as an add-in when you install SQL Server 2014 Service Pack 1 (SP1) or later versions of SQL Server. The RBS FILESTREAM provider uses the SQL Server FILESTREAM feature to store BLOBs in an additional resource that is attached to the same database and stored locally on the server. The FILESTREAM feature manages BLOBs in a SQL database by using the underlying NTFS file system.
> [!IMPORTANT] > The local FILESTREAM provider is supported only when it is used on local hard disk drives or an attached Internet Small Computer System Interface (iSCSI) device. You cannot use the local RBS FILESTREAM provider on remote storage devices such as network attached storage (NAS).
The RBS FILESTREAM provider is available as an add-in when you install SQL Serve
A remote RBS provider stores the BLOBs on a separate server. This is typically on a separate volume on the same network as the database server.
-Because the BLOBs are not stored in the same Filegroup with the metadata, some SharePoint Server features ΓÇö for example, backup and restore in Central Administration ΓÇö cannot be used with remote RBS providers. The metadata and the BLOBs must be managed separately. For more information about what features can be used with the provider, contact the provider manufacturer.
+Because the BLOBs aren't stored in the same Filegroup with the metadata, some SharePoint Server features ΓÇö for example, backup and restore in Central Administration ΓÇö canΓÇÖt be used with remote RBS providers. The metadata and the BLOBs must be managed separately. For more information about what features can be used with the provider, contact the provider manufacturer.
## Using RBS together with SharePoint Server <a name="Section3"> </a>
-SharePoint Server 2016 supports the FILESTREAM provider that is included in SQL Server 2014 (SP1). This version of RBS is included on the SQL Server installation media, but is not installed by the SQL Server Setup program..
+SharePoint Server Subscription Edition supports the FILESTREAM provider that is included in SQL Server 2019 and later versions of SQL Server. This version of RBS is included on the SQL Server installation media, but isn't installed by the SQL Server Setup program.
+
+SharePoint Server 2019 supports the FILESTREAM provider that is included in SQL Server 2016 and SQL Server 2017. This version of RBS is included on the SQL Server installation media, but isn't installed by the SQL Server Setup program.
+
+SharePoint Server 2016 supports the FILESTREAM provider that is included in SQL Server 2014 (SP1). This version of RBS is included on the SQL Server installation media, but isn't installed by the SQL Server Setup program.
SharePoint 2013 supports the FILESTREAM provider that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014. These versions of RBS are available at the following locations:
SharePoint 2013 supports the FILESTREAM provider that is included in the SQL Ser
- [Microsoft SQL Server 2014 Feature Pack](https://www.microsoft.com/download/details.aspx?id=42295)
-Be aware that SQL Server Remote BLOB Store installation package for SQL Server 2014 is the only version of RBS that is supported by SharePoint Server 2016. SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2 and later are the only versions of RBS that are supported by SharePoint 2013. Earlier versions are not supported. Third-party RBS providers can also be used with the RBS APIs to create a BLOB storage solution that is compatible with SharePoint Server.
+Be aware of the following:
+
+- SQL Server Remote BLOB Store installation package for SQL Server 2019 and later versions of SQL Server are the only versions of RBS that are supported by SharePoint Server Subscription Edition.
+- SQL Server Remote BLOB Store installation package for SQL Server 2016 and SQL Server 2017 are the only versions of RBS that are supported by SharePoint Server 2019.
+- SQL Server Remote BLOB Store installation package for SQL Server 2014 is the only version of RBS that is supported by SharePoint Server 2016.
+- SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2 and later are the only versions of RBS that are supported by SharePoint 2013. Earlier versions aren't supported.
+
+Third-party RBS providers can also be used with the RBS APIs to create a BLOB storage solution that is compatible with SharePoint Server.
In SharePoint Server, site collection backup and restore and site import or export will download the file contents and upload them back to the server regardless of which RBS provider is being used. This process is known as a deep copy. However, the FILESTREAM provider is the only provider that is currently supported for SharePoint Server farm database backup and restore operations. To use RBS, you must install an RBS provider on each server where SharePoint Server is installed and on each database server in the topology. The provider includes a set of DLLs that implement methods for the RBS APIs and perform the actual operation of externalizing the BLOBs. > [!NOTE]
-> If Visio web services runs on SharePoint Server application servers that do not have an RBS provider installed, a Visio error occurs when you attempt to open a Visio diagram from this server. You must install an RBS client on SharePoint Server servers that run the Visio Graphics Service if you want to open Visio diagrams on that server.
+> If Visio web services runs on SharePoint Server application servers that do not have an RBS provider installed, a Visio error occurs when you attempt to open a Visio diagram from this server. You must install an RBS client on SharePoint Server servers that run the Visio Graphics Service if you want to open Visio diagrams on that server.
+
+**SharePoint Server Subscription Edition:** To run RBS on a remote server, you must be running SQL Server 2019 or later versions of SQL Server Enterprise on the server that is running SQL Server where the metadata is stored in the database.
- **SharePoint Server 2016:** To run RBS on a remote server, you must be running SQL Server 2014 (SP1) Enterprise on the server that is running SQL Server where the metadata is stored in the database.
+If you plan to store BLOB data in an RBS store that differs from your SharePoint Server Subscription Edition content databases, you must run SQL Server 2019 or later versions of SQL Server. This is true for all RBS providers.
+
+**SharePoint Server 2019:** To run RBS on a remote server, you must be running SQL Server 2016 or SQL Server 2017 Enterprise on the server that is running SQL Server where the metadata is stored in the database.
+
+If you plan to store BLOB data in an RBS store that differs from your SharePoint Server 2019 content databases, you must run SQL Server 2016 or SQL Server 2017. This is true for all RBS providers.
+
+**SharePoint Server 2016:** To run RBS on a remote server, you must be running SQL Server 2014 (SP1) Enterprise on the server that is running SQL Server where the metadata is stored in the database.
If you plan to store BLOB data in an RBS store that differs from your SharePoint Server 2016 content databases, you must run SQL Server 2014 (SP1). This is true for all RBS providers.
- **SharePoint Server 2013:** To run RBS on a remote server, you must be running SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 Enterprise on the server that is running SQL Server where the metadata is stored in the database.
+**SharePoint Server 2013:** To run RBS on a remote server, you must be running SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 Enterprise on the server that is running SQL Server where the metadata is stored in the database.
If you plan to store BLOB data in an RBS store that differs from your SharePoint 2013 content databases, you must run SQL Server 2008 with SP1 and Cumulative Update 2, SQL Server 2012, or SQL Server 2014. This is true for all RBS providers.
-The FILESTREAM provider that is recommended for upgrading from stand-alone installations of Windows SharePoint Services 3.0 that have content databases that are over 4 gigabytes (GB) to SharePoint 2013 associates data locally with the current content database, and does not require SQL Server Enterprise.
+The FILESTREAM provider that is recommended for upgrading from stand-alone installations of Windows SharePoint Services 3.0 that have content databases that are over 4 gigabytes (GB) to SharePoint 2013 associates data locally with the current content database, and doesn't require SQL Server Enterprise.
> [!IMPORTANT] > Although RBS can be used to store BLOB data externally, accessing or changing those BLOBs is not supported using any tool or product other than SharePoint Server. All access must occur by using SharePoint Server only.
SharePoint Oidc 1 0 Authentication https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/security-for-sharepoint-server/oidc-1-0-authentication.md
To do this, perform the following steps:
In the [previous step](#step-3-configure-sharepoint-to-trust-the-identity-provider) you have already created an OIDC `SPTrustedIdentityTokenIssuer` by using `New-SPTrustedIdentityTokenIssuer` PowerShell cmdlet. In this step, you will create a claim provider which uses the User Profile Application service to search and resolve users and groups in the People Picker and specifies to use the OIDC `SPTrustedIdentityTokenIssuer`: ```powershell
- $claimprovider = New-SPClaimProvider -AssemblyName "Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, publicKeyToken=71e9bce111e9429c" -DisplayName 'OIDC Claim Provider' -Type "Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByUPAClaimProvider" -TrustedTokenIssuer $tokenissuer
+ $claimprovider = New-SPClaimProvider -AssemblyName "Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, publicKeyToken=71e9bce111e9429c" -DisplayName 'OIDC Claim Provider' -Type "Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByUPAClaimProvider" -TrustedTokenIssuer $tokenissuer -Description ΓÇ£OIDC Claim ProviderΓÇ¥ -Default:$false
``` There are three parameters that need to be specified here:
There are three parameters that need to be specified here:
| AssemblyName | To be specified as "Microsoft.SharePoint, Version=16.0.0.0, Culture=neutral, publicKeyToken=71e9bce111e9429c". | | Type | To be specified as "Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByUPAClaimProvider" so that this command creates a claim provider which uses UPA as the claim source. | | TrustedTokenIssuer | To be specified as the OIDC `SPTrustedIdentityTokenIssuer` created in the [previous step](#step-3-configure-sharepoint-to-trust-the-identity-provider) which will use this claim provider. This is a new parameter the user needs to provide when the type of the claim provider is "Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByUPAClaimProvider". |
+| Default | As we have created a claim provider by using this cmdlet, this cmdlet can only work with SPTrustedIdentityTokenIssuer and ΓÇ£DefaultΓÇ¥ parameter must be set to false so that it wonΓÇÖt be used by any other authentication method assigned to the web application by default. |
#### 2. Connect `SPTrustedIdentityTokenIssuer` with `SPClaimProvider`
To enable the People Picker control to work with groups, the following steps nee
1. For AD Import synchronization, SID will be synchronized automatically without additional setup from the source identity provider to the SharePoint User Profile Application service. 2. For MIM synchronization, the property mapping needs to be taken from the identity provider to MIM and then from MIM to the SharePoint User Profile Application service so that MIM can synchronize the group ΓÇ£SIDΓÇ¥ from the identity provider to the SharePoint User Profile Application service. This is similar to how we do user profile synchronization for the `SPS-ClaimID` property for user profiles.
-3. For MIM synchronization, ΓÇ£sAMAccountNameΓÇ¥ should also be mapped to ΓÇ£accountNameΓÇ¥ from MIM to the SharePoint User Profile Application service.
+3. For MIM synchronization, ΓÇ£sAMAccountNameΓÇ¥ should also be mapped to ΓÇ£accountNameΓÇ¥ from MIM to the SharePoint User Profile Application service. If it doesnΓÇÖt exist, admin should create mapping pair from ΓÇ£sAMAccountNameΓÇ¥ to ΓÇ£accountNameΓÇ¥ in MIM manually.
#### 5. Enable fields being searchable in UPSA
If you choose to use AD FS as identity provider, perform the following steps to
:::image type="content" source="../media/add-transform-claim-rule.png" alt-text="Add Transform Claim Rule":::
- 3. Give your Claim rule a name of **AD** and select **Active Directory** from the Attribute store drop down menu. Create two mappings using the drop-down boxes as shown:
+ 3. Give your Claim rule a name of **AD** and select **Active Directory** from the Attribute store dropdown menu. Create two mappings using the drop-down boxes as shown:
| Attribute | Value | |||