OpenOffice-Enterprise Users' Manual

Table of Contents

Installation


Desktop Software Installation

These instructions describe the steps needed to perform a network installation of the OpenOffice.org office suite and the OpenOffice-Enterprise client software using Windows Group Policy.

These instructions are copyright Open Office Technology. They may be linked to but not copied. Their permanent location is http://OpenOfficeTechnology.com/OpenOffice-Enterprise/Desktop_Installation

Overview

The three software packages discussed in these instructions are:

  1. The OpenOffice.org office suite. Installation of this package on each client is required.
  2. The OpenOffice-Enterprise client software. Provides Group Policy management for the OpenOffice.org office suite. Installation of this package on each managed client is required.
  3. Sun's Java runtime environment (JRE). Certain functions in the OpenOffice suite depend on the Java runtime, such as the database application, mail merge and the document wizards in Writer. (For a more complete list, see Java and OpenOffice.org). If these features are not required, the JRE does not need to be installed. Full functionality requires the JRE version 1.5.x. See System Requirements for OpenOffice.org.

These instructions describe the installation procedure using the most recent application versions as of the date these instructions were written. The OpenOffice suite and Java JRE are not distributed by Open Office Technology, and the information related to these packages may change from time to time. If you find any discrepancies in these instructions, please let us know.

Step 1 – Download Software Packages

The first step in the installation process is to download the software packages.

A. If OpenOffice is not already installed on the client machines, download the OpenOffice installer for Windows without the JRE bundled. As of the date of these instructions:

B. Optionally, download the Java JRE offline installation package for Windows. As of the date of these instructions:

C. Download the OpenOffice-Enterprise client software installer. As of the date of these instructions:

Step 2 – Create Network Installation Images

The next step is to create network installation images for each of the software packages. This places the installation images on a network file server that is accessible to the client computers. To complete this process, you must have write access to this location. The client computer should have read-only access.

A. Extract the Java JRE msi file:

  1. Run the JRE installation executable file, jre-6u18-windows-i586.exe. The License Agreement screen will appear. Do not click either "Decline" or "Accept".
  2. The installer executable will have placed a folder called "jre1.6.0_18" into the directory "C:\Documents and Settings\<your username>\Application Data\Sun\Java". (In order to see this directory, you may need to select View | Refresh in Windows Explorer.) Copy the contents of this folder (an .msi and possibly a .cab file) to a network installation point, which is a location on the network accessible to the client computers, such as

    \\fileserver\net_install_images\jre1.6.0_18\

    Note 1: Earlier versions of JRE installation executable placed the .msi file into a subdirectory such as "C:\Documents and Settings\<your username>\Local Settings\Application Data\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}", where the name of the subdirectory depends on the JRE version. The .msi file corresponding to the JRE version can be located by looking in all subdirectories with names matching this pattern.
    Note 2: Neither the Java installer executable nor the .msi file support the “/a” administrative installation option.
  3. Returning to the License Agreement screen, click "Cancel" or "Decline". The installer will delete the Application Data\Sun\Java directory and then terminate.

B. Perform an administrative installation of the OpenOffice suite:

  1. Run the OpenOffice installer, OOo_3.2.0_Win32Intel_install_en-US.exe, with no parameters.
  2. When prompted, enter a location to unpack the installation files, such as a subdirectory called OOo_installer_files in your current working directory.
  3. When the next stage of the installer runs (“Welcome to the Installation Wizard for OpenOffice.org 3.2”), click “Cancel” and abort the installation.
  4. The OpenOffice installer should have unpacked several executable and data files into the directory you selected. From the command prompt, launch the setup file using the following command line:

    setup /a

    When prompted, enter a network installation point such as

    \\fileserver\net_install_images\OpenOffice-3.2.0\

    and then click “Install”. The installer will create the directory you specified, if it doesn't already exist, and then unpack the file “openofficeorg32.msi” along with a handful of subdirectories into this location.
  5. After creating the network installation point, you can delete the directory containing the unpacked installation files (i.e., OOo_installer_files in your current working directory).

C. Perform an administrative installation of the OpenOffice-Enterprise client software:

  1. From the command prompt, launch the installer file using the following command line:

    msiexec /a ooewin-630.msi

    When prompted, enter a network installation point such as

    \\fileserver\net_install_images\ooewin-630\

    and then click “Next” twice. The installer will copy the .msi file to this folder and unpack several files and one subdirectory.

Before continuing, ensure that the client computers have read-only access to the network installation points that you used above.

Step 3 – Create Installation Group Policy Object

This step creates a Group Policy Object or "GPO" that will install the software packages.

  1. Launch the Group Policy Management Console on your administrative workstation (Start -> Run -> "gpmc.msc"). Note: The Group Policy Management Console is included with Windows Server 2008. For Windows Server 2003, the Group Policy Management Console can be downloaded from http://www.microsoft.com/windowsserver2003/gpmc/
  2. Expand the tree for your domain, then right-click on “Group Policy Objects” and select “New”. Enter a name such as “OpenOffice-Enterprise Installation”. Your new Group Policy Object will appear in the tree under “Group Policy Objects”. Right-click on its name and select “Edit...”. This will open the Group Policy Object Editor.
  3. In the Group Policy Object Editor, under “Computer Configuration”, expand “Software Settings”, right-click on “Software Installation” and select “New --> Package...”.
  4. Click on “My Network Places”. (Note: This is a required step. You must select the package to install from a network location rather than a local location. If you do not first click on “My Network Places”, the selection of a package to install will not be accepted.)
  5. Navigate to the network location containing your OpenOffice-Enterprise administrative install, and double-click on the .msi file “ooewin-630.msi”.
  6. For the deployment method, select “Assigned” and click "OK". The OpenOffice-Enterprise installation package should appear in the view pane of the Group Policy Editor.
  7. Right-click on “Software Installation” and select “New --> Package...” again.
  8. Navigate to the network location where you placed the Java JRE install file “jre1.6.0_18.msi” and double-click on this file. If you are not installing Java, skip this step and move down to the installation of OpenOffice.
  9. For the deployment method, select “Assigned” and click "OK". The JRE installation package should appear in the view pane of the Group Policy Editor.
  10. Right-click on “Software Installation” and select “New --> Package...” again.
  11. Navigate to the network location containing your OpenOffice suite administrative install, and double-click on the .msi file “openofficeorg32.msi”.
  12. For "Deployment Method" select “Advanced” and click “OK”. After a short pause, the Properties dialog should appear.
  13. Under the "Deployment" tab of the Properties dialog, select "Advanced...", check the box next to "Ignore language when deploying this package", then click "OK".
  14. Download the file Check_OOE_v3.mst and add it to the directory that contains the OpenOffice installation file openofficeorg32.msi.
  15. Several additional installation transform files for OpenOffice are available here. If you want to install OpenOffice with one or more of these transforms, download the transform (.mst) files and add them to the directory that contains the OpenOffice installation file openofficeorg32.msi.
  16. Return to the OpenOffice installation Properties dialog, and click on the “Modifications”. Add Check_OOE_v3.mst and all of the additional transform files you downloaded, then click “OK”.
  17. Click "OK" to close the Properties dialog for the OpenOffice installation. The OpenOffice installation package should appear in the view pane of the Group Policy Editor.
  18. To set additional options, double-click on each package name in the view pane. For example, selecting “Uninstall this application when it falls out of the scope of management” will cause the applications to be automatically uninstalled if this group policy object is deleted or unlinked. (Alternately, the software can be uninstalled later by right-clicking on each package name and selecting “All Tasks” -> “Remove...”). Any options selected must be set for each package individually, so be certain to double-click on each package name in succession and set the desired options.
  19. When done, double check your selections and close the Group Policy Object Editor.

Step 4 – Set Policy Scope and Link to Domain

This final step selects the computers on which the software will be installed. This involves designating a group or list of computers, along with one or more domains or organizational units. The software will be installed on a computer if it is both in the group that you designated and in one of the domains or organizational units you select.

The default is to “assign” the installation to all users which will ultimately cause the software to be installed on all computers in the selected domains, including servers and domain controllers. This is probably not what you want.

A typical configuration will only install this software on desktop workstations, not on domain controllers. Here are instructions to accomplish this:

  1. Back in the Group Policy Management console, click on the name of your Group Policy Object (e.g., “OpenOffice-Enterprise Installation” or whatever name you previously chose). In the pane on the right, under “Security Filtering” in the “Scope” tab, select “Authenticated Users” and click on “Remove”.
  2. Click “Add...”, and in the dialog box that appears, under “Enter the object name to select”, type “domain computers” and click OK. “Domain Computers” refers to all workstations in your domain; it does not include domain controllers. It may however include servers, so you should check the members of this group. In the Group Policy Management view pane, click on the word “Domain Computers”, then click “Properties”. In the Properties dialog, select the “Members” tab. This brings up a list of the computers in the “Domain Computers” group. If this group includes more computers than desired, you can "Remove" this group and then “Add...” computers individually, or you can create a custom group using Active Directory Users and Computers. You can also select computers using WMI filters, but this is beyond the scope of this document.
  3. When you are finished selecting computers, click on the name of your Group Policy Object in the tree view again, and without releasing the mouse button, drag the pointer to the name of the domain or organization unit in which to install the software. The pointer will change shape to a pointer with a “+”. Release the mouse button and click OK to link your Group Policy Object to this domain. Repeat this process for any additional domains or organizational units.

The Group Policy Object will begin to propagate and will be applied on each selected computer in the domain(s) within approx. 90 minutes (depending on how Group Policy is configured). To apply the GPO immediately on a particular computer, go to that computer and run “gpupdate” from a command prompt. Once the Group Policy Object is applied, the software will be installed the next time the computer is rebooted. The installation process will take several minutes.

Upgrading OpenOffice-Enterprise

The following instructions describe how to upgrade an existing Group Policy installation to a new version of the OpenOffice-Enterprise client software.

  1. Download the new release of the OpenOffice-Enterprise client software, as described in Step C of Download Software Packages.
  2. Perform an administrative installation of the new release, as described in Step C of Create Network Installation Images. CAUTION: Do not overwrite the previous version; install the new release in a different directory. Do not delete the previous version until you are certain all desktops have been upgraded.
  3. Launch the Group Policy Management console on your administrative workstation. Expand the tree for your domain, then expand the tree for “Group Policy Objects”. Right-click on the Group Policy Object used to install the previous version of OpenOffice, then select “Edit...”. This will open the Group Policy Object Editor.
  4. In the Group Policy Object Editor, under “Computer Configuration”, expand “Software Settings”, right-click on “Software Installation” and select “New --> Package...”.
  5. Click on “My Network Places”. (Note: This is a required step. You must select the package to install from a network location rather than a local location. If you do not first click on “My Network Places”, the selection of a package to install will not be accepted.)
  6. Navigate to the network location containing the administrative installation of the new version of the OpenOffice-Enterprise client software and and double-click on the .msi file “ooewin-630.msi”.
  7. Select “Advanced” as the deployment method and click “OK”. After a short pause, the Properties dialog should appear.
  8. Under the "Deployment" tab of the Properties dialog, select "Advanced...", check the box next to "Ignore language when deploying this package", then click "OK".
  9. Under the "Upgrade" tab of the Properties dialog, click "Add..." and under "Package to upgrade", select "OpenOffice-Enterprise" and click "OK". The properties dialog will display the text "Replace OpenOffice-Enterprise".
  10. The option “Uninstall this application when it falls out of the scope of management” can be set under the "Deployment" tab. This option will cause the application to be automatically uninstalled if this group policy object is deleted or unlinked. Alternately, the application can be uninstalled later by right-clicking on its package name and selecting “All Tasks” -> “Remove...”
  11. When all of the installation properties look correct, click "OK" to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on each selected computer in the domain(s) within approx. 90 minutes (depending on how Group Policy is configured). To apply the GPO immediately on a particular computer, go to that computer and run “gpupdate” from a command prompt. Once the Group Policy Object is applied, the new version of the OpenOffice-Enterprise client software will be installed the next time the computer is rebooted. The installation process will take only a few seconds.

Upgrading OpenOffice

New releases and updates for OpenOffice are announced at the OpenOffice announcement mailing list. To subscribe, send an empty email to announce-subscribe@openoffice.org.

The following instructions describe how to upgrade an existing Group Policy installation to a new version of the OpenOffice.org office suite.

IMPORTANT: Before upgrading to OpenOffice v3.1 or higher, you must be running the OpenOffice-Enterprise client software Build 624 or higher (ooewin-624.msi). If you are running an earlier version, upgrade the OpenOffice-Enterprise client before upgrading OpenOffice. For instructions, see Upgrading OpenOffice-Enterprise.

To upgrade to a new release of the OpenOffice.org suite:

  1. Download the new release of OpenOffice, as described in Step A of Download Software Packages.
  2. Perform an administrative installation of the new release, as described in Step B of Create Network Installation Images. CAUTION: Do not overwrite the previous version; install the new release in a different directory. Do not delete the previous version until you are certain all desktops have been upgraded.
  3. Download the file Check_OOE_v3.mst and add it to the network installation directory that contains the OpenOffice installation file openofficeorg32.msi.
  4. Download any additional installation transform (.mst) files you would like to use, and add them to the OpenOffice network installation directory. You can use the same transform files you used when you originally deployed OpenOffice, or you can use any other set of transform files or no additional transform files. Note however that if you originally deployed OpenOffice using a transform file (such as the transform to use OpenOffice to open Microsoft Office document formats) and you want to maintain the provided functionality after the upgrade, then you must apply that transform to the upgrade installation as well.
  5. Launch the Group Policy Management console on your administrative workstation. Expand the tree for your domain, then expand the tree for “Group Policy Objects”. Right-click on the Group Policy Object used to install the previous version of OpenOffice, then select “Edit...”. This will open the Group Policy Object Editor.
  6. In the Group Policy Object Editor, under “Computer Configuration”, expand “Software Settings”, right-click on “Software Installation” and select “New --> Package...”.
  7. Click on “My Network Places”. (Note: This is a required step. You must select the package to install from a network location rather than a local location. If you do not first click on “My Network Places”, the selection of a package to install will not be accepted.)
  8. Navigate to the network location containing the administrative installation of the new version of OpenOffice and and double-click on the .msi file “openofficeorg32.msi”.
  9. Select “Advanced” as the deployment method and click “OK”. After a short pause, the Properties dialog should appear.
  10. Under the "Deployment" tab of the Properties dialog, select "Advanced...", check the box next to "Ignore language when deploying this package", then click "OK".
  11. Navigate to the "Upgrade" tab of the Properties dialog. If one or more existing packages appear under "Packages that this package will upgrade", click on each existing package and then click "Remove". The package name should disappear.
  12. Under "Packages that this package will upgrade", click "Add..." and under "Package to upgrade", select "OpenOffice.org x.x" and click "OK". The Properties dialog will display the text "Replace OpenOffice.org x.x". Repeat this process until all previously installed versions of OpenOffice.org appear under "Packages that this package will upgrade".

    IMPORTANT: The OpenOffice installer will fail if you attempt an in-place upgrade. You must be certain the Upgrade tab displays "Replace OpenOffice.org x.x", not "Upgrade OpenOffice.org x.x".

  13. Under the “Modifications” tab, add Check_OOE_v3.mst and the other transforms you downloaded earlier (if any), then click “OK”. The selected transforms will appear in the properties dialog.
  14. The option “Uninstall this application when it falls out of the scope of management” can be set under the "Deployment" tab. This option will cause the application to be automatically uninstalled if this group policy object is deleted or unlinked. Alternately, the application can be uninstalled later by right-clicking on its package name and selecting “All Tasks” -> “Remove...”
  15. When all of the installation properties look correct, click "OK" to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on each selected computer in the domain(s) within approx. 90 minutes (depending on how Group Policy is configured). To apply the GPO immediately on a particular computer, go to that computer and run “gpupdate” from a command prompt. Once the Group Policy Object is applied, the new version of OpenOffice will be installed the next time the computer is rebooted. The installation process will take several minutes.

Installation Troubleshooting

There a several methods to obtain information about the installation process:

  1. Installation failure and success messages are logged in each computer's Application Event Log.
  2. Group Policy and software installation operations can also be logged. For more information, see the manual section Logging Group Policy and/or Software Installation.

Server Installation


Administrative Template Files

OpenOffice-Enterprise includes administrative template (.adm) files that defines the settings that can be managed by Group Policy. These files have to be installed on the server or administrative workstation where you will be creating and editing Group Policy Objects.

First, download the administrative template distribution file. As of the date of these instructions, the most recent revision of this file is distributed as ooeadm-310.zip and can be downloaded from http://OpenOfficeTechnology.com/download.

This zip file contains the 95 administrative template (.adm) files. Copy these files to the directory “C:\Windows\inf” on the computer where you will be creating and editing Group Policy Objects.

Set Baseline Policy

After installing the administrative template file, the next step is to create a Group Policy Object that will enforce your baseline site-wide policies.

  1. Launch the Group Policy Management Console on your administrative workstation. Note: The Group Policy Management Console can be downloaded from http://www.microsoft.com/windowsserver2003/gpmc/
  2. Expand the tree for your domain, then right-click on “Group Policy Objects” and select “New”. Enter a name such as “OpenOffice Base Policy”. Your new Group Policy Object will appear in the tree under “Group Policy Objects”. Right-click on its name and select “Edit...”. This will open the Group Policy Object Editor.
  3. In the Group Policy Object Editor, under “User Configuration”, right-click on “Administrative Templates” and select “Add/Remove Templates...”. In the Add/Remove dialog, click “Add...” and open the file openoffice-enterprise-v2.adm. Then click "Add..." again and open the file oo2-Setup.adm. Verify that these two files are displayed under "Current Policy Templates", and click “Close”.
  4. Back in the Group Policy Editor, under “User Configuration”, expand “OpenOffice-Enterprise v2”, then select “OpenOffice-Enterprise”. Or, in the more recent versions of Windows, under “User Configuration”, expand "Policies", then "Administrative Templates", then "Classic Administrative Templates", then “OpenOffice-Enterprise v2”, then select “OpenOffice-Enterprise”
  5. In the view pane, double-click on “License”. If you have a license for OpenOffice-Enterprise, enable this setting, enter your license in the “Value” field and click OK. If you have not yet purchased or received a license, OpenOffice-Enterprise will still function but a reminder dialog will be displayed when OpenOffice is run.
  6. The OpenOffice-Enteprise client software automatically applies a baseline enterprise configuration to OpenOffice. These settings can be overridden if desired.

    For example, in order to make it easy to see when OpenOffice-Enterprise is installed and working, the baseline configuration changes the title bar text of the OpenOffice application from “OpenOffice.org” to “OpenOffice-Enterprise”. To change the titlebar text to some other string:

    In org.openoffice.Setup\Product
    set ooName to the new title bar string

    Additional settings can be added at this time, or they can be added later either by editing this Group Policy Object or by creating a new one. For guidance on setting additional policies, please see the OpenOffice Configuration Knowledgebase.

  7. When you have finished adding your domain-wide base settings, close the Group Policy Object Editor.

Link Baseline Policy to Domain

Back in the Group Policy Management console, click on the name of your Group Policy Object (e.g., “OpenOffice Base Policy” or whatever name you previously chose), and without releasing the mouse button, drag the pointer to the name of your domain. The pointer will change shape to a pointer with a “+”. Release the mouse button and click OK to link your Group Policy Object to this domain. Repeat this process for any additional domains.

The Group Policy Object will begin to propagate and will be applied on each selected computer in the domain(s) within approx. 90 minutes (depending on how Group Policy is configured). To apply the GPO immediately on a particular computer, go to that computer and run “gpupdate” from a command prompt. Once the Group Policy Object is applied, the configuration changes will appear in the OpenOffice application the next time it is restarted.

Logging Group Policy and/or Software Installation

Diagnostic logging of Group Policy operations and/or software installation operations can be enabled by setting registry values on each workstation where logging is to take place. There are two ways to do this. The first is by using regedit, and the second is by creating a Group Policy Object.

Set Logging via Local Registry

The local registry values that affect Group Policy and software installation logging are:

GPO Logging to the Event Log

The following registry setting enables verbose logging of GPO processing to the computer's Application Event Log. Note that in Win2K these events show up as Informational events, while in XP, they appear as Error events.


HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
RunDiagnosticLoggingGroupPolicy DWORD 1

GPO Logging to userenv.log

The following registry settings log GPO processing to the file C:\Windows\Debug\UserMode\userenv.log. Note that the modes of logging presented here are just a few of the options. For more information, see http://support.microsoft.com/kb/221833.


HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
No Logging: UserEnvDebugLevel DWORD 0
Normal Logging: UserEnvDebugLevel DWORD 0x10001
Verbose Logging: UserEnvDebugLevel DWORD 0x10002

Software Deployment Logging

The following registry setting logs software installation and upgrade decisions made by the Group Policy engine to the file C:\Windows\Debug\UserMode\appmgmt.log.


HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics
AppmgmtDebugLevel DWORD 0x9B

Software Installation Logging

The following registry settings log all Windows Installer actions. Group Policy initiated software installation is logged to files named %windir%\temp\MSI*.log, and user initiated software installation is logged to files named %temp%\MSI*.log


HKLM\Software\Policies\Microsoft\Windows\Installer
Logging STRING voicewarmup
Debug DWORD 0x3

More Information

For more information on diagnostic logging for Group Polcy, see http://technet.microsoft.com/en-us/library/cc775423.aspx.

Set Logging via Group Policy

Logging options can be set by creating and applying a Group Policy Object, as follows:

  1. Download the file gpolog.zip from http://www.gpoguy.com/Free-GPOGuy-Tools.aspx.
  2. This zip file contains one adm file, gpolog.adm. Extract and install this adm file.
  3. Create a new Group Policy Object and open the Group Policy Editor.
  4. In the tree view, under “Computer Configuration”, click “Administrative Templates”.
  5. At the upper menu bar, click “View”, then “Filtering...”, then uncheck the option “Only show policy settings that can be fully managed” and click “OK”.
  6. Under “Computer Configuration”, “Administrative Templates”, right-click on “Administrative Templates” and select “Add/Remove Templates...”. In the Add/Remove dialog, add the file gpolog.adm.
  7. Under “Computer Configuration”, “Administrative Templates”, select “System”, “Group Policy”, “Logging”. A number of options related to Group Policy logging should appear in the view pane on the right.
  8. After choosing the desired options, close Group Policy Editor.
  9. Using the Group Policy Management console, link this Group Policy Object to your domain, or to the computer(s) you wish to troubleshoot.

Note that because these settings are not “fully managed”, they will not be removed from the target computers' registries when the GPO is deleted or unlinked. To change the settings back using Group Policy, you must explicitly change the setting options to “Enabled” and the values to unchecked or “no logging”, etc. For settings that do not allow you to select a value, change the setting option to “Disabled”. Note that selecting “Not Configured” leaves the value in the target computer's registry unchanged.

Do not confuse this behavior with settings that are “fully managed”. With these settings, deleting the GPO, unlinking it or changing a setting to “Not Configured” removes the setting value from the registry of the target computers, causing the state to revert to its default value.