deploying registry changes with an MSI

[Bugs]

Hi All,

Iv been given the task of packaging the audacity lame codec so it can be deployed so our version of audacity (1.2.6) can save as MP3, we dont want to upgrade as yet as this software is very widespread across our RM CC4 multi-site network.

Iv created an MSI using the witem installer software which drop the codec files into "C:\program Files\Audacity\Audacity 1.2.6\Plug-Ins\" and also write two registry keys one to the HKCU hive giving the location of the Lame.dll file, also in HKLM under the active setup theres a key detailing the MSI's GUID and to copy anything detailed in the HKCU to all users.

The first couple of tests I did seemed to work OK, when logging in I got a little Audacity setup screen with a progress bar and it found the lame codec, great I thought but next time I came to test it didnt display any setup dialogues on login and couldnt locate the lame codec, I tried again on a different machine and this one did display the dialogue on login but then asked for the installation source MSI file.

It all just seems a bit hit and miss, does anyone have a concrete solution for deploying the lame codec?

Thanks

[glennda]

Personally when creating the MSI for Audacity I also installed Lame so the MSI contained both softwares.

[Bugs]

well personally I would have done that but it has been deployed now minus the codec so I need to create another package to drop the codec in place and setup so audacity can locate it

[glennda]

Ah ok - Do you have access to create startup scripts with RM CCx? I've never used it but you should be able to change the reg keys and then export them on a single machine and use a startup script like

If exist C:\lamereg.txt goto end
reg import filename.reg
echo done>C:\lamereg.txt

end

Basicly check if i have done this before if yes go to the end if not
import reg file
say i have done it
end

[Bugs]

I dont think my line manager would go for that, he'd prefer all changes to happen at installation, sorry to be a pain!

[irsprint84]

or use APP V! well if you re on volume licensing

[sted]

Fire out reg setting with gpp
Setting the key in users\default might work but i dont believe so

[SYNACK]

You could even make an ADM file to push out the reg setting via GPO, I think the Audiacity stuff is per user only (stupid) so pushing it via GPO may be faster than an MSI triggering on every single logon to 'repair' the reg settings for each an every user with the ensuing prompts and waiting.

[SYNACK]

Here's a guide: Guide to Creating Custom ADM Files for GPO Distribution

[Mr.Ben]

How about just upgrading to version 2?


The new version checks the 'Plugins' Directory each time it starts, allowing you to just copy new ones into the directory and they immediately work.

[Bugs]

Thanks SYNACK, but I need to deploy the reg settings via the MSI really, Mr Ben - I do have this package already deployed out but version 1.2.6 is also deployed and just for a quick MP3 fix I wanted to deploy the Lame codec to these machines.

[Bugs]

UPDATE: Iv re-created the MSI using Witem Installer and it doesnt seem to recognise any of the GUID's, when I login the small config runs but then says "this action is only available to installed programs" I tried using Advanced Installer but this one changes the GUIS everytime so I cant get it into the setup without changing it.