Updating Streamed Package without Working Directory
Updated: 29 Jul 2010 | 2 comments
We are in the process of upgrading our virtual/streaming infrastructure. One of the main reasons to upgrade was the possibility to patch streamed virtual applications. Because there was no use for the "package folder" this folder (working dir of streaming composer) was not saved, and only the end-product (zip file) was saved. Is there any way to patch our old streamed applications without this working directory?
discussion Filed Under:
Comments
Hmmm!
Hey Jonathan,
Unfortunately not. The original package must exist in order to create an upgrade, since all package specific information (GUID, app info, package format version,) are stored inside the package for reference.
While upgrading the package these things are looked for in order to maintain the same GUID for the upgrade package. This helps the streaming agent to bring down the blocks for the upgrade package whn clients requests blocks.
Hope this helps
Bala
Added note
Hi Jonathan,
As an addendum, this is same as upgrading an application installed conventionally from version x to version y.
The working principle is no different in streaming.
Regards,
Bala
Would you like to reply?
Login or Register to post your comment.