6.1  Example client migration

We perform a migration of a single type of client to show how the methods 

described in the planning part of this book can be put into practice. The example 

client migration will be a simple one. However, the infrastructure integration is 

almost completely as described in 4.2,  Integrating with existing network 

services  on page 45. 

6.1.1  Assess the client usage pattern

The client we use for the example migration is an ITSO desktop used to write this 

book. The migration client has the following properties:

It is a registered workstation in an NT4 domain.

Intranet and Internet access modes using MS Internet Explorer.

Adobe FrameMaker  is the primary content authoring application on the 

client.

Paintshop Pro is used to create and work on screen shots.

Use network printers to print.

Outlook to MS Exchange for e mail.

The client is running Windows 2000 with Service Pack 4 installed. We will 

migrate to Linux, using the Red Hat Desktop distribution.

6.1.2  Identify important applications and infrastructure integration 

points

Since the user role for this workstation is primarily for writing books using Adobe 

FrameMaker, that most important application and the most important 

infrastructure components are printing and access to network file shares.

The first thing to note about the Adobe FrameMaker application is that there is no 

Linux alternative. There is no Linux native version, and moving to another 

application on Linux is not acceptable from a  business  point of view. In other 

words, FrameMaker is a unmigratable application that has to be handled like 

described in 4.7.2,  Terminal Server, Citrix Metaframe, or NoMachine solutions  

on page 82.

Printing using the network printers and accessing shares in the NT4 domain 

means that the methods from 4.2,  Integrating with existing network services  on 

page 45, have to be followed. 

114 

Linux Client Migration Cookbook   A Practical Planning and Implementation Guide for Migrating to Desktop