/build/static/layout/Breadcrumb_cap_w.png

Same Customized MSI behaves differntly on installation

The Msi in concern is McAfee Virusscan 8.0i

Hi All,

The Customized Msi is already having the below mentioned registry entries with values as in the original Msi.
The problem is the same customized Msi is behaving differently when installed. There are two scenarios

Installation commandline : msiexec /I “msiname.msi” ADDLOCAL=All /qb used in both cases



1. The customized Msi installs with all the below mentioned registry entries but no values

In this scenario the “Virus Console shortcut” window has 6 tasks ( 2 additional being Scan All Fixed Disks and AutoUpdate).

I tried to create a script that edits the registry and adds value to the “szMoveFolder” as Quarantine.This seems to work


2. The customized Msi installs with all the below mentioned registry entries also with required values


In this scenario the “Virus Console shortcut” window has 4 tasks . There is no problem with this shortcut as the registry entry
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\Shared Components\On Access Scanner\Vshield\E-Mail Scan\ActionOptions]
szMoveFolder = Quarantine


The problem is with the shortcut Virusscan On-Demand scan, once this shortcut is clicked the application self heals and finally the shortcut launches flushing the above registry entry “szMoveFolder” thus leaving the Move To Folder in the “On Delivery Email scan” task in the Virusscan Console.

FYI

Eventlog shows the application is in search of

EventId 1004

HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\TVD\VirusScan Enterprise\CurrentVersion\Tasks\{818C7543-358A-4C84-899A-14334EMS4BGS}\ \dwProgramHeuristicsLevel does not exist.
Component - DefaultOnDemandScanTask_REG
Feature - OnDemandScanner


As both these scenarios are being caused by the same customized Msi and we are not sure on which installation which scenario occurs.

The only notable change from the original vendor MSI and the customized MSI is the deletion of the component – RemoveCurrentUser_REG having HKCU entry.

Key: HKCU\SOFTWARE\Network Associates\TVD\Shared Components\On Demand Scanner Name : ‘-‘
‘-‘ Uninstall Only
Key: HKCU\SOFTWARE\Network Associates\TVD\VirusScan Enterprise Name: ‘-‘
‘-‘ Uninstall Only


Thanks and Regards,
Charan.

0 Comments   [ + ] Show comments

Answers (6)

Posted by: akhlaque 19 years ago
Orange Senior Belt
0
Hi charan,

Its not clear whether ur original msi is also having this prob or its working fine.
And the original msi was repackage?
Posted by: wiseapp 19 years ago
Second Degree Green Belt
0
Hi People:

Akhlaque I believe his first MSI that is original MSI is working whereas seems to be a problem with customised MSI, am I right Charan? Do let us know to help you out.
Posted by: charan 19 years ago
Orange Belt
0
Yes Bhupesh, you are right..
The only difference i see from the original vendor MSI and my Customised Msi are shortcuts are advertised in my customization.

Thanks,
Charan.
Posted by: wiseapp 19 years ago
Second Degree Green Belt
0
Hi Charan:

Thanks for responding, anyways I think the customised MSI holds keypath to the registry that you are modifying after running your script. Now what happens is when you try to start the application and the registry key has been modified the system runs a self-healing option and the registry is restored back to original what I would suggest is instead of creating a customised MSI(Repackaging) try to create transforms for the same or create a wrapper that will call this installation. I hope this would answer your doubts. However in case should you like to have any further clarifications regarding the same kindly revert back.
Posted by: charan 19 years ago
Orange Belt
0
We are customizing the Msi and creating transforms by taking a difference between base Msi (original vendor MSi) and the customized Msi.
Posted by: wiseapp 19 years ago
Second Degree Green Belt
0
Hi Charan:

I believe when you are creating a transform it's same as customising an MSI indirectly. However if you creating a transform what makes you differetiate between the base MSI and your customised MSI, If you want only the registry entries to be customised you can do that in the base MSI and creating a MST corresponding to your base MSI.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ