Front cover Linux Client Migration Cookbook, Version 2 A Practical Planning and Implementation Guide for Migrating to Desktop Linux For any organization that is exploring or planning for a Linux desktop migration Provides in-depth detail on the technical and organizational challenges Includes methods for planning and implementation Chris Almond Jeroen van Hoof Nick Lassonde Ben Li Kurt Taylor ibm.com/redbooks International Technical Support Organization Linux Client Migration Cookbook, Version 2 A Practical Planning and Implementation Guideline October 2006 SG24-6380-01 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Second Edition (October 2006) © Copyright International Business Machines Corporation 2004, 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Forward . xv Bernard Golden, Navica . xv Greg Kelleher, IBM . xvii Preface . xix The team that wrote this redbook. xx Acknowledgements . xxi Become a published author . xxii Comments welcome. xxii Part 1. Choosing Linux. 1 Chapter 1. Introduction. 1 1.1 The migration landscape today . 2 1.2 Identifying suitable environments . 2 1.3 Strategic context . 3 1.4 Client environments. 5 1.5 Why Linux . 6 1.6 Linux overview and distribution choices . 7 1.7 Desktop Linux futures . 7 1.8 The rest of this book . 23 Chapter 2. The case for migration . 25 2.1 Why migrate . 27 2.1.1 Desktop security . 27 2.1.2 Costs related to Linux client . 32 2.1.3 Manageability of the Linux client . 34 2.1.4 Client customization . 37 2.1.5 Free software and the open source philosophy . 38 2.1.6 Ease of use and retraining . 38 2.1.7 New economies of scale . 38 2.2 When to migrate - Or not to migrate . 39 2.2.1 Desktop Linux markets — the threshold of entry . 39 2.2.2 Client roles fit thin and slim client model . 40 2.2.3 High number of migratable applications . 41 2.2.4 Organizational readiness . 41 © Copyright IBM Corp. 2004, 2006. All rights reserved. iii 2.3 What makes Linux so different . 42 2.3.1 The movements: free software and open source . 42 2.4 Migration goals . 43 2.4.1 Pilot migration . 44 2.4.2 Full migration. 44 Part 2. Planning the pilot migration . 47 Chapter 3. Organizational and human factors planning . 49 3.1 Assessing usage patterns . 50 3.1.1 Functional segmentation - Fixed function to general office. 50 3.1.2 Surveying user data . 52 3.1.3 User survey . 52 3.2 Establishing functional continuity . 53 3.2.1 Bridging applications . 53 3.2.2 Functionally equivalent utility applications . 54 3.2.3 Web applications. 55 3.2.4 Building bridges to the server . 55 3.3 Human factors . 56 3.4 Retraining considerations . 57 3.4.1 Bridging applications can separate retraining from migration . 58 3.4.2 Learning a new look and feel . 58 3.4.3 Familiar actions . 58 3.4.4 File systems: Everything has been moved . 58 3.4.5 Hands-on Linux prior to migration . 59 Chapter 4. Technical planning . 61 4.1 Assessing the client IT environment . 63 4.1.1 Assessing the client hardware . 63 4.1.2 Assessing the client software configuration . 65 4.1.3 Assessing data dependencies . 66 4.1.4 Assessing application equivalency . 67 4.1.5 Assessing the infrastructure . 67 4.1.6 Assessing the user . 68 4.2 Integrating with existing network services . 69 4.2.1 Setting the environment . 69 4.2.2 Authenticating within a Windows domain . 70 4.2.3 File sharing using domain shares . 72 4.2.4 Printing services in the domain . 73 4.2.5 DHCP and DNS configuration. 75 4.2.6 Web proxy interface . 75 4.3 Standardizing the desktop. 75 4.3.1 Linux distributions . 76 4.3.2 Linux desktop environments . 76 iv Linux Client Migration Cookbook, Version 2 4.3.3 Look and feel. 79 4.3.4 User lockdown. 83 4.3.5 Application choices . 83 4.3.6 File systems and partitions . 83 4.4 Migrating applications . 84 4.4.1 Moving back to client/server computing . 84 4.4.2 Logical segmentation - Thin, slim, or fat . 85 4.5 Client administration planning . 86 4.5.1 Operating system and vendor distribution updates. 87 4.5.2 Application updates. 88 4.5.3 Remote administration . 88 4.5.4 Rollout of additional or replacement clients . 89 4.5.5 Backup of clients . ..