This outline describes a plan for adapting our computers to deal with the
Y2k problem. 

Outline for the Y2k Update Procedure

I. Update the Inventory.
    A. Let everyone know what we are going to be doing.
	1. E'mail
	2. Alert meetings
	3. By Department
    B. Locate each computer, update information in inventory.
	1. Check/update location.
	2. Get BIOS version, add to inventory.
	3. Check amount of free space on HDD.
	4. Check other info for accuracy: CPU/speed, HD size, RAM, O/S.
    C. Check software against inventory.
	1. Mirada version
	2. F-Prot and Command AV
	3. MS Office
	4. MS Office Programs: Access, Excel, PowerPoint, MS Word (Will
		match MS Office version unless they were installed separately).
    D. Get rid of error messages (i.e. "Computer/Workgroup name cannot be
	same as...").
    F. Test for Y2k compliance using the Y2k test disk.  There are
	Separate tests for RTC, BIOS, and O/S clocks.  Note results.

II. Software Upgrade
    A. Install and test Y2k fix files.
    B. Copy config files from programs to be upgraded. (list to be posted)
    C. Get rid of obsolete versions of software.
	1. MS Office (only if upgrading)
	2. Old F-Prot versions
	3. On-line Services
	4. MS Internet Explorer (if user doesn't want it and is short of
	   disk space)
    D. Delete unnecessary files.
	1. Unused config files older than a year or so.
	2. Files in DOS directory, pre Win95 files
	    a. Temp files
	    b. Rootsave
	    c. Batch directory
	    d. Remove unnecessary items from path statement in
	       autoexec.bat
	3. In Windows directory pre Win95 files
	    a. Temp files (leave the directory!)
	    b. Old backup files
	    c. Directory Aim95
    E. Upgrade software to Y2k compliant or most recent versions.
	1. Novell
	2. MS Office
	3. Mirada
	4. Command AV
	5. Netscape
	    a. For 486, install ver 3.01
	    b. For Pentiums install ver. 4.07
		i. After install, remove Aim subdirectory
		ii. Change default settings on public machines.
	    c. Configure settings to match those specified.
    F. Recopy bookmarks, various config files to appropriate locations
    G. Test all installed software.
	1. Check icons and start menu to see that they point to the right
	   places.
	2. Run any programs we install to make sure they work.

III. Follow-up
    A. Draw up a monthly maintenance routine.
	1. Post to a web site.
	2. Periodically remind users.
    B. Check settings in Command AV, Fortres, Netscape, etc.
    C. Consider other ways to disseminate info to general users.