-You can't move the site from "/sites" to "/teams." For info about changing your SharePoint domain name, see [Change your SharePoint domain name (preview)](change-your-sharepoint-domain-name.md).

- For example, the full URL will resemble the following: **https://fabrikam.sharepoint.com/_layouts/15/people.aspx/membershipGroupId=0**

-[About SharePoint](https://dev.office.com/sharepoint)

-This is especially important in a cross-site publishing scenario (see [An introduction to cross-site publishing in SharePoint Server](an-introduction-to-cross-site-publishing.md)). With cross-site publishing, content is stored in an Authoring site collection and displayed in a Publishing site collection. Managed navigation is used together with category pages and catalog item pages to display content (see [Stage 8: Assign a category page and a catalog item page to a term in SharePoint Server](stage-8-assign-a-category-page-and-a-catalog-item-page-to-a-term.md)). This means that when a visitor views an item on the publishing site, the usage event happens on the catalog item page, for example *http://www.contoso/sites/Pages/ContosoItemPage.aspx*. Because the same catalog item page is used to display many items, the usage event cannot be recorded using the URL of the catalog item page. For Usage analytics to work in a cross-site publishing scenario, the usage event must be recorded using the URL of the item in the authoring site collection, for example *http://www.contoso/sites/catalog/Lists/Products/DispForm.aspx?ID=12*.

-[BI and analytics](https://www.microsoft.com/cloud-platform/bi-analytics)

-Configuring task Synchronization can be relatively complex. By following the guidance below, you should be able to quickly configure task synchronization between your Exchange Server 2016, SharePoint Server 2013 and Project Server 2013 environments. This is great functionality for any business, because you are able to integrate tasks from different applications into one application, like Outlook 2016 or SharePoint MySites.

-We'll start by getting a copy of the **EWSManagedAPI.msi** from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=42951) (https://www.microsoft.com/download/details.aspx?id=35371). Download this to each application server (App server) in your SharePoint environment. These are the servers which users browse to when going to your SharePoint site. This component is needed for SharePoint and Exchange to be able to have this cross-product functionality.You need to install the EWSManagedAPI.msi file via a command-line window. Open that window as an administrator, then make sure you change directories as needed to get to the location of the downloaded file. You'll need to run this one line of script once you're there, exactly as you see it below:

-This will start the EWS API 2.2. wizard, where you'll be able to accept the license agreement terms and then get to the following screen.

-

-

-

-Run this script (It's installed with Exchange, so it's already there) from the Exchange Management Shell on all Exchange Mailbox servers in your organization from this location, "C:\Program Files\Microsoft\Exchange Server\V15\Scripts.":

-Note that you may need to import the Exchange Server SSL certificate from Exchange Server to SharePoint Server, and from SharePoint Server to Exchange Server. This is only necessary if the certificate is not trusted for the API endpoints (such as a Self-SSL Certificate in a lab environment).

-1. Download EWSManagedAPI.msi from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=42951) and save it to a folder on each web and application server.

- Write-Warning "If $($metadataEndpoint) does not exist you may specify an alternate FQDN using ExchangeAutodiscoverDomain."

-1. On your instance of Exchange Server open the Exchange Management PowerShell window as Administrator and change to the "C:\Program Files\Microsoft\Exchange Server\V15\Scripts" directory .

-|5 <br/> |ServerBusy <br/> |Exchange timed out during AutoDiscovery. It should be intermittent, please retry, but if it is persistent, follow-up with the Exchange Administrator. <br/> |

-|10 <br/> |UnknownError <br/> |An unknown error condition has occurred. Run the Check script and confirm that a valid, trusted instance of SharePoint is available, review prerequisites, confirm AutoDiscover has been set-up properly with the Exchange Administrator. <br/> |

-|102 <br/> |AssociatedOwnersGroupNull <br/> |One or both of the default Owners and Members groups for the site have been deleted. Each of these two default groups are required to exist on any site where users install site mailboxes. A site administrator should be able to direct a site owner to recreated these required groups. <br/> |

-> Administrators typically use the SharePoint Central Administration website and the SharePoint Management Shell to manage deployments. For information about accessibility for administrators, see [Accessibility for SharePoint 2013](../accessibility-guidelines.md). > Because SharePoint Server runs as websites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide. SharePoint Server supports the accessibility features of supported browsers. For more information, see the following resources: > [Plan browser support in SharePoint Server 2016](../install/browser-support-planning-2016-2019.md)> [Accessibility features in SharePoint](https://office.microsoft.com/sharepoint-foundation-help/accessibility-features-HA010369400.aspx)> [Keyboard shortcuts](https://office.microsoft.com/sharepoint-server-help/keyboard-shortcuts-HA010369395.aspx)> [Touch](/windows/desktop/wintouch/windows-touch-gestures-overview)

-In this example, the root site collection, http://intranet.fabrikam.com, represents the default home page for the intranet. This site is intended to host content for users.

-In this example, the root site collection, https://teams.fabrikam.com, does not necessarily host content for users.

-Single-name URLs, such as http://teams, can be configured for intranet access. A client computer resolves these URLs by appending the DNS suffix of the client computer, such as fabrikam.com, and then issuing a DNS lookup for the name with the suffix. For example, when a client computer in the fabrikam.com domain requests http://teams, the computer sends a request to DNS for http://teams.fabrikam.com.

-After a client browser receives the load-balanced IP address, the client browser connects to a front-end web server in the farm, and then sends an HTTP request that has the original single-name URL, http://teams. IIS and SharePoint Server recognize this as a request for the Intranet zone, based on the settings that are configured in alternate access mappings. If a user instead requests https://teams.fabrikam.com, the process is similar, but IIS and SharePoint Server receive this FQDN instead, and therefore recognize this request for the Default zone.

-1. From a browser, go to [AdventureWorks sample database](https://go.microsoft.com/fwlink/?LinkId=260952) and download the AdventureWorks2008R2_Data.mdf file.

-1. Create a resource group with a vNet and then create two subnets. You can use the [SQL Managed Instance Virtual Network Environment](https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-managed-instance-azure-environment) template to create an Azure Virtual Network with two subnets.

-[Scripting with Windows PowerShell](https://go.microsoft.com/fwlink/p/?LinkId=193051)

- For SharePoint 2013, [download the RBS_amd64.msi file](https://go.microsoft.com/fwlink/p/?LinkId=271938).

-[Yammer - Admin Help](/yammer/)

-[Yammer Customer Success Center](https://go.microsoft.com/fwlink/p/?LinkID=331300)

-SQL Server 2008 R2 Reporting Services supports two types of SharePoint integration. Full integration relies on the SharePoint integrated mode. Partial integration relies on two Web Parts, Report Explorer and Report Viewer, which you must install on a SharePoint site and point to a remote report server instance. For more information, see [Overview of Reporting Services and SharePoint Technology Integration](/previous-versions/sql/sql-server-2008-r2/bb326358(v=sql.105)&preserve-view=true) and [Planning for SharePoint Integration](/previous-versions/sql/sql-server-2008-r2/bb326405(v=sql.105)&preserve-view=true).

-For more information, see [Guidance for Using SQL Server BI Features in a SharePoint Farm](https://technet.microsoft.com/library/hh231680.aspx), [Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1)](/sql/sql-server/install/guidance-for-using-sql-server-bi-features-in-a-sharepoint-2010-farm?view=sql-server-2014&preserve-view=true), and [Install SQL Server BI Features with SharePoint (PowerPivot and Reporting Services)](/previous-versions/sql/sql-server-2016/hh231671(v=sql.130)).

-The Power Pivot for SharePoint 2013 add-in enables PowerPivot Gallery, Schedule Data Refresh, and the PowerPivot Management Dashboard in Central Administration. For more information, see [PowerPivot for SharePoint (SSAS)](/sql/analysis-services/power-pivot-sharepoint/power-pivot-for-sharepoint-ssas?view=sql-server-2017&preserve-view=true).

-It is possible to capture the site-level and web-level search configuration items and export them to an XML file by using PowerShell. For example, the next PowerShell example will export configuration items from the site "http://intranet.contoso.com" to an XML file that is named intranetcontosocom.xml. This approach was published to the SharePoint community and is used with their permission. You can view this blog post at [Importing and Exporting Search Configuration Settings in SharePoint 2013](https://go.microsoft.com/fwlink/?LinkID=506746&amp;clcid=0x409)

-> To add support for TLS 1.1 and TLS 1.2 in Windows Server 2012 R2, you must install a KB update, and then manually configure Windows Registry keys. > For Windows Server 2016, you only configure the registry keys.

-To enable strong cryptography in .NET Framework 4.5 and 4.5.1 on Windows 7 and Windows Server 2008 R2, see the KB article [Description of the security update for the .NET Framework 4.5 and the .NET Framework 4.5.1 on Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1: May 13, 2014](https://support.microsoft.com/kb/2938782).

-Thank you to Waqas Sarwar, Microsoft MVP, for providing the following article about web part security in SharePoint Server 2016, [SharePoint 2016 Central Admin - Security - Manage Web Part security](https://krossfarm.com/?p=1483).

-|{URLToken.\<integer\>} <br/> |A value from the URL of a page. The integer represents the position of the value in the URL as counted from right to left. For example, for the page http://www.contoso/audio/mp3/1010101, the query variable {URLToken.1} will query for the last value in the URL, 1010101. The query variable {URLToken.3} will query for the third last property in the URL, audio. You can query for values up to the ninth last position in a ULR. <br/> |

-For more information about the Microsoft PowerShell for Azure cmdlets, see [Get-AzureVM](/previous-versions/azure/mt126007(v=azure.100)) and [Add-AzureEndpoint](https://msdn.microsoft.com/library/mt589127.aspx)

-

-[Deploy SharePoint Framework web parts to SharePoint Server 2016 with Feature Pack 2](https://dev.office.com/blogs/now-available-deploy-sharepoint-framework-web-parts-to-sharepoint-server-2016-with-feature-pack-2)