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

Symptoms

When using Microsoft Application Virtualization 4.6 SP 1 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.

For example, if the package is named "Application A", the default save location would be "C:\users\administrator\desktop\Application A\Application A.sprj". If the same "Application A.sprj" is saved to C:\packages\App A\App A.sprj" the CODEBASE HREF does not reflect that change. 

The CODEBASE HREF from the non-default save will look like:

<CODEBASE HREF="RTSPS://%SFT_SOFTGRIDSERVER%:322/Application A/App A.sft" .... />

This contains the original designated package folder name with the updated SPRJ name.

Cause

The sequencer expects the package to be saved with the nomenclature established when the package is named during sequencing.

Resolution

The recommended resolution is to save the package to the default location on the sequencer before copying to the CONTENT share.

The workarounds for a non-default save include:

1) Opening the package for edit in the sequencer to update the path. 

2) Manually editing each OSD to update the path. 

3) Adjusting the name of the folder in the content share.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×