New Quicktime MSI creation Problems

Installer issues this message when you try to install so called "small update" or "minor upgrade".

See http://msdn.microsoft.com/en-us/library/aa371855%28VS.85%29.aspx about how to apply such patch - read from "For information on how to apply a small update". The same applies to minor upgrades as well.

If you deployed the original version from admin installation, http://support.microsoft.com/kb/226936 tells how to deploy the patch.

I'm not sure how to create a .msp for quicktime, I've always just used the .msi via gpo's.  I set the old msi to uninstall and the new msi to install.  It's been so long since I've messed with creating an .msp I've forgotten how.  The current install was pushed via gpo.

This question seems to give answer. Also, Google is your friend.

You won't be able to distribute patch by gpo, only by login script. The best is to patch original administrative installation and then re-deploy it. The ability to patch later is one of the main reasons for using admin installation rather than compressed MSI. This also ensures that future installations will install updated version, otherwise you will have to remember to reapply the patch every time you install this product for someone.

In this light, it's intresting to note that many of Microsoft installations don't have administrative sequence at all, so admin image can't be created and hence patch can't be applied. Access Runtime and Office Compatibility Pack are two notable examples, and both had later service packs released. Quite a nightmare. I even sent an inquiry to MS, why such blatant violation of all deployment standards; unsurprisingly, the response started with the word "Unfortunately,..." (after thanking for being microsoft customer).

Okay, well I can get the .exe from apple or I can get the .msi from the temp file.  What's my best option?

you can't deploy the exe by gpo, so you need the msi. Either from apple, or extracted by the exe.

Note that if it's involving installshield/installscript, msi will refuse to work with the exe.

I either use Orca to edite the MSI DB or another method is using a transform file.

Orca.exe is a FREE database table editor for creating and editing Windows Installer packages and merge modules.
http://msdn.microsoft.com/library/en-us/msi/setup/orca_exe.asp
MsiTran.exe is a FREE tool to generate or apply a transform file.
http://msdn.microsoft.com/library/en-us/msi/setup/msitran_exe.asp

If you use a transform file then your command line would be similar to
msiexec /i QuickTime.msi /t 1031.MST ISSETUPDRIVEN=1

> ISSETUPDRIVEN=1
unless they really use installscript in their project.

thesupplyguy26

this assumes a logon script is used to install the msi?  If so, can a windows batch file call the sysvol via UNC?  \\domain\sysvol\domain\QT.msi

Thanks

No, thi is doing the install purely with SMS. No logon script necessary. I do not brleve you can call the sysvol via a batch.

SCCM 2007 - During the Package Wizard setup, does the "command line field" require an .exe or can we also use a .msi (please see attached command line image). Reason asking is because later on in the SCCM package/program wizard, we have the option to also add a .msi. Apple has both a .exe and an .msi to choose from. (see attached quicktime image)

Do we need to modify the command line with a transform file.
Example - command line would be similar to
msiexec /i QuickTime.msi /t 1031.MST ISSETUPDRIVEN=1
command-line.JPG
quicktime.JPG

You are using SMS. Without SMS just using domain gpo software distribution, I am sure it would work if you selected to upgrade the previous installation and set it to uninstall the previous one.

if you want to deploy it by GPO, then do this:

1. you must have old quicktime in the GPO, and having users' quicktime installed from there, i.e. from "add new programs", or assigned. Even if it is not, you can do it now - assign it, and it will be re-cached for the users. You can even create wmi filter and install it only for those who already have it.

2. then put in place new quicktime msi, and on the page "upgrades" specify that it upgrades that old version, and specify "replace" - then gpo will first uninstall the old verison and then install the new one.