Tweet

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.

Expand this image

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

• How to install (update) Windows Automated Installation Kit (WAIK) for Windows 7 SP1 on Windows Server (existing WAIK installation)
• System Center Service Manager (SCSM) 2010 is available in RTM !
• SCCM 2012 | Deploy with Automatic Deployment Rules error 0X87D20417
• WSUS 3.0 SP2 Beta Program now available on Microsoft Connect!
• Download the public RC of Windows Server 2008 R2