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 index 8b3704c3a9..bd506092d0 100644 --- 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 @@ -441,14 +441,14 @@ After you download the Office 2016 applications through the Office Deployment To

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. + + >**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: diff --git a/mdop/appv-v5/how-to-view-and-configure-applications-and-default-virtual-application-extensions-by-using-the-management-console-51.md b/mdop/appv-v5/how-to-view-and-configure-applications-and-default-virtual-application-extensions-by-using-the-management-console-51.md index 34ae20a4f8..e61be318ba 100644 --- a/mdop/appv-v5/how-to-view-and-configure-applications-and-default-virtual-application-extensions-by-using-the-management-console-51.md +++ b/mdop/appv-v5/how-to-view-and-configure-applications-and-default-virtual-application-extensions-by-using-the-management-console-51.md @@ -29,7 +29,8 @@ Use the following procedure to view and configure default package extensions. 5. To edit other application extensions, modify the configuration file and click **Import and Overwrite this Configuration**. Select the modified file and click **Open**. In the dialog box, click **Overwrite** to complete the process. ->**Note** If the upload fails and the size of your configuration file is above 4MB, you will need to increase the maximum file size allowed by the server. This can be done by adding the maxRequestLength attribute with a value greater than the size of your configuration file (in KB) to the httpRuntime element on line 26 of C:\Program Files\Microsoft Application Virtualization Server\ManagementService\Web.config. For example, changing' ' to '' will increase the maximum size to 8MB +>**Note** If the upload fails and the size of your configuration file is above 4MB, you will need to increase the maximum file size allowed by the server. This can be done by adding the maxRequestLength attribute with a value greater than the size of your configuration file (in KB) to the httpRuntime element on line 26 of `C:\Program Files\Microsoft Application Virtualization Server\ManagementService\Web.config`. +For example, changing `` to `` will increase the maximum size to 8MB **Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv). diff --git a/mdop/appv-v5/planning-for-using-app-v-with-office51.md b/mdop/appv-v5/planning-for-using-app-v-with-office51.md index c6edab05da..0f34f1b356 100644 --- a/mdop/appv-v5/planning-for-using-app-v-with-office51.md +++ b/mdop/appv-v5/planning-for-using-app-v-with-office51.md @@ -28,82 +28,15 @@ Use the following information to plan how to deploy Office by using Microsoft Ap You can use the App-V 5.1 Sequencer to create plug-in packages for Language Packs, Language Interface Packs, Proofing Tools and ScreenTip Languages. You can then include the plug-in packages in a Connection Group, along with the Office 2013 package that you create by using the Office Deployment Toolkit. The Office applications and the plug-in Language Packs interact seamlessly in the same connection group, just like any other packages that are grouped together in a connection group. -**Note**   +>**Note**   Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack.   ## Supported versions of Microsoft Office - -The following table lists the versions of Microsoft Office that App-V supports, methods of Office package creation, supported licensing, and supported deployments. - - ------- - - - - - - - - - - - - - - - - - - - - - - - - - -
Supported Office VersionSupported App-V VersionsPackage CreationSupported LicensingSupported Deployments

Office 365 ProPlus

-

Also supported:

-
    -

  • Visio Pro for Office 365

    • -

  • Project Pro for Office 365

    • -
    -

  • App-V 5.0

    • -

  • App-V 5.0 SP1

    • -

  • App-V 5.0 SP2

    • -

  • App-V 5.0 SP3

    • -

  • App-V 5.1

    • -

Office Deployment Tool

Subscription

    -

  • Desktop

    • -

  • Personal VDI

    • -

  • Pooled VDI

    • -

  • RDS

    • -

Office Professional Plus 2013

-

Also supported:

-
    -

  • Visio Professional 2013

    • -

  • Project Professional 2013

    • -
    -

  • App-V 5.0

    • -

  • App-V 5.0 SP1

    • -

  • App-V 5.0 SP2

    • -

  • App-V 5.0 SP3

    • -

  • App-V 5.1

    • -

Office Deployment Tool

Volume Licensing

    -

  • Desktop

    • -

  • Personal VDI

    • -

  • Pooled VDI

    • -

  • RDS

    • -
+See [Microsoft Office Product IDs that App-V supports](https://support.microsoft.com/en-us/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click) for a list of supported Office products. +>**Note**  You must use the Office Deployment Tool to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported. You cannot use the App-V Sequencer.   @@ -149,7 +82,7 @@ The Office documentation provides extensive guidance on coexistence for Windows The following tables summarize the supported coexistence scenarios. They are organized according to the version and deployment method you’re starting with and the version and deployment method you are migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience. -**Note**   +>**Note**   Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.   diff --git a/windows/manage/appv-planning-for-using-appv-with-office.md b/windows/manage/appv-planning-for-using-appv-with-office.md index bd79da1f4f..b18a9df8d0 100644 --- a/windows/manage/appv-planning-for-using-appv-with-office.md +++ b/windows/manage/appv-planning-for-using-appv-with-office.md @@ -28,81 +28,20 @@ Use the following information to plan how to deploy Office by using Microsoft Ap You can use the App-V Sequencer to create plug-in packages for Language Packs, Language Interface Packs, Proofing Tools and ScreenTip Languages. You can then include the plug-in packages in a Connection Group, along with the Office package that you create by using the Office Deployment Toolkit. The Office applications and the plug-in Language Packs interact seamlessly in the same connection group, just like any other packages that are grouped together in a connection group. -**Note**   +>**Note**   Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack. ## Supported versions of Microsoft Office -The following table lists the versions of Microsoft Office that App-V supports, methods of Office package creation, supported licensing, and supported deployments. +See [Microsoft Office Product IDs that App-V supports](https://support.microsoft.com/en-us/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click) for a list of supported Office products. +>**Note**  You must use the Office Deployment Tool to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported. You cannot use the App-V Sequencer. + +>**Note** +Support for the [Office 2013 version of Office 365 ended in Februrary 2017](https://support.microsoft.com/kb/3199744) + - ------ - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Supported Office VersionPackage CreationSupported LicensingSupported Deployments

Office 365 ProPlus (either the Office 2013 or the Office 2016 version)

-

Also supported:

-
    -

  • Visio Pro for Office 365

    • -

  • Project Pro for Office 365

    • -

Office Deployment Tool

Subscription

    -

  • Desktop

    • -

  • Personal VDI

    • -

  • Pooled VDI

    • -

  • RDS

    • -
    -

  • Visio Professional 2016 (C2R-P)

    • -

  • Visio Standard 2016 (C2R-P)

    • -

  • Project Professional 2016 (C2R-P)

    • -

  • Project Standard 2016 (C2R-P)

    • -

Office Deployment Tool

Volume Licensing

    -

  • Desktop

    • -

  • Personal VDI

    • -

  • Pooled VDI

    • -

  • RDS

    • -

Office Professional Plus 2013

-

Also supported:

-
    -

  • Visio Professional 2013

    • -

  • Project Professional 2013

    • -

Office Deployment Tool

Volume Licensing

    -

  • Desktop

    • -

  • Personal VDI

    • -

  • Pooled VDI

    • -

  • RDS

    • -
## Planning for using App-V with coexisting versions of Office @@ -148,7 +87,7 @@ The Office documentation provides extensive guidance on coexistence for Windows The following tables summarize the supported coexistence scenarios. They are organized according to the version and deployment method you’re starting with and the version and deployment method you are migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience. -**Note**   +>**Note**   Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.