From ecad192f65a883ca937970427b9d4efed6fbdf68 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Wed, 28 Feb 2018 15:59:09 -0800 Subject: [PATCH] Editorial changes --- .../appv-deploying-microsoft-office-2013-with-appv.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2013-with-appv.md b/windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2013-with-appv.md index 207464926b..8663684ff1 100644 --- a/windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2013-with-appv.md @@ -528,12 +528,12 @@ Use the steps in this section to enable Office plug-ins with your Office package Since the Office 2013 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 2013 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 updated 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 2013 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. +10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2013 App-V package is in use when the Connection Group is enabled. If that happens, you'll 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 2013 application and verify that the plug-in you published and added to the Connection Group works as expected. ### Disabling Office 2013 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 2013 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 2013 App-V Package 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 2013 App-V package has been published, you will save the changes, add the Office 2013 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 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. For more information, see [Reference for Click-to-Run configuration.xml file](http://technet.microsoft.com/library/jj219426.aspx).