Changes for the end user in migrating to the Linux client might be:

The end user no longer has full control over file system contents.

Even when the desktop presents a similar look and feel, the process of 

changing the desktop settings is completely different.

Right click menus are either gone or styled completely differently.

The look and feel of favorite desktop applications has changed, or those 

applications have been entirely replaced with functional equivalents.

Most of these changes can be managed and anticipated by providing proper 

training and enablement materials. To prepare for this training a mapping has to 

be created that maps client tasks to applications on both the old and the new 

client. This mapping may be different for all roles in the organization. For 

example, a transactional worker using an application that migrates to a Linux 

version will have very little impact. If an application is replaced by another with a 

similar function the changes may be large.

4.8.2  How to handle the unexpected

While it is possible to fully prepare the end user in advance, some problems will 

still arise post migration and during normal operation. Most of these problems 

are tasks for which support staff and administrators can be prepared and trained. 

To tackle the unexpected problems, the support staff has to use an 

OSS/Linux oriented approach to problem solving. To enable support staff to 

become used to this different approach, the differences have to be investigated.

In general, Windows operating system methodology for troubleshooting usually 

starts with:

Rebooting the system

Checking event log

Checking drivers and installing latest versions

The Linux operating system has more easily identifiable modules. Also there are 

lots of log files. This means that the methodology for troubleshooting starts with:

Identify the affected module of the Linux distribution.

Check all involved system logs starting with the sys log.

Verify configuration files do not contain errors or faulty settings.

Restart services involved.

Check errors generated by restart.

When using a Windows client, a reboot will solve more than half of the problems; 

when using a Linux client the problem usually remains after a reboot. This means 

that support staff has to learn how to approach the problem on the new client.

 Chapter 4. Technical planning 

85