Software Deployment

Hi Peter,
could you be more specific, please.
Please tell us, what MUI's you are talking about, here.
Regards, Nick

Hi Nick, thanx for such quick reply!

Ok, I need to pack the French, German, Italian, Norweigan and Swedish Mui, with swedish as default. (FR.MUI, GER.MUI, IT.MUI, NO.MUI, SV.MUI)

To get the swedish default this should be the string for muisetup.exe /i 0407 0410 040c 0414 /d 041d /s /r
The thing is that we're deploying it using SysCent. Conf.mgr so i would need it to be a msi file so we can distribute the software through distibutionpoints.

Should i try to make a capture of the installation ? Using wise ?

Why do you think you're restricted to MSIs with SCCM? One can pass any command line one likes, be that BAT/CMD, EXE, MSI. Certainly I just pushed out Visio 2007 with a command file as the executable...

Ok, well i've been told that there could be broblems with uninstalling if you don't use a MSI file. But im very new to packaging and deployment so i really don't know. How would you deploy it ? The reason that i would like a MSI file (so i can run it silently) is that im deploying it with a OS image and the pop-ups in the MUI when we deploy via exe halts the installation.

Hi Peter,
we still don't know of which MUI package we are talking about.
However, when looking at your posts, i assume it's XP's MUI.
Here is a list of all things needed to make a clean MUI experience for deu/fra/ita:
muisetup.exe /i 0407 040c 0410 /d 0407 /r /s
wmp11setup_muideu.exe /q
wmp11setup_muifra.exe /q
wmp11setup_muiita.exe /q
mm21_muideu.exe /q
mm21_muifra.exe /q
mm21_muiita.exe /q
WindowsXP-KB841625-x86MUI-DEU.exe /quiet /norestart
WindowsXP-KB841625-x86MUI-FRA.exe /quiet /norestart
WindowsXP-KB841625-x86MUI-ITA.exe /quiet /norestart
sp3\update\update.exe /quiet /norestart

That means: XP MUI, Mediaplayer MUI, MovieMaker MUI, Help Update and the XP-MUI sp3.

Hope, this gives you a starter.
Regards, Nick

AAAAAaaaaaaaaaaaaaaahhhhhhhhh! LOTS and LOTS of command lines! :)

Straight away I'd say avoid re-packaging into MSIs. Instead, build a (robust) script or command file (I prefer the former, as one can build in much better error-trapping) and, when you're sure it does the job, use it in your SCCM command line.

As for uninstall, I guess that, once these doo-hickies are installed, you'll find their uninstall command lines in the relevant 'Uninstall' entries in the registry.Once you have those, you can build a companion uninstall script.