The issue is that when adding a virtual Office package to Microsoft Application Virtualization 5.0, the action will fail if you are using the Office builds 15.0.4649.1001 or 15.0.4649.1003. The error you receive is:
Add-AppvClientPackage : Package manifest is invalid. Validation of elements in AppV namespace failed.
Operation attempted: Retrieve Package and Version IDs From Package URL.
AppV Error Code: 1400000007.
Please consult AppV Client Event Log for more details.
There are two options available to work around this issue:
1. Uninstall the September updates. Note that there were no security bulletins for Office in September.
2. Specify the older build version in the config.xml file so that the package uses that version. This can be done by updating the version field in the config.xml file as shown in the example below.
<Add SourcePath="…" OfficeClientEdition="…" Version="15.0.4649.1001">
<Add SourcePath="…" OfficeClientEdition="…" Version="18.104.22.168.4631.1002 ">
Note that this issue will be fixed in the next Office update due in October.
Priya Raghavan | Senior Test Lead | Microsoft
System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/