TestNav 7 Technology Guidelines

Transcription

1 PearsonAccess TestNav 7 Technology Guidelines Configuring Your Test Delivery Environment Copyright 2012, Pearson Education, Inc. Published June 21, 2012

2 Document Revisions This list shows the recent updates to the. The most recent updates are listed first. June 21, 2012 Added section 2.1 IPv4 Network. Updated 5.0 Configure TestNav section. March 9, 2012 Updated section 5.0 Configuring Proctor Caching for TestNav. February 6, 2012 Added section 7.1 Windows and Mac Settings. December 1, 2011 Added the functionality in Configure TestNav to save client response backup files. Updated screen shots and instructions. Added Windows Browser Settings section. Removed requirement for Adobe Reader. Updated Section 4.0, TestNav System Details to include TestNav Folder and File Permissions, TestNav Logging, and EWS System. Changed the title of Section 3 from Deployment to System Requirements. Removed System Requirements from this document and moved them to a HTML page: August 26, 2011 Updated browsers and operating systems support chart under System Requirements. Updated URLs for firewall in sections 2.1.1, 2.1.2, and Added list of common error codes in section 4.1. Deleted third party logos. Updated the TN7 login screen in section 6. Replaced cover page with new PearsonAccess title page. April 29, 2011 Updated System Requirements for Test Delivery. Modified section Who Should Use This Guide, for a clearer description of the differences between the two manuals, section 1.1. Updated Configuring Proctor Caching for TestNav to implement new functionality, section 5. Added sentence about retaining the TestNav Logs directory when using imaging tools, section 4. Removed references to Linux; it will not be used for TestNav 7.5 spring pilots. Updated the cover page and title with PearsonAccess green banner. March 11, 2011 Updated Edit and Visit features to proctor caching servers. Updated screen shots. Updated Adobe Flash Player from Version to Version 10. Replaced the Pearson logo. Microsoft, Windows, and Internet Explorer are registered trademarks of Microsoft Inc. Firefox is a trademark of the Mozilla Foundation. Safari is a registered trademark of Apple Computer, Inc. Mac is a trademark of Apple Computer, Inc. Adobe, Acrobat, and Flash are either registered trademarks or trademarks of Adobe System Incorporated in the United States and/or other countries. All rights reserved. TestNav is a trademark of Pearson Education, Inc. or its affiliate(s). All rights reserved. 2 of 26

3 3 of 26

4 1.0 Overview Who Should Use This Guide Getting Help Network Setup IPv4 Network Intermediate Network Devices Firewall Windows Settings Proxy Servers/Content Filtering Proxy Environments Configuring a Proxy Environment for TestNav Domain Names Internet Bandwidth Wireless Testing Planning a Wireless Network Wireless Protocols Optimizing a Wireless Network System Requirements Freezing Your Online Testing Environment Disabling Applications and Processes TestNav System Details TestNav Folder and File Permissions TestNav Logging Common Error Messages EWS System Configure TestNav Proctor Caching Computer Response File Backup Locations Launching TestNav in a Browser Security Warning Trusting TestNav Content and Certificates of 26

5 7.1 Windows and Mac Settings Windows Security Warning Windows Browser Settings Mac OS X 10.4 and 10.5 Security Warning Mac OS X 10.6 Security Warning Readiness Checklist of 26

6 1.0 Overview TestNav is Pearson s proprietary test delivery application written in Java and Flash. The TestNav application is accessed over the Internet to deliver secure tests online. Test Delivery Workstations are used to deliver tests to students. Students access online tests by means of TestNav. Proctor Caching is software used to cache test content. Proctor Caching software pre-caches test content, which accelerates the delivery of test content to students and reduces the amount of bandwidth required for electronic testing. Topics covered in this guide include: Everything you need to know to set up TestNav for optimal performance Hardware and software requirements and other considerations Technical references TestNav installation 1.1 Who Should Use This Guide This document is intended primarily for network or IT personnel who are responsible for setting up and configuring a school s test delivery environment prior to online testing. See the following documents for more information: provides guidelines for computers and networks used for delivering online tests to students. PearsonAccess Technology Guidelines: Recommended Hardware and Software on the Support > Resources screen provides guidelines (both TestNav 6 and 7) for preparing computers used for test administrative tasks by educators (teachers, test administrators, test proctors, etc.). 1.2 Getting Help For technical support, please contact the Pearson Support Center. Tennessee (Eastern) Monday-Friday, 7:00am 8:30pm (Central) Monday-Friday, 6:00am 7:30pm. NPS npshelpdesk@ecollege.com 6 of 26

7 2.0 Network Setup Network setup, hardware and software requirements, and technical details should all be considered and in place before using TestNav. TestNav may fail or not perform optimally if it is not set up correctly. 2.1 IPv4 Network Your network must be set up to use IPv4 DNS (Domain Name System) servers. If you have not made any explicit changes to use only IPv6 for DNS, you should not have any issues. You will know if this is properly configured because your TestNav and Proctor Cache machines will communicate properly with one another. If you do not have any network issues between these machines, no action is required. If there are problems, contact your network administrator. Currently, IPv4 is the standard method for how computers communicate with each other. Because there are a finite number of IP addresses that can be used with IPv4, a newer version, called IPv6, was developed. An example of an IPv4 address is and an example of an IPv6 address is 2012:0db8:85a3:0000:0000:8a2e:0370: Intermediate Network Devices This section presents guidelines for schools using firewalls and proxy servers Firewall The TestNav 7 hardware and software requirements are located on the following page: Windows Settings A security setting may not allow Flash items to display properly, or even cause the test session to end prematurely. To allow Flash delivery on Windows machines, the javaw.exe file must be listed as an exception in the Windows Firewall Settings. 1. Go to Control Panel > Windows Firewall > Exceptions. 2. Check to see whether javaw or javaw.exe are listed under Programs and Services. 3. If either javaw or javaw.exe file is listed, make sure that the check box is selected for the file. The checked box marks the file as an exception. Verify that the file is specified for the location where Java is installed (either the workstation path: C:\program files\java\jre\bin\javaw.exe.. 4. If neither javaw nor javaw.exe are listed, click Add Program and browse to javaw.exe in your java directory (typically the file is in C:\program files\java\jre\bin\javaw.exe. 5. After locating the file, double-click the javaw.exe. The file will then be added to the list in the Exceptions dialog box and should be in checked status (which marks it as an exception in the firewall settings). 7 of 26

8 The Windows Data Execution and Prevention (DEP) feature can interfere with test delivery. It may cause items to not display to test takers when it is turned on for all programs and services on workstations running the Windows XP operating system. If you are delivering items on workstations running XP, set DEP for Windows programs and services only. 1. Go to Control Panel > System > Advanced tab. 2. Click on Settings (under Performance). 3. Click on the Data Execution Prevention tab. 4. Select Turn on DEP for essential Windows programs and services only. 5. Click OK Proxy Servers/Content Filtering The TestNav 7 hardware and software requirements are located on the following page: Proxy Environments Many school districts use proxy servers in their network environments. Proxy servers are placed between client nodes and the Internet and are used to forward requests from internal nodes to the Internet. Proxy servers may perform some or all of the following functions: Protocol Filtering to control which protocols are forwarded to the Internet User Authentication to control who can access the Internet Workstation Authentication to control which workstations can access the Internet Content Filtering to control which Internet content users can access Content Caching to speed up access for frequently visited sites In order for an application to access the Internet in a proxy server environment, the application must know the hostname and port number of the proxy server. Once the application is made aware of the proxy server, it sends all requests for network services to the proxy server for processing. The proxy server receives the incoming requests and must determine what to do with them. If all of the functions listed above have been implemented, the proxy server will: Verify that the protocol of the request is serviceable (e.g., ICMP, UDP, etc., may be blocked by the proxy server). Ask the user to authenticate that the proxy server does not already recognize them as being logged in. Verify that the source address of the request is on the list of allowed workstations. Verify that the requested network object is not blocked by an Internet content filter. (Most Internet content filter vendors provide lists of sites organized by category that administrators can decide to block or allow.) 8 of 26

9 Check the proxy server s local disk to see whether the requested object exists in cache. (If the object is in cache, the proxy server will send it directly to the requestor without having to access it from the Internet.) Assuming that the request passes all of the above steps, the proxy server then stores a record of the request in memory and issues its own request for the same object out to the Internet. When the reply returns to the proxy server, the server matches the reply to the original request stored in memory and forwards the reply to the original requestor Configuring a Proxy Environment for TestNav The TestNav 7 hardware and software requirements are located on the following page: Domain Names When accessing PearsonAccess, school and district systems must be configured to accept s from the following address domains: 2.3 Internet Bandwidth All communications for administrative tasks and test delivery occur via TCP/IP. All workstations must have TCP/IP installed and the network must be capable of routing traffic to the Internet. Prior to testing, an analysis should be performed to determine whether network bottlenecks exist and at what level of usage they potentially will impact testing. The protocol/port combinations used are: Protocol/Port TCP/http port: 80 TCP/https port: 443 TCP/https port: 443 Function Test Delivery and Administrative workstations Administrative workstations Prior to using TestNav, it is important to have measured the available internet bandwidth of your environment. Available bandwidth can vary depending on the time and whether the Internet connection is shared by multiple locations or if it is managed at a higher level, such as a district or region level. You can determine available bandwidth by using various internet speed tools or your school content filter or network management tools may include performance tools. Your available bandwidth will determine how many students can test simultaneously. For further information about Proctor Caching, refer to the Proctor Caching 7 User s Guide located on your Support page in PearsonAccess. 9 of 26

10 2.4 Wireless Testing Online testing will run successfully in a healthy wireless lab environment. The key to successful online testing on any network is a steady Internet connection with enough bandwidth to support the number of students testing at a given time. The number of access points needed for coverage, along with the location of each, is dependent on several factors: the number of students using the access point(s), the wireless protocols used, and the interference sources in the building (e.g., wires, pipes, wall and stud types, other signals, etc.). Key aspects of wireless networks, including planning, wireless protocols, and network optimization are detailed below Planning a Wireless Network Determining the number of access points needed for coverage, along with the location of each, depends on the number of students using the access point(s) and the interference sources in the building (e.g., wires, pipes, wall and stud types, other signals, etc.). A radio frequency (RF) site survey is a good first step in the deployment of a wireless network and is the most important step to ensure desired operation. A site survey is a task-by-task process during which a surveyor studies the facility to understand the RF behavior, maps RF coverage areas, checks for RF interference, and determines the appropriate placement of wireless devices. A proper site survey provides detailed information that addresses coverage, interference sources, equipment placement, power considerations and wiring requirements. The site survey documentation serves as a guide for network design and for the installation and verification of the wireless communication infrastructure. Do an RF survey at each location. Sites that appear to be similar could indeed require noticeably different wireless network configurations, placement, and equipment Wireless Protocols The wireless protocol used or supported by a wireless network can also determine the network s speed, and thus the quality of the online testing experience for students. Following are the key protocols used, sorted by speed: Protocol/Port Speed Range b 11 Mbps 150 ft a 54 Mbps 50 ft g 54 Mbps 150 ft n 300 Mbps 300 ft Note: The speeds and ranges listed for these protocols are the theoretical statistics what they should be capable of delivering under ideal circumstances. Real-world performance is normally 50% of the numbers above, based on overhead, interference, and other factors. 10 of 26

11 General protocol recommendations that we suggest include: Use a consistent protocol (e.g., n), as opposed to mixing protocols (e.g., some a, g, and n) if possible. Use protocol n, if possible, for its speed and range advantages Optimizing a Wireless Network The following example using a classroom with 30 computers illustrates the difference between a non-optimized wireless classroom and a wired classroom. In the wired classroom of 30 computers, each computer is connected to a separate network port using standard 10/100 Megabits/second (Mbps) network cables, which allow each computer to have a full 100 Mbps access to the Internet for a total bandwidth of 3,000 Mbps. 30 computers x 100 Mbps each = 3,000 Mbps total bandwidth In a non-optimized wireless classroom of 30 computers, a single 10/100 Mbps network cable brings an Internet connection to a wireless access point. The wireless access point then provides the class s 30 computers with wireless Internet. However, the classroom s total bandwidth is now limited to 100 Mpbs instead of 3,000 because of the bottleneck created by the single network cable. 30 computers sharing 1 wireless access point connected to a network port = 100 Mbps total bandwidth: In this scenario, both the wired and wireless classrooms should have access to 3,000 Mbps, but only the wired classroom does because each computer is connected to a separate network port using standard 10/100 Mbps network cables. To optimize the wireless network in the case above, the district or school could evaluate and update the hardware on the backbone of its network. For example, using 1,000 Mbps network cables and adding additional wireless access points will provide additional network bandwidth. 11 of 26

12 3.0 System Requirements The TestNav 7 hardware and software requirements are located on the following page: Freezing Your Online Testing Environment Note: If you are using NComputing, this section is not applicable. A user no longer has a physical computer when using NComputing. TestNav supports NComputing. For maximum reliability, performance, and security during testing Pearson strongly recommends that you freeze your online testing environment during scheduled testing windows once you have certified that TestNav works in your environment. This means that you should not implement hardware or third-party software updates or auto-updates during an online testing administration. A Safari auto-update or a JVM auto-update can potentially negatively affect the TestNav test delivery engine. Therefore, Pearson strongly recommends that the Apple Software Update function be disabled during test delivery windows. If you do not want Apple to automatically notify you when a software update is available, go to Settings > Software Update and deselect Check For Updates Disabling Applications and Processes To ensure maximum reliability, performance, and security during testing, we strongly recommend that only those applications and processes needed for online testing be running on test delivery workstations before TestNav is launched. The TestNav delivery engine does not permit access to other desktop applications (including applications that may be launched automatically) without terminating the test. Configure these common applications to NOT launch during testing sessions: Anti-virus software performing automatic updates Power management software on laptops warning of low battery levels Screen savers with auto message notification 12 of 26

13 4.0 TestNav System Details 4.1 TestNav Folder and File Permissions TestNav creates a Pearson directory in the home directory of the testing computer: Windows XP C:\Documents and Settings\username\Pearson\... Windows Vista and 7 C:\Users\username\Pearson\... Mac //Users/username/Pearson/... Note: Pearson recommends that the Pearson directory be excluded if desktop restoration tools such as DeepFreeze are used. 4.2 TestNav Logging TestNav client logging creates a directory called logs within the Pearson folder in the user s home directory. TestNav client logging captures the current system output and error messages for diagnostic purposes. This information is helpful should you need to contact our technical support team for assistance. If TestNav shuts down successfully, the log file will be automatically removed from the system. If TestNav does not shut down successfully, you can look up the error message in the Early Warning System 7 Reference Manual located on your Support page in PearsonAccess. You can also call the Pearson Support Center for instructions on retrieving the log file. 13 of 26

14 4.3 Common Error Messages The following table lists the most common error codes and messages you may see when using TestNav 7. Code Message 7004: Your login information is not recognized. Please try again. Message 7008: The session has not been started. It must be started before students in the session are able to take the test. Please contact your teacher or test proctor. Message 7014: Your test assignment must be resumed in Manage Test Sessions before you can log back in. Please contact your teacher or test proctor. Message 7016: TestNav has detected that another application attempted to become the active window, which may compromise the security of this test. TestNav has been shut down. You may need assistance from your test monitor to restart the test. Message 7026: Necessary components could not be downloaded. Please verify that you are connected to the Internet and try again. Message 8622: Unable to save student response file. Solution Refer to the URL and login information printed on the authorization ticket. The session status must be Started before you can log in to the test. Resume the student in Session Management and try logging in again. TestNav has detected another application is trying to take focus. Check the student log to see if TestNav captured the offending program. Internet connection has failed, or logged-in user does not have permission to write to the Pearson folder in the user s home directory. The Primary and (if specified) Alternate response file backup locations defined for the student s organization in the Configure TestNav area of PearsonAccess are inaccessible or invalid. Follow on-screen instructions in TestNav to browse to a new location where an encrypted backup copy of the student s responses can be stored to prevent loss in the event of power failure or loss of Internet connectivity. 14 of 26

15 4.4 EWS System The TestNav Early Warning System (EWS) is designed to help save student responses locally in the event of a network interruption. Selecting Response File Backup Locations EWS saves the student's responses to an encrypted backup file so the student can either continue testing or exit the system without losing data. This activity occurs in the background of the test delivery software while the software continues to provide test questions to the student. Selecting Response File Backup Locations You have the option of specifying the primary backup location within a TestNav Configuration (Test Setup > Configure TestNav). Selecting a secondary backup location is highly recommended. It must be different from the primary backup location. A network share is the recommended secondary location. The student needs to have write access to the primary and secondary backup locations, as well as the Pearson folder in the user s home directory. 15 of 26

16 5.0 Configure TestNav Two aspects of TestNav must be configured. Refer to the Proctor Caching Computer and the Response File Backup Locations sections. Both aspects are found on the same PearsonAccess screen. 5.1 Proctor Caching Computer The proctor caching computer downloads and stores test data, such as multimedia or test questions, and then serves that data to individual test computers from within the local network. This enables faster test page loading times and more efficient test taking. It is important to create TestNav configurations for your school before you create your test sessions for an online test administration. Once configurations are created for your school, you can use these configurations for any online administration. If you have created your sessions before a configuration is established for your school, you will need to manually assign a configuration to each test session. 1. Go to Test Setup > Configure TestNav. 2. Click New Configuration. Enter a name to identify the configuration, and then click Continue. 3. Select the organizations that will be associated to the configuration. Click Add Organization to select an organization not listed in the table. Click Remove to remove an organization. A configuration must have at least one associated organization. Click Continue. 4. Enter the details for the Proctor Caching Computer, including a name/description, IP Address, and Port. The default port is Response File Backup Locations When a student responds to a test item, that response is sent to the Pearson server. If that communication is delayed, the response will instead be preserved in a temporary backup location in a Saved Response File (SRF). This is done to ensure student responses are not lost and because the next test item will not be sent to the testing computer until it is confirmed that the response to the current test item has been safely recorded. On a busy network, with many testing computers attempting to send student test item responses concurrently, network congestion can occur. These backups prevent delays in testing while safeguarding student responses. Specify the primary and secondary locations where TestNav will store SRFs if the connection to the Pearson server is congested or interrupted. Choose backup locations that allow student accounts to have complete read and write access. Your options are to place the backup files in a directory on the computer the student is using to take the test or in a directory on a network file server. This chart outlines the pros and cons of each option. 16 of 26

17 Backup Location Options Local Directory on Testing Computer (TestNav client) Directory on Network Computer Pros Uses less internal network bandwidth Test item delivery will not be delayed by waiting for files to be written to the networked drive Backup file may be accessed from other computers, which is important if you have a hardware failure on a testing computer Cons Backup file is not accessible from any other computer, so a student cannot easily move from one testing computer to another to complete a test without the need for an administrator to manually move the backup file Uses more internal network bandwidth As a best practice, Pearson recommends using both by setting up both a primary and secondary backup location. The primary and secondary SRF backup files are updated as a student navigates from the item, or periodically for writing items. The next test item will be shown to the student as soon as the response to the currently submitted test item is recorded in any location the Pearson server, the primary backup, or the secondary backup but will continue to attempt to write to the other location until it is confirmed that the response has been recorded on the Pearson server. It is recommended that your Proctor Caching computer is not set as the location for either primary or secondary SRF backups, as this may increase traffic to the Proctor Caching computer beyond appropriate levels. 17 of 26

18 1. Enter the path to a local or network drive or select the Use Default Location checkbox. When the Use Default Location check box is selected, TestNav will save SRFs to the Pearson folder in the user s home directory, which is a location that varies by operating system. When specifying a custom location, the use of UNC paths is not recommended (for example, \\server\volume\directory\file). 2. Click Continue. 3. Click Save. Confirming Client Response File Backup Location To set up your client response file backup location, use one of the following options from the Configuration Details screen: 1. For the Primary Response File Backup Location, keep the Use Default Location box checked or uncheck the Default box and enter a location on your local computer. 2. For the Secondary Response File Backup Location, enter a shared network location. 18 of 26

19 3. When you are done, click Save in the top right corner of the screen to save these changes to the configuration. Deleting a Proctor Caching Location and Organization 1. Select the check box next to the configuration name you wish to delete, and then click Delete. 2. Select the check box next to the organization(s) you wish to delete, and then click Remove. 3. When you are done, click Save in the top right corner of the screen to save these changes to the configuration. 19 of 26

20 6.0 Launching TestNav in a Browser When students take a test online, TestNav is launched by entering the TestNav URL in a browser window from the testing workstation. To launch TestNav take the following steps: 1. On the workstation to be used for testing, open a new browser window. 2. Launch TestNav by entering the TestNav URL for your state, and then click GO. For example, the URL for the Reference site is: The TestNav URL for your state can be found on the Student Authorization Letter (test ticket). Be sure to enter the URL exactly as printed on the Student Authorization Letter in order to successfully launch the test. The Student Authorization Letter can be obtained by logging in to the PearsonAccess site (Home > Test Management > Manage Test Sessions > Session Details). When TestNav launches it checks to see that you have a supported version of the Adobe Flash Player installed. If a supported version of the Flash Player is not installed on the workstation, you will be prompted to upgrade Flash. Note: When TestNav is initially launched, you may first be prompted to trust the TestNav Java applet. This security warning screen may appear before the TestNav login screen and the Flash Player prompt. In order to successfully continue, you must trust the TestNav Java applet. Follow the specific instructions in the Security Warning section below to continue. Enter (or select) the URL from the Student Authorization Ticket (test ticket) Note: The letters at the end of the URL after the / refer to your testing program. Be sure to enter the URL exactly as printed on the 20 of 26

21 7.0 Security Warning Trusting TestNav Content and Certificates Because TestNav is browser based, you must trust the TestNav java applet the first time TestNav is launched on a computer. This is required by the browser in order to launch TestNav. The instructions below provide the initial steps for trusting the TestNav java applet. It is important that you do not bypass the warning screen and go directly to the TestNav login screen. Follow the instructions below for addressing the warning screen that appears on Windows and Macintosh computers. Note that the screens shown below may vary slightly depending on the version of the operating system. The following on screen message indicates that the security warning has been bypassed, and the TestNav applet is not yet trusted. You did not accept the applet permission/digital signature request, and TestNav cannot run properly without it. Please close your browser (all windows), re-launch, return to this page, and accept the applet permission/digital signature request when prompted. You must trust the TestNav Java applet so that TestNav can run properly. To continue, close your browser, and then re-launch TestNav. Wait for the security warning message to appear before taking any further action. Once the security warning appears, follow the instructions below to trust the TestNav applet. 7.1 Windows and Mac Settings If the below screen appears when the TestNav Java applet attempts to download, click No to continue to the TestNav login screen. To avoid this error message in the future, change this setting: Windows: Control Panel Java Advanced Security Mixed code (sandboxed vs. trusted) security verification Select the Enable hide warning and run with protections option button. 21 of 26

22 Mac: Applications Utilities Java Preferences Advanced Verify Mixed Security code (sandboxed vs. trusted) Select the Enable run with protections, no warnings option button. 22 of 26

23 7.2 Windows Security Warning If the below screen appears when the TestNav Java applet attempts to download, select the Always trust content from this publisher check box, and then click Run to continue to the TestNav login screen. 7.3 Windows Browser Settings On Windows machines, a session may fail to proctor cache even if no error message appears. This occurs when the browser has a proxy of its own and either the Automatically detect settings check box or the Use automatic configuration script check box is selected. Both of these settings override the proxy server setup. Because of this, the browser never uses the Proctor Caching machine for its Internet connection. In Internet Explorer, you will need to clear the Automatically detect settings and Use automatic configuration script check boxes in the Automatic Configuration section. [Navigation: Tools Internet Options Connections LAN settings] 23 of 26

24 In Firefox, you will need to select the Auto-detect proxy settings for this network option button on the Connection Settings window. [Navigation: Tools Options Advanced Settings] 7.4 Mac OS X 10.4 and 10.5 Security Warning When a warning screen appears as the TestNav java applet attempts to download, you have one of two options, depending on which version of the Mac OS (10.4 or Mac 10.5) operating system is running: 1. Click the Show Certificate button. 24 of 26

25 2. Select the Always trust these certificates check box, and then click Trust to continue to the TestNav login screen. 7.5 Mac OS X 10.6 Security Warning If the below screen appears when the TestNav java applet attempts to download, select the Allow all applets from xx.xx.xx.xxx with this signature check box, and then click Allow to continue to the TestNav login screen. 25 of 26

26 8.0 Readiness Checklist Requirement Section There must be a firewall between the workstations and the Internet using the appropriate destination/protocol/port combinations. The approved URLs must be allowed during testing. The approved domain names must be allowed. Configure the proxy environment as specified to properly run TestNav. Bandwidth must be calculated to determine how many students can test at one time. 2.0 For an optimum wireless performance, be sure that all correct protocols/ports are used and all the guidelines are followed. Test delivery workstations have TCP/IP installed and the network is capable of routing traffic to the Internet. Hardware and software requirements for test delivery workstations running TestNav have been satisfied. Test delivery workstations are running only those applications and processes needed for online testing before TestNav is launched. Applications that could launch automatically have been disabled on all workstations running TestNav. 3.0 Automatic notification when a new version of Safari or JVM is available has been disabled. TestNav logs have been set up in the appropriate Pearson folder. 4.0 Proctor caching computer(s) have been configured. 5.0 TestNav is launched in a browser using the appropriate URL of 26