Deploying LibreOffice via Group Policy (GPO)

LibreOffice can be reliably deployed, updated, and configured across Windows-based enterprise networks using Active Directory Group Policy Objects (GPO). By utilizing official Microsoft Installer (MSI) packages alongside dedicated Administrative Templates (ADMX/ADML), system administrators can automate silent installations and enforce centralized configuration settings across thousands of endpoints without third-party management tools.

Software Deployment via GPO

LibreOffice distributes standard MSI installation packages for Windows, making native GPO software deployment straightforward.

1. Download the Installer: Obtain the official 64-bit or 32-bit MSI installer from the LibreOffice download repository.
2. Set Up a Network Share: Place the MSI file in a network-accessible share with read-only permissions for Domain Computers and Domain Users.
3. Create the Group Policy Object:
   • Open Group Policy Management Console (GPMC).
   • Create a new GPO or edit an existing one targeted at the appropriate Organizational Unit (OU).
   • Navigate to: Computer Configuration > Policies > Software Settings > Software installation.
4. Assign the Package:
   • Right-click Software installation, select New > Package, and select the MSI installer via the UNC path (e.g., \\server\share\LibreOffice.msi).
   • Select Assigned deployment method to ensure the software installs automatically at system startup.

Customizing Installation with Transform Files (MST)

For advanced installation parameters (such as disabling specific modules, setting the user interface language, or preventing desktop shortcut creation), administrators can apply an MST transform file:

• Use tools like Microsoft Orca to generate a .mst file modifying LibreOffice’s standard properties (e.g., CREATEDESKTOP画SHORTCUT=0, UI画LANGS=en_US).
• In the GPO Software Installation properties, choose Advanced during package creation and add the .mst file under the Modifications tab.

Managing Configurations with ADMX/ADML Templates

Beyond automated installation, LibreOffice supports native policy enforcement via ADMX and ADML administrative templates.

• Template Availability: Official LibreOffice ADMX templates can be downloaded from the LibreOffice packaging repositories or extracted from enterprise-ready builds (such as LibreOffice Enterprise by certified partners).
• Installation: Copy the .admx files to \\<domain>\sysvol\<domain>\Policies\PolicyDefinitions and the corresponding language-specific .adml files to the appropriate subfolder (e.g., en-US).
• Enforceable Policies:
  • Setting default file formats (e.g., forcing Microsoft Office .docx/.xlsx formats or standard OpenDocument formats).
  • Disabling automated update checks to prevent unauthorized user prompts.
  • Enforcing macro security levels and trusted file paths.
  • Locking user interface elements and disabling telemetry reporting.

Enterprise Best Practices

• Use LibreOffice Enterprise: For production environments requiring long-term support (LTS), certified security patches, and direct vendor SLA, consider deploying enterprise builds provided by ecosystem partners rather than standard Community builds.
• Staged Rollouts: Deploy the GPO to a test OU containing pilot machines before broad organizational deployment to verify compatibility with existing extensions and documents.
• Removal and Upgrades: When deploying newer versions, configure the new GPO package to automatically upgrade and replace the existing version under the package’s Upgrades tab.