The primary reason is called self-healing, when circumstances require
rerunning part or all of the install. The common cause is user-based
registry keys or profile data that must be initialized when a user opens the
software for the first time. Apps that are completely machine-based, not
user-based, rarely if ever run into this.
Steve
----- Original Message -----
From: "Ben Scott" <[EMAIL PROTECTED]>
To: "NT System Admin Issues" <[email protected]>
Sent: Sunday, January 27, 2008 2:44 PM
Subject: Re: Updating Symantec client program
On Jan 26, 2008 12:55 AM, HELP_PC <[EMAIL PROTECTED]> wrote:
I don't remember that the client need the source.
I don't think it's the SAV client itself; I think it's the Microsoft
Installer engine which wants original MSI files sometimes. I've seen
this for all sorts of software, including Microsoft Office. Not
always, though -- it's inconsistent. I seem to recall there are some
MSKB articles which describe possible causes and what developers can
do to avoid it. IIRC, YMMV, etc.
-- Ben
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
