I've recently set up an Openfire server and I've settled on Jitsi as our
client, given that I can work out these last few kinks.
We're predominately a Windows 7 environment with Server 2008 R2 as our DC.
The easiest way to actually get the software onto all 75 workstations
be to push the MSI out through Group Policy, but then each client would
to be configured individually. Is there a configuration file in the MSI
I can edit before I deploy it so that certain options are already set on
install, such as starting Jitsi on Windows startup and setting the
It's not yet possible with msi-parameters only. I use a logon-script at work
to place write the two provisioning lines into
%appdata%\jitsi\sip-communicator.properties. The .msi has two properties for
the shortcuts  and the autostart is a user-registry key which you could
control through a Group Policy Preference (Key:
HKCU\Software\Microsoft\Windows\CurrentVersion\Run, Name: Jitsi, value:
We're currently working on providing a way to supply the provisioning URL as
an MSI property and it will probably make it into the next stable release.