native clients (that is, Personal Communications), Web interfaces (that is, 

Host on Demand and Host Publisher), or API connections (that is, HLLAPI).

4.1.6  Assessing the user

Another key element of a migration of workstations is the end user. In some 

cases, especially when talking about success and acceptance of a migration, this 

is the most important aspect at all. If users are committed to the change, looking 

forward to working in the new environment, or actively involved in development 

or deployment of the solution, then user expectation management issues can be 

minimized.

Questions to ask in this area are:

What are the most often performed tasks for a user or group of users? 

Are there definitions of user roles? If so, how are they defined?

What rules are defined, that users have to apply to?

Are there any defined exemptions from these user roles or rules?

Are there user specific settings, which need to be migrated, such as browser 

bookmarks, wallpapers, etc.?

Does any of the existing application uses plug ins or cookies for operation?

Are users involved in software selection process, and how?

Do users have the option to pull software from an installation repository? 

Is there a process to request, install, or delete software?

How often do users call the help desk and what are the average values of key 

measurements such as response time, re occurred calls, and level of support 

involved?

What is the skill level of users for the base operating system?

What is the skill level of users for productivity applications (that is, word 

processing)?

What is the skill level of users for business applications?

What type of devices (local and remote) do you require access to?

4.2  Integrating with existing network services

In this section we describe how to plan for integrating Linux clients in a existing 

network. We specifically look at how to incorporate Linux clients in a 

predominantly MS Windows based network/domain.

 Chapter 4. Technical planning 

45