The LibreOffice logo, from LibreOffice.org.
Andrew J. Nelson
Published: 9 May 2011
LibreOffice is a powerful, open source office suite which is compatible with many other office suites, including Microsoft Office, and is free. (Free as in speech, but also free as in beer.) There are two issues with using LibreOffice in a Windows network environment: modifying the application so that it installs transparently to the user, and distributing it via Active Directory. This article will explain creating the MSI and modifying it so that it is suitable for deployment via GPO and AD.
This instruction set was defined with LibreOffice 3.3.2 in a Windows Active Directory network environment, with SBS 2003 as the server and a mix of Windows XP Pro SP3 clients and Windows 7 Pro SP 1 clients. You will need:
In order for software to be deployed via Group Policy, it must be packaged as a Windows Installer (.msi) file. The LibreOffice installer comes as a .EXE. However, wrapped inside the .EXE is an .MSI which can be extracted. To do so:
We now have the extracted install files, including the libreoffice33.msi. Our next objective is to prepare an administrative install of the software on the network share.
An administrative installation creates an image of the software on a network share, from which clients in the network can install the software. To create the install, start a command line prompt (Start > Run > CMD > Enter), navigate to the directory containing the unpacked LibreOffice installation files, and enter the following command:
msiexec /a libreoffice33.msi
When the installation wizard starts, click next. Define the path to the network share for the installation to reside in. For instance, M:\AppDeploy\LibreOffice\LO_3-3-2\. When the process is complete, click finish.
As the LibreOffice install stands now, many IT managers would not want it distributed for the following reasons:
These issues can be overcome by modifying the .MSI file, which will be explained next. However, creating transforms and how MSI files work is beyond the scope of this document. A good place to start is this MSDN article. Essentially, an MSI file is a database of all the possible choices and changes that can be made to a piece of software. We need to edit that database to reflect our desires.
Assuming that you have downloaded and installed InstEd It, start it up and navigate to the network share containing the administrative installation libreoffice.msi. Make sure you are working on the network copy, not your local copy! On the left hand side of the interface, under the tables tab, click on the Property table. Values will show up in the right hand panel of the interface.
To disable auto updating, find the line:
Change the 1 to a 0. Likewise, to set LibreOffice as the default application for all Microsoft Office file types, find the line:
Change the 0 to a 1. Finally, there is an option to disable the EULA. I am unsure whether it is necessary to do so on the administrative install, but it doesn't hurt. Find the line:
Change the No to Yes. Save your changes. LibreOffice is now ready for transparent network deployment to your users.
This article demonstrates how to extract a Windows Installer MSI file from a LibreOffice executable, and how to modify that file to make it palatable for deployment in a business/network environment. The viability of open source projects such as LibreOffice, Firefox, and Thunderbird in corporate networks is dependent upon their ability to be distributed and managed in such a network. I hope that this article helps others achieve this goal with LibreOffice.
Open source developers will only set standard MSI deployment and ADM control packages as goals for their software if the community asks for it- and helps with it. If you are a believer in open source, encourage the developers to pursue these goals. Better yet, help them either by contributing your own skills or making financial donations to the projects.
If you have any questions, concerns, suggestions, or constructive criticism, please email me.