I. PURPOSE This document details a simple test plan for the Windows NT Gopher Server Performance Counters. II. OVERVIEW The Windows NT Gopher Server Performance Counters may be installed from \\KAYAK\RESKIT\GDCTRS. INSTALL.BAT will install the counters, and REMOVE.BAT will remove the counters. These .BAT files *MUST* be run from the GDCTRS directory. Running INSTALL.BAT will install the performance counters. These counters are used by PERFMON.EXE to monitor the activity of the Windows NT Gopher Server. The following attributes may be monitored: 0. Bytes Sent/sec This is the rate that data bytes are sent by the Gopher Server. 1. Bytes Received/sec This is the rate that data bytes are received by the Gopher Server. 2. Bytes Total/sec This is sum of Bytes Sent/sec and Bytes Received/sec. This is the total rate of bytes transferred by the Gopher Server. 3. Files Sent This is the total number of files sent by the Gopher Server. 4. Directory Listings Sent This is the total number of directory listings sent by the Gopher Server. 5. Searches Sent This is total number of searches performance by Gopher Server. 6. Current Anonymous Users This is number of anonymous users currently connected to the Gopher Server. 7. Current NonAnonymous Users This is number of non-anonymous users currently connected to the Gopher Server. 8. Total Anonymous Users This is total number of anonymous users that have ever connected to the Gopher Server. 9. Total NonAnonymous Users This is total number of non-anonymous users that have ever connected to the Gopher Server. 10. Maximum Anonymous Users This is maximum number of anonymous users simultaneously connected to the Gopher Server. 11. Maximum NonAnonymous Users This is maximum number of non-anonymous users simultaneously connected to the Gopher Server. 12. Current Connections This is the current number of connections to the Gopher Server. 13. Maximum Connections This is maximum number of simultaneous connections to the Gopher Server. 14. Connection Attempts This is the number of connection attempts that have been made to the Gopher Server. 15. Logon Attempts This is the number of logon attempts that have been made to the Gopher Server. 16. Aborted Connection Attempts This is the number of connection attempts that have been aborted by the Gopher Server. 17. Errored Connections This is the number of connections which had errors when processed. 18. Gopher Plus Requests This is the total number of Gopher+ requests received. III. TESTING These tests assume the test machine has TCP/IP installed, but does *NOT* yet have the Gopher Server installed. Also, LODCTR.EXE, UNLODCTR.EXE, and REGINI.EXE must be on the path. These tests also assume the user knows how to run PerfMon. 0. Run INSTALL.BAT from some directory other than PERFMON (i.e. cd to K:\FOO then execute \PERFMON\INSTALL). This should fail with an appropriate error message (must be run from PERFMON directory). 1. Do the same thing with REMOVE.BAT. This should also fail. 2. From the PERFMON directory, run REMOVE.BAT. This should fail. 3. From the PERFMON directory, run INSTALL.BAT. This should fail with an appropriate error message (Gopher Server not installed). NOTE: This will succeed on an IDW installation. 4. Run NCPA and install the Gopher Server. Reboot. 5. From the PERFMON directory, run REMOVE.BAT. This should fail. 6. From the PERFMON directory, run INSTALL.BAT. This should succeed. 8. Run PerfMon & verify that the counters are working. Select the Gopher Server object and the default counter. Then connect to the target machine via the Gopher client and verify the Bytes Total/sec counter is responding. Also, verify that each of the counters listed in section II are visible. 7. Run INSTALL.BAT again. This should also succeed. 9. Run PerfMon again to verify nothing screwed up. 10. Run REMOVE.BAT. This should succeed. 11. Run PerfMon to verify the Gopher Server object is no longer displayed in the "objects" combo box. 12. Run INSTALL.BAT again. This should succeed. 13. Run PerfMon to verify the counters were reinstalled. 14. While PerfMon is running, stop the Gopher Server with either NET.EXE or the Services applet. PerfMon should continue chugging along with no Gopher activity displayed. There will be no other indication in PerfMon that the service has been stopped. 15. While PerfMon is still running, restart the service. Verify that PerfMon is now displaying service activity by connecting to the server with the Gopher client. 16. While PerfMon is running, run REMOVE.BAT. This should succeed. PerfMon will still allow you to add/remove Gopher Server counters until you exit the PerfMon app. 17. Exit & restart PerfMon. The Gopher Server counters should not be available.