I'm deploying Symantec AV 10.0 which has got many features like registry scanning, for some reason, and immediately after reboot a full system scan runs in the background and triggers the msi installer to fix a missing component in the registry.
Does any body knows how the installer is triggered due to a missing registry component , and is there a way to get rid of the installer screen slider window to disappear and run completely in the background without the user knowing that some thing is getting fixed in his machine, because this will cause floods of calls to our help desk as we are deploying the software to more than 3000 workstation
please help
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Need more info really.. have you repackaged the application or used the vendor MSI? Packaging antivirus is always a bit of a mine field - if you've snapped the install you need very careful about what you include / exclude from your MSI.

Not sure you make make the repair run silently. Your best bet is to find out what component has a broken keypath and therefore causing the repair - by running event viewer and looking in the application log...

Cheers,
Rob.
Answered 08/28/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
for the Antivirus, I used the vendor msi, but the applications that report installer errors in the event log are packaged using Altiris software, another department is handling it, do you mean that there is a way to trace that error logged in the event log by modifying the package used to install those applications,
there are six of those applications that log this error (Maximo, Business objects, Smart Stream 6.5, etc...)
All of them are deployed using Altiris Software
thanks for your response
Answered 08/28/2005 by: elshaieb
Yellow Belt

Please log in to comment
0
Yes, the event log will give you a product code which you can use to identify the package which is self-healing and also a component GUID showing which actual component has a broken keypath.

You need to open your MSI either in Orca or in table view in Wise - the product code is in the property table and the component GUIDs are in the component table. Once you've found the offender you should be able to investigate and resolve the problem by looking at the keypath (either a file or registry key in that package) set on for that component. It's the keypath which is missing and causing the repair but you (or the other department [;)]) need to identify why...

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/searching_for_a_broken_feature_or_component.asp

Regards,
Rob.
Answered 08/29/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity