The ExternalCOMObjects parameter determines whether Windows creates and runs COM objects in the physical environment, rather than the virtual environment, to facilitate application compatibility with Omnissa ThinApp.
COM objects that are external to the virtual environment always run in the physical environment.
ThinApp sets an initial value for the ExternalCOMObjects parameter that creates and runs the COM objects in the virtual environment.
COM supports out‐of‐process executable servers and service‐based COM objects. If an application can create COM objects that generate modifications on the host computer, the integrity of the host computer is at risk. If ThinApp runs out‐of‐process and service‐based COM objects in the virtual environment, all changes that the COM objects make are stored by ThinApp in the sandbox.
The capture process does not generate this parameter. You can add this parameter to the Package.ini file under the[BuildOptions] section.
Running COM Objects Outside the Virtual Environment
When you troubleshoot a problem with the support team and determine that an application implements COM objects that are incompatible with ThinApp, you can modify the ExternalCOMObjects parameter to run the COM objects outside the virtual environment.
You can list the CLSID keys.
[BuildOptions]
ExternalCOMObjects={8BC3F05E-D86B-11D0-A075-00C04FB68820};{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}
Was this page helpful?