script that will collect all files in a zip or tar file and place them on a server before 

that server is backed up. Since these files are generally not that large, this 

method does not have a large impact on the backup.

Do remember to update the list of files as applications change or names of 

configuration files change with new versions.

Planning tip:

 Implement a method to back up key configuration and cache 

files from the client, to be used after client restore.

4.5.6  Virus mitigation

It is important to start protecting Linux clients from virus infection as soon as the 

clients become operational. Even though there are few viruses targeted at Linux, 

the number is expected to grow as the number of Linux clients grows.

Virus or worm protection is done in three ways:

E mail virus protection on the mail server

Regular virus scanning on the client (at least once a day or once a week)

Configuration of the client firewall to protect against worms

To scan for viruses on the mail server, several solutions are available, both OSS 

and commercial.

Virus scanning on the client should include all parts of the local file systems. 

Several solutions, both OSS and commercial, are available. The virus definition 

files of the tool chosen should be regularly updated automatically. The end user 

should not be allowed to stop the scanning operation.

The Linux client firewall should be configured to defend the client against 

infection by worms. The firewall configuration should not be changeable by the 

end user and should be regularly, centrally updated.

Planning tip:

 Plan to start virus mitigation procedures on Linux clients early in 

the migration process. Linux viruses will appear eventually. Be ready.

4.5.7  Example of administration of enterprise distributions

In this section we highlight how two recent enterprise desktop distributions 

handle the issue of administration.

72 

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