This is the pointfix for issue with AeXNSAgentHostSurrogate32.exe process crash happening Windows 8.1 x64 OS. Also includes fix for issue when AM not counting executable start from UNC or network mapped drives (see TECH232189).
This point-fix is for version 7.5 SP1 HF5. You will need to upgrade to this version before applying this fix.
Covered issues are not reproducible on later versions of Application Metering 7.6 and 8.0 due to redesign of the whole component.
HOW TO INSTALL THIS POINTFIX On Server Side:
Extract files from the archive to NS machine. Make sure PointFix is not extracted to Altiris directory (or any subfolder to it).
Execute PFInstaller.exe file with administrative privileges (right-click > Run as administrator).If UAC is enabled then accept UAC if prompted. Select ‘Install Files’ option.
Old files will be automatically backuped to the Backup folder at the same location where PFInstaller is and replaced with the new ones. Log-file Log.txt will be created at the same location where PFInstaller is.
Close PFInstaller window.
On Client Side:
To apply fix on clients, Rollout Application Metering Plugin Upgrade/Install policy on all clients.
After successful execution of plugin upgrade/install policy, Application Metering Plugin should be upgraded/installed with version 7.5.3310.0 on client machines.
Pointfix is applicable for Inventory Solution 7.5 SP1 HF5 with following comment:
If pointfix to be applied to 7.5 SP1 HF5 without any inventory pointfixes, then filter “Windows Computers Requiring Application Metering Plug-in Upgrade” needs to be modified if for whatever reason it will be decided to remove this pointfix. After point fix is uninstalled above filter should be edityed and Application metering version should be corrected to 7.5.3300 to match AM agent version from default Inventory Solution 7.5 SP1 HF5
NB! Pointfix has following known issues with Windows XP and Vista clients. Please check any applies to your system before applying.
If metered application is located in UNC share and executed directly from UNC (or network drive mapped to same UNC), then on different OS it is reported as different file resource. For example, if metered file X is located at UNC path and executed on Windows XP or Windows Vista, its usage will be reported for File Resource A. For execution on Windows 7, Windows 8 or Windows 8.1, usage will be reported for File Resource B. This may affect metering accuracy, because specific file resource is associated to software component. In order to have accurate Software product usage metering both file resources A and B should be associated with corresponding component.
In 7.5 SP1 HF5 both XP and Vista did not report start events and monthly summary for applications located at UNC at all, so metering was not possible on those platforms if application is located in UNC share.