4.1  Assessing the client IT environment

Before starting to look into technical details of a future Linux and Open 

Source based environment, it is critical that you thoroughly assess the current 

status of the IT infrastructure and the supporting processes. 

For the IT Infrastructure, many components will come to play, not only the core 

installation of a desktop installation, but also the any other infrastructure 

components around it. This might be servers providing file and print functions, 

databases, directory services, application servers (both native and Web based) 

up to mainframes, which will be accessed via host emulation or API based 

communication. Some of the key considerations and methods in this area are 

discussed in more detail in 4.2,  Integrating with existing network services  on 

page 45.

Because we are focusing on migrating client workstations, two key areas in the 

client IT environment need to be surveyed:

Human interactions: The end user application usage patterns

Physical systems: Desktop system properties, special devices, and peripheral 

integration requirements

4.1.1  Assessing the context

Prior to starting with any technical aspects of a migration, what type of 

non functional requirements are defined for this migration project need to be 

verified. A verification of those goals against the IT strategy is another critical 

success factor. 

Questions to ask in this area are:

What are the tactical goals of the migration?

What measurements of success will validate achieving those goals? 

What are the financial aspects of the migration (budget, return on investment, 

justification, etc.)?

What are the strategic goals for the migration? How does the migration fit into 

the overall IT strategy for the organization?

4.1.2  Assessing the client hardware

You need to complete a physical systems survey of all client systems targeted 

for migration. The results of this survey will enable you to identify any hardware 

support issues, and define rules for buying and replacing systems in the future.

 Chapter 4. Technical planning 

39