If the change is extensive and the client is thin, replace the entire client image 
with a new one.
In early proof of concept tests and pilot migrations most of the changes can (and 
will) be done manually. When the size of the pool of Linux clients grows, this 
quickly becomes unfeasible, and more automated methods need to be put in 
place.
Planning tip:
 Plan to create an update mechanism during early 
proof of concept or pilot migration of the Linux client. 
Special care should be taken to make sure that the desktop and menu structure 
are not adversely impacted when updating (or maybe even removing) 
applications. The menu should keep pointing to existing applications to prevent 
stale menu items. Icons on the desktop should point to applications still available, 
and to the right version if multiple versions exist simultaneously.
Important:
 Always include desktop and menu structure in changes related to 
application updates. A successful update can appear failed because the users 
are left with stale icons or menu items.
4.5.3  Remote administration
The Linux client enables remote administration without having to install extra 
software. An administrator can log on remotely through one of the standard 
mechanisms, for example, ssh or telnet. This enables the administrator to 
analyze and fix problems remotely (except networking problems that would 
prevent remote access). It also enables the administrator to remotely run scripts 
to monitor clients and gain data about the state of the clients.
Monitoring of the clients is used to pro actively prevent problems instead of 
reacting to users not being able to work. It is used to detect problems with disks, 
memory, and CPU usage, or even with certain applications. There are several 
products or solutions available to monitor systems, from commercial products 
like IBM Tivoli Software to OSS solutions like Nagios and Big Brother.
4.5.4  Roll out of additional or replacement clients
In a steady state situation (that is, after the initial roll out of Linux clients) there 
will still be on going replacement and addition of client systems. For both types 
there should always be an up to date initial image to put on a new client. Some 
extra updates after installing the initial client should not be a problem, but a new 
client should not mean applying years of updates.
70 
Linux Client Migration Cookbook   A Practical Planning and Implementation Guide for Migrating to Desktop Linux






footer




 

 

 

 

 Home | About Us | Network | Services | Support | FAQ | Control Panel | Order Online | Sitemap | Contact

spain web hosting

 

Our partners: PHP: Hypertext Preprocessor Cheap Web Hosting JSP Web Hosting Ontario Web Hosting  Jsp Web Hosting

Cheapest Web Hosting Java Hosting Cheapest Hosting

Visionwebhosting.net Business web hosting division of Vision Web Hosting Inc.. All rights reserved