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.

81 of 376 comments (clear)

  1. Store the OpenOffice config file on network drive by Harry+Balls · · Score: 5, Informative

    Elementary, Watson.

    Once a user logs on, a logon script mounts his own personal "network drive" from a central file server.

    Just configure OpenOffice so that OpenOffice will read (and write) the OO configuration from that personal "network drive".
    Yes, a user could still mess up his configuration, but that would only affect himself, not others.

  2. Why not? by ZiakII · · Score: 5, Insightful

    Why not just keep Office 2000/XP?

    1. Re:Why not? by MankyD · · Score: 5, Funny
      Why not just keep Office 2000/XP?
      You're not from around here are you.
      --
      -dave
      http://millionnumbers.com/ - own the number of your dreams
    2. Re:Why not? by buck_wild · · Score: 4, Informative

      Um, because he doesn't want to spend an extra $65k. At least, that may have only been clear to me.

      --
      If all you have is a hammer, everything looks like a nail.
    3. Re:Why not? by Ucklak · · Score: 5, Informative

      It they have an open license agreement with MS (as most do in a corporate case), they are required to upgrade in X number of years. They could still use the software but it would be illegal (in the eyes of the BSA, MS, and the EULA).

      Last time I checked, the retail version of MSOffice 2002/2003 doesn't allow the use of transform files which set corporate preferences for the user during profile setup.

      --
      if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
    4. Re:Why not? by Professor_UNIX · · Score: 2, Interesting

      But he's already running older versions of Office. They didn't just magically stop working when Office 2003 came out and they're going to be a lot more compatible with the Word document format than OpenOffice is. The only ones that tolerated us using OpenOffice to munge Word documents were other techies who could tolerate the formatting being screwed up on internal company forms. If I wanted to make sure it looked right I'd have to boot up VMWare on my Linux box and use OfficeXP.

    5. Re:Why not? by Doc+Squidly · · Score: 2

      Getting our versions of Office to 2003 is $65k+

      Its not going to cost him $65K to keep his current software. The posting says that his company already has Office 97/200/2002.

      --
      I think I think, therefore I think I am.
    6. Re:Why not? by pythas · · Score: 2, Informative

      Uh, that's 100% wrong. An open license doesn't require any kind of repurchase in a certain amount of years. Using it after that time isn't illegal.

      Who the hell modded this up?

    7. Re:Why not? by Fallingcow · · Score: 2, Insightful

      Just send PDFs to those outside the company. 99% of the time you're not sending stuff to people outside the company that needs to be edited, anyway. Printed and filled out or signed, maybe, and usually just read, but not often edited.

      Keep one copy of MS Office around for the rare occasions when you need to send something to the outside that needs to be edited, or the rare occasions when you recieve a doc from the outside that's completely unusable in OpenOffice.

      Sure, some shops do need to send out easily editable documents to others frequently, and it might not work for them, but for most small- to medium-sized places this would be fine.

      I agree on the "don't fix it if it's already working" thing, though. Unless they've got some truly ancient copies of Office floating around, I'd think that it'd still be less of an inconvenience to deal with what they've got than to switch to OpenOffice, assuming they deal with very many documents from the outside world.

    8. Re:Why not? by dekemoose · · Score: 4, Informative

      Oh? That's news to me. Most businesses I know get their Microsoft Licenses via one of their license programs. Typically you buy the license and upgrade assurance, after 3 years you lose the upgrade assurance, but still have the right to use that version of office you originally purchased.

    9. Re:Why not? by pythas · · Score: 2, Informative

      You are wrong, but it seems you're not willing to accept it.

      The only "subscription" based software licensing program Microsoft has right now is the Enterprise Subscription Agreement. On everything else, you OWN THE LICENSES once you purchase them, and not just for the term of the agreement.

    10. Re:Why not? by Ucklak · · Score: 2, Interesting

      I actually read the fine print.

      From Microsoft's own site:
      http://www.microsoft.com/licensing/programs/open/d efault.mspx

      Look at the 'Term' row, it is a two to three year span.
      On the certificate that you get in the mail when you purchase an agreement you'll see this line of text:

      "...provides you with rights to run the software only during the term of the agreement with Microsoft (nonperpetual)."

      hence at the end of the agreement, it becomes illegal to run said software because you no longer have the rights to run it.

      --
      if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
    11. Re:Why not? by IceCat · · Score: 2, Informative
      I actually read the fine print.


      Not quite... Check here. Scroll down to the 'Open Value Options' section. Note there are three options of Open Value licenses, one of which is subscription. It is that option that is nonperpetual and also according to this page not an option in the US or Canada.

    12. Re:Why not? by Ucklak · · Score: 2, Insightful

      The parent post states that he 'Owns' the license which is never a possibilty with Microsoft. Their license is the right to run their software on their terms, period.
      I have been called by an MS VAR (Through Ingram Micro) regarding an MOLP licensing issue with a small business (under 40 desktops) back in the Win2000/Office 2000 era. I had a client that didn't want to renew their license. They were aware that they would have to pay full price if they didn't renew now for future upgrades (big deal, they paid full price the first time and the cost savings mattered at the time.)

      Needless to say, they said we had to remove the software from their computers if we didn't renew, we got a letter from the BSA, yada yada, they renewed, I started to hate Microsoft at that point.

      Even recently, I had a deployment of Server 2000 (before 2003 came out and needed a stable environment for a project), project 2002, office 2002, visio 2002. We let it lapse in 2004 and I got a call and a letter stating I had to remove the software. The project was over anyway so it was a moot point.

      I have seen the BSA goons do an audit for a multimedia company (company that a friend that just hired as their admin) and fine them for $150,000. Don't tell me I don't have battle experience with Microsoft Licensing.

      --
      if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
    13. Re:Why not? by IceCat · · Score: 2, Informative
      Don't tell me I don't have battle experience with Microsoft Licensing.

      I am certainly not trying to say you don't have battle experience with MS Licensing. I am trying to say that from MS's Open licensing web page mentioned in my previous link that the following is said:

      Open Value Company-wide Option: And you'll have access to your licenses for as long as you need them (perpetual).

      In that scenario there is no reason anyone should be asking you to remove software from your machines. Now if you obtained your licenses outside of the US or Canada then there may have been a subscription based license involved (described in my previous links) where removing the software very well may have been requested.

    14. Re:Why not? by 19thNervousBreakdown · · Score: 2, Insightful

      You do realize how trivial it is to unlock a read-only Word / Excel doc, right? Might as well just tell people to not change it and go by the honor system.

      If you're just trying to prevent accidental modifications, use the file system's read-only attribute. If you want a secure read-only version of the file, don't give the users write permission to it. If you're going to be copying the file to people, who cares if they change it? You have the original. Honestly, I think it's a stupid feature, Is this something you just have to do because the PHB said so, or is there a valid reason for doing this that I haven't thought of?

      --
      <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    15. Re:Why not? by Duhavid · · Score: 2, Interesting

      You have a good point.

      One issue for that organization, thoughis that the old version will not
      read newer MSOfficeversion's files. This is not an issue if
      they only deal with internal documents, but if they receive
      documents from outside the organization, they will likely have
      no control over those external version, and would therefore
      be under pressure to upgrade to be able to read the newer
      formats.

      --
      emt 377 emt 4
    16. Re:Why not? by klubar · · Score: 2, Informative

      It's too bad that the original poster didn't provide any more details about his organization--how many users does he have? How many need full office? The $65K is the cost of about 2/3 of an employee (after benefits, etc.) If changing for Office to some alternative (training, support, help desk calls from clients) will cost an additional person, he's better off stick with Office. However, I'd recommend waiting until the upgrades for Office 12 are are available to get everyone on the newest version. (Yes, there will be training involved, but he will be up to date.)

      He should also consider whether everyone needs full Office--perhaps many users just need Word. Since he's considering OO the users don't need Access, so he could get away with Office Small Business. In the quantities that he should get a discount.

      Office Upgrade (Small Business=Word, Excel, PowerPoint, Publisher) costs about $200. So he must be talking about a $65,000/$200 = 325 person upgrade. At that quantity there is room for negoitated prices. Also, if the environment requires outlook (for shared calendars or contacts) then he probably needs Office--or at least Outlook.

    17. Re:Why not? by Anonymous Coward · · Score: 2, Informative
      It they have an open license agreement with MS (as most do in a corporate case), they are required to upgrade in X number of years

      That's funny. Where I am, we are using Office 97/2000, but we buy licenses of whatever's current. And it's been clearly established that there is no such requirement that we "upgrade" in so many years or the BSA will come down on us. If Microsoft went around demanding that people upgraded every x number of months they'd rapidly lose business to competitors who didn't.

      Last time I checked, the retail version of MSOffice 2002/2003 doesn't allow the use of transform files which set corporate preferences for the user during profile setup.

      Must not have checked very hard then. You can pretty much write whatever you want to into a transform file if you know what you're doing. Which your statements make increasingly clear you do not.

    18. Re:Why not? by wireloose · · Score: 2

      MS does have a corporate license upgrade plan. This is most likely what this fellow is facing. In order to use it, you have to already have licenses for office, and the licensing plan allows for upgrades to each license. But if you have some that are older licenses, the plan requires extra $$ to bring them all up to the same level.

      For example, if you have 500 computers to license, with 100 already running Office XP, 100 on Office 2000, and 100 on Office 97:

      You would have to pay MS for license for the 200 computers without licenses, plus upgrade costs for the 100 Off2k licenses, plus higher upgrade fees for the 100 Off97 licenses, *plus* the cost of the generalized upgrade for the 300 licensed computers to take everything up to 2003.

      MS doesn't quite state it that way, and the formula is somewhat hidden when you look at the contract, but the total cost isn't hidden.

      And yes, what that total cost gets you is an annually renewable contract. If you terminate the contract, you have to remove all copies, and you can keep only the original 300 licenses you had, at their respective version levels, plus you may be allowed to keep 200 copies of 2003 for the remaining computers *if* you can prove by your contract that you did indeed purchase licenses at the 2003 level for them.

      Good luck.

  3. OO.org does not have perfect file compatibility by vijayiyer · · Score: 5, Insightful

    While this doesn't address your question, you mention the necessity of using MS office files. Be absolutely sure you are aware of the limitations of importing/exporting MS office documents. Contrary to what a lot of slashdotters imply, the document compatibility is only so-so when working with complex Word and Powerpoint files, which forced me back away from OO.org. Don't get me wrong - I don't like MS Office myself. But when forced to work with MS Office files, it's incredibly difficult to use any other tool.

    1. Re:OO.org does not have perfect file compatibility by penguin-collective · · Score: 2, Insightful

      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.

      Being a card carrying OSS fanatic, I can tell you truthfully that OO.org is not fine to use on huge documents. But being a suffering MS Office user, I can tell you that MS Office is just as bad for huge documents.

      The professional way of writing huge documents is with a markup language and a revision control system.

    2. Re:OO.org does not have perfect file compatibility by swillden · · Score: 4, Informative

      No, no, I think you misunderstood.

      OOo is just fine on huge, complex documents. It's very stable, predictable and reliable.

      OOo has a hard time with rendering large, complex MS Word documents, though. They get all screwed up.

      MS Word, on the other hand, also has a hard time with large complex MS Word documents. The formatting is okay, but Word crashes constantly and tends to corrupt your files and lose all of your work.

      Does that clear it up?

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    3. Re:OO.org does not have perfect file compatibility by swillden · · Score: 2, Informative

      For Word, anything much over 50 pages seems to cause problems. Especially if you're using change tracking.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    4. Re:OO.org does not have perfect file compatibility by killjoe · · Score: 2, Insightful

      And as long as MS makes it hard to exchange your documents with other people you should rule them out as a vendor.

      Your point is exactly why somebody should dump office, not why they should keep it. You should not let your vendors dictate the products you use.

      --
      evil is as evil does
    5. Re:OO.org does not have perfect file compatibility by Mr.+Hankey · · Score: 2, Insightful

      But when forced to work with MS Office files, it's incredibly difficult to use any other tool.

      That's probably the number one reason to get rid of office. That, and the fact that it can be difficult to use different versions of Office in the same environment. When older versions of office are phased out, and no longer for sale or supported by Microsoft, it becomes necessary to upgrade everyone at what can be an inconvenient time due to version compatibility problems. Better IMO to work with something that you can add to any system without having to worry about the software being available.

      In any case, for any planned upgrade such as this it's often a good idea to solicit a group where in the company that would like to function as a test case for the software. Ask, don't force. There are plenty of people who like to try new things, as well as those who are afraid of change. Better to work with the former first if possible. You may well find out that there really isn't anything to worry about, but at least you'll know.

      --
      GPL: Free as in will
    6. Re:OO.org does not have perfect file compatibility by Goner · · Score: 2, Interesting

      It's true that while OOo doesn't have perfect file compatibility I will offer a few anecdotes to what it can do. Chapter x of a friends doctoral thesis simply would no longer open in Word (word just crashed). We imported it into OOo and exported it back out. (I can't remember if we made any fixes to the doc structure in OOo) and bang it worked in Word again.

      Just today, I made a 50 slide presentation, pretty simple, and I exported it to powerpoint. Looks fine on a mac. As a bonus, it also exports perfect PDFs as well.

      I really think OOo has come along way from when Wordperfect for linux was the best anyone thought it would get... what was that like... kde 2.0? something... anyhow. There are still a lot of things that it needs, but it is a testament to good open source coding and also to the folks at Sun who in spite of all of the criticism have done a lot for the future of open source computing.

      In all fairness, though, there are still glaring errors that can bite you in OOo. The upside is that they are usually predictable... I suppose Office errors are predictable too, they happen when you least want them to. (Note, I'm typing this on a windows machine, so take my M$ (I really just typed MS M$ reflexively... that's a problem I should talk to my shrink about) bashing with a grain of malaria research funding money)

  4. Use the source, Luke? by marimbaman · · Score: 4, Interesting

    I imagine it can't be too difficult to build your own distro of OOo that saves in MS Office format by default.

    1. Re:Use the source, Luke? by robpoe · · Score: 2, Informative

      In OOo with multiple user profiles, this is saved PER USER!

      You cannot expect a user to do this on every machine.

      I either need this globally set or some other elegant solution.

      --
      = Grow a brain...
    2. Re:Use the source, Luke? by Carl+T · · Score: 2, Informative

      How about changing the settings in the directory that is used to create a user's OOo directory the first time OOo is started? On our system this happens to be in /export/local/9.0/packages/OpenOffice.org2.0/share / but it would obviously be elsewhere on your MS Windows system. I get the impression that you're not using the network for home directories, so I'm guessing that you don't use it for anything else either. If OOo is installed separately on each computer, you'd have to somehow propagate the defaults (or skel, or whatever one should call it) out to every machine, but that's a whole different problem.

      --

      This signature is not in the public domain.
    3. Re:Use the source, Luke? by bit01 · · Score: 2, Informative

      In OOo with multiple user profiles, this is saved PER USER!

      So what?

      You cannot expect a user to do this on every machine.

      No, why would I?

      I either need this globally set or some other elegant solution.

      If you can't propagate a configuration value like this or even a software installation to all the machines you administer in seconds with minimal user impact you are a very poor system administrator and no amount of advice on /. is going to help you. It's just a file copy operation, no elegance needed.

      ---

      DRM =>Total Customer Control = Ultimate Customer Lockin = Death of the free market.

  5. Use a macro by David_Bloom · · Score: 5, Informative

    Make an OpenOffice.org BASIC macro that sets the configuration settings. Put the macro in an empty document, and make it autoopen that document on startup only once (also code the document so it closes automatically once it's done).

    --

    Karma: Excellent (fuck, even in the future moderation doesn't work!)
  6. TermServer/Citrix/XWindows/whatever by Gothmolly · · Score: 5, Insightful

    Since you're going to make a fairly large paradigm shift anyway, why not go all the way and centrally host it? Running it over your favorite remote protocol might work fine, it wont bloat or slow down the clients, you can insta-upgrade people to new versions, and the roaming profile requirement evaporates.
    If people save to some network share, and their PCs can access that, then there's no problem. Map some printers back to local clients (depends on how you do the remote session, might be LPD, share, or LPT redirect), and people might not ever know they're NOT on the local machine.

    --
    I want to delete my account but Slashdot doesn't allow it.
  7. in other news.... by mulcher · · Score: 5, Interesting

    For $65k you should be able to bargain with MSFT somehow. Academia does it by department which should be far less than what you pay... and it is department negoiated, not University wide. In other news, expect a slashdot article in a month stating that "I got fired for installing OO 2.0 on our corp. network".

    MS Office doesn't even work with highly complex objects and docs... even between versions or across different computers.

  8. Remote Folders by Doc+Squidly · · Score: 4, Informative

    Via group policy you can redirect the users' application data folder to a drive on a file server. Assuming Open Office saves the user configuration in the %user name%\Application Data folder, it should work.

    Of course, if you don't already have enough space on your servers; you've got another fight on your hands.

    Good luck!

    --
    I think I think, therefore I think I am.
  9. Open Office by scarolan · · Score: 5, Informative

    We are a much smaller company - at only $8m a year in sales, but here's how we do it:

    12-15 users all log into a central server running Fedora Core 3 using thin clients. We currently use the excellent LTSP (www.ltsp.org) packages to accomplish this. Through experience we have found that a Pentium 4 server with about 2 gigs of RAM can comfortably handle up to 15 users or so, more than that and the load gets a bit too heavy. The programs that eat up the most memory and CPU cycles are Firefox, Evolution, Open Office, and Adobe Acrobat. We do allow streaming radio with xmms, because it doesn't eat up too much bandwidth or memory, and our users like it. The desktop clients themselves are old Pentium II boxes with 64mb of ram, no hard drives, and no cd-roms.

    All our sales reps use OpenOffice every day to type up their quotes, fax cover sheets, etc. My secretary uses OpenOffice Calc to do spreadsheet work for our government contracts. It's easy to set all your clients to default to MS file formats - go into the File > Save settings and set them to always use .xls or .doc for your files.

    You don't need to use thin clients, however, to use Open Office. We just went the thin client route because it was inexpensive and easy to do with existing hardware. We are planning to upgrade soon so that each user has their own desktop machine running local apps, but still mounting the home directories on the server.

    I suppose if it can be done with 15 computers running linux, you could also do it with your Windows boxes. Just make sure they all have the same OO settings, and that they are all set to save in the proper file formats before your users even get a chance to work with it. OO works almost like MS Office - but be prepared for lots of complaining from users who will say "But Microsoft Office didn't work this way" . . .

  10. My OO.o tips by saskboy · · Score: 3, Interesting

    I'm far from an expert, but I've been using OO.o for over two years now.

    My first tip is at home or for basic users, you can go into
    Tools
    Options
    Java
    Disable the Java, and your startup time is almost certainly going to improve.
    [Another Slashdotter showed me this trick, and it apparently disables macros or something I don't use much if ever.]

    I install OO.o on a computer, and log into the profile that will run it, hit enter a few times to accept the agreement, and say I've already registered then proceed. This loads the quickstarter into the Startup, and if MS Antispyware is running it might even ask if you want it to run every time.

    Since I image computers and roll out a standard image when a machine needs redoing, I don't worry about standard config settings yet. Most machines I put it on don't have Word, so I set OO to automatically open Word files, when I install it.

    --
    Saskboy's blog is good. 9 out of 10 dentists agree.
  11. Be careful about compatibility by mferrare · · Score: 5, Insightful
    I used to run my own consultancy and I used OpenOffice (well StarOffice back then) as my office suite. I found it more useful to send documents around in PDF format instead of sending word documents to my clients. Most of my clients could read PDF back then (this was '99/2000) - even more should be able to now.


    Be careful about compatibility. The MS Office compatibility in OpenOffice is not all it's cracked up to be - even things like bullets and headings change fonts and spacings during conversions. IMHO it's better for you to work in native formats and send PDF files around.

    --
    Why would anyone want to use a text editor that is not vi?
    1. Re:Be careful about compatibility by EnronHaliburton2004 · · Score: 4, Informative

      The MS Office compatibility in OpenOffice is not all it's cracked up to be - even things like bullets and headings change fonts and spacings during conversions.

      And truth be told, MS Office compatibility in MS Office is not all it's cracked up to be. Opening MS Office 97/2000/2002 documents in a different version of MS Office can yield in wildly different results.

      Opening an Office 2000 document in Office 2000 can also result in different results, as I noticed yet again with my resume. The bullets are NOT as I left them last week.

      And here I am editing a document in Word 2003. I have a bulleted list, and I hit return. MS Word creates a new line with a bullet-- great! But it also automatically changed the font, itallics and spacing for the rest of the bulleted text in the list-- WRONG! This bug has existed since Office 1997--- I hate it!

  12. Roaming Profiles aren't a good solution... by Anonymous Coward · · Score: 5, Insightful

    They only solve this problem for EVERY app on your network.

    You're basically asking for the features of Roaming Profiles without having to actually implement them.

  13. Bite the bullet by GWBasic · · Score: 2, Insightful

    Consider biting the bullet and spending the money. $65k, depending on where you're located, could be much cheaper then the amount of money you'll have to spend on supporting Open Office. Microsoft Sharepoint allows people to easily move between computers, yet still have access to documents in a central repository.

    1. Re:Bite the bullet by Theatetus · · Score: 4, Interesting
      $65k, depending on where you're located, could be much cheaper then the amount of money you'll have to spend on supporting Open Office.

      Where is this magical world people are from in which MS Office works out of the box and doesn't require support? I "tech guy" for about 20 small organizations and as of this last invoice 65% of my time is supporting people on MS Office (90% if you count Outlook) because it freezes / craps out / corrupts their files / won't open older versions / won't open newer versions / does weird things where bullets aren't all the same size / messes up multi-column calculations half the time but not the other half of the time / etc.

      Do you really work with MS Office installations that don't require support?

      --
      All's true that is mistrusted
  14. Hosted Desktop anyone? by ice-e-fresh · · Score: 2, Interesting
  15. Unfair Moderation. by Doc+Squidly · · Score: 5, Insightful

    Why not just keep Office 2000/XP?

    This is a valid question that shouldn't have been modded as flamebait. Sure, its an unpopular question considering the /. crowd but, still valid.

    The first option that is usually overlooked in IT is, "Do Nothing". If any software product is meeting a businesses needs then why replace it without a good enough reason. Will the benefits of switching form product A to product C outweigh the cost.

    I love new stuff as much as the next guy but, if a product works, even one made by M$, then asking if your company should continue to use it is a question any IT Pro should ask.

    There plenty of good reasons to switch to OOo but, don't do it just because it's not a M$ product.

    [Gets off soap box]

    --
    I think I think, therefore I think I am.
    1. Re:Unfair Moderation. by buck_wild · · Score: 4, Informative

      Valid point. However, in a business environment there are other considerations, such as per-seat licenses. If his office is like mine, we were *required* to pay. In this case, doing nothing meant that you were no longer allowed to use MS Office, in which case stiff penalties applied if you were caught*.

      *Employees could 'report' usage to MS anonomously.

      --
      If all you have is a hammer, everything looks like a nail.
    2. Re:Unfair Moderation. by Anonymous Coward · · Score: 2, Informative
      Personally, I think the reason it might have been modded as flamebait is because the answer to his question is right in the brief article summary:
      "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?"
  16. Better Idea. by unixbugs · · Score: 2, Interesting

    Why don't you spend 35K on someone to implement all the OOo you can stand.

    --
    You are about to give someone a piece of your mind, something which you can ill afford...
  17. Portable OOo! by thecampbeln · · Score: 3, Interesting
    This is exactly what I was going to suggest (but some dumb ass modders downgraded both threads that mention it!?) Just in case the parent falls off, here is the URL.

    Despite what the parent says, you DO NOT NEED TO PUT THIS ON A THUMBDRIVE! All it really equates to is a fully preconfigured and compartimentalized "install" of OOo. Need to update it? No worries, roll out a new version (or a diff) of the changed files. Everything is housed under the one directory.

    I use the portable version of FireFox and Thunderbird for myself and the inlaws because you can always guarentee that you've got all of the config files and user data (bookmarks and emails in their cases) under the one folder, so backups and updates are 100x easier (least for me). YMMV, but it's worht a look!!

    --
    "1984" was ment to be a warning, not a guidebook. You hear that Kim Jong-il!? BushCo?!
  18. Re:Store the OpenOffice config file on network dri by Jjeff1 · · Score: 5, Informative

    No. Lets say we mount the users' home drive as drive letter H. You can do this with windows policies or a login script. No touching workstations. Then we configure the base install of OO.org to look in H:\ooo-settings\ for all it's config data.

    Boom! Unique settings for each user without roaming profiles

  19. Re:This is word processing, not desktop publishing by Daengbo · · Score: 2, Interesting

    You just want to change the view to "Web Layout." You can do that either by checking it, or by unchecking "Print View."

  20. Have you checked with your Finance department? by winkydink · · Score: 4, Insightful

    Especially the really heavy users of Excel? The ones who build "models"? Don't tell them, but all that "macro" stuff they build? It's essentially a furball of VB. Furball? Yes, because it's been written by somebody who doesn't know how to program. They just keep whacking at it until it works.

    And guess what? It doesn't work in OpenOffice.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:Have you checked with your Finance department? by markdavis · · Score: 2, Interesting

      Our finance department has no problem at all using OO. They have some very complex spreadsheets, but I don't think any use macros, anyway.

      By my estimates, OO 2.0 is probably a suitable MS-Office replacement for about 95-98% of users out there (given a nice random spread/variety of users).

  21. Re:Store the OpenOffice config file on network dri by Suppafly · · Score: 2, Informative

    Assuming a windows environment you would use offline files, that's normally how people sync with network drives.

  22. Perils and Pitfalls by mpapet · · Score: 2, Interesting

    I'm probably crazy but, I'm thinking it's kind of a "convince me" kind of post rather than a "solve my problem."

    Unless someone WAY at the top of the organization drives this, advocating the move is more likely to make you look bad. The first hiccup and the brown-stuff rolls downhill to your door. Present the facts and be done.

    If $65K really is an intollerably large chunk of change, then I don't really understand why there's even a question.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Perils and Pitfalls by robpoe · · Score: 2, Insightful

      Government entity (county level)

      The elected official has approved the move.

      The convincing has been done. We like the direct export PDF, we like the compatibility (and direct use of same product on Linux), might even be doing some linux stuff on the desktop in the future..

      Think of this as a first step ..

      --
      = Grow a brain...
  23. For all users, specify default Writer file format by ahziem · · Score: 2, Informative

    You must edit the OOo registry as shown here: http://www.oooforum.org/forum/viewtopic.phtml?p=10 5239

  24. A real earth-shaking idea by adolf · · Score: 5, Insightful

    Here's a thought:

    Pay someone else to do it. You're saving $65k, right? Give a (small) portion of that cash to someone familiar with OOo, and have them code the changes that you're after.

    Just because it's free software doesn't mean that it's afraid of money. Go ahead and buy the features you need.

  25. Re:Store the OpenOffice config file on network dri by alc6379 · · Score: 4, Insightful
    Just run the entire thing off of a thumb drive or live distribution that they can use anywhere they go that mounts your netdrive ;)

    Are you nuts? Do you really think you're going to get a whole organization to run in that fashion? Do you think end users are going to keep up with thumb drives and live CDs?

    I'm not going to belittle you, but that has to be the least feasible idea that I've ever run across as a suggestion for something like this. If the poster really wanted to do it properly, they'd implement roaming profiles, or at the very least, a mounted network share that synchronized at logout. If that was configured correctly, the operation of such a setup would be transparent to any program that accesses files from those directories.

    --
    I don't moderate anymore. Karma penalty for 90% fair mods? Can I mod that unfair?
  26. here's a cheaper way vs. $65K by agapits · · Score: 2, Funny

    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

  27. Re:Store the OpenOffice config file on network dri by buck_wild · · Score: 2, Insightful

    If you're at a customer site with your own (normal) laptop then you already have the appropriate settings, unless it's your first use of the laptop.

    Perhaps for those folks that roam natively (CEOs, sales folks, etc.) the thumb drive solution may work well. For everyone else, it's a way to carry porn home from your super-fast work connection, and something else to lose or break.

    --
    If all you have is a hammer, everything looks like a nail.
  28. OpenOffice Defaults by wehup · · Score: 2, Informative

    Open Office 2.0/StarOffice8 do not make it easy to configure defaults.  The first time any user opens the program on a given computer they are greeted with a EULA, and series of configuration screens. File save formats will default to OpenDoc.  One possible solution is to use scripting to copy the setup.xcu file from a fully configured user to the profile of each user.  This approach turns out to be rather clumsy. A solution that works involves modifying the installation files so that OO2/StarOffice8 sets up and configures each user with the desired defaults.

    I posted one possible solution to the OpenOffice.org forum on November 9th.  Link here:

    http://www.oooforum.org/forum/viewtopic.p html?t=24737&postdays=0&postorder=asc&start=15&sid =5c103f13a5f7aa0f198eb26452b22b36

    The following is for Windows System admins who want to maintain their sanity while transitioning users from MS Office to OpenOffice2 or StarOffice8. The idea is to introduce OO/Star without requiring an immediate switch to a new document format and to allow users to begin using OO2 or StarOffice8 without having to accept a license agreement and answer questions they may not know how to answer.

    Depending whether you are using StarOffice8 or OpenOffice.org 2.0 - Do the following on workstation after a a fresh installation of OO2 or StarOffice8::

    Add these lines to "C:\Program Files\Sun\StarOffice 8\share\registry\data\org\openoffice\Setup.xcu" at line 38:
    ((OR))
    Add these lines to "C:\Program Files\OpenOffice.org 2.0\share\registry\data\org\openoffice\Setup.xcu" at line 38:

    <prop oor:name="LicenseAcceptDate" oor:type="xs:string">
    <value>2005-11-05T18:30:11< /value>
    </prop>

    <prop oor:name="FirstStartWizardCompleted" oor:type="xs:boolean">
    <value>true</value>
    </pro p>

    In C:\Program Files\Sun\StarOffice 8\share\registry\modules\org\openoffice\Setup
    ((O R))
    In C:\Program Files\OpenOffice.org 2.0\share\registry\modules\org\openoffice\Setup

          Locate file: Setup-calc.xcu
          Replace " calc8" with "MS Excel 97"

          Locate file: Setup-impress.xcu
          Replace " impress8" with " MS PowerPoint 97"

          Locate file: Setup-writer.xcu
          Replace "writerglobal8" with " MS Word 97" **see note below**
          Replace "writer8" with " MS Word 97"

    After this is done, I suggest storing the modified files with the OO/StarOffice8
    installation (CD, Network share etc.). Write a post-installation batch file
    to replace these files on target computers immediately after installation.

    You may want to change out the respective files in the installation .cab files in the distribution. Doing so will eliminate the need for a post-installation script.

    The result is that all users of the target computer (new and existing) will
    not be prompted for user information on first use and will have the
    default file format set for compatibility with Microsoft Office 97/2000/XP.
    (This does not prevent the user from changing the default file save format
    any time she chooses)

    Then go forth - install and evangelize!
    Sell your users on the fact that OO/StarOffice8 is an *upgrade* from MS office.
    After about a year, go back and switch to OpenDoc and the battle is won.

    **note**

          I still have lingering questions about changing the ext.GlobalDocument
          ooSetupFactoryDefaultFilter from "writerglobal8" to "MS Word 97.
          It would be good for someone to test this to see if it is the right
          thing to do. .

  29. Tip: import MS, convert to OOo, export to MS by SysKoll · · Score: 4, Informative
    The key is to realize that complex MS Word documents are unstable: even when edited only with Word, they tend to accumulate cruft, that is, subtle changes of layout and format in parts nobody touched. When you open them with OOo, these unpredictable changes can really screw you up.

    So the trick is this: when you edit a .DOC file with OOo, convert it to the OOo format (.sxw) as soon as you start. Make sure the format is OK. Keep the file in .sxw format inside the company.

    When you need to interface with the outside world, publish the .DOC by saving in this format if needed. If you don't need outside people to actually edit the document, export it from OOo as a PDF, which is read-only, and publish the PDF instead of the DOC.

    And remember to edit only the .sxw file.

    --

    --
    Mad science! Robots! Underwear! Cute girls! Full comic online! http://www.girlgeniusonline.com/

  30. Re:hire a programmer? by Shawn+is+an+Asshole · · Score: 2, Informative

    Silent installs are easy with OpenOffice:

    msiexec /qb /i openofficeorg<version>.msi

    --
    "It ain't a war against drugs.it's a war against personal freedom" --Bill Hicks
  31. OO in Corporate Enviroment by vux984 · · Score: 2, Insightful

    It probably depends on the level of dependancy on 'advanced' features of MS Office... most companies I think have much less dependancy than they might think. For us, we simply phased OO in. 100% of the desktops had OO installed. 98% had Office uninstalled. Sure we could have left existing Office installs intact indefinately, but by standardizing we ensured that internally everyone was on the same version of OO. (getting rid of the myriad of various office version conflicts and also ensuring there wasn't any silliness where users with Office refused to use OO and users with OO felt like second class citizens or some other nonsense. For all internal documents we use OO. People adapted pretty quick. A few of our internal documents had issues, We cleaned them up, and there hasn't been an issue in months. We do get significant inbound correspondance in Excel/Word and even PP, but these are simple documents that OO handles flawlessly. And even if there were the odd formatting hiccup it wouldn't matter, we're not 'publishing' them, just getting information from them. (Purchase Orders, reports, etc). For outbound correspondance where we might want to send someone a word or excel document... we just don't... we settled on PDF a long time ago. Our pdf requirements are simple and easily met by free pdf creation software (ie not Acrobat). We do not require our customers have proprietary software. This has worked very well for us. Very occasionally we *are* required to deal with a large complex MS office file from a customer that OO just chokes on. No biggie, we have a couple units with MS Office on them, for just that purpose. So we only need 2 licenses of MS Office vs 150. Most of the use they see is for 'powerpoint' crap that vendors will send as 'training materials'... we just blast these through one of the "MS office" stations into pdf and distribute the pdf version. (Alternatively we could install the free powerpoint viewer from MS, but I don't see an advantage to that. Overall, for us, stability (by getting rid of the multiple versions of MS Office) has actually improved. Occasionally

  32. Re:neither does MS Office by hey! · · Score: 3, Insightful

    No, the parent post is right. I've had some very bad experiences with inconsistent Word rendering of long complex documents too. You can close a document and immediately reopen it on the same machine and it would be messed up.

    The only reliable and feasible answer I've found is to stick to simple layout when I'm using word processing program. If you want to get fancy, you should use a page layout program.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  33. Compatibilty Issues by protobion · · Score: 3, Informative

    I use Openoffice 2.0 on my computer and be advised that I faced serious compatibility issues when editing certain Microsoft Word (Office XP) files in Openoffice writer.
    These files were edited using the "Track changes" option in MS Office, that allows you to automatically mark changes that you have made to the file. Openoffice simply does not understand such a file and loads it without the accompanying change tracking information.

    Admiteddly, I liked OpenOffice at first and thought that MS Office could finally be replaced. However, several experiences (problems with huge loading time, slowing down the PC, OpenDocument format not popular etc.), including the above mentioned one, have forced me back to MS Office, and my personal conclusion is that MS Office has a lot more features and is much better as a regular word processing app. I hate paying Microsoft, but in this case, they take the cake. I'll have to wait for Oo3.

    PS : The only OO features that I noticed MS does not have, are the ability to render equations and make PDFs. However, MS Office + MathType + Adobe Acrobat Prof./any free PDF renderer can take care of that.

    --
    Essentia non sunt multiplicanda praeter necessitatem.
  34. Re:is it worth it? by robpoe · · Score: 3, Informative

    It's a 130 user government entity (county level). We have 1.5 people administrating it.

    (one 40 hour per week and 1 20 hour per week).

    The network is Novell/Email is Groupwise/Desktops are a mix of 98, 2K and XP.

    Existing licenses were purchased /w the machine.

    $65k for an office upgrade isn't in the cards, when we're having trouble getting $ budgeted for things we REALLY need, much less upgrading Office.

    We're doing mostly real plain jane documents, so complexity is not really an issue.

    --
    = Grow a brain...
  35. Open Office in a large municipal environment by mailuefterl · · Score: 2, Interesting

    It may not address your specific problem so much, but still be of interest for you:
    The Citiy of Vienna is currently making a partial "soft" shift to OSS on the workplace, using a selfdeveloped debian-based distribution called Wienux (Wien is the german name for Vienna) that also includes Open Office.
    Open Office is also beeing used on workplaces still using Windows and users are encouraged - but not forced - to switch to OO.
    See more at: http://www.wien.gv.at/ma14/oss.html.
    It's mostly German, but some of the Information is available in English too.

  36. Re:Distributing stuff in Word format is crazy by dchallender · · Score: 2, Insightful

    Have to agree, I prefer pdf or html where I know I have software that can render it. I used to have an old version of word "for emergencies" but over time I noticed that corporate docs always seem to be sent in one of the latest versions rather than the company using a lowest common denominator .doc format. Increasingly I use OpenOffice to open .doc files - odd formatting quirks aside at least it means I can read information - if anyone wants to guarantee a certain look and feel then pdf is the only viable option imho.

  37. Re:hire a programmer? by plebeian · · Score: 2, Informative

    For someone who wants ot perform a silent install using msiexec they should use the /qn switch not /qb /q n|b|r|f Sets the UI level. q , qn - No UI. qb - Basic UI. qr - Reduced UI.

    --
    "I myself am made entirely of flaws, stitched together with good intentions."
  38. Re:Store the OpenOffice config file on network dri by klubar · · Score: 2, Interesting

    The original poster is considering using OO to save money. The cost of thumb dries (even in bulk) will be $15/piece. Formatting, distribution, training and replacing lost drives will add another $20 to $30 per user. Add in the cost of a couple of snapped off USB ports when someone whacks the PC with the thumb drive in it, and you're pretty close to the cost of just buying office.

  39. Re:Store the OpenOffice config file on network dri by Directrix1 · · Score: 2, Informative

    He said live distribution, as in: on the thumb drive. Additionally, thumb drives are very easy to keep up with. Tell them to attach it to their key chain. It won't go anywhere then.

    --
    Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
  40. 95% of users don't need Excel sounds right by dedded · · Score: 2, Insightful
    "By my estimates, OO 2.0 is probably a suitable MS-Office replacement for about 95-98% of users out there" Well, that's a reflection of your experience.

    And a reflection of mine as well. I reckon about 70-80% of the Excel spreadsheets I see are purely documentation--without a single formula containing more than a single number or date. I recently received directions to a hotel in a spreadsheet! There are those for whom Excel is the right tool, but most can do all their spreadsheeting in any spreadsheet program at all.

  41. Re:Store the OpenOffice config file on network dri by Jonny_eh · · Score: 2, Insightful

    Don't forget to make it hidden!

    We don't want users seeing a directory and saying: "I don't use that! DELETE! Hey, why doesn't openoffice work?"

  42. Re:Store the OpenOffice config file on network dri by grahamdrew · · Score: 2, Funny

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

    --
    // Dumps core here
  43. Re:This is word processing, not desktop publishing by n8ur · · Score: 2, Informative

    But web view loses all concept of pagination -- it's just an endless roll of paper. The Word Normal view really is an excellent format for drafting because it makes the information (like page breaks) visible without slowing things down.

    There's a bug open for OOo to add normal view, and there's been a lot of noise recently on it, but since the bug has been there a couple of years and OOo 2.0 still hasn't implemented it, I'm not sure if we'll ever see a normal view. Which is a shame.

  44. Re:Store the OpenOffice config file on network dri by somersault · · Score: 2, Insightful

    when their car is stolen they'll soon learn ;)

    --
    which is totally what she said
  45. OOo 2.0 Network Installation Script by mgpeter · · Score: 4, Informative

    I created a Kixtart Net install script to rollout OpenOffice.org 2.0 - The requirements are simply a Domain Admin Account and the ability to access the Default Administrative Shares that Windows automatically creates.

    You can Download it at

    http://www.pcc-services.com/kixtart/scripts.html

    For the default saving into Office filetypes - All of the user settings are saved in XML files and you can edit these files before you roll-out OpenOffice.org. To do this simply adjust the settings on a separate machine, find out what file was modified to see what you need to change in the default installation. For instance I created a menu item for my script to add a "From Gallery" option to the "Insert - Picture" Menu.

    1. Re:OOo 2.0 Network Installation Script by mgpeter · · Score: 2, Informative

      Also, upon further thinking - to keep the settings consistant for each user as they use different machines, simply redirect the "Application Data" directory within the profile for each user to somewhere in their home directory. This way there program settings will follow them without actually having to use roaming profiles.

      To redirect folders, simply use Active Directory's Group Policy Objects, or use the older System Policy Editor to create an ntconfig.pol file to place in the netlogon directory of your Domain Controllers. (I also have a custom template for the System Policy Editor to use with Samba on my website.)

  46. Re:Store the OpenOffice config file on network dri by alc6379 · · Score: 2, Insightful
    I understand what he said-- it's still really unfeasible. What are they going to do-- restart a machine every time they sit down at it, or have to change seats? With a live distro, that can take a while.

    ...and then taking into account that not all systems in an organization will be USB bootable, or even have USB 2.0, making it fast enough to run a live distro.

    With the USB keys, I can see loads of broken USB ports in an entire organization as people plug and unplug those guys daily. Not only that, but many organizations have banned USB keys because of concerns such as industrial espionage. And considering the price of one needed to hold a decent live distro, that's not something I, were I an IT manager, would even consider handing out to everyone in an org.

    --
    I don't moderate anymore. Karma penalty for 90% fair mods? Can I mod that unfair?
  47. Re:Store the OpenOffice config file on network dri by RockDoctor · · Score: 2, Informative

    Just run the entire thing off of a thumb drive or live distribution that they can use anywhere they go that mounts your netdrive ;)

    Are you nuts? Do you really think you're going to get a whole organization to run in that fashion? Do you think end users are going to keep up with thumb drives and live CDs?


    More to the point, if the network security policy of the client organisation bans the use of "thumb" drives etc. you're stuffed. (As several of my client companies do. I often carry a hand-held computer with a serial cable and a terminal emulator because it's more reliable than floppies these days.)
    A good reason for doing this is to ensure that any data entering/ leaving the network goes through "sheepdip" computers. Another good reason is to stop the cow-orkers from downloading stuff on the work's internet charges and taking it home. Plenty of good reasons for doing it - see "diskless workstation" in the Jargon File.
    Where did I put that copy of Petter's NT electronic crowbar http://home.eunet.no/~pnordahl/ntpasswd/ ? Oh, it's in my briefcase where it should be.

    --
    Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"