Now that App-V 4.6 SP1 is released we decided to publish a couple KB articles to give you a heads up on some issues we saw during the beta. Most of these are just FYIs and configuration related scenarios but if you’re rolling out Microsoft Application Virtualization 4.6 Service Pack 1 then you’ll probably want to browse through these real quick.
KB2496653 - Sequencing AutoCAD 2008 on Windows 7 x86 computers fails when installing to Q:\
KB2496835 - Shortcuts cannot be edited or created when upgrading a package in App-V 4.6 SP1
KB2496852 - Creating a Package Accelerator from some applications may fail in Microsoft App-V 4.6 SP1
KB2496872 - Packages created from Package Accelerators (rehydrating) may fail to stream correctly in App-V 4.6 SP1
KB2496904 - SFTLIST.EXE crashes during the post-configuration steps in the Windows 7 Service Pack 1 upgrade process
KB2496964 - When using App-V 4.6 SP1 and saving a package to a parent folder with a name that is different from the default parent folder name, that change is not reflected in the CODEBASE HREF of the OSD file
KB2497312 - Known issues with the Sequencer Command Line Interface (CLI) in App-V 4.6 SP1
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials
KB2496964 is support.microsoft.com/.../2496964
This isnt related to the this blog post but I'm not sure on who to contact so i figure this is a fast way of shining some light on a most urgent issue. :)
I have this issue at a customer site and it's really annoying. I've written a script that removes the livessp value but it's not a nice sollution. Can you please adress this in an upcoming blog post!
Thanks for a great blog!
There are far bigger known issues than some of those listed here.
I'm very curious to know why we no longer have control over stopping and starting monitoring?
And there is a VERY clear difference between clicking the "Run." button in the sequencer and running something manually.
For instance, trying to do the RSAT I can run OptionalFeatures.exe via the run button and I am met with a blank window, I run it via start, or start->run (win7x64 btw) and it populates. But doesn't seem to recognize any of the files put down. Folders, yes, files, no.
I'm having a really hard time understanding why you guys cut functionality in the name of making the easiest part of App-V (getting around the sequencer) easier.
Likewise theres an issue with Tools-Options, any option you set prompts you to save the project. So if I open the sequencer, and know I'm about to sequence something that needs WU enabled, I have to go to options, check that, save as template, then New From Template otherwise when I hit Create New Package it asks me to save my project. It fails if I say yes, and discards the option setting if I say no, either way without a template (which makes accelerators impossible) that setting wont keep.
This is, frankly, beta code with a LOT of questionable design choices.
Thank you for providing this feedback. A key objective of the App-V 4.6 SP1 Sequencer was to lower the learning curve for sequencing. When we tested the usability of the wizard we found that many new users struggled with the Start/Stop buttons, and so we designed an interface that new users reported to be more intuitive.
We are troubled to learn of the behaviour you are experiencing with OptionalFeatures.exe. You can bypass the option for the sequencer to launch the installer by selecting “Perform a custom installation” and then run the installer from the desktop. We recommend that you submit a support case if you are unable to sequence this application.
You should be able to apply Options settings without saving a new project template. We acknowledge that the Save dialog you are seeing is not an optimal experience, however if you click No the settings will apply when you sequence the application.
4.6 SP1 still has the bug where it cannot be installed if .NET 4 is installed first. This is a major point of confusion for new users.
I'd also like to point out another big one-
If your application has UNC paths or drive mappings to dll's on a windows 2003 server, and the client is running on XP, it will fail. MS is working on the hotfix now for that.