One of many advantages of open source projects is for sure the eternal transition and evolutionary progress. This keeps people like my self busy just following the changes.
Last week I was asked to help a large organization prepare their LibreOffice install package for Windows and I thought “Cool – that gonna take about half an hour”. -Wrong!
The Windows installation parameters has been changed and as always it takes quite some time to find the documentation. You can find some documentation here:https://wiki.documentfoundation.org/Deployment_and_MigrationBut have ind mind that parameters has changed over time so you can’t trust all of it.
The idea of installing all modules ( ADDLOCAL=ALL) and the remove individual modules ( REMOVE=gm_r_ex_Dictionary_Fr, ….) is still valid. But choosing language for the GUI is a little easier than before (UI_LANGS=en_US,da). Earlier you had to add all the language codes to the string and then choose your choice for each (… IS1030=1 IS1031=0 …).
Below is an example that installs LibreOffice in Danish and US English with some but not all dictionaries:
Some other things that has been improved dramatically is the new way of handling settings. In earlier versions settings could be manipulated by installing an extension with some XML-files. Nice but not perfect as you had to distribute files to each and every computer.
From LibreOffice 4.2 its possible to change settings through the Windows Registry and this can be managed through one or more Group Policies in the Active Directory or similar adminsitration system.
Read more about that here:https://wiki.documentfoundation.org/ReleaseNotes/4.2#Windows_Registry_changes. You can find some more detailed examples here:http://ask.libreoffice.org/en/question/29537/42-registry-configuration-backend-not-applying-all-settings/.
I needed to make two small changes:
Set “Warn alien format” to “false” and lock the setting.
Set “Macro security level” to “High” and lock the settings
All I needed to do was to create two new keys in the Windows Registry and push this through a new Group Policy to the machines:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\LibreOffice\org.openoffice.Office.Common\Save\Document\WarnAlienFormat] "Value"="false" "Final"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\LibreOffice\org.openoffice.Office.Common\Security\Scripting\MacroSecurityLevel] "Value"="2" "Final"=dword:00000001
I must say this is a much easier approach than the extension method and it makes the whole setup much more flexible since we don’t need to handle extensions on each computer anymore.