Linux Desktop Migration Cookbook from IBM

almondjoy writes "I was project leader for publication of this recent IBM Redbook, available for free download here: Linux Client Migration Cookbook: A Practical Planning and Implementation Guide for Migrating to Desktop Linux. At this point, I'm gathering input for what we could improve on, and what additional topics should be covered in a second version of the book. I realize this is a broad topic to cover in a rapidly changing environment. And because these books are developed by IBM there are some content limitations. Nonetheless, in the next version we want to continue making the book as useful as possible for anyone considering a migration to Linux on the desktop."

Comments

Re:Scanning through it...

[qbzzt]

Hi,

But it seems a bit too much for the average user. I mean it feels a bit like preaching to the choir. The guide will be most popular among people that already have the ability and desire to move to linux, not necesarily the average joe who is dipping his feet in the water to explore.

I don't think it's meant for Joe user. Instead, it is meant for Jack CTO and Jane SysAdmin who will be the ones moving Joe user from Windows to Linux.

Excel

[chris_mahan]

I notice that you leave out the potentially greatest problem: Very Complex Excel spreadsheets migration to OO.org.

This, for most companies, and especially for financial companies, will be an enormous deal-breaker.

If the book is challenged on that point, then you will lose credibility.

Re:Excel

[nfk]

They do address that point, when they say the following:

"As for migration of office productivity suite applications, at this time we believe that the odds for migration success currently favor organizations or end users that do not rely heavily on use of advanced functions in Microsoft Office..."

Or just read the grey box marked Important, in the second page of the introduction.

Re:Excel

[IO ERROR]

Keep your MS Office if you must; versions up to Office 2000 run just fine in Wine. Wine is also VERY good at those little custom developed in-house vertical apps that all large companies seem to have lots of.

For one phone company I know of, which has such a Windows app for their customer service representatives to work with customers' accounts, I demonstrated it running perfectly in Wine. I was able to access and make changes to accounts just the same as if it were running on Windows, with no trouble whatsoever.

If it's not mentioned already, some discussion of Wine and its suitability for those types of applications definitely should be included.

I applaud IBM for this.

[michael path]

I applaud IBM for this Redbook. It is very detailed in terms of providing an IT Administrator the ammunition to begin a pilot project for a Linux migration.

I've never seen a great book for migrating to Linux on the desktop for enterprise users. What really sets this book apart is its discussion on the ability to move Linux to the desktop while maintaining Microsoft products on the server side. While most organizations start by adding Linux servers, and never migrate their clients, this provides a strong start point for desktop migration.

IBM is very committed to Linux. For most of their server products, like WebSphere, Tivoli Access Manager, DB2, etc., Linux is certainly a preferred platform. This book, and the sale of their desktop division, confirms that they're trying to dethrone Microsoft from enterprise dominance and assert their place as a Linux (and AIX) software and services company.

Re:Preheat the oven...

[IANAAC]

Most of your Win apps-only stuff can be handled through Crossover Office. Does wmv videos, IExplorer, Notes/Sametime. Yes, it's basically Wine, but Crossover is optimized for precisely these things.

My suggestions:

[Cat_Byte]

Page 27: using smbmount to map network resources. You could mention you can do this via a gui very similar to the network neighborhood thing if they are in Gnome or KDE.

You might want to add Mac software to the list of *nix equivalents.

Add a section on locking down the workstation. It won't take people long to figure out they can ssh to anyones box and start messing with people. Any users familiar with setting up windows shares can only share certain folders (barring administrator access to c$, etc), but they probably won't know that if they use a crappy password, someone can gain access to every folder they have. Which reminds me, mention password rulesets and how to implement on the authentication server solutions listed.