Slashdot Mirror
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.
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.
Why not hire a capable programmer for half of what buying office would have cost, and have him make changes which are useful for your company. Chances are that what one company needs, others will as well. Therefore you save money, 1/2 this time around, and get to customize it any way you see fit for your users, and if its something others like, then the changes can be pushed upstream and incorporated. I'm sure many companies would love a quiet auto installer which could be deployed via batch script without user clicking yes/no/next/I agree and with default output settings set to .doc.
Valid question or not, it still is flamebait. Whether it was intentional flamebait could be debated, but it was definetly flamebait. Anyone reading the post obviously saw that the guy was looking for ways to make OO work to replace it, so obviously 'just keep it' was the easy answer that had already been ruled out.
Different versions of MS Office also don't have "perfect compatibility" with each other. In my experience, using OOo is not much different from using a different version of MS Office. Overall, it's probably best simply to avoid "complex Word and PowerPoint files" altogether.
I use notepad.
You must not have installed any MOLP (Microsoft Open License Pack) setups. You get a certificate that clearly states the number of licenses, the agreement date and date of expiration which in mice type states that after the agreement expiration date ( usually 2 years ) you are no longer licensed to use said products which becomes illegal to use under the eyes of the BSA, MS, and the EULA on the media pack(CD).
if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
OH JESUS CHRIST.
:rolleyes:
I guess because I called you on your incorrect statement, I must not be able to understand acronyms and have no knowledge on what you're talking about.
We have plenty of software licensed from Microsoft through various licensing programs. The expiration date is for the expiration of Software Assurance (if you purchased it), or the expiration date to purchase any other licenses at the open license programs.