Technology Coordinator Training

1. Technology Coordinator Training

2. Statewide Training for CBT (WebEx) For FCAT (Retake/Grade 10 Math) Technology Coordinator TrainingFebruary 15, 16, or 17 District/School Assessment Coordinator TrainingFebruary 22, 23, or 24 For EOC (Algebra 1, Biology 1, Geometry) District/School Assessment Coordinator TrainingMarch 22, 23, or 24 Technology Coordinator TrainingMarch 29, 30, or 31 One training will be recorded and posted for any districts or schools who cannot attend. www.FLAssessments.com/Training

3. Administration Schedule and Timing Any deviation from this schedule requires written approval from the FDOE prior to implementation.

4. Complete District Readiness Activities Complete Final Phase of Computer-Based Assessments Certification. All schools who will participate in the FCAT or EOC computer-based assessments this spring must complete the survey in the tool. Email sent from Chancellor Haithcock on 1/26/2011 includes instructions and reference materials (forwarded to districts by Susie Lee). Phase III: Guide to the Computer-Based Assessments Certification (FCAT and EOC) Final Certification is also posted to www.FLAssessments.com/CertificationGuide District-level submission is due three weeks prior to the first day of testing. Districts will establish school survey deadlines.

5. Technology Coordinator Training Agenda Welcome and Introductions Overview Support Information CBT Glossary Configuring the Testing Environment Network and System Configurations System Specifications Preparation Information Proctor Caching Overview TestNav Overview Wireless Best Practices TestNav Configuration Best Practices TestNav System Check Tool Dial *1 to ask a question

6. Proctor Caching Downloading, Installing, and Verifying the Proctor Caching Software TestNav Downloading, Installing, and Launching TestNav 6.9 Pre-Caching Test Content TestNav Early Warning System Common Errors and Solutions Infrastructure Trial – Lessons Learned Contact Information Technology Coordinator Training Agenda, cont.

7. Support Information Where to find Support Resources www.FLAssessments.com/SpringRMS Spring 2011 Computer-Based Test Administration Manual for Grade 10 Mathematics and Reading & Mathematics Retakes (CBT Manual) www.FLAssessments.com/AdditionalResources TestNav Technology Guidelines TestNav Early Warning System Reference Manual Proctor Caching Guide Infrastructure Readiness Guide Contacting Pearson Support See Appendix C of the CBT Manual Note: Most www.FLAssessments.com links are simply redirects to www.PearsonAccess.com/fl. Dial *1 to ask a question

8. CBT Glossary PearsonAccess Used for almost all test preparation (e.g., PreID), setup, administration, and reporting tasks and accessible via the web. Administration must be selected every time you log in. Requires username and password setup. www.PearsonAccess.com/fl Proctor Caching Florida schools are required to use Proctor Caching. Pearson will provide the software and the instructions necessary to install and run Proctor Caching. Dial *1 to ask a question

9. CBT Glossary TestNav6.9 The computer-based platform that Florida will use for high-stakes assessments beginning in Spring 2011. TestNav6.9 is an application that is installed either on a file server or on each computer that will be used for testing. Dial *1 to ask a question

10. System Specifications for TestNav & Proctor Caching Dial *1 to ask a question

11. Preparation Information Infrastructure Trial Test The Infrastructure Trial Test must be run on each computer to be used for testing. (Not required to be part of district- or school-wide administration, although this is preferred.) Instructions are provided in the Infrastructure Readiness Guide posted to www.FLAssessments.com/AdditionalResources. Practice Tests/ePATs All students must complete a practice test prior to participating in any computer-based test administration. The ePAT Launcher and the test content must be downloaded on to each computer that will be used for the practice test. Instructions, the ePAT Launcher, and the test content are available at www.FLAssessments.com/ePAT. Dial *1 to ask a question

12. Proctor Caching – Network Diagram Dial *1 to ask a question

13. Proctor Caching – How does it help? Proctor Caching allows you to pre-cache test content to your local network before the test. Reduces burden on your ISP by eliminating redundancy in requests for test content. Stores an encrypted local copy of all pre-cached tests. A caching solution is required for Florida online testing and will deliver the best online testing experience. Dial *1 to ask a question

14. Proctor Caching – Misc. Runs on both Windows and Mac OS X. Does not require an underlying server-based operating system. TestNav must be configured through the installer or editing the proxysettings.properties file to communicate through Proctor Caching. Proctor Caching should be set up first so the IP address can be entered during TestNav installation. If all internet traffic must pass through an upstream proxy server, Proctor Caching will need to be configured to communicate through that device. TestNav requests test content from Proctor Caching on port 4480. Dial *1 to ask a question

15. Proctor Caching Computer Placement Can be at the lab- or the school-level. Should be as close as possible on the network to the TestNav workstations and prior to any potential bottlenecks. Use the TestNav System Check to determine the appropriate ratio of Proctor Caching machines to student workstations. Dial *1 to ask a question

16. Test Delivery – Local Installation Download and install TestNav on each workstation used for Test Delivery. Configure each machine to communicate with the Proctor Caching machine(s). More challenging to manage than a server installation. System automation tools like SMS (Windows) and Apple Remote Desktop (Mac) make local installs much more practical. Dial *1 to ask a question

17. Test Delivery – File Share Installation Download and install TestNav on a file share. Configure the file share installation to communicate with the Proctor Caching machine. Create a shortcut to the file share installation of TestNav on each workstation used for test delivery. Easier to manage than a local installation. Dial *1 to ask a question

18. Local Installation vs. File Share Installation Dial *1 to ask a question

19. Wireless Networks Best Practices DO use a local installation of TestNav A local install for wireless testing increases the odds of success. Local installations reduce network traffic on access points to just test content and student responses. DO NOT overload access points with too many clients. The bandwidth curve of online testing is different than normal internet usage. Use common sense wireless networking principles and past wireless performance as a guide. Reducing the client to access point ratio for online testing can avoid the access point bottleneck. Dial *1 to ask a question

20. TestNav Installation Best Practices The TestNav proxysettings.properties file is the only configurable settings file. This file can be edited with Notepad or TextEdit. Editable variables in proxysettings.properties Proxy_Host - Designates a proctor caching or proxy machine IP address Proxy_Port - Designates a proctor caching or proxy machine port number Primary_Save_Location & Alternate_Save_Location - Designates the Early Warning save locations Student machine logins will need full access to these directories TestNav/temp TestNav/Logs Early Warning Save Locations TestNav installation directory (read-only access) Dial *1 to ask a question

21. TestNav Installation Best Practices (contd.) Local Installation - If you use hard drive imaging tools like Deep Freeze, you must exclude the TestNav/Logs and Early Warning System save locations. Network Installation Do not run the TestNav installer on the file server itself. Run the installer on a client workstation and install TestNav to a shared folder on a network drive. Once installed to the network drive, ensure the proxysettings.properties file has valid file paths for the save locations. Dial *1 to ask a question

22. TestNav Installation Best Practices (contd.) Firewalls/Content Filters The following domains and ports must be allowed to pass through your Internet firewall or proxy system. Port 443 is for admin access only. Student level traffic is port 80. Hash encryption can inadvertently form a word. Dial *1 to ask a question

23. TestNav Installation Best Practices (contd.) Disable Popup Blocking Software (for PearsonAccess) A pop-up blocker will block the pre-caching screens from opening on administrative workstations. Configure Applications that launch automatically Any applications that may automatically launch on a computer should be configured not to launch during testing sessions. Common applications that may launch automatically include: Anti-virus software performing automatic updates, Power management software on laptops warning of low batteries, Screen savers, and Email with Auto message notification. Dial *1 to ask a question

24. TestNav Installation Best Practices (contd.) Screen resolution All tests are authored to a screen resolution of 1024x768 so make sure that your testing machines are capable of 1024x768 resolution. Screen Resolutions below this setting will cause an error as TestNav tries to load the test. Screen Resolutions above this setting will cause the test to appear smaller than the available screen size. Dial *1 to ask a question BRIAN and JENNY – need to check with CBT TEAM about Auto-resolution settings. Ensure this is true before we publish it. BRIAN and JENNY – need to check with CBT TEAM about Auto-resolution settings. Ensure this is true before we publish it.

25. System Check for TestNav The following steps will guide you through the process of using System Check for TestNav. The System Check tool can be found by going to www.PearsonAccess.com/fl and clicking on Support > Additional Resources. The specific URL is www.FLAssessments.com/SystemCheck  Click the TestNav 6 tab and follow the instructions provided. Once you see the “Congratulations” screen in the TestNav window, click the Network User Capacity tab. Dial *1 to ask a question

26. System Check for TestNav (contd) Click Add Caching Server. Enter a generic name for the Proctor Caching computer to be tested, the IP address of the Proctor Caching computer, and port 4480. Click Save. Dial *1 to ask a question

27. System Check for TestNav(contd.) Select the Florida Infrastructure Trial administration. Because this was designed to be the largest test Florida administers, using this administration will give the best possible scenario for all other administrations. Click Start and System Check will perform a bandwidth test. Once the test has been run, System Check will show an estimate for how many students can be tested on the specified Proctor Caching computer. Dial *1 to ask a question

28. System Check for TestNav (contd.) Click the Testing Volume Calculator tab. This tab will be used to estimate how many users can be tested with the bandwidth that is available. Dial *1 to ask a question

29. System Check for TestNav Enter the number of students that will be testing concurrently on a single caching server. Slide the green bar under “Available link speed between workstations and Proctor Caching workstations” to specify the available bandwidth between the testing workstations and the Proctor Caching computer. Dial *1 to ask a question

30. System Check for TestNav Now slide the green bar under “Average network utilization for the network between workstations and Proctor Caching workstations” to indicate the percentage of bandwidth normally used at this site (excluding the bandwidth congestion for testing). Once this is done, the “Outputs” box will now either be white, yellow, or red. Dial *1 to ask a question

31. System Check for TestNav In order for computer based testing to be successful, it is highly recommended that the Outputs box display a white background. If anything other than a white background is displayed, odds are that you will encounter difficulties during testing. Once all the tools within System Check for TestNav have been used, you have successfully established a plan for your testing environment. Dial *1 to ask a question

32. Demonstration Proctor Caching Downloading Proctor Caching Installing Proctor Caching Verifying Proctor Caching is Running TestNav 6.9 Downloading TestNav Installing TestNav Launching TestNav Dial *1 to ask a question

33. Mac Proctor Caching There are two files to be used for installing Proctor Caching software on a Mac: a template file and a command file.

34. Mac Proctor Caching Double click the command file and click Open on the security window. This will bring up another security window which prevents you from running the installer. The executable bit on the command file is not set so the OS will not allow you to execute it.

35. Mac Proctor Caching You must first correctly set the executable bit. Open Terminal and type “sudo chmod +x “ and drag the command file to the window to complete the path. Hit Return and you will be prompted for your admin password. Enter the password and hit Return and the executable bit is set.

36. Mac Proctor Caching Double-click the command file again and you are presented with the install screen. Type 1, then hit Return to begin the installation. Answer the proxy server questions appropriately and the install will complete.

37. Pre-Caching Test Content School assessment coordinators are responsible for setting up test sessions in PearsonAccess, and technology coordinators are responsible for pre-caching test content prior to testing. Test content will be available to be pre-cached at least one week prior to testing. Demonstration Configure browser settings Pre-cache test in PearsonAccess Dial *1 to ask a question

38. Pre-Caching Test Content (contd) Check Proctor Caching application to confirm cached content (see pages 101-102 of the CBT Manual) Windows Mac Dial *1 to ask a question

39. TestNav Early Warning System The TestNav™ Early Warning System (EWS) is designed to save student responses locally in the event of a network interruption. 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. Designate two (2) file save locations for student responses in the event of a connectivity loss to the testing servers. Best Practice: Primary response location should be a shared location because it allows access to stored student responses from one location. The alternate response location should be a location on the local workstation. Students must have full access to the designated “save locations.” When connectivity is restored and the students are resumed to continue testing, the locally saved responses are transmitted to the testing server and added to the responses already stored there. This activity occurs in the background of the test delivery software while the software continues to provide test questions to the student. Dial *1 to ask a question

40. TestNav Early Warning System TestNav will find the correct response file. A combination of the test ticket ID combined with the session token is used to uniquely identify a Student Response File (SRF). A SRF can only be used the next time the student resumes into a test. TestNav will only delete a SRF if it just successfully uploaded it. Dial *1 to ask a question

41. Reasons Why TestNav EWS Triggers TestNav client determines that neither Early Warning Save Location is viable. TestNav is unable to download portions of a test. The two above situations will result in immediate notification of the student. TestNav is unable to upload responses. This situation will result in notification of the student at the time of test submission. Dial *1 to ask a question

42. Early Warning – Screenshots (contd.) Invalid Save Locations Dial *1 to ask a question

43. Early Warning – Screenshots(contd.) Dial *1 to ask a question

44. Early Warning – Screenshots(contd.) Dial *1 to ask a question

45. Early Warning – Screenshots(contd.) Dial *1 to ask a question

46. Early Warning – Screenshots (contd.) Dial *1 to ask a question

47. Early Warning – Screenshots(contd.) Dial *1 to ask a question

48. Common Technical Errors/Solutions Proctor Caching Configuration error – Looping Not pointed to a proxy server to reach the internet Pre-caching Not changing browser settings before pre-caching Java JRE not installed TestNav Windows Firewall – Allow javaw.exe in the TestNav folder Network Local Congestion Errors Test loads slowly Percentage indicator increments slowly Note: See pages 106-107 of the CBT Manual for a table of common error codes and solutions. Dial *1 to ask a question

49. Statewide Infrastructure Trial - Lessons Learned Screen resolution must be set to 1024 x 768 on student workstations. Students must have full permissions to the TestNav/Temp and TestNav/Log folder. A primary save location must be set and students have read/write access to the save location. Screen savers, power management, and pop-up updates must be disabled on student workstations. Proctor Caching software must be installed and must be checked on each day of testing to ensure it is functioning correctly. Test content must be pre-cached prior to student testing. The test session must be started in PearsonAccess. Dial *1 to ask a question

50. Contact Information Pearson Support 877-847-3043 Florida@support.pearson.com Monday thru Friday, 7:00 am - 8:30 pm (EST) FDOE Bureau of K-12 Assessment CBT Specialists Jenny Black, 850-245-9470, jenny.black@fldoe.org Tara Gardner, 850-245-0742, tara.gardner@fldoe.org

51. Questions?This PowerPoint and one recorded training session will be posted to www.FLAssessments.com/Training Dial *1 to ask a question