Editing an OSD File to Make Advanced Changes to an App-V 4.x Package

AdminStudio 2025 | 29.0 | Automated Application Converter

Version:This information applies to App-V 4.x packages.

An .osd file is an XML-based file that describes an App-V 4.x package’s shortcuts, file extensions, dependencies, and other data that can influence the environment of the application.

For advanced control over the information that is stored in the .osd files, you can edit the .osd file in an XML or text editor. For example, you may want to edit an .osd file directly in a text editor to specify the location of an .sft file, instead of configuring the location in the Automated Application Converter or on the Package Information page of the InstallShield Microsoft App-V Assistant. The following instructions explain how to do this. These instructions are for advanced users only.

To use a text or XML editor to edit an .osd file for making advanced changes, such as specifying the App-V server location for an .sft file, perform the following steps:

To use a text or XML editor to edit an .osd file:

1. Open the OSD file using any XML or ASCII text editor—for example, Microsoft Notepad.

Note:Before modifying the .osd file, read the schema prescribed by the .xsd file in the install directory. Failing to follow this schema might introduce errors that prevent a sequenced application from starting successfully.

2. Locate the CODEBASE element. Below is a sample CODEBASE element:

<CODEBASE HREF="HTTP://%SFT_SOFTGRIDSERVER%:80/orca.sft" GUID="A895355A-5883-41C6-A144-1BDA12242AAA" PARAMETERS="" FILENAME="{A895355A-5883-41C6-A144-1BDA12242AAA}\Orca.exe" SYSGUARDFILE="{A895355A-5883-41C6-A144-1BDA12242AAA}\osguard.cp" SIZE="2555268"/>

3. Locate the HREF attribute of the CODEBASE element and enter a valid URL to the published location of that App-V package’s .sft file.

Guidelines for Editing an .OSD File

When editing an .osd file, adhere to the prescribed schema and the following guidelines:

Ensure that named elements are nested within the <SOFTPKG> root element.
Ensure that element names are in all uppercase letters.
Be aware that attribute values are case sensitive.
Type carefully, and observe the XML specifications.