My client is currently working on an upgrade to SMS 2003, I believe that a requirement of this is Windows Installer 3.0 onwards on the clients. Therefore we are planning to upgrade all clients in the very near future. Any horror stories, or anything in particular we should look out for in this process.

In particular I am interested in any packages that failed to work afterwards etc.

Many Thanks
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I had the lockdown of our security eventlog prevent Windows Installer 3.1 from installing or at least that is what the deployment team told me. One site I am at is running 3.0 the other is slowly migrating 3.1. No horror stories just a deployment hurdle.

I should note that Windows Installer 3.1 fixed an obscure error I was getting rolling out some patches for Aspen Icarus.
Answered 12/08/2005 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
I haven't run into any problems yet but here is some stuff I have found out there on this.

Good Q article on it. Windows Installer 3.1 v2 (3.1.4000.2435)

From another page:

Note for users of previous versions of the Windows Installer: The new Windows Installer redistributable follows a new naming convention that contains a knowledge base reference so it is easier to identify which version of the Windows Installer will be installed. The previous naming convention, INSTMSI.EXE, will no longer be used.
Answered 12/08/2005 by: Foleymon
Orange Senior Belt

Please log in to comment
As far as I know Windows Installer 3 are only compatible with Windows XP, Windows Server 2003 and Windows 2000 with SP3 or later. It´s mentioned in the KB, but i just wanted you to know.

Answered 12/09/2005 by: jonasm
Blue Belt

Please log in to comment