Software Deployment

How are you planning to deploy?

For example, you can do it with Group Policy, just add them in the correct order to the policy object and you'll be away!
SMS\SCCM\Altiris can deploy applications in a specified order also.

If i deploy it, i deploy with sccm...
The problem is in some cases, is not a deployment instalation.
Just is for install it in reduced number of computers.

Thanks for your answer ¡¡¡¡¡¡¡

So in SCCM, create a software package with as many MSI files in it as you require. Create install and uninstall programs for each.
Create a collection with the parameters you require to populate it, and advertise the programs you require to the collection.

If you make your collections query based, you can get them to reflect installation or uninstall actions based on what you require.

Deploytech, i know for deploy software with sccm..

I want to chain msi, to install without sccm or gpo etc...

To a user can install it manually....

Righto. Without a script to install, or using your deployment solution to control the install, I've never looked into it.
It kind of defeats the purpose of having SCCM.

Good luck!

Jaimie

In SCCM when you create your "package" you can add as many programs you want (MSI's etc)in that package.

All you need to do when setting up your programs is point the advertisement to the last install you want to run. Then on each program make sure you have selected "Run this program first" and then point to or chain to each previous install.

We often have 6 or so installs chained from the same single SCCM install advertisement.

This is used to install all your dependancies first, for example oracle client etc..

.

If it is for a reduced number then make a small collection and deploy.

If it is even smaller then deploy via remote control.

I know this...
But i want chain multiple msi in one...
Without sccm...
Thanks all for your replies.

Depending on the MSI version located on the clients you want to install the package(s) on you could either create a nested/concurrent install or chain the MSIs.
Mostly we like to have them in different packages to handle them separately. An MSI that is installed by a nested install cannot be managed as-is, you would need to ex. remove the whole package that installs all the nested MSIs. Nested install is considered as a bad method to install multiple packages meaning not recommended.

Ok angelD,I thought nested install it was a good idea ¡¡¡
The goal is to say, to have several separate packages...
If nested install is nor recommended, i go to try chain msi, but i think is not easy...
I have read The clients needs windows installer 4.5 and this is not supported to windows 2000, i have some computers with w2k..
I go to investigate but i think is not possible.
Thanks AngelD

Hello escubi,

I saw this post and I am looking for the exact same info you are. After a bit of searching, I found this article on the Microsoft Support site at:
http://support.microsoft.com/kb/828947

If you are using the standard ms SETUP.EXE bootstrap file, it is possible to chain installations to other EXE or MSI files by placing additional entries in the SETUP.EXE settings information (SETUP.INI) file. Specifically, adding additional [ChainedInstall_X] (where X is 1, 2, 3, etc..) entries allows the developer to supply the additional packages to be chained to the original install package.

The following is an example of the SETUP.INI file that can be used:


; SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must be in
; the same folder as Setup.exe, and both must be in the root of the installation
; tree.
MSI=\Files\YourAppName_Setup.msi

[Product]
ProductCode={F077B3FD-992E-4030-AE84-4FE6F2DD547E}
ProductName=YourAppName
ProductVersion=1.0.100608
SkipLangCheck=1

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
Display=full
CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name unique
;Type=vpiwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=501
WindowsBuild_1=2600
ServicePackLevel_2

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE <predefined> Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end of
; setup [0,1]
;CDCACHE=auto
;LOCALCACHEDRIVE=C:\
;DELETABLECACHE=1
;PURGE=0

[ChainedInstall_1]
TaskName=Program 2 Setup
TaskType=exe
Path=\Files\Program2_Setup.exe
IgnoreReturnValue=0
cmdline=/passive


In the previous code, notice that a "[ChainedInstall_1]" entry supplies the information for another EXE file to be run - "Program2_Setup.exe". This is run once the initial installation has been completed. And, this could also be another MSI file as well. And it looks like you can just keep adding entries for each additional item you need chained in the package.

Anyway, I actually found this information after reading this post and then came back to add the reply, because none of the other replies in the list seemed like the option that you (or I) was looking for...so I hope this helps.

A friend in the Matrix...
GeoffreyG