Microsoft Application Virtualization Sequencer Command Line Interface (CLI) in App-V 4.6 SP1 (KB2497312)
Hi,
Interesting, if you are a problem with the sequencer command line interface in app-V 4.6 SP1, read this post.
—————————————————————————————————————————————————————————————
ISSUE: CLI ignores AppendPackageVersionToFilename from a template – instead, the value from Options dialog is used.
When a package is created with the CLI, the value AppendPackageVersionToFilename from the specified SPRT file (in argument /DEFAULT:) is not used.

Instead, the CLI uses whichever value is set in the GUI in the Options dialog:

Resolution Here
—————————————————————————————————————————————————————————————
ISSUE: CLI ignores CompressPackage from a template – instead, the value from Options dialog is used.
If a package is sequenced with the CLI, using a project template (.SPRT) that has « compress package » set to « Yes », the resulting .SPRJ file will have « Compress Package » set to « No. » The resulting package is not compressed.
The value from the « Output Options » on the GUI Package Editor Deployment tab determines the compression setting:

This issue only occurs when using the CLI and works correctly when using the GUI and templates.
Resolution Here
—————————————————————————————————————————————————————————————
ISSUE: MSI not created from CLI, Package Accelerator Rehydrate when /MSI is used.
Create a package from a package accelerator with this syntax:
Resolution Here
related post
- Forefront Endpoint Protection 2010 Tools available !
- WSUS 3.0 SP2 Beta Program now available on Microsoft Connect!
- MDT 2010 / User Driven Installation | UDI System center configuration Manager and MDT Update 1 in video! see absolutely !
- System Center Configuration Manager (SCCM) 2007 SP2, R3 and Microsoft SQL Server 2012 !!! :-)
- Microsoft Enterprise Desktop Virtualization v2 Beta Program available | How to deploy and manage with System Center Configuration Manager 2007