Pre-cache file association is dependent on the content of the _extensionData.xml in the package.
Last Updated May 06, 2013
The pre-cache file associate feature doesn't appear to work when enabled in the Streaming Console.
The pre-cache file association feature uses the information from the _extensionData.xml file in the package. This feature does not work if the_extensionData.xml file is empty. When compiling a package, Symantec Virtual Composer scans the file extensions in HKCR and the associated programId information, but discards the data if a matching executable is not found in one of the "Application Shortcuts" resulting in an empty _extensionData.xml file.
Some installations automatically create "Application Shortcuts" during the capture process. However, for some applications (e.g., Citrix Receiver), the shortcut to associated application is not generated so the package ends up with the default shortcut to "DUMMY.EXE". Continuing the example with Citrix Reciever, when Composer looks for a match for the .ICA extension, "DUMMY.EXE" fails to match the .ICA extension so the_extensionData.xml file ends up empty.
To ensure the _extensionData.xml file gets data written to it, use Symantec Virtual Composer to define an application shortcut that matches the file extension found in HKCR. In the above example, create a shortcut that points to the executable WFCRUN32.EXE and then compile the package again.
Nothing (besides an empty header) is written to the _extensionData.xml file during the capture process.
Imported Document ID: TECH205918
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe