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

Merge pull request #440 from jamiejdt/VSO-8351909

Browse Source 
Fixed formatting error
This commit is contained in:
Elizabeth Ross 2017-03-16 17:08:37 -07:00 committed by GitHub
commit e10e6d371b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -441,14 +441,14 @@ 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>
</tbody> </tbody>
</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: