Article ID: 2590590
The VAppCollector component of System Center Configuration Manager 2007 (ConfigMgr 2007) will be launched on a client even if ConfigMgr 2007/Microsoft Application Virtualization (App-V) integration is disabled. This can potentially generate multiple errors in the event log such as Event IDs 2012, 3008, 3210 and 5009.
This can occur if the Asset Intelligence component is enabled in System Center Configuration Manager 2007. Regardless of whether ConfigMgr 2007 is managing App-V clients or not, it will trigger the launch of VAppCollector. This is by design.
There is no supported way to prevent VAppCollector from launching other than by disabling Asset Intelligence, although in most cases this is not a viable solution as it stops all licensing information for the System Center Configuration Manager site.
If you are unable to disable Asset Intelligence, the only other known workarounds are below:
1) Include the computer account as part of the App-V user group assigned in the App-V server. This will allow the system account to launch the applications and thus no errors will be reported in the application event log.
2) Use System Center Configuration Manager 2007 to deploy your virtual packages or to deploy your virtual applications using MSI.
3) Ignore the errors in the event logs as they will not affect the App-V operations.
4) Set the HKLM\software\Microsoft\Softgrid\4.5\Client\Configuration\RequireAuthorizationIfCached registry key to 0. Keep in mind that this affects security because any user can create a shortcut and launch the applications even when they are not authorized. Be sure you fully understand all the implications of this before modifying this registry key. See below definition of this key:
Indicates that authorization is always required, whether or not an application is already in cache. Possible values:
0=False: Always try to connect to the server. If a connection to the server cannot be established, the client still allows the user to launch an application that has previously been loaded into cache.
1=True (default): Application always must be authorized at startup. For RTSP streamed applications, the user authorization token is sent to the server for authorization. For file-based applications, file ACLs control whether a user may access the application.
Restart the sftlist service for the change to take effect. See http://technet.microsoft.com/en-us/library/dd464849.aspx for more details.
VAppCollector is a component developed by the System Center Configuration Manager team to collect information about virtual applications using the App-V client. Besides Asset Intelligence it is used to populate the information in the virtual applications reports in System Center Configuration Manager to gather errors, last launched, etc. It is also used to collect information for virtual applications for metering purposes. VAppCollector does not have its own log as do other components in System Center Configuration Manager 2007.
It is normal behavior to collect all this information during an Hardware inventory cycle and launch of each application. You can gather more information about Asset intelligence by looking at the following log:
You will see entries similar to these:
If VAppCollector ran successfully you will see consecutive executing lines otherwise you will receive time-out entries among the executing lines.
Another way to determine if VAppCollector ran is to look into the sftlog.txt and find the lines that do not have usr values in them. Below is an example.
Launched by a user:
Launched by VAppCollector (note the lack of a "usr=" entry in the log lines):
Although VAppCollector will run on clients that have received applications through App-V server, the virtual applications reports in System Center Configuration Manager will not populate as there are no virtual packages to correlate the data. Asset Intelligence reports will have information about virtual packages but due to the lack of permissions to launch the virtual applications it cannot collect information such as software company, version, etc. These columns will show as unidentified or unknown on these reports.
Other things to consider:
Any prelaunch scripts that are set in the OSD files of these virtual applications will be launched during the hardware inventory cycle. If for example you are using a prelaunch script to map a drive, there will be an attempt to map the drive using the system account and if the computer doesn't have rights to map the drive it will show as disconnected. To work around this issue and similar issues consider the use of Post shutdown scripts to gracefully disconnect drives and terminate any instance that is triggered during the prelaunch phase.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2590590 - Last Review: October 19, 2011 - Revision: 9.0