Re: *Completely* silent IE Patch distributions

From: Chuck Stevens (Chuck.Stevens@pfcenter.com)
Date: 08/09/02 

From: Chuck.Stevens@pfcenter.com (Chuck Stevens)
Date: 9 Aug 2002 08:56:56 -0700

chris@nospam.com wrote in message news:<nk96lu8gt81mpfnohekotnnlfumqnh49a7@4ax.com>...
> On 8 Aug 2002 12:17:00 -0700, Chuck.Stevens@pfcenter.com (Chuck
> Stevens) wrote:
>
> >chris@nospam.com wrote in message news:<diu3lu44ltg388m9r85dhj0rlt91u41koh@4ax.com>...
> >> On 7 Aug 2002 09:48:39 -0700, Chuck.Stevens@pfcenter.com (Chuck
> >> Stevens) wrote:
> >>
> >> >This question has been posed several times, but I have never seen an
> >> >actual answer. So I will as again. ;)
> >> >
> >> >I wish to use SMS to distribute the latest IE cumulative patch,
> >> >q321232.exe.
> >> >
> >> >The correct command line for a silent installation with no reboot is:
> >> >
> >> >q321232.exe /q:a /r:n
> >> >
> >> >HOWEVER, running the patch this way still displayes a file-copy
> >> >progress box, with a big Cancel button on it. I want no messages or
> >> >dialogs displayed to the user whatsoever. How do I go about this?
> >>
> >>
> >> If you're pushing this with SMS, it will get run under a different
> >> user context than the currently logged in user. This means that the
> >> user will not actually see the copy dialog box.
> >>
> >> I pushed Q32123 out using the same syntax, using psexec, and it was
> >> completely silent.
> >>
> >> -Chris
> >
> >
> >Unfortunately, this isn't completely true. Using SMS to push q321232
> >results in that file copy progress bar being displayed, regardless of
> >what context it runs in. I've tested that myself several times.
> >
> >Now, using PSEXEC is a different story. I'll look into that.
>
> I guess maybe because the SMS client is running in the system context?

The installation package can run under one of three different
contexts, depending on how you configure it:

1. The User's context. We can't use this, since users aren't
Administrators.
2. The SMSCliToknAcct& account. We can't use this, since this account
doesn't have Domain access
3. The Windows NT Client Software Installation account. This is the
account we use; it has domain access and is a local admin.

Chuck