Re: Creating an MSI winth Winistall
- From: "sherrylkissinger@xxxxxxxxx" <sherrylkissinger@xxxxxxxxx>
- Date: Wed, 25 Jul 2007 00:08:01 -0000
I'm not familiar with wininstall; but I'm guessing that you are
repackaging the vendor's applications into an .msi format, and then
deploying that with SMS?
Personally, it's rare these days when I have to repackage something.
Most vendors do now provide an .MSI--sometimes it's wrapped inside of
a setup.exe (run their setup natively, and then go look in %temp% for
the .msi). If it's not an .msi, but is an installshield or wise .exe;
sometimes you can get away with setup.exe /s (or -s or -silent) to
deploy the vendor's setup natively in SMS.
One resource you might want to look at is www.appdeploy.com. Many
people post how they setup a deployment.
In general, these days I would avoid repackaging unless there was no
alternative. I can definitely see where a vendor-supplied upgrade or
patch will fail if you deployed a repackage of the original
application.
On Jul 24, 2:20 pm, MSAdmin <MSAd...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I can create msi's with wininstall for various programs and have been able to
push them to workstations as MSI's using SMS. However, when I look in add
remove programs on the PC I pushed it to, the application is listed as the
MSI. When I install the same application manually at the PC, the application
is listed as the app in add/remove programs. The app works either if I push
it as an msi I created or installed manually. My question is as an msi, will
this cause issues down then line, as far as upgrades and patches for the
application? Many of these apps get patched frequently.
Thanks
.
- Prev by Date: RE: packaged received but didn't run
- Next by Date: Re: One program fails in dependency chain
- Previous by thread: RE: packaged received but didn't run
- Next by thread: Re: One program fails in dependency chain
- Index(es):
Relevant Pages
|
Loading
