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.

Comments

Re:OO.org does not have perfect file compatibility

[Anonymous Coward]

Goood point. But so frankly stated that you now need to stand by for a down-modding from the school of OSS fanatics who use OO.org to create their own one-page CV, and who have concluded from that OO.org is fine to use even on huge documents where problems in conversion to the MS formats might make your firm look stupid, zealotish and perhaps even lead to loss of business.

No-one ever got modded up on /. for giving an actual experience-based viewpoint on why some OSS tools really are not quite there yet.