Virtual composer startup blocks not gathering dlls during collection
Last Updated February 24, 2016
The tracking of DLLs are not getting the startup blocks for the DLLs if the process dynamically loads them without actually calling any functions. This means that the startup blocks for these DLLs are not captured and the streaming performance suffers because the DLLs are downloaded after the end user tries to execute the software.
The startup blocks are off by a magnitude of X due to the number of dlls that are ignored by the startup block capture.
Symantec is aware of this issue and will provide a fix once one becomes available.
Using the appmgrcmd.exe on the capture machine to capture the startup blocks captures correctly.
6.x command requires the package GUID when called.
In 7.x version it requires the package version number to be appended after the GUID.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe