Distributing MSI files using SMS2 Problems

[DubDave]

Hi

I'm trying to distribute MSI files to a numebr of desktops using SMS2 ...

Methods
1) Create MSI file (using wise installer )
2) Create Package
3) Create Program within the Package and distribute to Site Server's (sms2 service pk 2)
3) Associate Package with Collection
4) Setup Advertisement and set to mandatory ( As soon as possible




but I have the following problems :

Method 1
If I set the program command line to the MSI file the
Application fails to install as stated with the Advertised Program Manager.

If also fails to install with method 2

Method 2

I've wrapped the MSI within an exe file created with sms installer. The wrapper copies the MSI file to the temp dir execute's the MSI file waits to finish and then deletes the MSI file

I have tested the wrapper by running directly on the pc and all is successful ... So can anyone tell me how to setup a successful install of msi files using sms2 to distribute

Cheers

DubDave

 

[neilnick]

Dave,
Try something like this: Make up 3 ipf files
Copy.ipf, setup.ipf, remove.ipf

In the Copy.ipf put something like:
install file ..\setup.exe to %DIR%\setup.exe
install file ..\remove.exe to %DIR\remove.exe
install file ..\App1.msi to %DIR%\App1.msi
Execute setup.exe

set %DIR% to be something like c:\Program Files\cache\App1
This gets these files onto your client m/c

Now in setup.ipf put a line like:
Execute msiexec.exe /i %DIR%\App1.exe (wait)

And in remove.ipf put aline like:
Execute msiexec.exe /X %DIR%\App1.exe /qb(wait)
other line to remove bits and bats left.

make %DIR% were you want install to go

Idea is this leaves a cache on client were only engineers
can find stuff to repair/ reinstall/ remove app etc

This is the 'bones' I leave you to flesh it out.
Cheers

neilnick

 

[Farns]

It sounds like your biggest issue is that you might not have specified the msiexec executable before your MSI in your program command line. It should look something like "msiexec.exe /i yourmsi.msi". SMS isn't always capable of starting the package off of the MSI directly.

As far as keeping a local cache, I would propose keeping the .msi on a file server and utilizing the SOURCELIST property to redirect installs back to the stable network location. We do this with tens of thousands of machines and it works great.

 

[neilnick]

NeilNick
Sorry typo in previous post I said: 'App1.msi'
at top of text but put 'App1.exe' in sample lines?

Should be:
Execute msiexec.exe /i %DIR%\App1.msi (wait)

and:

Execute msiexec.exe /X %DIR%\App1.msi /qb(wait)

Thanks to 'Farns' for correction.