Installing a package from another installer

Mike Johnson

I'm not sure if this can be done or not. I have a Setup file (made with a
third party setup program) used for updates that needs to install MSI
packages on occasions. I don't have an issue with the setup file doing this,
but with the permissions of the MSI package.

The update setup file is downloaded via FTP by the software on the client
machine and run automatically by the auto updater that is part of the
software. I have a need to install the SQL Native Client package, on the
next update, on the client machines that do not have it installed. The
client machines (about 800 of them) are scattered throughout North America
and do not have Admin privileges. My setup program installs the SQL Native
Client package in quiet mode without a problem on clients were a local IT
person can intervene and allow the installation. However, most of the remote
offices do not have IT personnel in house to allow the setup utility to run
the MSI package.

I have looked at all the Windows Installer switches and saw the /a switch
for Admin patch installs, but my understanding of that switch is that the
patch/package has to be on a server that is accessible by all users.
Unfortunately, this is not the case here. So, my question is, "Is there any
way that I can make a package requiring Admin rights install on a client
machine that does not have Admin rights?"

Sorry for the lengthily post, but I wanted to make this as clear as I could.

Thanks,

Phil Wilson

The short answer (and I don't know all the details) is to use a group policy
object. I don't recall the exact terminilogy, but I think the "assign to the
machine" is the one you want. The other mode is "publish", but I think
that's the per-user install.
--
Phil Wilson

"Mike Johnson" <.com> wrote in message
news:.gbl...
> I'm not sure if this can be done or not. I have a Setup file (made with a
> third party setup program) used for updates that needs to install MSI
> packages on occasions. I don't have an issue with the setup file doing
> this,
> but with the permissions of the MSI package.
>
> The update setup file is downloaded via FTP by the software on the client
> machine and run automatically by the auto updater that is part of the
> software. I have a need to install the SQL Native Client package, on the
> next update, on the client machines that do not have it installed. The
> client machines (about 800 of them) are scattered throughout North America
> and do not have Admin privileges. My setup program installs the SQL Native
> Client package in quiet mode without a problem on clients were a local IT
> person can intervene and allow the installation. However, most of the
> remote
> offices do not have IT personnel in house to allow the setup utility to
> run
> the MSI package.
>
> I have looked at all the Windows Installer switches and saw the /a switch
> for Admin patch installs, but my understanding of that switch is that the
> patch/package has to be on a server that is accessible by all users.
> Unfortunately, this is not the case here. So, my question is, "Is there
> any
> way that I can make a package requiring Admin rights install on a client
> machine that does not have Admin rights?"
>
> Sorry for the lengthily post, but I wanted to make this as clear as I
> could.
>
> Thanks,
>
>
>

Mike Johnson

Thanks Phil, I'll look into that and give it a try and see how to implement
it with the installer that I am using.

Mike

"Phil Wilson" <.net> wrote in message
news:.gbl...
> The short answer (and I don't know all the details) is to use a group
policy
> object. I don't recall the exact terminilogy, but I think the "assign to
the
> machine" is the one you want. The other mode is "publish", but I think
> that's the per-user install.
> --
> Phil Wilson
>
> "Mike Johnson" <.com> wrote in message
> news:.gbl...
> > I'm not sure if this can be done or not. I have a Setup file (made with
a
> > third party setup program) used for updates that needs to install MSI
> > packages on occasions. I don't have an issue with the setup file doing
> > this,
> > but with the permissions of the MSI package.
> >
> > The update setup file is downloaded via FTP by the software on the
client
> > machine and run automatically by the auto updater that is part of the
> > software. I have a need to install the SQL Native Client package, on the
> > next update, on the client machines that do not have it installed. The
> > client machines (about 800 of them) are scattered throughout North
America
> > and do not have Admin privileges. My setup program installs the SQL
Native
> > Client package in quiet mode without a problem on clients were a local
IT
> > person can intervene and allow the installation. However, most of the
> > remote
> > offices do not have IT personnel in house to allow the setup utility to
> > run
> > the MSI package.
> >
> > I have looked at all the Windows Installer switches and saw the /a
switch
> > for Admin patch installs, but my understanding of that switch is that
the
> > patch/package has to be on a server that is accessible by all users.
> > Unfortunately, this is not the case here. So, my question is, "Is there
> > any
> > way that I can make a package requiring Admin rights install on a client
> > machine that does not have Admin rights?"
> >
> > Sorry for the lengthily post, but I wanted to make this as clear as I
> > could.
> >
> > Thanks,
> >
> >
> >
>
>