Sun Microsystems OpenOffice.org

Version: 2
Views: 3.3k  |  Created: 10/01/2007

Average Rating: 0
OpenOffice.org has 1 inventory records, 1 Questions, 0 Blogs and 3 links. Please help add to this by sharing more!

Deployment Tips (12)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 2 / 5 (Somewhat Easy) based on 6 ratings
Most Commonly Reported Deployment Method
Repackaged (to a setup.msi)
or cancel
120
Note
I found the best way to be rid of the Welcome/License/Registration wizard is to create an administrative install point and let OO copy the required file to each users profile the first time it is launched. You could probably also just replace the file in the openofficeorg1.cab file instead.

Install the program normally and go through the Welcome/License/Registration wizard choosing whatever you want for the default options. This will create your setup.xcu in C:\Documents and Settings\%UserID%\Application Data\OpenOffice.org2\user\registry\data\org\openoffice\setup.xcu

Copy this file to your install point in the following location:

OpenOfficefolder\share\registry\res\en-US\org\openoffice\setup.xcu

You will need to remove the following line from the file:

<prop oor:name="ooSetupInstCompleted" oor:type="xs:boolean">

Otherwise the users will get an error the first time the program is launched. The file should look similar to the following when completed. I would not copy and paste from here since some lines are probably wrapped.

<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="Setup" oor:package="org.openoffice">
<node oor:name="Office">
<node oor:name="Factories">
<node oor:name="com.sun.star.text.TextDocument">
<prop oor:name="ooSetupFactoryWindowAttributes" oor:type="xs:string">
<value>114,133,760,510;4;0,0,0,0;</value>
</prop>
</node>
</node>
<prop oor:name="LicenseAcceptDate" oor:type="xs:string">
<value>2010-09-20T10:16:18</value>
</prop>
<prop oor:name="FirstStartWizardCompleted" oor:type="xs:boolean">
<value>true</value>
</prop>
</node>
<node oor:name="L10N">
<prop oor:name="ooLocale" oor:type="xs:string">
<value>en-US</value>
</prop>
</node>
</oor:component-data>


During installation this file will be copied to the following location by the installer:
C:\Program Files\OpenOffice.org 2.x\share\registry\res\en-US\org\openoffice\Setup.xcu

I'm not sure why but all new users receive a setup.xcu file that does not contain any reference to the LicenseAcceptDate or FirstStartWizardCompleted and the wizard never launches.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
OpenOffice.org version 2 ships with an MSI installer. There is little to no documentation on the meaning of various properties, but you can get some useful information by reading selected bits of the source code.

I'm currently installing it like so:-

msiexec /qb! /i openofficeorg19122.msi ALLUSERS=1 SELECT_WORD=1 SELECT_EXCEL=1 SELECT_POWERPOINT=1

Those options make it silently register itself as the default handler for .doc .xls, and .ppt files.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
Use Orca/Windows Installer SDK (MS Platform SDK) to make a custom transform.

a. Set the properties you need in the Property table.
ALLUSERS=1 (actually not needed for AD deployment, AD installs with installmode 2)
SELECT_WORD=1
SELECT_EXCEL=1
SELECT_POWERPOINT=1

b. To disable the OO quickstarter, in Orca, duplicate the custom actions "qslnkmsidll" and "sdqsmsidll" in the CustomAction table. To do this copy and paste each row once. Take note that the new action names end with a zero. Now, move to the InstallExecuteSequence table and sort it by "Sequence". Insert the two new actions you created ("qslnkmsidll0" and "sdqsmsidll0") at the end of the sequence using some high sequence numbers, i.e 6666 and 6667. Condition for these should be "Not REMOVE="ALL" And Not PATCH". Close the transform to save it, apply it to the openoffice msi in a group policy object. Test =)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
The method of getting rid of the quickstarter, posted by jib, works for me! Here is the transform i've used.
Simply apply over the msi in the GPO.
It's exactly as described by jib but with these properties:
SELECT_WORD=0 (you must change this to 1 for workin)
SELECT_EXCEL=0 (you must change this to 1 for workin)
SELECT_POWERPOINT=0 (you must change this to 1 for workin)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Command Line
I installed OOo_2.0.156_Win32Intel_install.exe using

OOo_2.0.156_Win32Intel_install.exe /S

as it's an NSIS package. Excel and Word were already installed, and the .doc/.xls associations were not assigned to OO.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Command Line

You can configure the Memory Options for open office pre install: Here's how.

The file is common.xcs and i found at this path in my admin install package

share\registry\schema\org\openoffice\Office

It works a treat: setting Cache to 128mb and the Memory per Object to 24mb

Now I just need to find the setting that turns off Java.

Here you go.

the section of the file i have edited is:

<group oor:name="Cache">

<info>

<desc>Specifies cache related options.</desc>

</info>

<group oor:name="DrawingEngine">

<info>

<desc>Specifies the cache related options for the drawing engine.</desc>

</info>

<prop oor:name="OLE_Objects" oor:type="xs:int">

<info>

<desc>Determines the maximum number of OLE objects that can be held in RAM for drawings, presentations and inserted drawing objects. The fewer OLE objects contained in RAM, the more space is available for other functions. The more OLE objects in RAM, the faster you can page through the objects since they do not always need to be loaded from the hard drive.</desc>

</info>

<value>20</value>

</prop>

</group>

<group oor:name="Writer">

<info>

<desc>Specifies the cache related options for Writer.</desc>

</info>

<prop oor:name="OLE_Objects" oor:type="xs:int">

<info>

<desc>Determines the maximum number of OLE objects that can be held in RAM for the writer. The fewer OLE objects contained in RAM, the more space is available for other functions. The more OLE objects in RAM, the faster you can page through the objects since they do not always need to be loaded from the hard drive.</desc>

</info>

<value>20</value>

</prop>

</group>

<group oor:name="GraphicManager">

<info>

<desc>Specifies a group of graphic manager cache options.</desc>

<label>Graphic Manager Cache</label>

</info>

<prop oor:name="TotalCacheSize" oor:type="xs:int">

<info>

<desc>Specifies the maximum cache size for all graphical display objects.</desc>

<label>Total Graphic Cache Size</label>

</info>

<value>134900000</value>

</prop>

<prop oor:name="ObjectCacheSize" oor:type="xs:int">

<info>

<desc>Specifies the maximum cache size for a single graphic display object.</desc>

<label>Graphic Object Cache Size</label>

</info>

<value>24000000</value>

</prop>

<prop oor:name="ObjectReleaseTime" oor:type="xs:int">

<info>

<desc>Specifies the time in seconds after which a cached object is freed from the cache.</desc>

<label>Graphic Object Release Timeout</label>

</info>

<value>600</value>

</prop>

</group>

</group>

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
To get rid of the first-run wizard for any user, I replaced the default icons on the start menu with custom-made icons with targets as follows:

"C:\Program Files\OpenOffice.org 2.0\program\sbase.exe" -nofirststartwizard
"C:\Program Files\OpenOffice.org 2.0\program\scalc.exe" -nofirststartwizard
etc...
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Note

The method of getting rid of the quickstarter, posted by jib, doesn't work for me. I followed jib's steps exactly and tried installing it (each time on a fresh XP install) with TRANSFORMS= on the command line then with the edited MSI. Quickstarter still starts up.

I was able to get rid of the registration wizard by copying a replacement "C:\Program Files\OpenOffice.org 2.0\share\registry\data\org\openoffice\Setup.xcu" file (before starting Open Office), with modifications near the top of the file as follows (change "ooSetupInstCompleted" to true and add the other two elements after the "ooSetupShowIntro" element and before the "Factories" element):

<prop oor:name="ooSetupInstCompleted">

<value>true</value>

</prop>

<prop oor:name="LicenseAcceptDate" oor:type="xs:string">

<value>2005-10-30T12:10:25</value>

</prop>

<prop oor:name="FirstStartWizardCompleted" oor:type="xs:boolean">

<value>true</value>

</prop>

For some reason, I'm now not getting the quickstarter (maybe this is an unintended consequence of denying the registration wizard a chance to run; either way, I'm happy now). I'm also using ALLUSERS=1 on the MSI command line, too.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Note
Reg dialog, dictionaries and language:

All these customizations are possible to do in a transform, you don't need to "copy after installation". Easiest way to replace files in a transform is to use Wise Package Studio or Installshield AdminStudio. Its possible with only Orca and the SDK but harder.

Reg dialog:
INSTALLDIR\share\registry\data\org\openoffice\Setup.xcu

What mfearby says about getting rid of the registration dialog is almost correct but you dont need to change "ooSetupInstCompleted" to true, to add the other two are enough.

...
<node oor:name="Office">
...
<prop oor:name="LicenseAcceptDate" oor:type="xs:string">
<value>2005-10-24T15:59:47</value>
</prop>
<prop oor:name="FirstStartWizardCompleted" oor:type="xs:boolean">
<value>true</value>
</prop>
<node oor:name="Factories">
...

Dictionaries:
INSTALLDIR\share\dict\ooo
Add your dictionaries here, edit dictionary.lst to fit, add these to the transform.

Language:
Start OpenOffice once on your dev machine with the correct dictionary.lst. Change "Default languages for documents" in Tools, Options as suited. Close OpenOffice. This creates the file that contains the language settings, "Linguistic.xcu". It can now be found in the current user profile under "%APPDATA%\OpenOffice.org2\user\registry\data\org\openoffice\Office"

Add this file to your transform in the folder INSTALLDIR\share\registry\data\org\openoffice\Office. It will be copied to the user profile dir at first startup of OOo.

Save the transform, test again =)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Note
The -nofirststartwizard is the only thing that worked for me in my install of 2.1 today. All the Setup.xcu editing had no effect...which I found surprising.

For my Windows 2K computers on a Samba network, I followed these steps:

1. Install to a network share
2. Create the shortcuts to each application with the -nofirststartwizard parm. I have an autoit3 script which I use to copy the directory with .lnk shortcut files from the local start menu/programs folder "openoffice" to all the "all users/start menu/programs/openoffice".
3. Use another autoit3 script to run a couple of .reg registry files that I created for all the Ooo file association and MS Office "emulation" file associations on all our machines.

Now with a version change, I simply re-install over the network share version and as long as they don't change the name of their basic programs, every machine picks up the new version.

It's a bit hokey, but once you have a few "do something on every machine" scripts prepared for your environment, you can do that fairly simply.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Note
Found this information on forums and other websites, might be helpfull

Changing the Default File Saving Format, edit the following files in the
C:\Program Files\OpenOffice.org 2.0\share\registry\modules\org\openoffice\Setup directory

Edit the following lines in
setup-writer.xcu (this same default filter line appears twice in this file)

<prop oor:name="ooSetupFactoryDefaultFilter">
<value>MS Word 97</value>

setup-calc.xcu

<prop oor:name="ooSetupFactoryDefaultFilter">
<value>MS Excel 97</value>

setup-impress.xcu

<prop oor:name="ooSetupFactoryDefaultFilter">
<value>MS PowerPoint 97</value>

-----------------------------------------------------------
disable the whole welcome/license/registration dialog.

edit C:\Program Files\OpenOffice.org 2.0\share\registry\data\org\openoffice\setup.xcu
just replaced the subnodes of the node called Office.

<node oor:name="Office">
<!-- disable new user welcome/license/registration starts here -->
<prop oor:name="ooSetupInstCompleted" oor:type="xs:boolean">
<value>true</value>
</prop>
<prop oor:name="LicenseAcceptDate" oor:type="xs:string">
<value>2015-10-17T12:36:36</value>
</prop>
<prop oor:name="FirstStartWizardCompleted" oor:type="xs:boolean">
<value>true</value>
</prop>
<!-- disable new user welcome/license/registration end here -->

Until the year 2015 no registration box will appear.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
4
Command Line
To create an administrative installation:

Unpack your setup exes to different folders using the default installer. Just press cancel after the extraction. Run

setup.exe /a

to create an administrative install share. I tried to input a UNC path, that didn't work, but it might work for others? "setup.exe /a" also works for integrating language packs into the administartive share.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

OpenOffice.org

Version

2

Questions & Answers (1)

Questions & Answers related to Sun Microsystems OpenOffice.org

Blogs (0)

Blog posts related to Sun Microsystems OpenOffice.org

Reviews (0)

Reviews related to Sun Microsystems OpenOffice.org