|By Rob Sutherland||
|March 16, 2004 12:00 AM EST||
At the end of 2004, Microsoft will stop supporting Windows NT. At that point, anyone using Windows NT will have several choices: follow Microsoft's upgrade path to Windows 2003, continue to use Windows NT without Microsoft support, or switch to Linux.
Switching to Linux is the cheapest, safest alternative, according to such companies as Tramp Trampolines and Polyscientific Enterprise Sdn. Bhd, a distributor of chemical and industrial products. Both of these companies made successful migrations from Windows NT to Linux and are happily using Linux as a desktop today, bringing them cost savings and greater stability.
This article examines the Windows-to-Linux path for organizations using Windows NT as a desktop. We'll look at the first step, taking stock of the current situation, and then look at the choices that have to be made based on that. Then we'll look at the migration process and examine some of the problems and successes organizations have faced in making migrations work. Also covered are some of the recent technologies such as Live CDs and WINE (www.winehq.org), Win4Lin (www.netraverse.com), as well as application equivalents and data conversion tools that make migration less painful, such as Rekall (www.totalrekall.co.uk).
Convincing the BusinessThe first step in any successful migration is to have a solid commitment from the decision makers. Every migration I have ever been involved in has strongly resembled an ungodly combination of a train wreck and a bar fight. It takes a clear plan (fail to plan, plan to fail) and a lot of willpower combined with flexibility to get through to the end while reducing to a minimum the amount of bloodshed along the way. Without real buy-in by the decision makers it's not just difficult, it's impossible.
It's crucial to understand as well that not all the decision makers are in the boardroom - it's best to have a core of active supporters as a core team and a majority who are at least passive supporters of the migration effort. A little education and communication up front will go a long way in reducing the costs of the project and ensuring the active, willing cooperation of your core team. This is the second step in a successful migration. When I say core team, I don't mean the experts that may be brought in to install and train users; I mean users who have bought into the new technologies and are willing to put out the extra effort needed to carry it through. You'll need them.
Identifying the Task at HandThe third step in a successful migration is to take stock of the current state of the shop. You'll need to answer these questions:
- What are our key applications?
- What dependencies do they create?
- Who are our key users?
- How big is the job?
Once you have the answers to these questions you'll be in a position to conduct a systems triage. In a systems triage you divide your key applications into those that can be replaced by functional equivalents, those that cannot be replaced, and those that must be converted in detail. An example of the first group might be a word-processing package - OpenOffice, for example, can replace Microsoft Word.
The second group comprises two categories: applications that are unacceptably expensive to replace because of reengineering or retraining costs, and applications that cannot be replaced because of external requirements. A company may find that the retraining costs for moving people from Adobe Photoshop to the GIMP are unacceptably high, for example. Or they may have a requirement to provide material in certain formats that they cannot modify, such as a supplier whose largest customer stipulates that certain information must be transferred using Access or Excel.
The last group encompasses the "homegrown" components of the desktop system, such as Word macros or Visual Basic utilities, which would need to be rewritten in a new package.
This last group is where most of the migration "gotchas" lurk, and early identification of them is critical. Although zealots on both sides will often try to show that the choice between Windows and Linux is all or nothing, this isn't true in most cases. There is a set of technologies that allow Windows applications to be run on Linux. There are a lot of options here, from WINE, CodeWeavers (www.codeweavers.com), and Win4Lin, which provide a basic environment for executing Windows applications directly within Linux, through to full operating system emulation environments such as VMWare (www.vmware.com).
These technologies are quite solid and when properly applied can give you the best of both worlds. Users use applications, and applications use operating systems, so a solution that gives the users applications that they can work with and the applications a stable, secure operating system may be the best solution - or at least one that gives you a little more breathing space.
Building the New EnvironmentOnce the analysis is done, you'll be in a position to make evaluations that will lead to firm decisions about the specific technologies and packages you'll be using. This is an area where open source stops being an abstract and becomes a serious business advantage. You don't need to buy a pig in a poke - you can get several pigs and make them jump through hoops for a very low cost.
If you take advantage of Linux on bootable CD technologies such as KNOPPIX, you can reduce the cost of testing and evaluation significantly. For example, rather than setting up a test machine or network and moving over a typical set of material, you can simply boot your existing machines with KNOPPIX and try opening your existing Word documents with OpenOffice.
Your core users can try things like switching over to Linux and falling back to Windows when required. There are also a lot of resources for choosing Windows application equivalents on Linux and many articles describing Windows-to-Linux migration in general.
The best guide I've found is the Migration Guide put out by KBSt Publication Service, a 441-page PDF containing a thorough and well-written analysis sure to be useful to anyone looking at this.
The absence of license fees and ready availability of much of the software sharply reduces the cost of doing an incremental migration. The variety among Linux distributions is an advantage here, rather than a liability, because no matter what your existing hardware base is, you'll be able to find a distribution that will run on it. If the one you find can't do what you want, you'll be able to determine the needed upgrades much more exactly than by simply taking a minimum requirements list from a vendor's sales material. On the other hand, if you want to obtain professional services to assist your evaluation, companies such as IBM (www-1.ibm.com/linux) and Racemi (www.racemi.com) offer consulting services in this area.
I haven't found any products designed specifically for assisting desktop migrations; however, two tools I often recommend are OpenOffice and Rekall. OpenOffice's ability to read Word and Excel formats and write a variety of formats make it an ideal replacement for the Windows equivalents, while Rekall allows you to read an Access database via ODBC and write that data to PostgreSQL, MySQL, or a number of other databases. For the vast majority of desktop systems this will allow you to transfer the user data.
In situations where you cannot easily transfer data, you may have to change your approach to looking for an equivalent or compatible software package. For example, Polyscientific Enterprise had a problem with Lotus Smartsheet documents not being readable by OpenOffice, and reassessed their business problem to look for a solution within another package.
You can use one of the methods described previously to run a Windows application on Linux. In any event, when you have decided on the correct mix of application packages, make sure they can work together. Having your core team perform interoperability testing by actually moving real data around and verifying the results is the best way to discover problems. Once again, solutions such as Knoppix can be a real help at this point.
Realizing the MigrationSo, after you've gotten a solid commitment, decided on your migration plan, assembled the core team, and assembled and tested your solution, you're faced with training and supporting your end users. Some suggestions to make this easier:
- Try to do it a few users at a time, or one functional group at a time.
- Evaluate the material available for free from places such as Openoffice.org, and make this material available through an internal Web application such as a forum or a Wiki.
- Set up a Web-based training package such as Moodle (www.moodle.org).
- If you can, make your core team available to help people out.
- Test your chosen architecture and software suite and ensure that it fulfils your functional requirements.
- Test the interoperability of your new solutions with your legacy systems and verify that they work in a production environment before you commit them organization-wide.
- Test your training and documentation setup using typical users with no previous background. Remember that if people can't be brought up to speed on the new solutions in a cost-effective way, it won't work.
- Expect problems. Testing will reduce, but not eliminate, them and you'll have to react quickly while under a great deal of stress
SummaryPeople and commitment are the key to a successful migration. If you have them you can succeed - and if you can take advantage of the open source edge, you can do it for a lot less. Migrations are always a high-stress activity and desktop migration is particularly so because it forces users to cope with more-visible changes than, for example, upgrading an e-mail server. Careful goal definition, planning, solution evaluation, and end-user training are all critical components, as is a dedicated core team and a step-by-step approach. The lower cost, greater interoperability, and greater flexibility of open source technologies, when used properly as part of well-thought-out and coordinated plan, will get you to the end of your migration path with a stable, secure, and lower-cost desktop.
|John Dean 08/24/04 03:42:32 AM EDT|
- Linux & Games: Installing TransGaming's Latest Release, Cedega 4.0
- Migrating to Linux not easy for Windows users
- Migrating the Desktop from NT to Linux
- Sailing the Wine Dark Sea With Macromedia Fireworks MX
- Linux on the Desktop: Bringing Linux into the Corporate Environment
- How to install Neverwinter Nights on Linux
- Graphics Still the Hot Topic in Open Source .NET
- Fedora Software
- Novell Paying Microsoft Not to Sue
- Catching up with WINE