[jitsi-users] MSI and Pre-Provisioning


#1

I am a relatively new user of Jitsi. Thank you for all of your hard work.

I was thrilled to see that the new 2.4 version (I'm using
file jitsi-2.4.4997-x64.msi) allows me to "pre-provision Windows
installations through MSI params."

However, when conduct a clean installation with pre-provisioning using the
"PROV_URL" parameter, it does not appear to actually do the provisioning.

I have tried to input the provisioning parameters from the command line and
also through creating an MST transform with Orca.

I also was sure to test my provisioning URL, script, and parameters after
Jitsi had already been installed, and it does, in fact, successfully
provision.

Here is where I attempt to speculate, and I apologize if I am off base:

I did note that after doing a clean installation from the MSI, the
properties file is not created until AFTER Jitsi is run for the first time.
Unless I am missing something, Jitsi can't be pre-provisioned unless the
installation process creates the properties file and places the
provisioning commands in this file.

I welcome your comments and criticism if I have misunderstood the process.

Thank you for your time and assistance,

Sam


#2

The idea is that a file named jitsi-default-overrides.properties gets created in c:\Program Files\Jitsi\lib. Properties in there are read before the user specific ones from %appdata%\Jitsi.

Are you sure this file is not there?

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

···

On 10.01.2014, at 01:05, "Sam Schreiber" <samsmove@gmail.com> wrote:

I am a relatively new user of Jitsi. Thank you for all of your hard work.

I was thrilled to see that the new 2.4 version (I'm using file jitsi-2.4.4997-x64.msi) allows me to "pre-provision Windows installations through MSI params."

However, when conduct a clean installation with pre-provisioning using the "PROV_URL" parameter, it does not appear to actually do the provisioning.

I have tried to input the provisioning parameters from the command line and also through creating an MST transform with Orca.

I also was sure to test my provisioning URL, script, and parameters after Jitsi had already been installed, and it does, in fact, successfully provision.

Here is where I attempt to speculate, and I apologize if I am off base:

I did note that after doing a clean installation from the MSI, the properties file is not created until AFTER Jitsi is run for the first time. Unless I am missing something, Jitsi can't be pre-provisioned unless the installation process creates the properties file and places the provisioning commands in this file.

I welcome your comments and criticism if I have misunderstood the process.

Thank you for your time and assistance,

Sam
_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

Correct. "Jitsi-default-overrides.properties" does not seem to be created
in my Jitsi\lib folder, regardless of the installation method or parameters
I input.
I made multiple clean installation attempts again with either command line
parameters or through a transform MST file.

···

On Thu, Jan 9, 2014 at 11:22 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

The idea is that a file named jitsi-default-overrides.properties gets
created in c:\Program Files\Jitsi\lib. Properties in there are read before
the user specific ones from %appdata%\Jitsi.

Are you sure this file is not there?

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 10.01.2014, at 01:05, "Sam Schreiber" <samsmove@gmail.com> wrote:

I am a relatively new user of Jitsi. Thank you for all of your hard work.

I was thrilled to see that the new 2.4 version (I'm using
file jitsi-2.4.4997-x64.msi) allows me to "pre-provision Windows
installations through MSI params."

However, when conduct a clean installation with pre-provisioning using the
"PROV_URL" parameter, it does not appear to actually do the provisioning.

I have tried to input the provisioning parameters from the command line
and also through creating an MST transform with Orca.

I also was sure to test my provisioning URL, script, and parameters after
Jitsi had already been installed, and it does, in fact, successfully
provision.

Here is where I attempt to speculate, and I apologize if I am off base:

I did note that after doing a clean installation from the MSI, the
properties file is not created until AFTER Jitsi is run for the first time.
Unless I am missing something, Jitsi can't be pre-provisioned unless the
installation process creates the properties file and places the
provisioning commands in this file.

I welcome your comments and criticism if I have misunderstood the process.

Thank you for your time and assistance,

Sam

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#4

Correct. "Jitsi-default-overrides.properties" does not seem to be
created in my Jitsi\lib folder, regardless of the installation method or
parameters I input. I made multiple clean installation attempts again
with either command line parameters or through a transform MST file.

I'm sorry, there's a bug in the MSI. The manual [1] has been updated to
provide a solution for the stable builds, and I'm working on a fix for the
nightlies.

In case you're curious: when I developed that, I didn't include the JRE in
my local builds. As the JRE has a lib folder as well,
jitsi-default-overrides.properties ends up in the JRE's folder instead of in
Jitsi's own. The transforms fix that directory reference.

Ingo

[1] https://jitsi.org/Documentation/MSIParameters


#5

The fix works great. Thank you!

···

Sent from my iPhone

On Jan 10, 2014, at 11:15 AM, "Ingo Bauersachs" <ingo@jitsi.org> wrote:

Correct. "Jitsi-default-overrides.properties" does not seem to be
created in my Jitsi\lib folder, regardless of the installation method or
parameters I input. I made multiple clean installation attempts again
with either command line parameters or through a transform MST file.

I'm sorry, there's a bug in the MSI. The manual [1] has been updated to
provide a solution for the stable builds, and I'm working on a fix for the
nightlies.

In case you're curious: when I developed that, I didn't include the JRE in
my local builds. As the JRE has a lib folder as well,
jitsi-default-overrides.properties ends up in the JRE's folder instead of in
Jitsi's own. The transforms fix that directory reference.

Ingo

[1] https://jitsi.org/Documentation/MSIParameters

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users