Slashdot Mirror


Windows Drives Company To OpenBSD

Barry Lyndon writes "Computerworld reports that the nightmare of windows is driving PriceWaterhouseCoopers, one of the world's largest accountancy and business consulting companies, to OpenBSD and open source in general." From the article: "'My predecessor spent too much [so] I was told not to spend any money.' When asked what argument he used to convince management to use an open source solution, Uemura said: 'They didn't have an argument because they said don't spend any money.' 'They trusted me,' he said. 'The whole office was relying on one domain controller which was dying.' Uemura said a lot of work was done 'behind the scenes'. 'My experience is that if something has to be done, just do it - don't ask! They will thank you later,' he said."

8 of 476 comments (clear)

  1. It's just one of their offices... by JoostSchuttelaar · · Score: 4, Informative

    ... not the entire company. That would've been big news. Still good though :)

  2. Re:Does this mean by schwaang · · Score: 3, Informative
    No. TFA is about the back-end (servers). They apparently still use Windows for their desktops.

    (And believe me, you wouldn't just switch a bunch of employees over to BSD on a shoot-first basis without having your ass mailed to you with the personal belongings in your desk.)

    From the article:
    After the five-month migration, PWC's servers are now equally split between Windows and OpenBSD.
  3. Aurthur Andersen was Enron's auditor.. by Anonymous Coward · · Score: 3, Informative
    PWC was at the heart of the Enron scandal

    Hardly - you've mixed them up with Arthur Andersen.

    PwC actually benefited from the Enron scandle, in that it picked up some of the now defunct Andersen's practice. Furthur, PwC split off their consulting biz and sold it to IBM. http://www.computerworld.com/managementtopics/outs ourcing/story/0,10801,70769,00.html

  4. Have you ever used OpenBSD? by CyricZ · · Score: 5, Informative

    Have you ever actually used OpenBSD? If you have, then you would know that it's a massive time and money saver. Why is that? Because it just works. It's a well-engineered product. Your risk of security issues is virtually nil, and the support from the mailing lists often rivals that of anything from Microsoft or Red Hat.

    .

    --
    Cyric Zndovzny at your service.
  5. Uemera's responses from Undeadly.org by WhiteWolf666 · · Score: 4, Informative

    http://www.undeadly.org/cgi?action=article&sid=200 51024113247

    BTW: When he said, "just do it", he's not talking about informing management; he's talking about informing/surveying USERS. He's meaning, "Don't bother trying to convince users, instead, just tell them the procedures have changed, and this is 'The New Way' (TM) to do things. They'll do it, find it better/faster, than thank you"

    Shamelessly stolen, so don't mod me up.

    Mark T. Uemura (IP 221.249.159.51) (mark.uemura@gmail.com) on Tue Oct 25 14:18:17 2005 (GMT)
    It's unfortunate that reporters such as this guy would sensationalize
    a talk by carefully crafting his story from bits and pieces mostly
    taken out of context. So, in all fairness to my firm and to those who
    were not present, I feel compelled to set the story straight.

    First off, the story is not an interview even though it may come across
    as such. The title is rather sensational but I certainly wasn't
    desperate. There were problems and they were fixed and our team was
    just very resourceful in doing so.

    Gedda writes:
    > IT managers who want to deploy an open source solution but are worried
    > about company politics should go ahead and do it without asking,
    > according to PricewaterhouseCoopers (PWC) Japan IT manager Mark Uemura.

    No, this is taken out of context. What I said was that we had very big
    and important changes that we needed to make in order to restore network
    and application stability. My reference to just going ahead and doing it
    referred to making the necessary changes behind the scenes. It wasn't
    about company politics and it wasn't about migrating services from Windows
    to OpenBSD. My experience was that we did ourselves a disfavour by trying
    to inform and explain to users and management the technical reasons for
    the changes that needed to be made. In fact, all of the pushback had
    nothing to do with OpenBSD. We needed to migrate from an old Domain
    Controller with a corrupt Active Directory to a new one. We also
    introduced the concept of working on Application Servers in Terminal
    Services to take advantage of server power for resource intensive
    applications that ran very slowly on users' PCs. So, the push back was
    related to things like "you'll have to login to this new Domain rather
    than the old one from tomorrow onwards." or getting users to change the
    way they work and use applications running on a Terminal Servers for speed.
    In the end, when all was sad and done, users and management realized the
    difference that we had made; no more downtime or data loss. Furthermore,
    they've never had everything running so smoothly and as efficiently for
    as long as they could remember. Their IT problems went away as a result
    of our efforts and the decisions that we made.

    In fact, all of the migrations to OpenBSD were either behind the scenes
    where the users were oblivious to the changes. Well, almost oblivious.
    Often times we would get "Hey, the Internet is really fast today, cool!"
    or "Man, can you guys like spill some coffee in the server room or
    something? We're not used to this much uptime. It means we can't go
    home early anymore!"

    In those cases where users did have to interact with OpenBSD, it was
    always well received and positive such as moving off of a very slow VPN
    for remote access on to a quicker and more user friendly alternative
    such as port forwarding applications through OpenSSH.

    > Faced with an unreliable network, Uemura went ahead and migrated systems
    > from Windows to OpenBSD on the premise that management would trust his
    > judgement.

    Once again, migrating services to OpenBSD was not an issue. So long as
    we did not compromise security in doing so. Generally, we did so to
    improve security and that's what OpenBSD is famous for and yet ther

    --
    WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  6. Re:Wondering by Ath · · Score: 4, Informative
    You can completely run eDirectory with Zenworks (to manage group policies) on a Windows server. You can also use Windows clients without any Novell client software if you activate CIFS on the server (Netware or Open Enterprise Server with the Linux kernel).

    There is no need to run the Novell client anymore. We run Netware servers all over the world and no one uses the Novell client to connect to the services on them. They have iPrint, iFolder, and the Zen gina for connecting to a middletier server that is used to push applications and manage workstations. None of that is needed, but it makes the client management relatively painless.

    It seems that, with the miniscule pricing of eDirectory, there is not much incentive to develop and manage a separate bundle of LDAP services and tools. The problem often comes back to ignorance from the market, who do not realize the current offerings from Novell. Instead, the discussions is always about Novell products circa 1995, about the same year that Apple was going out of business.

  7. More from PWC IT Manager by LoganEkz · · Score: 4, Informative
    From Mark T. Uemura's post on OpenBSD Journal:

    It's unfortunate that reporters such as this guy would sensationalize
    a talk by carefully crafting his story from bits and pieces mostly
    taken out of context. So, in all fairness to my firm and to those who
    were not present, I feel compelled to set the story straight.

    First off, the story is not an interview even though it may come across
    as such. The title is rather sensational but I certainly wasn't
    desperate. There were problems and they were fixed and our team was
    just very resourceful in doing so.

    Gedda writes:
    > IT managers who want to deploy an open source solution but are worried
    > about company politics should go ahead and do it without asking,
    > according to PricewaterhouseCoopers (PWC) Japan IT manager Mark Uemura.

    No, this is taken out of context. What I said was that we had very big
    and important changes that we needed to make in order to restore network
    and application stability. My reference to just going ahead and doing it
    referred to making the necessary changes behind the scenes. It wasn't
    about company politics and it wasn't about migrating services from Windows
    to OpenBSD. My experience was that we did ourselves a disfavour by trying
    to inform and explain to users and management the technical reasons for
    the changes that needed to be made. In fact, all of the pushback had
    nothing to do with OpenBSD. We needed to migrate from an old Domain
    Controller with a corrupt Active Directory to a new one. We also
    introduced the concept of working on Application Servers in Terminal
    Services to take advantage of server power for resource intensive
    applications that ran very slowly on users' PCs. So, the push back was
    related to things like "you'll have to login to this new Domain rather
    than the old one from tomorrow onwards." or getting users to change the
    way they work and use applications running on a Terminal Servers for speed.
    In the end, when all was sad and done, users and management realized the
    difference that we had made; no more downtime or data loss. Furthermore,
    they've never had everything running so smoothly and as efficiently for
    as long as they could remember. Their IT problems went away as a result
    of our efforts and the decisions that we made.

    In fact, all of the migrations to OpenBSD were either behind the scenes
    where the users were oblivious to the changes. Well, almost oblivious.
    Often times we would get "Hey, the Internet is really fast today, cool!"
    or "Man, can you guys like spill some coffee in the server room or
    something? We're not used to this much uptime. It means we can't go
    home early anymore!"

    In those cases where users did have to interact with OpenBSD, it was
    always well received and positive such as moving off of a very slow VPN
    for remote access on to a quicker and more user friendly alternative
    such as port forwarding applications through OpenSSH.

    > Faced with an unreliable network, Uemura went ahead and migrated systems
    > from Windows to OpenBSD on the premise that management would trust his
    > judgement.

    Once again, migrating services to OpenBSD was not an issue. So long as
    we did not compromise security in doing so. Generally, we did so to
    improve security and that's what OpenBSD is famous for and yet there's
    so much more.

    > "PricewaterhouseCoopers is a Windows shop but we were forced to use open
    > source," he said. "I inherited a real nightmare with servers going up
    > and down. There were e-mail outages and on top of that there was a bad
    > relationship between our users and IT."

    Well it's either replac

  8. Almost... by shis-ka-bob · · Score: 3, Informative

    Katanas are used to cut others. The wakizashi is used for Seppuku,as well as cutting others that get too close. See the wikipedia article on Seppuku for details...

    --
    Think global, act loco