Deploying Open Office?

scubacuda asks: "I've mass deployed OpenOffice at work. Of the 40 computers running, ALL are running OpenOffice (only about 5 are running Microsoft Office in addition). I'm quite surprised at how well-received the deployment has been thus far: secretaries seem to be pleased with how well it integrates with Avery labels, it converts to/from Microsoft Office DOC/XLS files, etc. Have any other slashdotters implemented OpenOffice in an enterprise environment? If so, what have been the reactions from users and management?"

Comments

Good-ish experiences

[Snafoo]

My office is divided between the savvy Engineering department, which uses Linux and gcc for development and, believe it or not, groff for written stuff, and the Sales department, which used to use MSOffice 97. Due to extensive lobbying by the lead engineer, and some incompatibilities between Office97 and 2000, when the hour came for an upgrade we seized the opportunity to switch sales and management to an OO-based environment.

The results so far are that:

(1) Some unexpected people are going to _need_ MS Office, point-blank. The popular financial package we use only 'exports' data to Excel. Not excel file formats; just Excel (via OLE or COM or whatever they're calling it this week.) Although it has a 'print to CSV' feature (don't ask), it saves the file with some silly Lotus-specific extension that OpenOffice doesn't believe is actually a CSV file. Although renaming should in principle be easy, the people who need to use this data are simply not up to the task of understanding (a) why they need to set their folder options to show all those funny little three-letter thingies at the end of the filename, and (b) why they can't just click the 'Excel' button like they used to. So the people that need to regularly manipulate the data in the financial database at a relatively low level need MSO. Also, upper management simply adores Outlook, so you might have to appease them with the real mccoy. So buy a couple of copies of MSO, just in case.

(2) Many other people won't notice the switch. (Seriously!) Or, at least until they try to open a heavily-formatted word document sent to them from someone outside the company, which leads to point

(3). Always install the freely-downloadable viewers for Office documents, which are available for free on MS' website, and make sure that they map to the MSO filetypes. Really, the Word-document import engine of OO is not yet up to snuff, and the spreadsheet (although very, very close in quality and feel to Excel) barfs in some strange places where Excel is still (perversely) happy. For instance, if you cut and paste a column of cells into a column absolutely referenced by the formulae in those cells, it becomes self-referential and then, in the judgement of both reason and OpenOffice, should display an error. However, Excel will simply display the original contents of the cells before they were copied, and silently ignores the formulae. OO's is obviously the theoretically correct response, but many of the (ahem) generalists in Sales have a hard time understanding what, precisely, they're copying, and Excel's behaviour often gives them what they want despite their incompetence. This is just one small fruit on the tree grown of the millions of dollars spent by Microsoft on focus-group testing and UI design, which is still growing and bearing dividends. OpenOffice has a formidable competitor, even if it is overpriced.

(4) Consider using StarOffice, which is cheap (although not free, obviously) and handles Word and Excel documents better. Or, wait for whatever it is that 'GoBe Productive' is metamorphosing into, which I have not tried and cannot speak knowledgably about.