|By Luis Aguilar||
|March 10, 2005 12:00 AM EST||
Corporate migration to a Linux desktop requires rigorous premigration planning to succeed. The goal of migration is to finish with a Linux desktop that is cost-effective and responsive to the organization's needs. Without proper data center planning, the migration won't meet this goal and can become a technical and organizational challenge.
During premigration planning, it's crucial to answer the questions: What can I migrate? What do I need to migrate? How much is it going to cost? Who's going to do it? And when is it going to happen?
It's useful to keep in mind what the organization's IT requirements will be in the future, what the current hardware lifecycle is, and what the time frame is for software licensing.
A company or agency determined to move IT towards web-based applications for key business activities can easily switch to a Linux desktop with a browser such as Firefox. An organization determined to increase the hardware lifecycle from three to five years can consider Linux desktops to extend the life of its old hardware. An organization with a large long-term software licensing deal due that expires in the next three years should test the Linux desktop, if for no other reason than to use it as a negotiating weapon. Lowering costs with Mozilla, Evolution and OpenOffice does not necessarily require a complete migration to a Linux desktop.
Alacos (www.alacos.com) uses a best-practices desktop migration methodology called Migration Mapping. Migration Mapping consists of five key steps necessary to a successful migration. They are:
- Audit the Current Environment
- Analyze the Audit Data
- Design the Solution
- Map to an Organizational Matrix
- Automate the Organizational Transition
Audit the Current EnvironmentAn audit, the first key step, determines the actual cost of your current software and hardware environment, the applications currently in use and how the IT infrastructure is bound together. The point of this step is to determine how third-party applications, proprietary applications and external-facing applications (both proprietary and licensed) are deployed and used in your organization.
The base data to gather are the number of desktops in use, the number of applications used, the printer situation, line-of-business applications and the server and database infrastructure. Data on usage should be coordinated in a spreadsheet that contains information on software and hardware by department, by function and by business need. The cost of the OS, software, hardware, printing, back-end and support should be included.
The quickest, but least reliable, way to audit an organization's IT needs is to count software licenses. It will give you an overstated picture of software usage because most users rarely use all of the software installed on their desktops. This approach won't uncover any unlicensed software or illegal programs downloaded from the Internet that are being used. Knowing what's actually installed and used in an organization is crucial to creating a migration plan and integrating it successfully.
The most rigorous way to measure an organization's software use is to run an auditing and usage program on its network. Useful and actionable data will be available after a week of running auditing software, but it's preferable to run it for a full quarter to really understand changing software usage patterns with-in departments. For example, a finance department might use significantly different software during a quarterly or annual wrap-up than it does during a regular month.
There are various software tools available to conduct an audit. The Business Software Alliance (www.bsa.com) offers free trials of audit tools. Sassafras Software (www.sassafras.com) and Tally Systems (www.tallysystems.com) both offer commercial usage and auditing software. The cost can range from $15-$25 per computer for usage audit software licenses. Microcost (www.microcost.com) offers usage consulting in Europe and a lengthy report about software usage.
Beyond usage auditing, it's crucial to review the network and desktop data situation. Although many companies strive for all data to be on a network and backed up, that's rarely the case. Users have important business files on their desktops, as well as e-mail files and address books. Employees with laptops often don't keep data adequately synchronized to the network - if it's not automatic, they don't do it. Each organization is structured differently so it's important to spend time reviewing what business data resides on the network and what lives on the user desktop.
The last audit to undertake is to inventory the IT skills of both an organization's IT staff and its general population. Who on the IT staff can run Linux capably? Who already uses Linux at home? Who likes OpenOffice or StarOffice? Ask these questions at an early stage to identify the Linux champions in your company.
Analyze the Audit DataThe second key step, analyzing the audit data, requires reporting and visualization capabilities. Use a spreadsheet to sort and define data by group and function. Use Visio or Draw to create a visual map of the network and desktop environment. The goal here is to detail the IT structure and determine where migrating to desktop Linux would add value. It also pinpoints which groups can be migrated to Linux most easily.
It's usually a big surprise finding out what employees do with their desktops. The top activities are usually e-mail, Word documents and proprietary business applications (Internet or desktop). Applications like Excel and PowerPoint are usually found in heavy use only by small groups of key employees.
There are often a lot of programs installed on user desktops that shouldn't be there. They're either unlicensed software (remove it quick before you're visited by the BSA) or programs downloaded from the Internet. It's always interesting to find hacking tools hidden on the in-house network.
Games and Internet use are generally higher than most companies would like and good usage data may translate into changes in business policies. Switching to a Linux desktop will let IT administrators control software use more easily.
A typical audit will find that a company needs to replace its front-end mail client, office suite and web browser for security reasons and move employees to a network and printer environment using Samba.
Any changes in the desktop environment should reflect changes that have been made or will be made in the back-end infrastructure. Although one could switch to a new mail client and use a special connector to access a proprietary mail server, it's more useful to move the mail server to a Linux server running an open source mail server such as Open-Exchange.
Design the SolutionThe third key step is to design the solution based on an analysis of the IT audit. Because the decision-making is based on data, a solution can be developed that meets the organization's needs. The goal is to build a Linux desktop that replaces Windows at a fraction of the cost with no loss in business capabilities. A data-centered process will allow a company to fix on an IT structure that outcompetes rivals in the future.
Use the data to determine what applications and servers need to be migrated. Then find out whether an alternative exists on Linux or whether a compromise solution is available.
The usual way to develop a solution is to go through a series of choices for each application. First, find a Linux version of the software. If there's no Linux version, find a viable alternative such as StarOffice instead of Microsoft Office. If there's no alternative, then consider emulators such as CodeWeavers, Win4Lin or VMWare to run Windows applications on Linux. If the emulator approach won't work, then run a terminal server such as Citrix or LSP to deliver desktop access to the Windows program.
If none of these solutions work, then port the application to either a web-based application or a Linux desktop application. Porting an application is time-consuming and expensive, but if a company is already moving to web-based applications then that approach fits into its overall IT business strategy.
An organization will usually choose a Linux distribution that delivers enterprise-level support and training. The current desktop distributions that provide these services are the Novell Linux Desktop, Red Hat Enterprise, Sun's Java Desktop System, Mandrakesoft and Turbolinux. Xandros delivers customer support and service to smaller and mid-sized enterprises.
Choosing a new mail client, web browser and office suite is straightforward. Linux alternatives exist for each of these applications. Office suites that are commercially supported are StarOffice, while OpenOffice is freely available. The biggest problem with current office alternatives is that Excel macros don't work in Calc, the alternate spreadsheet program. This can be a challenge for moving financial and accounting groups to open source office alternatives, but it's worth re-creating those macros in Calc so everybody in a company uses the same standard program.
The other issue for office applications is communicating with external business partners. Using PDF as the standard for business communications will mitigate most document issues. PDF is also more secure because it's virus-free.
One goal of software design is to drop applications. Many companies rely on outdated applications that don't meet business objectives. Moving to more flexible and modern applications can result in significant efficiency and cost-savings.
Map to an Organizational MatrixThe fourth key step in the process is to map the software solution to the hardware across an organizational matrix. An application matrix for each group in a company is applied against the group's desktop hardware. Every piece of software that's going on the desktop should be determined prior to implementation. Every new hardware system should be defined at this point.
Once the solution has been mapped to the organizational matrix, then software, hardware and training costs can be established. Overall, the cost of moving to a Linux desktop and the cost of going to the next-generation Windows system will be equivalent so long-term savings are seen through the OS, office applications, lower IT costs for network management and lower security risks.
Automate the Organizational TransitionThe fifth and final key in pre-migration planning is to finalize the transition plan using automated migration tools. A transition plan consists of laying the software design and organizational matrix against the real-world organization and timeline to determine how to automate mass migration. Although these considerations have already played a part in developing the IT solution, this is the moment to place those plans against group schedules and deadlines.
The goal is to set down in detail who in the organization will migrate, when it will occur and what post-migration support will be needed. It's important to the success of the migration. Consider the quarterly and yearly cycles of the various groups. Take into account the trade show plans of the sales and marketing staff. Remember quarterly and annual financial preparations. Migrating during a group's busiest time ensures failure.
Every possible migration process that can be automated is defined at this point. Automation is crucial to mass migration. The transition plan should include who's doing the work using which migration tools for servers and desktops. Manually migrating user data and manually installing a desktop OS and software is a painstaking, error-prone process that requires an experienced Windows and Linux technician. Since it's time-consuming, migrating manually is expensive.
ConclusionThe most important part of a Linux desktop migration is to develop a rigorous migration plan during the pre-migration phase. Migration Mapping consists of the five key steps in a successful plan - Audit the Current Environment, Analyze the Audit Data, Design the Solution, Map to an Organizational Matrix and Automate the Organizational Transition. Following these five key steps provides a data center approach to revising an organization's desktop and software infrastructure.
Alacos: Linux Migration SpecialistsAlacos (www.alacos.com) a Linux software company located in Seattle, Washington is focused on the migration of Windows data to Linux. Alacos is the maker of Linux Migration Agent, which can move data from a Windows PC to a Linux PC via a crossover cable or network. Linux Migration Agent can move email from Outlook to Novell's Evolution e-mail client, Internet Explorer browser settings to Mozilla and accomplish many other time consuming tasks that are involved in a Windows to Linux Migration.
- WebRTC Summit Silicon Valley Call for Papers Now Open
- DevOps Summit Silicon Valley Call for Papers Now Open
- Fanning the Flames of Agile
- Call for Papers for Cloud Expo 2014 Silicon Valley Opens
- Docker + Stackato: The Perfect Workload Portability Solution
- An API Strategy Is a Business Strategy
- DevOps Summit Power Panel | Is DevOps Really Changing How IT Is Working?
- Cloud Infrastructure for the Real World
- Big Data Expo 2014 Silicon Valley Call for Papers Now Open
- SaaS Represents the Commoditization of Business Function
- WSO2 Introduces Industry’s First Enterprise Identity Bus With the Launch of WSO2 Identity Server 5.0
- Network Security: Is It Time to Think Like a Thief?
- Global Financial Firms Can Effectively Address Technology Risk Guidelines
- WebRTC Business Models: Building a Web-Based Telecom Co
- More Mainstream Businesses Depend on Open Source
- AMAG, HP, ImageWare Systems, March Networks and StrikeForce Discuss Security Solutions in SecuritySolutionsWatch.com Interviews
- Enterprise Cloud Analytics and Business Intelligence
- WebRTC Summit Silicon Valley Call for Papers Now Open
- DevOps Summit Silicon Valley Call for Papers Now Open
- Intelligent Systems in Transportation
- PEER 1 Hosting to Exhibit at Cloud Expo New York
- Learn How You Can Easily Extend Your Infrastructure with Microsoft Azure
- Fanning the Flames of Agile
- Select the Right Partner for Privileged Identity Management
- The i-Technology Right Stuff
- After Ubuntu, Windows Looks Increasingly Bad, Increasingly Archaic, Increasingly Unfriendly
- Linux.SYS-CON.com Exclusive: Linus Discloses *Real* Fathers of Linux
- SCO CEO Posts Open Letter to the Open Source Community
- Linus' Top Ten SCO Barbs
- A Closer Look at Damn Small Linux
- Netscape Co-Founder's 12 Reasons for Growth of Open Source
- Where Are RIA Technologies Headed in 2008?
- Linux.SYS-CON.com Exclusive: What Would UserLinux Look Like?
- *POINT - COUNTERPOINT SPECIAL* What's Wrong with the Open Source Community?
- Why Recovering a Deleted Ext3 File Is Difficult . . .
- Introducing "Cooperative Linux" - Linux for Windows, No Less