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.
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.