Want to generate an Office 2013 package with a unique App-V package id? Use the property PACKAGEGUID!
Sample XML
See more at the reference documentation!
Want to generate an Office 2013 package with a unique App-V package id? Use the property PACKAGEGUID!
Sample XML
See more at the reference documentation!
With the latest release (June 5) of Office Deployment Tool there is the ability to exclude applications when creating a package. For example, if you don’t want to deploy – say Lync? – even though you are technically licensed for it.
How does it work?
The XML defines what product you want to deploy / create an App-V package for.
A reference can be found on Technet, with the entire list of all applications that can be excluded. Do note that each application you want to exclude is a new line within the XML-file
<Configuration> <Add SourcePath="c:\media\" OfficeClientEdition="32" > <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> <ExcludeApp ID="Access" /> <ExcludeApp ID="InfoPath" /> <ExcludeApp ID="Lync" /> </Product> </Add> <Display Level="None" AcceptEULA="TRUE" /> <Property Name="AUTOACTIVATE" Value="1" /> </Configuration>
Download source media;
setup.exe /download c:\media\configuration.xml
Create the App-V package;
setup.exe /packager c:\media\configuration.xml c:\media\package
Just to deploy!
Remember, Office is only supported to be deployed as a global package when using App-V
Read more about this on Technet!
To be able to import the Office 2013 Preview Packages that can be downloaded – you need the following;
1. App-V 5 beta 2 client
2. Scripts needs to be enabled for the import to occur. To enable this and then import – run the following Powershell commands;
Set-ExecutionPolicy RemoteSigned Import-Module AppvClient Set-AppVClientConfiguration -EnablePackageScripts 1 Add-AppvClientPackage 'C:\media\ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86.appv' | Publish-AppvClientPackage -Global
Obviously – you need to alter the path to where the package is located.