Re: Deploying Hotfixes, SPs and other Software

From: Sata (sata@infierno.cl)
Date: 11/29/01 

Message-ID: <00b401c178ec$f6901fe0$010aa8c0@quimera>
From: "Sata" <sata@infierno.cl>
To: <focus-ms@securityfocus.com>
Subject: Re: Deploying Hotfixes, SPs and other Software
Date: Thu, 29 Nov 2001 12:46:08 -0300

Im actually watching this very closely, I have your exact same problem =)
Anyway I have managed to fix some part of the problem through the customized
Office installation. In the section where you specify aditional aplications
to be installed, I specify Sp2 and whatever I like, like Acrobat Reader or
Winzip.

Sata

----- Original Message -----
From: <Thor@HammerofGod.com>
To: <focus-ms@securityfocus.com>
Sent: Thursday, November 29, 2001 11:37 AM
Subject: RE: Deploying Hotfixes, SPs and other Software

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> At 12:36 PM 11/28/2001 -0500, Pete Jacob wrote:
>
> >look in the resource kit...
> >
> >there are MS utilitys to create .MSI packages out of
> >anything... even non MS packages...
>
> Could you be a bit more specific? I have looked all through the resource
> kit and can't find any .msi package creation tools. Veritas has WinLite
> (or something) software that ships with Windows to create .msi files- but
> then, you are to start with a 'clean' PC, take Discovery snapshots and
> build the .msi files like that- a *royal* PITA. I have messaged around
> with it a bit, and tried other methods of building packages, but it seems
> that you have to buy the full version for any real functionality.
>
> I too think that hotfixes, SP's, and other install packages not being in
> MSI format is uncool. Why should I have to run SMS to distribute software
> when Group Policy allows me to do it so easily (and without additional
> cost, administration, and security concerns).
>
> Is anyone else actually *doing* this and happy with a method of easily
> creating .msi packages from .exe setup files?
>
> Thanks
> AD
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 7.1
>
> iQA/AwUBPAZIRohsmyD15h5gEQItPwCg0K62J8s4HKXqQvEPz/g+9d1YKuIAn209
> UaOc52DN1VXHeGkdRa4IUL3v
> =W1GF
> -----END PGP SIGNATURE-----
>

Relevant Pages

  • RE: Deploying Hotfixes, SPs and other Software
    ... Deploying Hotfixes, SPs and other Software ... even non MS packages... ... > creating .msi packages from .exe setup files? ...
    (Focus-Microsoft)
  • RE: Deploying Hotfixes, SPs and other Software
    ... Deploying Hotfixes, SPs and other Software ... there are MS utilitys to create .MSI packages out of ... even non MS packages... ...
    (Focus-Microsoft)
  • RE: Custom Exceptions in COM+
    ... automatically during proxy installation. ... you need modify the MSI packages to archieve this, ... You may try embed the dcomcnfg generated MSI into a setup project MSI using ... MSI and inject it into your own setup project. ...
    (microsoft.public.dotnet.framework.interop)
  • Problems with code signing
    ... the assemblies and the MSI packages) following Microsoft recomendations. ... timeout is reached) and consequently the whole installation is aborted. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: How to make an automated batch?
    ... Then you can use Group policy to deploy software. ... You only need for this .msi packages, but for example Office will have them by default. ... Or you can create on installation packages with InstallerLE http://technet.microsoft.com/en-us/library/bb742609.aspx ... Everyday i have to install the same app. ...
    (microsoft.public.win2000.networking)