OpenOffice.Org in a Corporate Environment?

robpoe asks: "I've been working on a rollout plan for OpenOffice.org 2.0 for a medium sized network. This network runs a number of different MS Office versions, and we absolutely must retain the Microsoft Office 97/2000/2002 file formats (for interoperability with the public and other entities). Getting our versions of Office to 2003 is $65k+, so we're looking closely at OOo. The problem is, since OOo keeps track of changes per user, and we have users that move around (and no, Roaming Profiles are not an option for us), and you cannot expect a user to change those preferences on every computer they log in to. Let's hear some great deployment plans for keeping the default file type, and even general rollout plans. How are you doing it?"

"It seems that nobody has done this (or documented it) that I've found. Let's see if we can get a good thing going by documenting a good, easy to manage rollout plan. Oh, and the default for saving files has to remain in Office 97/2k/xp format.

What are you using to deploy OOo automatically on your network. Assume that we have capability of login script (batch files / registry changes), but no SMS/ZenWorks/etc.

Re:Why not?

[MankyD]

Why not just keep Office 2000/XP?

You're not from around here are you.

Re:Why not?

[Anonymous Coward]

Nope. We don't laaayyyk winders in these here parts

Re:Use the source, Luke?

[Anonymous Coward]

Man, your house must be a wreck.

Because you swat flies with a sledge hammer.

here's a cheaper way vs. $65K

[agapits]

1. install OO in workstations
2. buy:

          * big whiteboard - $35
          * whiteboard marker - $5

3. then write the instructions on the white board on how to configure OO

total expenses: $40

Re:Store the OpenOffice config file on network dri

[grahamdrew]

... and then users will start leaving their keys attatched to the USB ports along with their thumb drives.