deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-14 14:27:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'refs/remotes/origin/master' into vs-9912231

Browse Source
This commit is contained in:
LizRoss 2017-03-17 09:35:39 -07:00
commit eecb603bb4
4 changed files with 16 additions and 143 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md
View File

@ -441,6 +441,7 @@ After you download the Office 2016 applications through the Office Deployment To
<td align="left"><p>PACKAGEGUID (optional)</p></td> <td align="left"><p>PACKAGEGUID (optional)</p></td>
<td align="left"><p>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.</p> <td align="left"><p>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.</p>
<p>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.</p> <p>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.</p>
>**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.
</td> </td>
</tr> </tr>
@ -448,7 +449,6 @@ After you download the Office 2016 applications through the Office Deployment To
</table> </table>
   
2. Use the /packager command to convert the Office applications to an Office 2016 App-V package. 2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
For example: For example:

3
mdop/appv-v5/how-to-view-and-configure-applications-and-default-virtual-application-extensions-by-using-the-management-console-51.md
View File

@ -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. 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'<httpRuntime targetFramework="4.5"/> ' to '<httpRuntime targetFramework="4.5" maxRequestLength="8192"/>' 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 `<httpRuntime targetFramework="4.5"/>` to `<httpRuntime targetFramework="4.5" maxRequestLength="8192"/>` 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). **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).

75
mdop/appv-v5/planning-for-using-app-v-with-office51.md
View File

@ -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. 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. Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack.
   
## <a href="" id="bkmk-office-vers-supp-appv"></a>Supported versions of Microsoft Office ## <a href="" id="bkmk-office-vers-supp-appv"></a>Supported versions of Microsoft Office
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.
The following table lists the versions of Microsoft Office that App-V supports, methods of Office package creation, supported licensing, and supported deployments. >**Note**&nbsp;&nbsp;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.
<table>
<colgroup>
<col width="20%" />
<col width="20%" />
<col width="20%" />
<col width="20%" />
<col width="20%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Supported Office Version</th>
<th align="left">Supported App-V Versions</th>
<th align="left">Package Creation</th>
<th align="left">Supported Licensing</th>
<th align="left">Supported Deployments</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Office 365 ProPlus</p>
<p>Also supported:</p>
<ul>
<li><p>Visio Pro for Office 365</p></li>
<li><p>Project Pro for Office 365</p></li>
</ul></td>
<td align="left"><ul>
<li><p>App-V 5.0</p></li>
<li><p>App-V 5.0 SP1</p></li>
<li><p>App-V 5.0 SP2</p></li>
<li><p>App-V 5.0 SP3</p></li>
<li><p>App-V 5.1</p></li>
</ul></td>
<td align="left"><p>Office Deployment Tool</p></td>
<td align="left"><p>Subscription</p></td>
<td align="left"><ul>
<li><p>Desktop</p></li>
<li><p>Personal VDI</p></li>
<li><p>Pooled VDI</p></li>
<li><p>RDS</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Office Professional Plus 2013</p>
<p>Also supported:</p>
<ul>
<li><p>Visio Professional 2013</p></li>
<li><p>Project Professional 2013</p></li>
</ul></td>
<td align="left"><ul>
<li><p>App-V 5.0</p></li>
<li><p>App-V 5.0 SP1</p></li>
<li><p>App-V 5.0 SP2</p></li>
<li><p>App-V 5.0 SP3</p></li>
<li><p>App-V 5.1</p></li>
</ul></td>
<td align="left"><p>Office Deployment Tool</p></td>
<td align="left"><p>Volume Licensing</p></td>
<td align="left"><ul>
<li><p>Desktop</p></li>
<li><p>Personal VDI</p></li>
<li><p>Pooled VDI</p></li>
<li><p>RDS</p></li>
</ul></td>
</tr>
</tbody>
</table>
   
@ -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. 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. 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.
   

77
windows/manage/appv-planning-for-using-appv-with-office.md
View File

@ -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. 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. Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack.
## <a href="" id="bkmk-office-vers-supp-appv"></a>Supported versions of Microsoft Office ## <a href="" id="bkmk-office-vers-supp-appv"></a>Supported versions of Microsoft Office
<!-- As of February 28, 2017, the first row of the table should be updated, because at that point, support for the Office 2013 version of Office 365 will end. It might also be good to have a link to this KB article: https://support.microsoft.com/kb/3199744 --> <!-- As of February 28, 2017, the first row of the table should be updated, because at that point, support for the Office 2013 version of Office 365 will end. It might also be good to have a link to this KB article: https://support.microsoft.com/kb/3199744 -->
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**&nbsp;&nbsp;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)
<table>
<colgroup>
<col width="20%" />
<col width="20%" />
<col width="20%" />
<col width="20%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Supported Office Version</th>
<th align="left">Package Creation</th>
<th align="left">Supported Licensing</th>
<th align="left">Supported Deployments</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Office 365 ProPlus (either the Office 2013 or the Office 2016 version)</p>
<p>Also supported:</p>
<ul>
<li><p>Visio Pro for Office 365</p></li>
<li><p>Project Pro for Office 365</p></li>
</ul></td>
<td align="left"><p>Office Deployment Tool</p></td>
<td align="left"><p>Subscription</p></td>
<td align="left"><ul>
<li><p>Desktop</p></li>
<li><p>Personal VDI</p></li>
<li><p>Pooled VDI</p></li>
<li><p>RDS</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><ul>
<li><p>Visio Professional 2016 (C2R-P)</p></li>
<li><p>Visio Standard 2016 (C2R-P)</p></li>
<li><p>Project Professional 2016 (C2R-P)</p></li>
<li><p>Project Standard 2016 (C2R-P)</p></li>
</ul></td>
<td align="left"><p>Office Deployment Tool</p></td>
<td align="left"><p>Volume Licensing</p></td>
<td align="left"><ul>
<li><p>Desktop</p></li>
<li><p>Personal VDI</p></li>
<li><p>Pooled VDI</p></li>
<li><p>RDS</p></li>
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Office Professional Plus 2013</p>
<p>Also supported:</p>
<ul>
<li><p>Visio Professional 2013</p></li>
<li><p>Project Professional 2013</p></li>
</ul></td>
<td align="left"><p>Office Deployment Tool</p></td>
<td align="left"><p>Volume Licensing</p></td>
<td align="left"><ul>
<li><p>Desktop</p></li>
<li><p>Personal VDI</p></li>
<li><p>Pooled VDI</p></li>
<li><p>RDS</p></li>
</ul></td>
</tr>
</tbody>
</table>
## <a href="" id="bkmk-plan-coexisting"></a>Planning for using App-V with coexisting versions of Office ## <a href="" id="bkmk-plan-coexisting"></a>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. 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. 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.