Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

applying update using an .msi package

Status
Not open for further replies.

primate

IS-IT--Management
Jan 6, 2003
123
GB
Hi,

I'm trying to deploy a MS security patch using an .msi package via a GPO.

I created the .msi file using WinInstall LE.

Upon deployment the package appears to install fine but the files that its supposed to update do not actually get updated.

The correct updated files exist in the source for the .msi

If you apply the patch manually the machine requires a reboot since it replaces open files, however the machine does not reboot when the .msi package is applied, and even if you subsequently reboot manually the files don't appear to be updated.

Has anyone got any ideas? I really need some help with this, I have been struggling with .msi's for some time, my network is too big for me to be able to do it all manually and I'm getting genuinely pi$$ed off with the whole thing!
 
I've learned that the softwares and patches that have the most trouble with MSI packages are the ones for the Windows operation system itself!!

I gave up also, but you do have 2 good choices that I know of:

1) There are batch commands you can run to place it in Silent or Quiet mode.

I basically have one large batch file that runs all the patches before Service Pack 4. It contains about 20 patches. Since the installation of service pack 4, the batch file has dropped to about 3 files now. You can run a command prompt and do a /? after the filename to get the commands available. Mostly, /Q (quiet) and /u (Unattended) are available for most of them.

2) Take a look at Microsoft Software Update Service (SUS). It's the software update you use in Windows Update on the Microsoft Web Site, but you can set it up on your servers. You can then program your clients to auto-update or not. The fun part is, you can distribute the new client (the one that replaces the current Windows Update one) via an MSI package.



"In space, nobody can hear you click..."
 
Thanks for your response, I had planned on setting up SUS later in the year, I was just looking for a "quick" way to fill the gap in the meatime but now I am starting to think I shouldn't have bothered :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top