LO 24 deployment

Hi,
I’m used to deploy LO on my Windows computers for years.
But since new 24* versions, automatic update is activated and it’s problematic for me, as sometimes our tools are not fully complient with newest LO versions.

How can I deploy LO 24* without auto-update activated ?

Best regards.

Tools > Options > LibreOffice > Online updates menu.

1 Like

Hi, Hrbrgr
I want to avoid going on each desktop after the deployment.
I’m searching for an option when I use msiexec -i /qn libreoffice.msi /NOREBOOT …
Thx.

  1. For now, the new updater is not a separate feature in the MSI, so no, you can’t specify that.
  2. You may configure deployed LibreOffice using tips from Post deployment configuration section in the wiki; the options include creating custom XCUs, configuration extensions (both of which may be deployed using e.g. logon scripts); or using group policy (with a bit of customization of ADMX mentioned there).

Any of the 25,000 LibreOffice settings can be configured and managed through Windows Registry,

25,000? :astonished:
Does this include 3rd-party and OS settings that may influence LO one way or the other?

I would say, that 25,000 is an obsolete number. It was written long ago; since then, we only increased the available options :slight_smile: (But I have no actual number myself, just a thought.)
And no, there are not OS settings. These are only things that can appear in registrymodifications.xcu. I think that whoever counted them, didn’t try to count unknown settings of third-party extensions (that of course would add to the count). And yes, when I repeat, that this is a complex software, and that it is simply impossible to test all combinations (multiplied by infinite number of possible document situations), I really mean it :wink:

Which one has the precedence when a setting is defined in both registry and the xcu?

registrymodifications.xcu has precedence, unless the one in the shared config is marked “final” (which is what many admin configurations will necessarily do). Configuration is applied from shared config first; then from user config; and if the following config has a setting for an earlier config, that setting is overwritten, unless it is already final.

1 Like

Thank you @mikekaganski. I’ll check that