Updates from: 02/09/2021 04:24:48
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint https://docs.microsoft.com/en-us/SharePoint/let-users-sync-irm-protected-files https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/let-users-sync-irm-protected-files.md
@@ -24,47 +24,23 @@ description: "Enable users in your organization to sync IRM-protected locations
# Let users sync IRM-protected files with the OneDrive sync app
-This article is for Microsoft 365 global or SharePoint admins who want their users to be able to sync IRM-protected SharePoint document libraries and OneDrive locations using the new OneDrive sync app.
-
-## Prerequisites
+This article is for Microsoft 365 global or SharePoint admins who want their users to be able to sync IRM-protected SharePoint document libraries and OneDrive locations using the new OneDrive sync app (OneDrive.exe).
> [!NOTE]
-> Any IRM-protected files will maintain their IRM protection during the sync process, both during upload and download.
--- You've applied [Information Rights Management (IRM) to a list or library](https://support.office.com/article/3bdb5c4e-94fc-4741-b02f-4e7cc3c54aa1). (On-premises SharePoint Server libraries can't be synced with the new OneDrive sync app.)
-
-- Your users have disabled syncing using the previous OneDrive for Business sync app
-
-## Known issues
+> Any IRM-protected files will maintain their IRM protection during the sync process, both during upload and download. The OneDrive sync app doesn't support the IRM setting that expires document access rights.
+
+## Prerequisites
-- This feature doesn't support the IRM setting that expires document access rights.
-
-## Disabling the previous OneDrive for Business sync app
+- You've applied [Information Rights Management (IRM) to a library](https://support.office.com/article/3bdb5c4e-94fc-4741-b02f-4e7cc3c54aa1) in Microsoft 365.
-To prevent reliability issues, any users that are using the previous OneDrive for Business sync app (Groove.exe) to sync an IRM-protected library must disable syncing.
-
-1. On a computer that uses the previous sync app to sync IRM-protected libraries, right-click the blue OneDrive icon in the notification area, at the far right of the taskbar:
-
- ![OneDrive - System icon](media/a776932c-5360-4e97-990c-d7da3f3bb2d3.jpg)
-
-2. Select **Stop syncing a folder**.
-
- ![OneDrive - Menu](media/c475b620-0cc4-4ea0-b562-07f52e25a027.jpg)
-
-3. Select the IRM-protected library, and select **Stop syncing**.
-
- ![OneDrive - stop sync dialog](media/414bc509-a0cd-4ecd-9566-12543735365e.jpg)
-
-## Setup instructions
+- You've installed the RMS client on your users' computers. [Download the Rights Management Service client](https://aka.ms/odirm).
-To enable this feature, you need to install the RMS client on your users' computers. [Download the Rights Management Service client](https://aka.ms/odirm).
-
-To silently install the client on computers, use the /qn switch as part of the command-line options of the Microsoft Windows Installer Tool (Msiexec.exe). For example, the following command shows the silent mode installation (assuming the RMS Client installer package is already downloaded to C:\Downloads).
+ To silently install the client on computers, use the /qn switch as part of the command-line options of the Microsoft Windows Installer Tool (Msiexec.exe). For example, the following command shows the silent mode installation (assuming the RMS Client installer package is already downloaded to C:\Downloads).
-msiexec /qn c:\downloads\setup.msi
+ msiexec /qn c:\downloads\setup.msi
-You can have the setup file on a network share and use managed software deployment to run the msiexec command.
+ You can have the setup file on a network share and use managed software deployment to run the msiexec command.
## To sync an IRM-protected library
-Have your users browse to the library in SharePoint and click the Sync button. This will open the OneDrive sync app and create the sync relationship for the location.
+Users sync IRM-protected libraries in the same way they sync other libraries. For info, see [Sync SharePoint files with the new OneDrive sync app](https://support.office.com/article/6de9ede8-5b6e-4503-80b2-6190f3354a88).
SharePoint https://docs.microsoft.com/en-us/SharePoint/let-users-use-new-onedrive-sync-client https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/let-users-use-new-onedrive-sync-client.md
@@ -1,89 +0,0 @@
- Title: "How to let users sync SharePoint files with the OneDrive sync app"------ NOCSH--
-localization_priority: Normal
--- Strat_SP_admin-- M365-collaboration--- seo-marvel-mar2020-- SPO160-- ODB160-- SPB160-- ODB150-- BSA160-- MET150
-description: "Learn how to enable users in your organization to sync SharePoint files with the new OneDrive sync app."
--
-# Let users sync SharePoint files with the new OneDrive sync app
-
-This article is for IT administrators in large organizations who want to enable users in their organizations to sync SharePoint team sites with the new OneDrive sync app. Smaller organizations and organizations that are new to Microsoft 365 are already set up to sync OneDrive and SharePoint files with the new OneDrive sync app.
-
-When you enable this feature, users will be able to sync the files in a SharePoint team site to their PCs and Macs using the OneDrive sync app (OneDrive.exe). As part of this, they will be able to:
-
-- Browse to a SharePoint site or shared folder and click **Sync** to sync all contents in the document library or only selected folders that are important to them.
-
-- Change the folders they sync directly from their PC or Mac.
-
-- Sync shared folders.
-
-- Sync read-only files and folders.
-
-- Coauthor files in real time with Office 2016 (C2R build 16.0.7167.2xxx or MSI build 16.0.4432.100x)
-
-- Automatically transition from the previous OneDrive sync app (Groove.exe)
-
-
-## Deploy and configure the OneDrive sync app
-<a name="TestFeature"> </a>
-
-To enable users in your organization to sync SharePoint team sites with the OneDrive sync app, you first need to deploy the OneDrive sync app to your organization.
-
-See [Deploy the new OneDrive sync app using Microsoft Endpoint Configuration Manager](/onedrive/deploy-on-windows)
-
-See [Deploy and configure the new OneDrive sync app for Mac](/onedrive/deploy-and-configure-on-macos)
-
-For info about the latest sync app releases, see [New OneDrive sync app release notes](https://support.office.com/article/845dcf18-f921-435e-bf28-4e24b95e5fc0).
-
-## Set SharePoint to sync with the OneDrive sync app
-<a name="admincenter"> </a>
-
-1. Go to the [Settings page of the new SharePoint admin center](https://admin.microsoft.com/sharepoint?page=settings&modern=true), and sign in with an account that has [admin permissions](/sharepoint/sharepoint-admin-role) for your organization.
-
->[!NOTE]
->If you have Office 365 Germany, [sign in to the Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=848041), then browse to the SharePoint admin center and open the Settings page. <br>If you have Office 365 operated by 21Vianet (China), [sign in to the Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=850627), then browse to the SharePoint admin center and open the Settings page.
-
-2. Select **classic settings page**.
-
-3. Make sure "OneDrive Sync Button" is set to "Show the Sync button."
-
- ![Admin settings for OneDrive sync button](media/66be619a-fec1-4719-a819-7e3fa6e222f1.PNG)
-
- To sync SharePoint files with the new client, you must also sync OneDrive files with the new client.
-
-4. For "Sync Client for SharePoint," select **Start the new client**.
-
- ![Admin setting for OneDrive sync app](media/894772b5-3e43-4a60-9887-99aca47a261c.PNG)
-
- > [!NOTE]
- > If you don't see the "Sync Client for SharePoint" setting on the Settings page, your organization is already set up to use the new OneDrive sync app. When users sign in to the OneDrive sync app (OneDrive.exe), it will automatically take over syncing the site libraries that the previous new OneDrive sync app (Groove.exe) was syncing. For information about how this works, and about the types of libraries that will continue syncing with the previous sync app, see [Transition from the previous OneDrive for Business sync app](/onedrive/transition-from-previous-sync-client).
-
-5. Select **OK**.
-
- These changes take several hours to propagate. To check that they've propagated, go to a SharePoint site and select **Sync**. In the browser dialog that confirms the request to open a program, the "Program" should appear as "Microsoft OneDrive" and the "Address" should start with "odopen://"
-
-## See also
-<a name="admincenter"> </a>
-
-[Sync SharePoint files with the new OneDrive sync app](https://support.office.com/article/6de9ede8-5b6e-4503-80b2-6190f3354a88)
SharePoint https://docs.microsoft.com/en-us/SharePoint/modern-experience-sharing-permissions https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/modern-experience-sharing-permissions.md
@@ -75,9 +75,9 @@ The SharePoint admin must specify which users can connect other sites to the hub
![Screenshot of hub site registration dialog in the SharePoint admin center](media/permissions-register-hub-site.png)
-## Sharable links
+## Shareable links
-Giving people permissions to a site, group, or team gives them access to all site content. If you want to share an individual file or folder, you can do so with sharable links. There are three primary link types:
+Giving people permissions to a site, group, or team gives them access to all site content. If you want to share an individual file or folder, you can do so with shareable links. There are three primary link types:
- *Anyone* links give access to the item to anyone who has the link, including people outside your organization. People using an *Anyone* link don't have to authenticate, and their access can't be audited. - *People in your organization* links work for only people inside your Microsoft 365 organization. (They don't work for guests in the directory, only members).
SharePoint https://docs.microsoft.com/en-us/SharePoint/SharePointServer/administration/outgoing-email-planning https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/administration/outgoing-email-planning.md
@@ -107,7 +107,7 @@ SharePoint supports the following Simple Authentication and Security Layer (SASL
### Use TLS connection encryption
-Set **Use TLS connection encryption** to Yes to require SharePoint to extablish an encrypted connection to the SMTP server before sending email. A valid server certificate must be installed on the SMTP server to establish an encrypted connection. If this is set to Yes and an encrypted connection can't be established, no emails will be sent.
+Set **Use TLS connection encryption** to Yes to require SharePoint to establish an encrypted connection to the SMTP server before sending email. A valid server certificate must be installed on the SMTP server to establish an encrypted connection. If this is set to Yes and an encrypted connection can't be established, no emails will be sent.
> [!NOTE] > SharePoint supports STARTTLS to establish TLS connection encryption to an SMTP server. It doesn't support SMTPS to establish SSL connection encryption to an SMTP server.
@@ -127,7 +127,7 @@ Some SMTP servers may block impersonation to protect users from unauthorized att
- [Use an externally secured receive connector](#connector)
-####Grant permission for the SharePoint authenticated email account to impersonate users <a name="users"> </a>
+#### Grant permission for the SharePoint authenticated email account to impersonate users <a name="users"> </a>
Microsoft Exchange Server allows you to grant permission for a user to impersonate other users when sending email through a receive connector. Those permissions include:
@@ -146,7 +146,7 @@ Run this command on your Microsoft Exchange Server to grant permission for the S
> [!NOTE] > When using Microsoft Exchange Server 2013 or later, this permission should be applied to the client proxy receive connector. When using Microsoft Exchange Server 2010 or earlier, this permission should be applied to the client frontend receive connector.
-### Disable SharePoint email impersonation <a name="disable"> </a>
+#### Disable SharePoint email impersonation <a name="disable"> </a>
You can configure each SharePoint web application to disable email impersonation. This will ensure that SharePoint always uses the From and Reply-To address specified at the web application level. Run the following to disable SharePoint email impersonation:
@@ -154,13 +154,11 @@ You can configure each SharePoint web application to disable email impersonation
2. Run the following commands: ```powershell
-...
$webapp = Get-SPWebApplication <web application URL> $webapp.OutboundMailOverrideEnvelopeSender = $true $webapp.Update()
-...
```
-### Use an externally secured receive connector <a name="connector"> </a>
+#### Use an externally secured receive connector <a name="connector"> </a>
Microsoft Exchange Server receive connectors can be configured to automatically trust all emails as authenticated, even if no authentication is performed. SharePoint will then send emails to this receive connector anonymously. Follow these steps to create an externally secured receive connector:
SharePoint https://docs.microsoft.com/en-us/SharePoint/SharePointServer/governance/co-authoring-overview https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/governance/co-authoring-overview.md
@@ -21,73 +21,71 @@ description: "Provides information about co-authoring and the permissions and so
**Audience**: IT Professionals
-Use the co-authoring feature in SharePoint Server to enable multiple users to work on a document, at any time, without interfering with each other's changes. Co-authoring removes barriers to server-based document collaboration and helps organizations to reduce the overhead associated with traditional document sharing through attachments. This functionality requires no additional server setup and is the default state for documents stored in SharePoint Server. Co-authoring functionality is managed by using the same tools and technologies that are already used to manage SharePoint, helping to minimize the impact on administrators.
+Co-authoring in SharePoint Server lets multiple users work on a document, at any time, without interfering with each other's changes. Co-authoring removes barriers to server-based document collaboration. This feature helps organizations avoid unintentional multiple versions of documents by reducing the need to share attachments. This feature requires no extra server setup and is the default state for documents stored in SharePoint Server. You manage co-authoring by using the same tools and technologies that are already used to manage SharePoint.
-Office provides co-authoring functionality for Word, PowerPoint, OneNote, and Visio. If you have SharePoint Server configured to use Office Web Apps Server, users can also co-author documents in Word, PowerPoint, Excel, and OneNote Web Apps.
+Office provides co-authoring functionality for Word, PowerPoint, OneNote, and Visio. If you have SharePoint Server configured to use Office Web Apps Server, users can also co-author documents in Word, PowerPoint, Excel, and OneNote Web Apps.
> [!IMPORTANT]
-> This article is for IT Professionals managing SharePoint Server. > **Are you looking for help with co-authoring?** You may be looking for [Document collaboration and co-authoring](https://go.microsoft.com/fwlink/p/?LinkId=275815), which will help you understand and use the co-authoring and versioning and applies to SharePoint in Microsoft 365.
+> This article is for IT Professionals managing SharePoint Server. **Are you looking for help with co-authoring?** You may be looking for [Document collaboration and co-authoring](https://go.microsoft.com/fwlink/p/?LinkId=275815), which will help you understand and use the co-authoring and versioning and applies to SharePoint in Microsoft 365.
## Co-authoring functionality in SharePoint Server <a name="bkmk_ca_in_sp"> </a> In traditional collaboration, documents are shared via email attachments. Tracking versions and edits from multiple authors is difficult and time-consuming for users. Email systems have to contend with storing multiple copies of the same document, not to mention increased network traffic as documents are sent repeatedly.
-The use of SharePoint to store documents for collaboration has reduced these problems by providing consistent access to up-to-date versions of documents, the ability to track earlier versions, and centralized management. Storing a single document, instead of many attachments, also reduces network and storage overhead.
+Storing documents for collaboration on SharePoint reduces these problems by: providing consistent access to up-to-date versions of documents, allowing users to track earlier versions, and centralizing management. Storing a single document, instead of many attachments, also reduces network and storage overhead.
-But this solution hasn't been perfect. When one author has a document open, other authors can't work on it. If someone forgets to close a document or check it in, other users may be locked out indefinitely, a situation that often requires a call to the IT department.
+But this solution hasn't been perfect. When one author has a document open, other authors can't work on it. Forgetting to close a document or check it in may lock out other users indefinitely, which can require help from the IT department to fix.
Co-authoring in SharePoint Server addresses these issues by making it possible for multiple users to work on a document, at any time, without interfering with each other's changes. This approach streamlines many common document-collaboration scenarios. For example: -- Two or more authors work on different parts of a composite document. While one author works on his section of the document, another author can work on hers, without either interrupting the other's work.
-
-- Several authors work on a composite slide show. Each author can add slides to the presentation and edit them, instead of working in isolation and trying to merge several documents and make them consistent all at the same time.
-
-- A document is sent out to several experts and stakeholders, each of whom provides some edits or additions. No user's edits are lost, because they are all working on a central, server-stored document.
-
+- Two or more authors work on different parts of a composite document. While one author works on part A of the document, another author can work on part B, without either interrupting the other's work.
+
+- Several authors work on a composite slide show. Each author adds slides to the presentation and edits them, instead of working on separate presentations and trying to merge them later.
+
+- A document is sent out to several experts and stakeholders, and each of them provides some edits or additions. No user's edits are lost, because they're all working on a central, server-stored document.
+ ## Understanding the end-user experience of co-authoring in SharePoint Server <a name="bkmk_understd"> </a>
-Co-authoring is easy to use from the end user's point of view. When a user wants to work on a document in Word, PowerPoint, OneNote, Visio or one of the Office Web Apps, he or she merely opens it from SharePoint Server, as usual. If another user already has the document open, both users can edit the document at the same time. One exception to this is that users can co-author in Excel Web App only if everyone uses the Excel Web App to access the workbook. If anyone uses Excel (the client application) to access the workbook, co-authoring in Excel Web App will be disabled for that workbook while it is open in the client application.
+Co-authoring is easy to use from the end user's point of view. When a user wants to work on a document in Word, PowerPoint, OneNote, Visio or one of the Office Web Apps, they open it from SharePoint Server, as usual. If another user already has the document open, both users can edit the document at the same time. One exception to this is that users can co-author in Excel Web App only if everyone uses the Excel Web App to access the workbook. If anyone uses Excel (the client application) to access the workbook, co-authoring in Excel Web App turns off for that workbook while it's open in the client application.
-When a user saves a Word, PowerPoint, or Word document, other current users are notified that there are new edits. Those users can refresh their views immediately to see the changes or continue their work and refresh later to see the latest edits. PowerPoint Web App, and Excel Web App auto-save so that users can view any changes automatically. The authors can see one another's work, and everyone knows who is working on the document. SharePoint Server versioning and tracking tools protect the document so that authors can roll back unwanted changes. When Skype for Business is available, users can see the online status of fellow co-authors and start instant messaging conversations without leaving the document.
+When a user saves a Word, PowerPoint, or Word document, other current users are notified that there are new edits. Those users can refresh their views immediately to see the changes or continue their work and refresh later to see the latest edits. PowerPoint Web App, and Excel Web App autosave so that users can view any changes automatically. The authors see one another's work, and everyone knows who is working on the document. SharePoint Server versioning and tracking tools protect the document so that authors can roll back unwanted changes. When Skype for Business is available, users see the online status of fellow co-authors and start instant messaging conversations without leaving the document.
-In OneNote and OneNote Web App, shared notebooks enable users to share notes seamlessly. When a user edits a page of the notebook, those edits are automatically synchronized with other users of that notebook so that everybody has a complete set of notes. Edits made by multiple users on the same page appear automatically, which enables near real-time collaboration. Versioning and other shared features in OneNote make it possible for users to roll back edits, show what edits are new, and determine who made a specific edit.
+In OneNote and OneNote Web App, shared notebooks allow users to share notes seamlessly. When a user edits a page of the notebook, those edits automatically synchronize with other users of that notebook so that everybody has a complete set of notes. Edits made by multiple users on the same page appear automatically for nearly real-time collaboration. Versioning and other shared features in OneNote let users roll back edits, show what edits are new, and determine who made a specific edit.
-The Excel client application does not support co-authoring workbooks in SharePoint Server. The Excel client application uses the Shared Workbook feature to support non-real-time co-authoring workbooks that are stored locally or on network (UNC) paths. Co-authoring workbooks in SharePoint is supported by using the Excel Web App.
+The Excel client application doesn't support co-authoring workbooks in SharePoint Server. The Excel client application uses the Shared Workbook feature to support non-real-time co-authoring workbooks that are stored locally or on network (UNC) paths. Co-authoring workbooks in SharePoint is supported by using the Excel Web App.
## Important planning considerations for co-authoring in SharePoint Server <a name="bkmk_imp_consid"> </a>
-There are several factors that administrators will want to consider when planning how to use co-authoring in their environment.
-
Co-authoring functionality in SharePoint is designed to be easy to set up and requires minimal effort to manage. But, there are several things to consider when you set up and manage co-authoring: -- **Permissions** - For multiple users to be able to edit the same document, users need edit permissions for the document library where that document is stored. The simplest way to guarantee that this is to give all users access to the SharePoint site where documents are stored. In cases in which only a subset of users should have permission to co-author documents in a particular library, SharePoint permissions can be used to manage access. For more information, see [Overview of site permissions in SharePoint Server](/sharepoint/sites/overview-of-site-permissions-in-sharepoint-server).
-
-- **Versioning** -SharePoint Server versioning keeps track of changes to documents while they are being edited, and even stores earlier versions for reference. By default, this feature is turned off in SharePoint Server. SharePoint Server supports two kinds of versioning, major and minor. It is best that minor versioning remain off for document libraries that are used for co-authoring in OneNote, because it may interfere with the synchronization and versioning capabilities that are part of the product. This limitation only applies to minor versioning. Major versioning may be used with OneNote. For more information, see [How does versioning work in a list or library?](https://go.microsoft.com/fwlink/p/?LinkId=275819).
-
-- **Number of versions** - The number of document versions retained affects storage requirements on the server. This number can be tuned in the document library settings to limit the number of versions retained. OneNote notebooks that are frequently updated may result in many versions being stored on the server. To avoid using unnecessary disk space, we recommend that an administrator set the maximum number of versions retained to a reasonable number on document libraries used to store OneNote notebooks. For more information, see [Enable and configure versioning for a list or library](https://go.microsoft.com/fwlink/p/?LinkId=275820)
-
-- **Versioning period** - The versioning period determines how often SharePoint Server will create a version of a Word or PowerPoint document that is being co-authored. Setting this period to a low value will capture versions more often, for more detailed version tracking, but may require more server storage. The versioning period does not affect OneNote notebooks. This value can be altered by adjusting the coAuthoringVersionPeriod property on the server. For more information about adjusting this setting, see [Configure the co-authoring versioning period in SharePoint Server](configure-the-co-authoring-versioning-period.md).
-
-- **Check out** - When a user checks out a document for editing, the document is locked for editing by that user. This prevents co-authoring. Do not enable the **Require Check Out** feature in document libraries in which co-authoring will be used. By default, **Require Check Out** is not enabled in SharePoint Server. Users should not check out documents manually when co-authoring is being used. For more information, see [Set up a library to require check-out of files](https://go.microsoft.com/fwlink/p/?LinkId=275822).
+- **Permissions** - Each user who wants to edit a document needs edit permissions for the document library where that document is stored. The simplest way to guarantee that is to give all users access to the SharePoint site where documents are stored. In cases where only a subset of users should have permission to co-author documents in a particular library, SharePoint permissions can be used to manage access. For more information, see [Overview of site permissions in SharePoint Server](/sharepoint/sites/overview-of-site-permissions-in-sharepoint-server).
+
+- **Versioning** - SharePoint Server versioning keeps track of changes to documents while they're being edited, and even stores earlier versions for reference. By default, this feature is turned off in SharePoint Server. SharePoint Server supports two kinds of versioning, major and minor. Minor versioning should remain off for document libraries that are used for co-authoring in OneNote, because it may interfere with OneNote's synchronization and versioning. This limitation only applies to minor versioning. Major versioning may be used with OneNote. For more information, see [How does versioning work in a list or library?](https://go.microsoft.com/fwlink/p/?LinkId=275819).
+
+- **Number of versions** - The number of document versions kept affects storage requirements on the server. Tune this number in the document library settings to limit the number of versions. Frequently updated OneNote notebooks can result in many versions being stored on the server. To avoid using unnecessary disk space, set the maximum number of versions to a reasonable number on document libraries used to store OneNote notebooks. For more information, see [Enable and configure versioning for a list or library](https://go.microsoft.com/fwlink/p/?LinkId=275820)
+
+- **Versioning period** - The versioning period determines how often SharePoint Server creates a version of a Word or PowerPoint document that is being co-authored. Setting this period to a low value captures versions more often, for more detailed version tracking, but may require more server storage. The versioning period doesn't affect OneNote notebooks. Adjust this value with the `coAuthoringVersionPeriod` property on the server. For more information about adjusting this setting, see [Configure the co-authoring versioning period in SharePoint Server](configure-the-co-authoring-versioning-period.md).
+
+- **Check out** - When a user checks out a document for editing, the document is locked for editing by that user. This feature prevents co-authoring. Don't enable the **Require Check Out** feature in document libraries in which co-authoring will be used. By default, **Require Check Out** isn't enabled in SharePoint Server. Users shouldn't check out documents manually when co-authoring is being used. For more information, see [Set up a library to require check-out of files](https://go.microsoft.com/fwlink/p/?LinkId=275822).
## Planning considerations for co-authoring in OneNote notebooks <a name="bkmk_onenote"> </a> Unlike Word and PowerPoint, OneNote stores version information within the file itself. For this reason, administrators should follow these recommended practices when storing OneNote notebooks in a SharePoint Server document library: -- Do not enable minor versioning. By default, minor versioning is not enabled in SharePoint Server.
-
-- Major versioning is enabled in SharePoint Server by default. Set a reasonable maximum number of versions to store.
+- Don't turn on minor versioning. By default, minor versioning is turned off in SharePoint Server.
+
+- Major versioning is turned on in SharePoint Server by default. Set a reasonable maximum number of versions to store.
## Performance and scalability considerations for co-authoring in SharePoint Server <a name="bkmk_perf"> </a>
-SharePoint Server and Office applications minimize the performance and scalability impact that is associated with co-authoring in your environment. Office clients do not send or download co-authoring information from the server until more than one author is editing. When a single user is editing a document, the performance impact resembles that of earlier versions of SharePoint.
+SharePoint Server and Office applications minimize the performance and scalability impact that is associated with co-authoring in your environment. Office clients don't send or download co-authoring information from the server until more than one author is editing. When a single user is editing a document, the performance impact resembles that of earlier versions of SharePoint.
-Office clients are configured to reduce server impact by reducing the frequency of synchronization actions that are related to co-authoring when the server is under heavy load, or when a user is not actively editing the document. This helps reduce overall performance impact.
+To reduce server impact, Office clients synchronize co-authoring actions less often when the server is under heavy load, or when users are not actively editing the document. This helps reduce overall performance impact.
## See also <a name="bkmk_perf"> </a>
SharePoint https://docs.microsoft.com/en-us/SharePoint/SharePointServer/governance/disable-co-authoring https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/governance/disable-co-authoring.md
@@ -19,56 +19,44 @@ description: "Learn how to disable co-authoring functionality in SharePoint Serv
[!INCLUDE[appliesto-2013-2016-2019-xxx-md](../includes/appliesto-2013-2016-2019-xxx-md.md)]
-Co-authoring in SharePoint Server makes it possible for multiple users to work on a document, at any time, without interfering with each other's changes. Although we have engineered co-authoring to be scalable and efficient, some organizations that have hardware limitations may want to turn off co-authoring to minimize any additional effects on server performance.
+Co-authoring in SharePoint Server allows multiple users to work on a document, at any time, without interfering with each other's changes. Although co-authoring is scalable and efficient, some organizations that have hardware limitations may want to turn off co-authoring to minimize effects on server performance.
-This article describes how to disable co-authoring functionality in SharePoint Server by using Group Policy or by using PowerShell.
-
-## Disable co-authoring in SharePoint Server
- There are three ways to disable co-authoring: - You can use Group Policy to disable co-authoring functionality on the client-side. For more information, see [Group Policy overview for Office 2013](/previous-versions/office/office-2013-resource-kit/cc179176(v=office.15)).
-
-- You can use Microsoft PowerShell to set the DisableCoauthoring server property. This disables the co-authoring property for Word and PowerPoint documents on the server. This property applies to documents or presentations that are authored in Word 2010, Word 2013, Word Online, PowerPoint 2010, PowerPoint 2013 and PowerPoint Web App.
-
-- You can enable the Require Check Out setting in a document library. This disables co-authoring in the document library. For more information, see [Configure Require Check Out in SharePoint Server 2013](configure-versioning-for-co-authoring.md#bkmk_req_co).
-
-Procedures in this task:
-- To disable co-authoring by using Group Policy
-
-- To disable co-authoring for Word documents and PowerPoint presentations at the web service level by using Windows PowerShell
-
-- To disable co-authoring for Word documents and PowerPoint presentations at the web application level by using Windows PowerShell
-
- **To disable co-authoring by using Group Policy**
+- You can use Microsoft PowerShell to set the DisableCoauthoring server property. This setting disables the co-authoring property for Word and PowerPoint documents on the server. This property applies to documents or presentations in Word 2010, Word 2013, Word Online, PowerPoint 2010, PowerPoint 2013, and PowerPoint Web App.
+
+- You can enable the Require Check Out setting in a document library. This setting disables co-authoring in the document library. For more information, see [Configure Require Check Out in SharePoint Server 2013](configure-versioning-for-co-authoring.md#bkmk_req_co).
+
+## Turn off co-authoring by using Group Policy
1. Start **Group Policy Management**.
-
+
2. In **Group Policy Management**, expand the Forest and Domain nodes for the domain where you want to set the policy, and then expand **Group Policy Objects**.
-
+
3. Choose (right-click) the Group Policy Object where your co-authoring settings are configured, and then choose **Edit**.
-
+
4. For Word 2013, expand **User Configuration**, **Administrative Templates**, **Microsoft Word 2013**, **Collaboration Settings**, **Co-authoring**, and then open (double-click) **Prevent Co-authoring**.
-
+
For PowerPoint 2013, expand **User Configuration**, **Administrative Templates**, **Microsoft PowerPoint 2013**, **Collaboration Settings**, **Co-authoring**, and then choose **Prevent Co-authoring**.
-
+
5. In the **Prevent Co-authoring Properties** dialog, select **Enabled**, and then choose **OK**.
-
- **To disable co-authoring for Word documents and PowerPoint presentations at the web service level by using Windows PowerShell (save as script and run script)**
+
+## Turn off co-authoring for Word documents and PowerPoint presentations at the web service level by using Windows PowerShell (save as script and run script)
1. Verify that you have the following memberships:
+
+ - **securityadmin** fixed server role on the SQL Server instance.
- - **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 PowerShell cmdlets.
+ - **db_owner** fixed database role on all databases that are to be updated.
- An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets.
+ - Administrators group on the server on which you're running 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 Permissions and [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps).
+ > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see Permissions and [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps).
2. Paste the following code into a text editor, such as Notepad:
@@ -85,10 +73,10 @@ Procedures in this task:
|:--|:--| | _servername_ <br/> |Server name <br/> |
-4. Save the file and add the .ps1 extension, such as SuggestedNameOfFile.ps1.
+4. Save the file and add the `.ps1` extension, such as SuggestedNameOfFile.ps1.
> [!NOTE]
- > You can use a different file name, but you must save the file as an ANSI-encoded text file whose extension is .ps1.
+ > You can use a different file name, but you must save the file as an ANSI-encoded text file whose extension is `.ps1.`
5. Start the SharePoint 2013 Management Shell as Administrator.
@@ -100,20 +88,20 @@ Procedures in this task:
./SuggestedFileName.ps1 ```
- **To disable co-authoring for Word documents and PowerPoint presentations at the web application level by using Windows PowerShell (save as script and run script)**
+## Turn off co-authoring for Word documents and PowerPoint presentations at the web application level by using Windows PowerShell (save as script and run script)
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 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 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 Permissions and [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps).
+ > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see Permissions and [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps).
2. Paste the following code into a text editor, such as Notepad:
@@ -126,20 +114,20 @@ Procedures in this task:
``` 3. Specify the following parameter:
-
+
|**Parameter**|**Value**| |:--|:--| | _servername_ <br/> |Server name <br/> |
-4. Save the file and add the .ps1 extension, such as SuggestedNameOfFile.ps1.
-
+4. Save the file and add the `.ps1` extension, such as SuggestedNameOfFile.ps1.
+
> [!NOTE]
- > You can use a different file name, but you must save the file as an ANSI-encoded text file whose extension is .ps1.
+ > You can use a different file name, but you must save the file as an ANSI-encoded text file whose extension is `.ps1.`
5. Start the SharePoint 2013 Management Shell as Administrator.
-
+
6. Change to the directory to which you saved the file.
-
+
7. At the PowerShell command prompt, type the following command: ```
SharePoint https://docs.microsoft.com/en-us/SharePoint/SharePointServer/install/new-onedrive-sync-client https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/install/new-onedrive-sync-client.md
@@ -21,6 +21,7 @@ description: "Learn how to configure the new OneDrive sync app (OneDrive.exe) fo
[!INCLUDE[appliesto-xxx-xxx-2019-xxx-md](../includes/appliesto-xxx-xxx-2019-xxx-md.md)] When you deploy SharePoint Server 2019 in your organization, your users can sync their OneDrive files as well as SharePoint team site files by using the new OneDrive sync app (OneDrive.exe) for Windows or Mac. Compared with the previous OneDrive sync app (Groove.exe), the new sync app provides:+ - Improved performance and reliability - Files On-Demand - Support for larger files
@@ -44,20 +45,22 @@ When you deploy SharePoint Server 2019 in your organization, your users can sync
### 1. Allow WNS Traffic
-For the best user experience, SharePoint Server 2019 will send change notifications to sync clients via WNS web push notifications. This feature ensures sync users quickly have the latest copies of any SharePoint Server file updates. You may need to take steps to ensure outbound requests from your SharePoint Server and your user's sync client computers can reach and properly interact with the WNS service.
+For the best user experience, SharePoint Server 2019 will send change notifications to sync apps via WNS web push notifications. This feature ensures sync users quickly have the latest copies of any SharePoint Server file updates. You may need to take steps to ensure outbound requests from your SharePoint Server and your users' computers can reach and properly interact with the WNS service.
For SharePoint Server:+ - Allow outbound HTTPS connection to reach \*.notify.windows.com
-For OneDrive Sync client computers:
+For computers running the OneDrive sync app:
+ - Allow outbound TLS encrypted TCP/IP socket connection to reach \*.wns.windows.com - Avoid HTTPS decryption for \*.wns.windows.com on your proxy server as this likely will disconnect the socket connection.
-If either the SharePoint Server or the OneDrive sync client is unable to communicate with the WNS service then the sync client will fall back to polling the SharePoint Server roughly every two minutes looking for changes. As a result, your users may see delays of more than two minutes from the time of a server change to when the sync client downloads the changed file.
+If either the SharePoint Server or the OneDrive sync app is unable to communicate with the WNS service, then the sync app will fall back to polling the SharePoint Server roughly every two minutes looking for changes. As a result, your users may see delays of more than two minutes from the time of a server change to when the sync app downloads a changed file.
-### 2. Opt-in to Sharing Improvement Information
+### 2. Opt in to Sharing Improvement Information
-When configuring the SharePoint server you have the option to enable sharing of improvement information with Microsoft. Enabling this opts connected sync clients into sending troubleshooting information. This allows the sync client team to proactively detect and correct problems, respond to customer reported problems, and improve the product over time. If this is disabled, customer escalations are harder to investigate and will require the customer to manually gather and provide logs from the impacted sync client machines.
+When configuring the SharePoint server, you can enable sharing of improvement information with Microsoft. Enabling this allows connected sync apps to send troubleshooting information. This allows the sync app team to proactively detect and correct problems, respond to customer reported problems, and improve the product over time. If this is disabled, customer escalations are harder to investigate and will require the customer to manually gather and provide logs from the impacted computers.
## Configure OneDrive for SharePoint Server 2019
@@ -115,18 +118,21 @@ Alternatively, you can also directly configure the following underlying registry
If your organization also uses the OneDrive sync app to sync files in Microsoft 365, here's what will be different for users who sync on-premises files. ### Single Top-level URL+ If you have deployed multiple on-premises SharePoint Server farms in your enterprise, on a given client computer, you will only specify a single "SharePointOnPremFrontDoorUrl". For a given user, you should configure their computer with the SharePoint Server URL that hosts their individual OneDrive site or if they don't have a OneDrive site, where the team sites they are most likely to sync are hosted. Your users will be able to start syncing team site content from any of your on-premises SharePoint Server farms by navigating to the web experience of the Team Site and clicking the Sync button on that site.
-For example, you have a SharePoint Server farm for your Finance department and another for the rest of your company. Users who are members of the Finance department have their individual OneDrive site hosted on the Finance department's SharePoint Server farm. For those Finance employees, you use your computer management system to set the SharePointOnPremFrontDoorUrl registry key policy on their computer to have your Finance specific farm's URL. For all other employees, you set the SharePointOnPremFrontDoorUrl to your other SharePoint Server farm URL. The sync client will look for and provision on-demand as needed, the user's OneDrive site on the appropriate SharePoint Server farm.
+For example, you have a SharePoint Server farm for your Finance department and another for the rest of your organization. Users who are members of the Finance department have their individual OneDrive site hosted on the Finance department's SharePoint Server farm. For those Finance employees, you use your computer management system to set the SharePointOnPremFrontDoorUrl registry key policy on their computer to have your Finance specific farm's URL. For all other employees, you set the SharePointOnPremFrontDoorUrl to your other SharePoint Server farm URL. The sync app will look for and provision the user's OneDrive on the appropriate SharePoint Server farm as needed.
### Folder names+ The OneDrive sync app creates the following folders on users' computers: OneDrive ΓÇô Contoso (for syncing personal My Site files) Contoso (for syncing SharePoint team site files)
-In SharePoint in Microsoft 365, "Contoso" is the tenant name that has been set for the SharePoint in Microsoft 365 instance. In SharePoint on-premises, there is no tenant name associated to the instance of SharePoint. You can set the this with the "Specify SharePoint Server URL and organization name" group policy, or the sync app will use the first segment of your SharePoint URL.
+In SharePoint in Microsoft 365, "Contoso" is the tenant name that has been set for the SharePoint in Microsoft 365 instance. In SharePoint on-premises, there is no tenant name associated to the instance of SharePoint. You can set this with the "Specify SharePoint Server URL and organization name" group policy, or the sync app will use the first segment of your SharePoint URL.
### File thumbnails and previews+ Thumbnails don't appear in File Explorer for files synced from SharePoint on-premises. If you enable Files On-Demand, and a file is online-only, a file preview won't be available. Image files and Office files will not have a thumbnail in File Explorer until the file is downloaded. ### Sharing from File Explorer
SharePoint https://docs.microsoft.com/en-us/SharePoint/SharePointServer/sites/onedrive-for-business-planning https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/sites/onedrive-for-business-planning.md
@@ -17,7 +17,7 @@
- IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: c033a091-2c08-4d20-8d3f-783317d718fa
-description: "Learn about things you need to consider when planning to setup OneDrive in a SharePoint Server on-premises environment."
+description: "Learn about things you need to consider when planning to set up OneDrive in a SharePoint Server on-premises environment."
# Plan for Microsoft OneDrive in SharePoint Server
@@ -57,7 +57,7 @@ In a SharePoint Server on-premises environment, you may have the option to save
The sync app also provides your users the added convenience of working with files directly from the local OneDrive sync folder. Work with and saving your files directly in the folder is more convenient than opening your My Sites document library. > [!IMPORTANT]
-> Use the [OneDrive sync app for Groove.exe](https://support.microsoft.com/kb/2903984) when using OneDrive in a SharePoint Server on-premises environment. The OneDrive Next Generation sync app (OneDrive.exe) is currently not supported to work in a SharePoint Server on-premises environment.
+> Use the [previous OneDrive for Business sync app (Groove.exe)](/onedrive/install-previous-sync-app.md) to sync files in SharePoint Server 2016 or earlier. The new OneDrive sync app (OneDrive.exe) is supported only in SharePoint Server 2019. [Configure the OneDrive sync app for SharePoint Server 2019](/SharePoint/install/new-onedrive-sync-client.md)
**Changes in file location**
SharePoint https://docs.microsoft.com/en-us/SharePoint/SharePointServer/what-s-new/what-s-deprecated-or-removed-from-SharePoint-Server-2019 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/what-s-new/what-s-deprecated-or-removed-from-SharePoint-Server-2019.md
@@ -58,11 +58,11 @@ The aggregated newsfeed feature (available at newsfeed.aspx and typically access
To ensure that users receive highly relevant help content, we are moving from away from our legacy on-premises SharePoint help engine, which is based on help collections being installed in the on-prem farm. The new SharePoint help system is now rendered in the cloud and will have updated, synchronized content with Microsoft 365. Custom help based on the legacy SharePoint help engine will remain supported, but deprecated, for the SharePoint Server 2019 release.
-### Groove Sync App
+### Groove.exe (Previous OneDrive for Business sync app)
-The Groove sync app is our app for syncing documents between your personal devices and SharePoint Server 2010, 2013, and 2016 Team sites. SharePoint Server 2019 introduces support for the new OneDrive Sync app (a.k.a. the Next Generation Sync Client), which provides a more reliable and feature-rich syncing experience. If Groove detects that your existing sync relationships are to a site that has been upgraded to SharePoint Server 2019, it will attempt to migrate those sync relationships to the OneDrive sync app. Administrators can control this migration experience.
+The previous OneDrive for Business sync app (Groove.exe) was used for syncing files in SharePoint Server 2010, 2013, and 2016. SharePoint Server 2019 introduces support for the new OneDrive sync app (OneDrive.exe), which provides a more reliable and feature-rich syncing experience. If a user's existing sync relationships are to a site that has been upgraded to SharePoint Server 2019, the new OneDrive sync app will attempt to take over syncing. Administrators can control this transition experience.
-The Groove sync app will remain supported, but deprecated, for the SharePoint Server 2019 release.
+The previous OneDrive sync app will remain supported, but deprecated, for the SharePoint Server 2019 release.
### InfoPath Services
@@ -88,7 +88,7 @@ The Variations will remain supported but deprecated for the SharePoint Server 20
### PerformancePoint Services
-PerformancePoint Services has a significant dependency on Microsoft Silverlight, which is a technology that will no longer be supported as of October 12, 2021. PerformancePoint Services will remain supported, but deprecated, for the SharePoint Server 2019 release. Customers are recommended to explore Microsoft [PowerBI](https://powerbi.microsoft.com/) as an alternative to PerformancePoint Services as we are making many new business intelligence investments in PowerBI.
+PerformancePoint Services has a significant dependency on Microsoft Silverlight, which is a technology that will no longer be supported as of October 12, 2021. PerformancePoint Services will remain supported, but deprecated, for the SharePoint Server 2019 release. Customers are recommended to explore Microsoft [Power BI](https://powerbi.microsoft.com/) as an alternative to PerformancePoint Services as we are making many new business intelligence investments in Power BI.
### SharePoint Designer
@@ -130,7 +130,7 @@ SharePoint Server 2019 Preview included a built-in PDF viewer which allowed Shar
### PowerPivot Gallery and Refresh
-Since the feature was first introduced in SharePoint, Microsoft BI strategy has shifted away from heavy integration to a standalone BI solution, Power BI, to give customers a flexible, optional integration with SharePoint along with standalone capabilities. Both [PowerBI.com](https://powerbi.com/) and [Power BI Report Server](https://powerbi.microsoft.com/report-server/) offer the option to host and view Excel Workbooks with PowerPivot models today and is the preferred method for customers going forward to host and use their Excel Workbooks with PowerPivot models, or simply to migrate to PBIX files using the migration option in Power BI Desktop for Excel Workbooks.
+Since the feature was first introduced in SharePoint, Microsoft BI strategy has shifted away from heavy integration to a standalone BI solution, Power BI, to give customers a flexible, optional integration with SharePoint along with standalone capabilities. Both [Power BI.com](https://powerbi.com/) and [Power BI Report Server](https://powerbi.microsoft.com/report-server/) offer the option to host and view Excel Workbooks with PowerPivot models today and is the preferred method for customers going forward to host and use their Excel Workbooks with PowerPivot models, or simply to migrate to PBIX files using the migration option in Power BI Desktop for Excel Workbooks.
### SharePoint Workflow Manager (SharePoint Server 2019 Preview)