Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Packages created from Package Accelerators (rehydrating) may fail to stream correctly in App-V 4.6 SP1
Article ID: 2496872 - View products that this article applies to.
Packages created from Package Accelerators (rehydrating) may fail to stream correctly in Microsoft Application Virtualization 4.6 SP1. This may occur with Microsoft provided or 3rd-Party provided Package Accelerators.
When you obtain your Package Accelerators from a site, the OSD files are included and they reflect the paths of the original packages. For example:
<CODEBASE HREF="rtsps://%SFT_SOFTGRIDSERVER%:322/WinZip90/WinZip90.sft" …../>
From the path above, the original package was saved into "WinZip90" folder, where all the OSD, SPRJ, SFT files were put.
During Rehydration, the user has the ability to change the package name to anything. For example, the user changes it from "WinZip90" to "WinZip90_Rehydrated." By default, the sequencer will save it to "WinZip90_Rehydrated" folder. However, the CODEBASE path will still have "WinZip90" in the path. As a result, if the package folder is copied directly to the content share, when the package is deployed (assuming the customer simply copies the new folder to the "content" folder), sft cannot be found by Client. Based on the OSD, it is expected to be found in "content\WinZip90" folder, while it actually lives now in "contents\WinZip90_Rehydrated" folder.
Collapse this imageExpand this image
To summarize the above, each time a user changes package name at the rehydration time, the package will require re-configuration to work via server deployment, as the sft will not be found at the default path specified.
There are several workarounds:
1. Name the package/folder so that it matches the path in the OSD file. (i.e. back to WinZip90). However, this assumes that you are using "content\<Folder>\.sft" setup for the Server and not "content\.sft" AND you are willing to change the name of the folder of the original package.
2. You can update the path in every OSD of the rehydrated package. It is a relatively easy if you have 1 or 2 OSD files, however it can become tedious if you have a package with a significant number of OSD files.
3. You can run a package upgrade on the rehydrated package and correct the path in the tabs, then resave the package. This however requires you to perform a package upgrade simply to correct one issue. Plus it will increment the revision of the SFT.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.