locked
Sp1 Sequencer bug: Don't use VFS installs RRS feed

  • General discussion

  • While installing the virtual applciation to the asset folder is the "best practice" for sequencing, this is not always possible. 

    We uncovered a new bug in the 4.1 SP1 sequencer in our latest App-V training class that renders packages where the virtualized app is installed to the C:\Program Files folder (aka "a VFS install") useless if you try to later upgrade the package.  More information on this issue in my blog:

    http://www.tmurgent.com/TmBlog/?p=402

    The end result is that such a package, opened for upgrade and saved, will fail to launch at the client

             39-0000010B

             The directory name is invalid.


    Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "The Client Book" and "OSD Reference Book" (http://www.tmurgent.com/Books )
    Saturday, May 21, 2011 2:50 PM
    Moderator

All replies

  • Tim,

    I have had a read of your blog post and have experimented myself to see if i could reproduce your issue.  Curiously, I couldn't.  I have sequenced an app to c:\program files\<app name>, opened for upgrade, made no changes, saved it and launched this new version on the client.  No problem!

    Because this issue is only relating to 4.6 SP1 maybe this issue has something to do with the new symbolic link functionality on the sequencer?  Do your machines have real Q: drives or the new symbolic linked ones?

    If you use the new option to "Expand Package To Local System..." before you open the sequence, does this work around this issue?


    Blog: http://Softwaredeployment.wordpress.com
    Monday, May 23, 2011 11:12 AM