diff --git a/mdop/appv-v5/TOC.md b/mdop/appv-v5/TOC.md
index 2836e9c7ab..db147e8a98 100644
--- a/mdop/appv-v5/TOC.md
+++ b/mdop/appv-v5/TOC.md
@@ -40,6 +40,7 @@
##### [About App-V 5.1 Reporting](about-app-v-51-reporting.md)
##### [How to install the Reporting Server on a Standalone Computer and Connect it to the Database 5.1](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database51.md)
#### [App-V 5.1 Deployment Checklist](app-v-51-deployment-checklist.md)
+#### [Deploying Microsoft Office 2016 by Using App-V 5.1](deploying-microsoft-office-2016-by-using-app-v51.md)
#### [Deploying Microsoft Office 2013 by Using App-V 5.1](deploying-microsoft-office-2013-by-using-app-v51.md)
#### [Deploying Microsoft Office 2010 by Using App-V 5.1](deploying-microsoft-office-2010-by-using-app-v51.md)
### [Operations for App-V 5.1](operations-for-app-v-51.md)
@@ -155,6 +156,7 @@
##### [About App-V 5.0 Reporting](about-app-v-50-reporting.md)
##### [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database.md)
#### [App-V 5.0 Deployment Checklist](app-v-50-deployment-checklist.md)
+#### [Deploying Microsoft Office 2016 by Using App-V](deploying-microsoft-office-2016-by-using-app-v.md)
#### [Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md)
#### [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md)
### [Operations for App-V 5.0](operations-for-app-v-50.md)
diff --git a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v.md b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v.md
new file mode 100644
index 0000000000..326877092e
--- /dev/null
+++ b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v.md
@@ -0,0 +1,876 @@
+---
+title: Deploying Microsoft Office 2016 by Using App-V
+description: Deploying Microsoft Office 2016 by Using App-V
+author: jamiejdt
+ms.assetid: cc675cde-cb8d-4b7c-a700-6104b78f1d89
+ms.pagetype: mdop, appcompat, virtualization
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.prod: w10
+---
+
+
+# Deploying Microsoft Office 2016 by Using App-V
+
+
+Use the information in this article to use Microsoft Application Virtualization 5.0, or later versions, to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md). For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md).
+
+This topic contains the following sections:
+
+- [What to know before you start](#bkmk-before-you-start)
+
+- [Creating an Office 2016 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
+
+- [Publishing the Office package for App-V 5.0](#bkmk-pub-pkg-office)
+
+- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
+
+##
What to know before you start
+
+
+Before you deploy Office 2016 by using App-V, review the following planning information.
+
+###
Supported Office versions and Office coexistence
+
+Use the following table to get information about supported versions of Office and about running coexisting versions of Office.
+
+
+
+
+
+
+
+
+
+
+
+[Supported versions of Microsoft Office](planning-for-using-app-v-with-office.md#bkmk-office-vers-supp-appv) |
+
+Supported versions of Office Supported deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), pooled VDI) Office licensing options |
+
+
+[Planning for Using App-V with coexsiting versions of Office](planning-for-using-app-v-with-office.md#bkmk-plan-coexisting) |
+Considerations for installing different versions of Office on the same computer |
+
+
+
+
+
+
+###
Packaging, publishing, and deployment requirements
+
+Before you deploy Office by using App-V, review the following requirements.
+
+
+
+
+
+
+
+
+
+
+
+Packaging |
+
+All of the Office applications that you want to deploy to users must be in a single package. In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer. If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project). |
+
+
+Publishing |
+ |
+
+
+Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services:
+ |
+You must enable [shared computer activation](http://technet.microsoft.com/library/dn782860.aspx).
+You don’t use shared computer activation if you’re deploying a volume licensed product, such as:
+ |
+
+
+
+
+
+
+### Excluding Office applications from a package
+
+The following table describes the recommended methods for excluding specific Office applications from a package.
+
+
+
+
+
+
+
+
+
+
+
+Use the ExcludeApp setting when you create the package by using the Office Deployment Tool. |
+
+Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word. For more information, see [ExcludeApp element](http://technet.microsoft.com/library/jj219426.aspx#bkmk-excludeappelement). |
+
+
+Modify the DeploymentConfig.xml file |
+
+Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client. For more information, see [Disabling Office 2016 applications](#bkmk-disable-office-apps). |
+
+
+
+
+
+
+##
Creating an Office 2016 package for App-V with the Office Deployment Tool
+
+
+Complete the following steps to create an Office 2016 package for App-V 5.0 or later.
+
+**Important**
+In App-V 5.0 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
+
+
+### Review prerequisites for using the Office Deployment Tool
+
+The computer on which you are installing the Office Deployment Tool must have:
+
+
+
+
+
+
+
+
+
+
+
+Prerequisite software |
+.Net Framework 4 |
+
+
+Supported operating systems |
+
+64-bit version of Windows 10 64-bit version of Windows 8 or 8.1 64-bit version of Windows 7 |
+
+
+
+
+
+**Note**
+In this topic, the term “Office 2016 App-V package” refers to subscription licensing and volume licensing.
+
+
+### Create Office 2016 App-V Packages Using Office Deployment Tool
+
+You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with Volume Licensing or Subscription Licensing.
+
+Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
+
+### Download the Office Deployment Tool
+
+Office 2016 App-V Packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
+
+1. Download the [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
+
+2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
+
+ Example: \\\\Server\\Office2016
+
+3. Check that a setup.exe and a configuration.xml file exist and are in the location you specified.
+
+### Download Office 2016 applications
+
+After you download the Office Deployment Tool, you can use it to get the latest Office 2016 applications. After getting the Office applications, you create the Office 2016 App-V package.
+
+The XML file that is included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
+
+1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
+
+ 1. Open the sample XML file in Notepad or your favorite text editor.
+
+ 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the configuration.xml file:
+
+ ``` syntax
+
+
+
+
+
+
+
+
+
+
+ ```
+
+ **Note**
+ The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To “uncomment” these lines, remove the "" from the end of the line.
+
+ The above XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2016, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2016 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
+
+
+
+
+
+
+
+
+
+
+
+
+ Add element |
+ Specifies the products and languages to include in the package. |
+ N/A |
+
+
+ OfficeClientEdition (attribute of Add element) |
+ Specifies the edition of Office 2016 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value. |
+ OfficeClientEdition="32"
+ OfficeClientEdition="64" |
+
+
+ Product element |
+ Specifies the application. Project 2016 and Visio 2016 must be specified here as an added product to be included in the applications. |
+ Product ID ="O365ProPlusRetail "
+ Product ID ="VisioProRetail"
+ Product ID ="ProjectProRetail"
+ Product ID ="ProPlusVolume"
+ Product ID ="VisioProVolume"
+ Product ID = "ProjectProVolume"
|
+
+
+ Language element |
+ Specifies the language supported in the applications |
+ Language ID="en-us"
|
+
+
+ Version (attribute of Add element) |
+ Optional. Specifies a build to use for the package
+ Defaults to latest advertised build (as defined in v32.CAB at the Office source). |
+ 15.1.2.3
|
+
+
+ SourcePath (attribute of Add element) |
+ Specifies the location in which the applications will be saved to. |
+ Sourcepath = "\\Server\Office2016”
|
+
+
+ Branch (attribute of Add element) |
+ Optional. Specifies the update branch for the product that you want to download or install. For more information about update branches, see Overview of update branches for Office 365 ProPlus. |
+ Branch = "Business"
|
+
+
+
+
+ After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2016 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
+
+2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2016 applications that will later be converted into an App-V package. Below is an example command with description of details:
+
+ ``` syntax
+ \\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml
+ ```
+
+ In the example:
+
+
+
+
+
+
+
+
+ \\server\Office2016 |
+ is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml. |
+
+
+ Setup.exe |
+ is the Office Deployment Tool. |
+
+
+ /download |
+ downloads the Office 2016 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2016 App-V package with Volume Licensing. |
+
+
+ \\server\Office2016\Customconfig.xml |
+ passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \\Server\Office2016. |
+
+
+
+
+
+
+### Convert the Office applications into an App-V package
+
+After you download the Office 2016 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2016 App-V package. Complete the steps that correspond to your licensing model.
+
+**Summary of what you’ll need to do:**
+
+- Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10 computers.
+
+- Create an Office App-V package for either Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
+
+ The following table summarizes the values you need to enter in the CustomConfig.xml file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
+
+
+
+
+
+
+
+
+
+
+
+
+Office 2016 |
+ProPlusVolume |
+O365ProPlusRetail |
+
+
+Office 2016 with Visio 2016 |
+ProPlusVolume
+VisioProVolume |
+O365ProPlusRetail
+VisioProRetail |
+
+
+Office 2016 with Visio 2016 and Project 2016 |
+ProPlusVolume
+VisioProVolume
+ProjectProVolume |
+O365ProPlusRetail
+VisioProRetail
+ProjectProRetail |
+
+
+
+
+
+
+**How to convert the Office applications into an App-V package**
+
+1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
+
+
+
+
+
+
+
+
+
+
+
+ SourcePath |
+ Point to the Office applications downloaded earlier. |
+
+
+ ProductID |
+ Specify the type of licensing, as shown in the following examples:
+
+ Subscription Licensing
+ <Configuration>
+ <Add SourcePath= "\\server\Office 2016" OfficeClientEdition="32" >
+ <Product ID="O365ProPlusRetail">
+ <Language ID="en-us" />
+ </Product>
+ <Product ID="VisioProRetail">
+ <Language ID="en-us" />
+ </Product>
+ </Add>
+ </Configuration>
+ In this example, the following changes were made to create a package with Subscription licensing:
+
+
+
+
+
+
+
+ SourcePath |
+ is the path, which was changed to point to the Office applications that were downloaded earlier. |
+
+
+ Product ID |
+ for Office was changed to O365ProPlusRetail. |
+
+
+ Product ID |
+ for Visio was changed to VisioProRetail. |
+
+
+
+
+ Volume Licensing
+ <Configuration>
+ <Add SourcePath= "\\Server\Office2016" OfficeClientEdition="32" >
+ <Product ID="ProPlusVolume">
+ <Language ID="en-us" />
+ </Product>
+ <Product ID="VisioProVolume">
+ <Language ID="en-us" />
+ </Product>
+ </Add>
+ </Configuration>
+ In this example, the following changes were made to create a package with Volume licensing:
+
+
+
+
+
+
+
+ SourcePath |
+ is the path, which was changed to point to the Office applications that were downloaded earlier. |
+
+
+ Product ID |
+ for Office was changed to ProPlusVolume. |
+
+
+ Product ID |
+ for Visio was changed to VisioProVolume. |
+
+
+
+
+ |
+
+
+ ExcludeApp (optional) |
+ Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath. |
+
+
+ PACKAGEGUID (optional) |
+ By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
+ An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
+
+ Note
+ Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
+
+
+ |
+
+
+
+
+
+
+2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
+
+ For example:
+
+ ``` syntax
+ \\server\Office2016\setup.exe /packager \\server\Office2016\Customconfig.xml \\server\share\Office2016AppV
+ ```
+
+ In the example:
+
+
+
+
+
+
+
+
+ \\server\Office2016 |
+ is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml. |
+
+
+ Setup.exe |
+ is the Office Deployment Tool. |
+
+
+ /packager |
+ creates the Office 2016 App-V package with Volume Licensing as specified in the customConfig.xml file. |
+
+
+ \\server\Office2016\Customconfig.xml |
+ passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage. |
+
+
+ \\server\share\Office 2016AppV |
+ specifies the location of the newly created Office App-V package. |
+
+
+
+
+
+
+ After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
+
+ - **App-V Packages** – contains an Office 2016 App-V package and two deployment configuration files.
+
+ - **WorkingDir**
+
+ **Note**
+ To troubleshoot any issues, see the log files in the %temp% directory (default).
+
+
+
+3. Verify that the Office 2016 App-V package works correctly:
+
+ 1. Publish the Office 2016 App-V package, which you created globally, to a test computer, and verify that the Office 2016 shortcuts appear.
+
+ 2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
+
+##
Publishing the Office package for App-V 5.0
+
+
+Use the following information to publish an Office package.
+
+### Methods for publishing Office App-V packages
+
+Deploy the App-V package for Office 2016 by using the same methods you use for any other package:
+
+- System Center Configuration Manager
+
+- App-V Server
+
+- Stand-alone through PowerShell commands
+
+### Publishing prerequisites and requirements
+
+
+
+
+
+
+
+
+
+
+
+Enable PowerShell scripting on the App-V clients |
+To publish Office 2016 packages, you must run a script.
+Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:
+Set-AppvClientConfiguration –EnablePackageScripts 1
|
+
+
+Publish the Office 2016 package globally |
+Extension points in the Office App-V package require installation at the computer level.
+When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2016 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages. |
+
+
+
+
+
+
+### How to publish an Office package
+
+Run the following command to publish an Office package globally:
+
+- `Add-AppvClientPackage
| Publish-AppvClientPackage –global`
+
+- From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
+
+## Customizing and managing Office App-V packages
+
+
+To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
+
+- [Enabling Office plug-ins by using connection groups](#bkmk-enable-office-plugins)
+
+- [Disabling Office 2016 applications](#bkmk-disable-office-apps)
+
+- [Disabling Office 2016 shortcuts](#bkmk-disable-shortcuts)
+
+- [Managing Office 2016 package upgrades](#bkmk-manage-office-pkg-upgrd)
+
+- [Managing Office 2016 licensing upgrades](#bkmk-manage-office-lic-upgrd)
+
+- [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project)
+
+### Enabling Office plug-ins by using connection groups
+
+Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You cannot use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
+
+**To enable plug-ins for Office App-V packages**
+
+1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
+
+2. Sequence your plug-ins using the App-V 5.0 Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
+
+3. Create an App-V 5.0 package that includes the desired plug-ins.
+
+4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
+
+5. Add the Office 2016 App-V package and the plug-ins package you sequenced to the Connection Group you created.
+
+ **Important**
+ The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2016 App-V package first, and then add the plug-in App-V package.
+
+
+
+6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2016 App-V package.
+
+7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2016 App-V package has.
+
+ Since the Office 2016 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2016 App-V package you published.
+
+8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
+
+9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
+
+10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2016 App-V package is in use when the Connection Group is enabled. If that happens, you have to reboot to successfully enable the Connection Group.
+
+11. After you successfully publish both packages and enable the Connection Group, start the target Office 2016 application and verify that the plug-in you published and added to the connection group works as expected.
+
+### Disabling Office 2016 applications
+
+You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, you will save the changes, add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
+
+**Note**
+To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
+
+
+**To disable an Office 2016 application**
+
+1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
+
+2. Search for the Office application you want to disable, for example, Access 2016.
+
+3. Change the value of "Enabled" from "true" to "false."
+
+4. Save the Deployment Configuration File.
+
+5. Add the Office 2016 App-V Package with the new Deployment Configuration File.
+
+ ``` syntax
+
+
+ Lync 2016
+
+
+
+
+
+
+ Access 2016
+
+
+
+
+ ```
+
+6. Re-add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
+
+### Disabling Office 2016 shortcuts
+
+You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
+
+**To disable shortcuts for Office 2016 applications**
+
+1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
+
+2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
+
+ ``` syntax
+ Shortcuts
+
+ -->
+
+
+
+
+ [{Common Programs}]\Microsoft Office 2016\Access 2016.lnk
+ [{AppvPackageRoot}])office16\MSACCESS.EXE
+ [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
+
+
+ Microsoft.Office.MSACCESS.EXE.15
+ true
+ Build a professional app quickly to manage data.
+ l
+ [{AppVPackageRoot}]\officel6\MSACCESS.EXE
+
+ ```
+
+3. Save the Deployment Configuration File.
+
+4. Republish Office 2016 App-V Package with new Deployment Configuration File.
+
+Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
+
+### Managing Office 2016 package upgrades
+
+To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2016 package, perform the following steps.
+
+**How to upgrade a previously deployed Office 2016 package**
+
+1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
+
+ **Note**
+ Office App-V packages have two Version IDs:
+
+ - An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
+
+ - A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
+
+
+
+2. Globally publish the newly created Office 2016 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2016 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
+
+3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
+
+### Managing Office 2016 licensing upgrades
+
+If a new Office 2016 App-V Package has a different license than the Office 2016 App-V Package currently deployed. For instance, the Office 2016 package deployed is a subscription based Office 2016 and the new Office 2016 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
+
+**How to upgrade an Office 2016 License**
+
+1. Unpublish the already deployed Office 2016 Subscription Licensing App-V package.
+
+2. Remove the unpublished Office 2016 Subscription Licensing App-V package.
+
+3. Restart the computer.
+
+4. Add the new Office 2016 App-V Package Volume Licensing.
+
+5. Publish the added Office 2016 App-V Package with Volume Licensing.
+
+An Office 2016 App-V Package with your chosen licensing will be successfully deployed.
+
+### Deploying Visio 2016 and Project 2016 with Office
+
+The following table describes the requirements and options for deploying Visio 2016 and Project 2016 with Office.
+
+
+
+
+
+
+
+
+
+
+
+How do I package and publish Visio 2016 and Project 2016 with Office? |
+You must include Visio 2016 and Project 2016 in the same package with Office.
+If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow [Deploying Microsoft Office 2010 by Using App-V](../appv-v5/deploying-microsoft-office-2010-by-using-app-v.md). |
+
+
+How can I deploy Visio 2016 and Project 2016 to specific users? |
+Use one of the following methods:
+
+
+
+
+
+
+
+
+
+
+Create two different packages and deploy each one to a different group of users |
+Create and deploy the following packages:
+
+A package that contains only Office - deploy to computers whose users need only Office. A package that contains Office, Visio, and Project - deploy to computers whose users need all three applications. |
+
+
+If you want only one package for the whole organization, or if you have users who share computers: |
+Follows these steps:
+
+Create a package that contains Office, Visio, and Project. Deploy the package to all users. Use [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project. |
+
+
+
+ |
+
+
+
+
+
+
+## Additional resources
+
+
+**Office 2016 App-V 5.0 Packages 5.0 Additional Resources**
+
+[Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
+
+[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
+
+**Office 2013 and Office 2010 App-V Packages**
+
+[Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md)
+
+[Deploying Microsoft Office 2011 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md)
+
+**Connection Groups**
+
+[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
+
+[Managing Connection Groups](managing-connection-groups.md)
+
+**Dynamic Configuration**
+
+[About App-V 5.0 Dynamic Configuration](about-app-v-50-dynamic-configuration.md)
+
+## Got a suggestion for App-V?
+
+
+Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
diff --git a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md
new file mode 100644
index 0000000000..efb700aace
--- /dev/null
+++ b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md
@@ -0,0 +1,884 @@
+---
+title: Deploying Microsoft Office 2016 by Using App-V
+description: Deploying Microsoft Office 2016 by Using App-V
+author: jamiejdt
+ms.assetid: e0f4876-da99-4b89-977e-2fb6e89ea3d3
+ms.pagetype: mdop, appcompat, virtualization
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.prod: w10
+---
+
+
+# Deploying Microsoft Office 2016 by Using App-V
+
+
+Use the information in this article to use Microsoft Application Virtualization (App-V) 5.1, or later versions, to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see [Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v51.md). For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v51.md).
+
+This topic contains the following sections:
+
+- [What to know before you start](#bkmk-before-you-start)
+
+- [Creating an Office 2016 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
+
+- [Publishing the Office package for App-V 5.1](#bkmk-pub-pkg-office)
+
+- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
+
+## What to know before you start
+
+
+Before you deploy Office 2016 by using App-V, review the following planning information.
+
+### Supported Office versions and Office coexistence
+
+Use the following table to get information about supported versions of Office and about running coexisting versions of Office.
+
+
+
+
+
+
+
+
+
+
+
+[Planning for Using App-V with Office](planning-for-using-app-v-with-office51.md#bkmk-office-vers-supp-appv) |
+
+Supported versions of Office Supported deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), pooled VDI) Office licensing options |
+
+
+[Planning for Using App-V with Office](planning-for-using-app-v-with-office51.md#bkmk-plan-coexisting) |
+Considerations for installing different versions of Office on the same computer |
+
+
+
+
+
+### Packaging, publishing, and deployment requirements
+
+Before you deploy Office by using App-V, review the following requirements.
+
+
+
+
+
+
+
+
+
+
+
+Packaging |
+
+All of the Office applications that you want to deploy to users must be in a single package. In App-V 5.1 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer. If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project). |
+
+
+Publishing |
+ |
+
+
+Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services:
+ |
+You must enable [shared computer activation](http://technet.microsoft.com/library/dn782860.aspx).
+You don’t use shared computer activation if you’re deploying a volume licensed product, such as:
+ |
+
+
+
+
+
+
+### Excluding Office applications from a package
+
+The following table describes the recommended methods for excluding specific Office applications from a package.
+
+
+
+
+
+
+
+
+
+
+
+Use the ExcludeApp setting when you create the package by using the Office Deployment Tool. |
+
+Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word. For more information, see [ExcludeApp element](http://technet.microsoft.com/library/jj219426.aspx#bkmk-excludeappelement). |
+
+
+Modify the DeploymentConfig.xml file |
+
+Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client. For more information, see [Disabling Office 2016 applications](#bkmk-disable-office-apps). |
+
+
+
+
+
+
+## Creating an Office 2016 package for App-V with the Office Deployment Tool
+
+
+Complete the following steps to create an Office 2016 package for App-V 5.1 or later.
+
+**Important**
+In App-V 5.1 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
+
+
+
+### Review prerequisites for using the Office Deployment Tool
+
+The computer on which you are installing the Office Deployment Tool must have:
+
+
+
+
+
+
+
+
+
+
+
+Prerequisite software |
+.Net Framework 4 |
+
+
+Supported operating systems |
+
+64-bit version of Windows 10 64-bit version of Windows 8 or later 64-bit version of Windows 7 |
+
+
+
+
+
+
+**Note**
+In this topic, the term “Office 2016 App-V package” refers to subscription licensing and volume licensing.
+
+
+
+### Create Office 2013 App-V Packages Using Office Deployment Tool
+
+You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with Volume Licensing or Subscription Licensing.
+
+Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
+
+### Download the Office Deployment Tool
+
+Office 2016 App-V Packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
+
+1. Download the [Office 2-16 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
+
+ > [!NOTE]
+ > You must use the Office 2016 Deployment Tool to create Office 2016 App-V Packages.
+
+2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
+
+ Example: \\\\Server\\Office2016
+
+3. Check that a setup.exe and a configuration.xml file exist and are in the location you specified.
+
+### Download Office 2016 applications
+
+After you download the Office Deployment Tool, you can use it to get the latest Office 2016 applications. After getting the Office applications, you create the Office 2016 App-V package.
+
+The XML file that is included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
+
+1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
+
+ 1. Open the sample XML file in Notepad or your favorite text editor.
+
+ 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the configuration.xml file:
+
+ ``` syntax
+
+
+
+
+
+
+
+
+
+
+ ```
+
+ **Note**
+ The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To “uncomment” these lines, remove the "" from the end of the line.
+
+
+
+ The above XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office2016, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2016 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
+
+
+
+
+
+
+
+
+
+
+
+
+ Add element |
+ Specifies the products and languages to include in the package. |
+ N/A |
+
+
+ OfficeClientEdition (attribute of Add element) |
+ Specifies the edition of Office 2016 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value. |
+ OfficeClientEdition="32"
+ OfficeClientEdition="64" |
+
+
+ Product element |
+ Specifies the application. Project 2016 and Visio 2016 must be specified here as an added product to be included in the applications. |
+ Product ID ="O365ProPlusRetail"
+ Product ID ="VisioProRetail"
+ Product ID ="ProjectProRetail"
+ Product ID ="ProPlusVolume"
+ Product ID ="VisioProVolume"
+ Product ID = "ProjectProVolume"
|
+
+
+ Language element |
+ Specifies the language supported in the applications |
+ Language ID="en-us"
|
+
+
+ Version (attribute of Add element) |
+ Optional. Specifies a build to use for the package
+ Defaults to latest advertised build (as defined in v32.CAB at the Office source). |
+ 16.1.2.3
|
+
+
+ SourcePath (attribute of Add element) |
+ Specifies the location in which the applications will be saved to. |
+ Sourcepath = "\\Server\Office2016"
|
+
+
+ Branch (attribute of Add element) |
+ Optional. Specifies the update branch for the product that you want to download or install. For more information about update branches, see Overview of update branches for Office 365 ProPlus. |
+ Branch = "Business"
|
+
+
+
+
+
+
+ After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2016 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
+
+2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2016 applications that will later be converted into an App-V package. Below is an example command with description of details:
+
+ ``` syntax
+ \\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml
+ ```
+
+ In the example:
+
+
+
+
+
+
+
+
+ \\server\Office2016 |
+ is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml. |
+
+
+ Setup.exe |
+ is the Office Deployment Tool. |
+
+
+ /download |
+ downloads the Office 2016 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2016 App-V package with Volume Licensing. |
+
+
+ \\server\Office2016\Customconfig.xml |
+ passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \\Server\Office2016. |
+
+
+
+
+
+
+### Convert the Office applications into an App-V package
+
+After you download the Office 2016 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2016 App-V package. Complete the steps that correspond to your licensing model.
+
+**Summary of what you’ll need to do:**
+
+- Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10 computers.
+
+- Create an Office App-V package for either Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
+
+ The following table summarizes the values you need to enter in the CustomConfig.xml file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
+
+
+
+
+
+
+
+
+
+
+
+
+Office 2016 |
+ProPlusVolume |
+O365ProPlusRetail |
+
+
+Office 2016 with Visio 2016 |
+ProPlusVolume
+VisioProVolume |
+O365ProPlusRetail
+VisioProRetail |
+
+
+Office 2016 with Visio 2016 and Project 2016 |
+ProPlusVolume
+VisioProVolume
+ProjectProVolume |
+O365ProPlusRetail
+VisioProRetail
+ProjectProRetail |
+
+
+
+
+
+
+**How to convert the Office applications into an App-V package**
+
+1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
+
+
+
+
+
+
+
+
+
+
+
+ SourcePath |
+ Point to the Office applications downloaded earlier. |
+
+
+ ProductID |
+ Specify the type of licensing, as shown in the following examples:
+
+ Subscription Licensing
+ <Configuration>
+ <Add SourcePath= "\\server\Office 2016" OfficeClientEdition="32" >
+ <Product ID="O365ProPlusRetail">
+ <Language ID="en-us" />
+ </Product>
+ <Product ID="VisioProRetail">
+ <Language ID="en-us" />
+ </Product>
+ </Add>
+ </Configuration>
+ In this example, the following changes were made to create a package with Subscription licensing:
+
+
+
+
+
+
+
+ SourcePath |
+ is the path, which was changed to point to the Office applications that were downloaded earlier. |
+
+
+ Product ID |
+ for Office was changed to O365ProPlusRetail. |
+
+
+ Product ID |
+ for Visio was changed to VisioProRetail. |
+
+
+
+
+ Volume Licensing
+ <Configuration>
+ <Add SourcePath= "\\Server\Office2016" OfficeClientEdition="32" >
+ <Product ID="ProPlusVolume">
+ <Language ID="en-us" />
+ </Product>
+ <Product ID="VisioProVolume">
+ <Language ID="en-us" />
+ </Product>
+ </Add>
+ </Configuration>
+ In this example, the following changes were made to create a package with Volume licensing:
+
+
+
+
+
+
+
+ SourcePath |
+ is the path, which was changed to point to the Office applications that were downloaded earlier. |
+
+
+ Product ID |
+ for Office was changed to ProPlusVolume. |
+
+
+ Product ID |
+ for Visio was changed to VisioProVolume. |
+
+
+
+
+ |
+
+
+ ExcludeApp (optional) |
+ Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access. |
+
+
+ PACKAGEGUID (optional) |
+ By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
+ An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
+
+ Note
+ Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
+
+
+ |
+
+
+
+
+
+
+2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
+
+ For example:
+
+ ``` syntax
+ \\server\Office2016\setup.exe /packager \\server\Office2016\Customconfig.xml \\server\share\Office2016AppV
+ ```
+
+ In the example:
+
+
+
+
+
+
+
+
+ \\server\Office2016 |
+ is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml. |
+
+
+ Setup.exe |
+ is the Office Deployment Tool. |
+
+
+ /packager |
+ creates the Office 2016 App-V package with Volume Licensing as specified in the customConfig.xml file. |
+
+
+ \\server\Office2016\Customconfig.xml |
+ passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage. |
+
+
+ \\server\share\Office 2016AppV |
+ specifies the location of the newly created Office App-V package. |
+
+
+
+
+ After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
+
+ - **App-V Packages** – contains an Office 2016 App-V package and two deployment configuration files.
+
+ - **WorkingDir**
+
+ **Note**
+ To troubleshoot any issues, see the log files in the %temp% directory (default).
+
+
+
+3. Verify that the Office 2016 App-V package works correctly:
+
+ 1. Publish the Office 2016 App-V package, which you created globally, to a test computer, and verify that the Office 2016 shortcuts appear.
+
+ 2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
+
+## Publishing the Office package for App-V 5.1
+
+
+Use the following information to publish an Office package.
+
+### Methods for publishing Office App-V packages
+
+Deploy the App-V package for Office 2016 by using the same methods you use for any other package:
+
+- System Center Configuration Manager
+
+- App-V Server
+
+- Stand-alone through PowerShell commands
+
+### Publishing prerequisites and requirements
+
+
+
+
+
+
+
+
+
+
+
+Enable PowerShell scripting on the App-V clients |
+To publish Office 2016 packages, you must run a script.
+Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:
+Set-AppvClientConfiguration –EnablePackageScripts 1
|
+
+
+Publish the Office 2016 package globally |
+Extension points in the Office App-V package require installation at the computer level.
+When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2016 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages. |
+
+
+
+
+
+
+### How to publish an Office package
+
+Run the following command to publish an Office package globally:
+
+- `Add-AppvClientPackage | Publish-AppvClientPackage –global`
+
+- From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
+
+## Customizing and managing Office App-V packages
+
+
+To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
+
+- [Enabling Office plug-ins by using connection groups](#bkmk-enable-office-plugins)
+
+- [Disabling Office 2016 applications](#bkmk-disable-office-apps)
+
+- [Disabling Office 2016 shortcuts](#bkmk-disable-shortcuts)
+
+- [Managing Office 2016 package upgrades](#bkmk-manage-office-pkg-upgrd)
+
+- [Managing Office 2016 licensing upgrades](#bkmk-manage-office-lic-upgrd)
+
+- [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project)
+
+### Enabling Office plug-ins by using connection groups
+
+Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You cannot use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
+
+**To enable plug-ins for Office App-V packages**
+
+1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
+
+2. Sequence your plug-ins using the App-V 5.1 Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
+
+3. Create an App-V 5.1 package that includes the desired plug-ins.
+
+4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
+
+5. Add the Office 2016 App-V package and the plug-ins package you sequenced to the Connection Group you created.
+
+ **Important**
+ The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2016 App-V package first, and then add the plug-in App-V package.
+
+
+
+6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2016 App-V package.
+
+7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2016 App-V package has.
+
+ Since the Office 2016 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2016 App-V package you published.
+
+8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
+
+9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
+
+10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2016 App-V package is in use when the Connection Group is enabled. If that happens, you have to reboot to successfully enable the Connection Group.
+
+11. After you successfully publish both packages and enable the Connection Group, start the target Office 2016 application and verify that the plug-in you published and added to the connection group works as expected.
+
+### Disabling Office 2016 applications
+
+You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, you will save the changes, add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
+
+**Note**
+To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
+
+
+
+**To disable an Office 2016 application**
+
+1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
+
+2. Search for the Office application you want to disable, for example, Access 2016.
+
+3. Change the value of "Enabled" from "true" to "false."
+
+4. Save the Deployment Configuration File.
+
+5. Add the Office 2016 App-V Package with the new Deployment Configuration File.
+
+ ``` syntax
+
+
+ Lync 2016
+
+
+
+
+
+
+ Access 2016
+
+
+
+
+ ```
+
+6. Re-add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
+
+### Disabling Office 2016 shortcuts
+
+You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
+
+**To disable shortcuts for Office 2016 applications**
+
+1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
+
+2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
+
+ ``` syntax
+ Shortcuts
+
+ -->
+
+
+
+
+ [{Common Programs}]\Microsoft Office 2016\Access 2016.lnk
+ [{AppvPackageRoot}])office15\MSACCESS.EXE
+ [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
+
+
+ Microsoft.Office.MSACCESS.EXE.16
+ true
+ Build a professional app quickly to manage data.
+ l
+ [{AppVPackageRoot}]\officel6\MSACCESS.EXE
+
+ ```
+
+3. Save the Deployment Configuration File.
+
+4. Republish Office 2016 App-V Package with new Deployment Configuration File.
+
+Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
+
+### Managing Office 2016 package upgrades
+
+To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2016 package, perform the following steps.
+
+**How to upgrade a previously deployed Office 2016 package**
+
+1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
+
+ **Note**
+ Office App-V packages have two Version IDs:
+
+ - An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
+
+ - A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
+
+
+
+2. Globally publish the newly created Office 2016 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2016 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
+
+3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
+
+### Managing Office 2016 licensing upgrades
+
+If a new Office 2016 App-V Package has a different license than the Office 2016 App-V Package currently deployed. For instance, the Office 2013 package deployed is a subscription based Office 2016 and the new Office 2016 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
+
+**How to upgrade an Office 2016 License**
+
+1. Unpublish the already deployed Office 2016 Subscription Licensing App-V package.
+
+2. Remove the unpublished Office 2016 Subscription Licensing App-V package.
+
+3. Restart the computer.
+
+4. Add the new Office 2016 App-V Package Volume Licensing.
+
+5. Publish the added Office 2016 App-V Package with Volume Licensing.
+
+An Office 2016 App-V Package with your chosen licensing will be successfully deployed.
+
+### Deploying Visio 2016 and Project 2016 with Office
+
+The following table describes the requirements and options for deploying Visio 2016 and Project 2016 with Office.
+
+
+
+
+
+
+
+
+
+
+
+How do I package and publish Visio 2016 and Project 2016 with Office? |
+You must include Visio 2016 and Project 2016 in the same package with Office.
+If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic. |
+
+
+How can I deploy Visio 2016 and Project 2016 to specific users? |
+Use one of the following methods:
+
+
+
+
+
+
+
+
+
+
+Create two different packages and deploy each one to a different group of users |
+Create and deploy the following packages:
+
+A package that contains only Office - deploy to computers whose users need only Office. A package that contains Office, Visio, and Project - deploy to computers whose users need all three applications. |
+
+
+If you want only one package for the whole organization, or if you have users who share computers: |
+Follows these steps:
+
+Create a package that contains Office, Visio, and Project. Deploy the package to all users. Use [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project. |
+
+
+
+ |
+
+
+
+
+
+
+## Additional resources
+
+
+**Office 2016 App-V Packages Additional Resources**
+
+[Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
+
+[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
+
+**Office 2013 and Office 2010 App-V Packages**
+
+[Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v51.md)
+
+[Deploying Microsoft Office 2011 by Using App-V](deploying-microsoft-office-2010-by-using-app-v51.md)
+
+**Connection Groups**
+
+[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
+
+[Managing Connection Groups](managing-connection-groups51.md)
+
+**Dynamic Configuration**
+
+[About App-V 5.1 Dynamic Configuration](about-app-v-51-dynamic-configuration.md)
+
+## Got a suggestion for App-V?
+
+
+Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
diff --git a/smb/TOC.md b/smb/TOC.md
new file mode 100644
index 0000000000..4c2433fafc
--- /dev/null
+++ b/smb/TOC.md
@@ -0,0 +1 @@
+# [SMB](index.md)
diff --git a/smb/docfx.json b/smb/docfx.json
new file mode 100644
index 0000000000..033a3552a9
--- /dev/null
+++ b/smb/docfx.json
@@ -0,0 +1,35 @@
+{
+ "build": {
+ "content": [
+ {
+ "files": [
+ "**/*.md"
+ ],
+ "exclude": [
+ "**/obj/**",
+ "smb/**",
+ "**/includes/**"
+ ]
+ }
+ ],
+ "resource": [
+ {
+ "files": [
+ "**/*.png",
+ "**/*.jpg"
+ ],
+ "exclude": [
+ "**/obj/**",
+ "smb/**",
+ "**/includes/**"
+ ]
+ }
+ ],
+ "overwrite": [],
+ "externalReference": [],
+ "globalMetadata": {},
+ "fileMetadata": {},
+ "template": [],
+ "dest": "smb"
+ }
+}
\ No newline at end of file
diff --git a/smb/index.md b/smb/index.md
new file mode 100644
index 0000000000..eaeb8132cd
--- /dev/null
+++ b/smb/index.md
@@ -0,0 +1,4 @@
+---
+title: SMB placeholder
+description: SMB placeholder
+---
diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index dc86e81da7..b49144c4ca 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -16,13 +16,11 @@ localizationpriority: high
**Applies to**
- Windows 10
-This topic provides a brief introduction to Windows 10 installation processes, and provides resolution procedures that IT administrators can use to resolve issues with Windows 10 upgrade.
-
-If you are not an IT administrator, you can try the [quick fixes](#quick-fixes) listed in this topic. If the quick fixes do not resolve your issue, see [Get help with Windows 10 upgrade and installation errors](https://support.microsoft.com/en-us/help/10587/windows-10-get-help-with-upgrade-installation-errors) for more information.
+>**Important**: This topic contains technical instructions for IT administrators. If you are not an IT administrator, see [Get help with Windows 10 upgrade and installation errors](https://support.microsoft.com/en-us/help/10587/windows-10-get-help-with-upgrade-installation-errors) for more information.
## In this topic
-The following sections and procedures are provided in this guide:
+This topic contains a brief introduction to Windows 10 installation processes, and provides resolution procedures that IT administrators can use to resolve issues with Windows 10 upgrade. The following sections and procedures are provided in this guide:
- [The Windows 10 upgrade process](#the-windows-10-upgrade-process): An explanation of phases used during the upgrade process.
- [Quick fixes](#quick-fixes): Steps you can take to eliminate many Windows upgrade errors.
diff --git a/windows/deploy/upgrade-analytics-get-started.md b/windows/deploy/upgrade-analytics-get-started.md
index 1d08d1f5cb..8aaa283d61 100644
--- a/windows/deploy/upgrade-analytics-get-started.md
+++ b/windows/deploy/upgrade-analytics-get-started.md
@@ -97,9 +97,12 @@ The compatibility update KB scans your computers and enables application usage t
IMPORTANT: Restart user computers after you install the compatibility update KBs for the first time.
+If you are planning to enable IE Site Discovery, you will need to install a few additional KBs.
+
| **Site discovery** | **KB** |
|----------------------|-----------------------------------------------------------------------------|
-| [Review site discovery](upgrade-analytics-review-site-discovery.md) | Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update. |
+| [Review site discovery](upgrade-analytics-review-site-discovery.md) | [KB3080149](http://www.catalog.update.microsoft.com/Search.aspx?q=3080149)
Updates the Diagnostic and Telemetry tracking service to existing devices. This update is only necessary on Windows 7 and Windows 8.1 devices.
For more information about this KB, see
Install the latest [Windows Monthly Rollup](http://catalog.update.microsoft.com/v7/site/Search.aspx?q=security%20monthly%20quality%20rollup). This functionality has been included in Internet Explorer 11 starting with the July 2016 Cumulative Update. |
+
### Automate data collection
diff --git a/windows/deploy/upgrade-analytics-resolve-issues.md b/windows/deploy/upgrade-analytics-resolve-issues.md
index 078290d9b3..6a61a18a33 100644
--- a/windows/deploy/upgrade-analytics-resolve-issues.md
+++ b/windows/deploy/upgrade-analytics-resolve-issues.md
@@ -18,7 +18,7 @@ Upgrade decisions include:
| Not reviewed | When you start to investigate an application or a driver to determine upgrade readiness, change their upgrade decision to **Review in progress.**
| Some applications are automatically assigned upgrade decisions based on information known to Microsoft.
All drivers are marked not reviewed by default.
|
| Review in progress | When you start to investigate an application or a driver to determine upgrade readiness, change their upgrade decision to **Review in progress**.
Until you’ve determined that applications and drivers will migrate successfully or you’ve resolved blocking issues, leave the upgrade decision status as **Review in progress**.
| Once you’ve fixed any issues and validated that the application or driver will migrate successfully, change the upgrade decision to **Ready to upgrade**.
|
| Ready to upgrade | Mark applications and drivers **Ready to upgrade** once you’ve resolved all blocking issues and you’re confident that they will upgrade successfully, or if you’ve decided to upgrade them as-is. | Applications with no known issues or with low installation rates are marked **Ready to upgrade** by default.
Be sure to review low install count applications for any business critical or important applications that are not yet upgrade-ready, despite their low installation rates.
All drivers are marked **Not reviewed** by default.
|
-| Won’t upgrade | By default, no applications or drivers are marked **Won’t upgrade** because only you can make that determination.
Use **Won’t upgrade** for computers you don’t want to upgrade.
| If, during your investigation into an application or driver, you determine that they should not be upgraded, mark them **Won’t upgrade**.
|
+| Won’t upgrade | By default, no applications or drivers are marked **Won’t upgrade** because only you can make that determination.
Use **Won’t upgrade** for applications and drivers you don’t want to upgrade.
| If, during your investigation into an application or driver, you determine that they should not or cannot be upgraded, mark them **Won’t upgrade**.
|
The blades in the **Resolve issues** section are:
diff --git a/windows/deploy/windows-10-upgrade-paths.md b/windows/deploy/windows-10-upgrade-paths.md
index e555794d61..0c5b8ff890 100644
--- a/windows/deploy/windows-10-upgrade-paths.md
+++ b/windows/deploy/windows-10-upgrade-paths.md
@@ -19,7 +19,7 @@ author: greg-lindsay
This topic provides a summary of available upgrade paths to Windows 10. You can upgrade to Windows 10 from Windows 7 or a later operating system. This includes upgrading from one release of Windows 10 to later release of Windows 10. Migrating from one edition of Windows 10 to a different edition of the same release is also supported. For more information about migrating to a different edition of Windows 10, see [Windows 10 edition upgrade](windows-10-edition-upgrades.md).
->**Windows 10 LTSB**: The upgrade paths displayed below do not apply to Windows 10 LTSB. In-place upgrade from Windows 7 or Windows 8.1 to Windows 10 LTSB is not supported.
+>**Windows 10 LTSB**: The upgrade paths displayed below do not apply to Windows 10 LTSB. In-place upgrade from Windows 7 or Windows 8.1 to Windows 10 LTSB is not supported. (Note that Windows 10 LTSB 2015 did not block this upgrade path. This was corrected in the Windows 10 LTSB 2016 release, which will now only allow data-only and clean install options.)
>**Windows N/KN**: Windows "N" and "KN" editions follow the same upgrade paths shown below. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process.
diff --git a/windows/keep-secure/event-4713.md b/windows/keep-secure/event-4713.md
index 482ad0768e..c35ede099f 100644
--- a/windows/keep-secure/event-4713.md
+++ b/windows/keep-secure/event-4713.md
@@ -21,7 +21,7 @@ author: Mir0sh
***Event Description:***
-This event generates when [Kerberos policy](https://technet.microsoft.com/en-us/library/cc782061(v=ws.10).aspx) was changed.
+This event generates when [Kerberos](https://msdn.microsoft.com/library/windows/desktop/aa378747.aspx) policy was changed.
This event is generated only on domain controllers.
diff --git a/windows/keep-secure/images/remote-credential-guard-gp.png b/windows/keep-secure/images/remote-credential-guard-gp.png
index 98c97825fa..a65253b04e 100644
Binary files a/windows/keep-secure/images/remote-credential-guard-gp.png and b/windows/keep-secure/images/remote-credential-guard-gp.png differ
diff --git a/windows/keep-secure/remote-credential-guard.md b/windows/keep-secure/remote-credential-guard.md
index 2a813caee1..a8f2f46557 100644
--- a/windows/keep-secure/remote-credential-guard.md
+++ b/windows/keep-secure/remote-credential-guard.md
@@ -21,10 +21,30 @@ You can use Remote Credential Guard in the following ways:
- Helpdesk employees in your organization must connect to domain-joined devices that could be compromised. With Remote Credential Guard, the helpdesk employee can use RDP to connect to the target device without compromising their credentials to malware.
-Use the following diagrams to help understand how Remote Credential Guard works and what it helps protect against.
+## Comparing Remote Credential Guard with a server protected with Credential Guard
+
+Use the following diagrams to help understand how Remote Credential Guard works, what it helps protect against, and how it compares with using a server protected with Credential Guard. As the diagram shows, Remote Credential Guard blocks NTLM (allowing only Kerberos), prevents Pass the Hash, and prevents usage of a credential after disconnection.
+## Comparing Remote Credential Guard with other options for Remote Desktop connections
+
+Use the following table to compare different security options for Remote Desktop connections.
+
+> [!NOTE]
+> This table compares different options than are shown in the previous diagram.
+
+| Remote Desktop with Credential Delegation | Remote Credential Guard | Restricted Admin mode |
+|---|---|---|
+| Protection: Provides **less protection** than other modes in this table. | Protection: Provides **moderate protection**, compared to other modes in this table. | Protection: Provides **the most protection** of the modes in this table. However, it also requires you to be in the local “Administrators” group on the remote computer. |
+| Version support: The remote computer can be running **any operating system that supports credential delegation**, which was introduced in Windows Vista. | Version support: The remote computer must be running **at least Windows 10, version 1607, or Windows Server 2016**. | Version support: The remote computer must be running **at least patched Windows 7 or patched Windows Server 2008 R2**.
For more information about patches (software updates) related to Restricted Admin mode, see [Microsoft Security Advisory 2871997](https://technet.microsoft.com/library/security/2871997.aspx). |
+| NA | Helps prevent:
- **Pass the Hash**
- Usage of a **credential after disconnection** | Prevents:
- **Pass the Hash**
- Usage of **domain identity during connection** |
+| Credentials supported from the remote desktop client device:
- **Signed on** credentials
- **Supplied** credentials
- **Saved** credentials | Credentials supported from the remote desktop client device:
- **Signed on** credentials only | Credentials supported from the remote desktop client device:
- **Signed on** credentials
- **Supplied** credentials
- **Saved** credentials |
+| Access: **Users allowed**, that is, members of remote desktop users group of remote host. | Access: **Users allowed**, that is, members of remote desktop users group of remote host. | Access: **Administrators only**, that is, only members in administrators group of remote host. |
+| Network identity: Remote desktop session **connects to other resources as signed on user**. | Network identity: Remote desktop session **connects to other resources as signed on user**. | Network identity: Remote desktop session **connects to other resources as remote host’s identity**. |
+| Multi-hop: From the remote desktop, you **can connect through Remote Desktop to another computer**. | Multi-hop: From the remote desktop, you **can connect through Remote Desktop to another computer**. | No multi-hop: From the remote desktop, you **cannot connect through Remote Desktop to another computer**. |
+| Supported authentication protocol: **Any negotiable protocol**. | Supported authentication protocol: **Kerberos only**. | Supported authentication protocol: **Any negotiable protocol**. |
+
## Hardware and software requirements
The Remote Desktop client and server must meet the following requirements in order to use Remote Credential Guard:
@@ -58,7 +78,11 @@ You can use Remote Credential Guard on the client device by setting a Group Poli
### Turn on Remote Credential Guard by using Group Policy
1. From the Group Policy Management Console, go to **Computer Configuration** -> **Administrative Templates** -> **System** -> **Credentials Delegation**.
+
2. Double-click **Restrict delegation of credentials to remote servers**.
+
+ 
+
3. Under **Use the following restricted mode**:
- If you want to require either [Restricted Admin mode](http://social.technet.microsoft.com/wiki/contents/articles/32905.how-to-enable-restricted-admin-mode-for-remote-desktop.aspx) or Remote Credential Guard, choose **Prefer Remote Credential Guard**. In this configuration, Remote Credential Guard is preferred, but it will use Restricted Admin mode (if supported) when Remote Credential Guard cannot be used.
@@ -66,10 +90,10 @@ You can use Remote Credential Guard on the client device by setting a Group Poli
- If you want to require Remote Credential Guard, choose **Require Remote Credential Guard**. With this setting, a Remote Desktop connection will succeed only if the remote computer meets the [Hardware and software requirements](#hardware-and-software-requirements) listed earlier in this topic.
+ - If you want to require Restricted Admin mode, choose **Require Restricted Admin**. For information about Restricted Admin mode, see the table in [Comparing Remote Credential Guard with other options for Remote Desktop connections](#comparing-remote-credential-guard-with-other-options-for-remote-desktop-connections), earlier in this topic.
+
4. Click **OK**.
- 
-
5. Close the Group Policy Management Console.
6. From a command prompt, run **gpupdate.exe /force** to ensure that the Group Policy object is applied.
@@ -96,7 +120,7 @@ mstsc.exe /remoteGuard
- Remote Desktop Gateway is not compatible with Remote Credential Guard.
-- You cannot used saved credentials or credentials that are different than yours. You must use the credentials of the user who is logged into the device.
+- You cannot use saved credentials or credentials that are different than yours. You must use the credentials of the user who is logged into the device.
- Both the client and the server must be joined to the same domain or the domains must have a trust relationship.
diff --git a/windows/keep-secure/tpm-recommendations.md b/windows/keep-secure/tpm-recommendations.md
index 277ad8c4ba..0b34d5a9a8 100644
--- a/windows/keep-secure/tpm-recommendations.md
+++ b/windows/keep-secure/tpm-recommendations.md
@@ -63,7 +63,7 @@ TPM 2.0 products and systems have important security advantages over TPM 1.2, in
- TPM 1.2 implementations vary in policy settings. This may result in support issues as lockout policies vary.
- TPM 2.0 lockout policy is configured by Windows, ensuring a consistent dictionary attack protection guarantee.
-- While TPM 1.2 parts are discrete silicon components which are typically soldered on the motherboard, TPM 2.0 is available as a **discrete (dTPM)** silicon component in a sinple semiconductor package, an **integrated** component incorporated in one or more semiconductor packages - alongside other logic units in the same package(s) - and as a **firmware (fTPM)** based component running in a trusted execution environment (TEE) on a general purpose SoC.
+- While TPM 1.2 parts are discrete silicon components which are typically soldered on the motherboard, TPM 2.0 is available as a **discrete (dTPM)** silicon component in a single semiconductor package, an **integrated** component incorporated in one or more semiconductor packages - alongside other logic units in the same package(s) - and as a **firmware (fTPM)** based component running in a trusted execution environment (TEE) on a general purpose SoC.
## Discrete, Integrated or Firmware TPM?
diff --git a/windows/keep-secure/vpn-routing.md b/windows/keep-secure/vpn-routing.md
index 5065c6aaa5..3372161696 100644
--- a/windows/keep-secure/vpn-routing.md
+++ b/windows/keep-secure/vpn-routing.md
@@ -23,7 +23,7 @@ In a split tunnel configuration, routes can be specified to go over VPN and all
Routes can be configured using the VPNv2/*ProfileName*/RouteList setting in the [VPNv2 Configuration Service Provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn914776.aspx).
-For each route item in the list the following can be specified:
+For each route item in the list, the following can be specified:
- **Address**: VPNv2/*ProfileName*/RouteList/*routeRowId*/Address
- **Prefix size**: VPNv2/*ProfileName*/RouteList/*routeRowId*/Prefix
@@ -37,11 +37,11 @@ Routes can also be added at connect time through the server for UWP VPN apps.
In a force tunnel configuration, all traffic will go over VPN. This is the default configuration and takes effect if no routes are specified.
-The only implication of this setting is the manipulation of routing entries. In the case of a force Tunnel VPN V4 and V6 default routes (for example. 0.0.0.0/0) are added to the routing table with a lower Metric than ones for other interfaces. This sends traffic through the VPN as long as there isn’t a specific route on the Physical Interface itself.
+The only implication of this setting is the manipulation of routing entries. In the case of a force tunnel, VPN V4 and V6 default routes (for example. 0.0.0.0/0) are added to the routing table with a lower metric than ones for other interfaces. This sends traffic through the VPN as long as there isn’t a specific route on the physical interface itself.
For built-in VPN, this decision is controlled using the MDM setting **VPNv2/ProfileName/NativeProfile/RoutingPolicyType**.
-For a UWP VPN plug-in, this property is directly controlled by the app. If the VPN plug-in passes only 2 include routes (default route for both v4 and v6), the Windows VPN Platform marks the VPN as force tunnel.
+For a UWP VPN plug-in, this property is directly controlled by the app. If the VPN plug-in indicates the default route for IPv4 and IPv6 as the only two Inclusion routes, the VPN platform marks the connection as Force Tunneled.
## Configure routing
diff --git a/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index c6e5606348..ca86b2cd46 100644
--- a/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -835,7 +835,7 @@ Apply the Speech/AllowSpeechModelUpdate MDM policy from the [Policy CSP](https:/
-or-
-- Create a REG\_DWORD registry setting called **AllowSpeechModelUpdate** in **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\PolicyManager\\Current\\Device\\Speech**, with a value of 0 (zero).
+- Create a REG\_DWORD registry setting called **ModelDownloadAllowed** in **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Speech_OneCore\\Preferences**, with a value of 0 (zero).
### 16.7 Account info
@@ -1359,4 +1359,4 @@ You can turn off automatic updates by doing one of the following. This is not re
To learn more, see [Device update management](http://msdn.microsoft.com/library/windows/hardware/dn957432.aspx) and [Configure Automatic Updates by using Group Policy](http://technet.microsoft.com/library/cc720539.aspx).
-To help make it easier to deploy settings to restrict connections from Windows 10 to Microsoft, you can apply the [Windows Restricted Traffic Limited Functionality Baseline](https://go.microsoft.com/fwlink/?linkid=828887). This baseline was created in the same way as the [Windows security baselines](../keep-secure/windows-security-baselines.md) that are often used to efficiently configure Windows to a known secure state. Running the Windows Restricted Traffic Limited Functionality Baseline on devices in your organization will allow you to quickly configure all of the settings covered in this document. However, some of the settings reduce the functionality and security configuration of your device and are therefore not recommended. Make sure should you've chosen the right settings configuration for your environment before applying.
\ No newline at end of file
+To help make it easier to deploy settings to restrict connections from Windows 10 to Microsoft, you can apply the [Windows Restricted Traffic Limited Functionality Baseline](https://go.microsoft.com/fwlink/?linkid=828887). This baseline was created in the same way as the [Windows security baselines](../keep-secure/windows-security-baselines.md) that are often used to efficiently configure Windows to a known secure state. Running the Windows Restricted Traffic Limited Functionality Baseline on devices in your organization will allow you to quickly configure all of the settings covered in this document. However, some of the settings reduce the functionality and security configuration of your device and are therefore not recommended. Make sure should you've chosen the right settings configuration for your environment before applying.
diff --git a/windows/manage/waas-configure-wufb.md b/windows/manage/waas-configure-wufb.md
index 5cabd0a38e..1ef0609987 100644
--- a/windows/manage/waas-configure-wufb.md
+++ b/windows/manage/waas-configure-wufb.md
@@ -134,9 +134,9 @@ You can also pause a system from receiving Quality Updates for a period of up to
| MDM for version 1511: ../Vendor/MSFT/Policy/Config/Update/**DeferUpgrade** | \Microsoft\PolicyManager\default\Update\Pause |
-You can check what date Quality Updates were paused at by checking the registry key **PausedQualityDate** under **HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\Settings**.
+You can check the date that Quality Updates were paused at by checking the registry key **PausedQualityDate** under **HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\Settings**.
-The local group policy editor (GPEdit.msc) will not reflect if your Quality Update Pause period has expired. Although the device will resume Quality Updates after 60 days automatically, the pause checkbox will remain checked in the policy editor. To see if a device has auto-resumed taking Quality Updates, you can check the status registry key **PausedQualityStatus** under **HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\Settings**.
+The local group policy editor (GPEdit.msc) will not reflect if your Quality Update Pause period has expired. Although the device will resume Quality Updates after 35 days automatically, the pause checkbox will remain checked in the policy editor. To see if a device has auto-resumed taking Quality Updates, you can check the status registry key **PausedQualityStatus** under **HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\Settings**.
| Value | Status|
| --- | --- |
diff --git a/windows/whats-new/contribute-to-a-topic.md b/windows/whats-new/contribute-to-a-topic.md
index df040f8573..2f75b278ca 100644
--- a/windows/whats-new/contribute-to-a-topic.md
+++ b/windows/whats-new/contribute-to-a-topic.md
@@ -1,6 +1,6 @@
---
title: Edit an existing topic using the Contribute link
-description: Instructions about how to edit an existing topic by using the Contribute link.
+description: Instructions about how to edit an existing topic by using the Contribute link on TechNet.
keywords: contribute, edit a topic
ms.prod: w10
ms.mktglfcycl: explore