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.
7 thoughts on “App-V 5 and Office 2013 Preview packages”
Is there a way to produce a MSI to accompany the APPV file so I could install it like in App-V 4.x?
The 5.0 beta 2 sequencer produces a MSI when doing a “save”, but it doesn’t installer due to a 1603 error.
Packages can be converted from a 4.X format to a 5.X format, however you can not use any 5.x packages on a 4.X client and there is no way to convert them.
This behavior is probably as Microsoft have designed it.
The 5.0 Beta 2 Sequencer UI produces an MSI. I believe that only when Sequencing via command-line, that the /MSI parameter is required to produce an MSI.
It is possible (maybe probable) that when the App-V 5 team worked with the Office 2013 team, they Sequenced in command-line and did not actually produce an MSI to accompany the AppV file.
The MSI produced by “saving” the AppV in the 5.0 beta 2 Sequencer does not work for installation. It fails with a 1603 error.
Yes, I can still mount and make available the Sequenced Office 2013 with the PowerShell commands, but I would like to deploy it like I normally do.
SCCM 2012 SP1 will interface and deploy AppV files like they were MSIs. Maybe non-SCCM deployment suites will follow suit. But I would really like to have the MSI produced (if one was) when Office 2013 was Sequenced.
You can always submit this feedback on Connect
Good point! Thanks.
Is there a way to deploy the AppV version of Office 2013 Preview through SCCM 2007 R2? I’ve been able to deploy the app v 5.0 beta and dependencies through SCCM.
I’m guessing a package that copied the .appv locally then runs the powershell commands to do the rest is a possible option. Am I missing something here?
App-V 5 packages are supported in SCCM 2012 SP1 (and the CTP release of it). Support might come later – but not official announcement regarding SCCM 2007 R2 support