1 / 63

Pre-Administration Tasks for Technology Staff

Pre-Administration Tasks for Technology Staff. The Office of Student Assessment Services February 12, 2019. Presenters. Scott Kelley, Data & Reporting Specialist Jodie Zalk, Test Administration Coordinator Elizabeth Pennington, Project Manager at Pearson

dredmond
Télécharger la présentation

Pre-Administration Tasks for Technology Staff

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pre-Administration Tasks for Technology Staff The Office of Student Assessment Services February 12, 2019

  2. Presenters • Scott Kelley, Data & Reporting Specialist • Jodie Zalk, Test Administration Coordinator • Elizabeth Pennington, Project Manager at Pearson • Joseph Henkelman, Level 2 Technical Support at Pearson

  3. Logistics for This Session • Questions may be asked at any time using the Questions feature on the GoToWebinar screen. • Questions about a specific student should be sent by email to mcas@doe.mass.edu. • We will attempt to answer all questions asked during the session; after the session, all questions will be answered and emailed out to participants. • This session is being recorded and will be available online in about one week at: • MCAS Resource Center ― mcas.pearsonsupport.com/training • In the section entitled “Training Sessions Previously Offered This School Year”

  4. Computer-Based Testing Components • PearsonAccess Next • Online test management system for principals, test coordinators, and technology coordinators to manage user accounts, student registration, and computer-based test sessions. • TestNav8 • Online testing platform used by students to take the computer-based MCAS assessments • ProctorCache • Software that allows for precaching of test content on a designated precaching machine located at the school or district. ProctorCache is recommended in order to reduce bandwidth requirements and provide a more seamless testing experience for students.

  5. 2018-2019 Technology Changes • ProctorCache for Mac available by contacting MCAS Service Center. • 2018 ProctorCache version will still work for Mac • Browser-based testing is no longer supported • Android is no longer a supported OS (due to test security concerns)

  6. Quick Guide for Technology Staff • Verify access to PearsonAccess Next training and operational sites. • Verify all student and ProctorCache devices meet technology specifications, ensure external hardware is available (e.g., headphones, chargers). • Configure devices and servers. • Whitelist provided URLs in any applicable network appliance or software such as Content Filters, Firewalls, and AntiVirus solutions. • Download and install TestNav and ProctorCache. • Create TestNav Configurations in PAN. • Precache test content. • Conduct the Infrastructure Trial.

  7. Bring Your Own Device (BYOD) • Districts should have already informed DESE; if not, email mcas@doe.mass.edu now. • Recommendations • Use devices managed by the school/district. • Confirm that devices meet minimum system requirements. • Update the operating system before testing. • Run AppCheck after installing TestNav. • Have small inventory of back-up devices and chargers, in case BYOD ones do not work on test day. • Have devices at school overnight charging the day prior to testing. • Chromebooks from 2017 and newer need to be licensed with Google, or managed using the Google Admin Console.

  8. 01 06 TestNav Installation Resources, Support, and Next Steps 02 ProctorCache Installation 03 Technology Staff Responsibilities during Infrastructure Trials CONTENTS 04 Troubleshooting 05 Saved Response Files (SRFs)

  9. TestNav Installation 01

  10. TestNav Introduction • Test content will be delivered to TestNav via the ProctorCache server (if ProctorCache is installed) or directly from TestNav servers (if ProctorCache is not used) and accessed with a student testing ticket printed out from PearsonAccess Next. • TestNav must be installed on all devices that will be used for testing. • Browser-based testing is no longer supported. • Students using a screen reader or other assistive technology can test using the app • Recommended: test the student’s external software with the app prior to administration

  11. Getting Started • Review technology specifications for student devices • Before updating a device’s operating system, confirm it is listed on the TN8 requirements page • https://support.assessment.pearson.com/display/TN/TestNav+System+Requirements • Download TestNav: http://mcas.pearsonsupport.com/technology-setup/

  12. TestNav Download • Each available platform has its own TestNav app. • Confirm that you are downloading the correct app for your device.

  13. Network Configuration • Firewalls, content filters, spam filters, and any other routing or blocking systems should be set to allow access to the following (must include asterisk): • *.testnav.com: 80 • *.testnav.com: 443 • *.pearsontestcontent.com • *.thawte.com • *.usertrust.com • *.comodoca.com • *.google-analytics.com (optional)

  14. Windows, OS X, and Linux Requirements for TestNav App • Supported Operating Systems • Windows 7, 8.1, 10 (includes Windows Store app) • OS X: 10.11, 10.12, 10.13, 10.14 • Linux: Fedora 24 (64-bit); Ubuntu 18.04 (64-bit)

  15. Chromebook System Requirements for TestNav App • Chromebooks require Chrome OS 66-71 • Must use installable Chrome OS TestNav app • 2017 and newer Chrome OS devices must be either managed or registered with Google in order to run TestNav and other applications in Kiosk mode • support.google.com/chromebook/answer/3134673?hl=en • Tablet mode is not supported (for convertible Chromebooks)

  16. Overview of Chromebook Setup Methods

  17. iPad System Requirements for TestNav App • Supported iOS: • 10.3.1 - 10.3.3, 11.2.5, 11.2.6, 11.4, 11.4.1, 12, 12.1, 12.1.1 • For more information on iOS 11.0, see Pearson Technical Bulletin: https://support.assessment.pearson.com/display/TN/TestNav+-+iOS+11+and+Secure+Testing

  18. Set Up TestNav on iPad • Install TestNav app • Run App Check • Confirm App Self Lock • Passing systems display • Failing systems display • Start the TestNav app • The first time TestNav is launched, it displays the Enable Microphone Permission message. • Tap/click Yes to grant microphone permission. • If a student taps/clicks No, TestNav displays another prompt.

  19. Demonstrations: TestNav • TestNav download site • App check • Logging in correctly (choosing a customer)

  20. ProctorCache Installation 02

  21. Internet Connectivity with ProctorCache Wireless access points – more is better Limit number of computers per wireless access point Distance – closer is better Limit obstructions Test performance before scaling Avoid load balancing of Wireless Access Points

  22. ProctorCache System Requirements and Recommendations • ProctorCache runs on Windows and requires a static (fixed) internal IP address • Does not require an underlying server-based operating system • TCP ports include 80/443 (communication with Pearson servers), and 4480/4481 (ProctorCache ports - LAN traffic only) • For setting up an upstream proxy, refer to the Windows “Set Up and Use ProctorCache” section in the TestNav 8 Proctor Caching User Guide. • https://support.assessment.pearson.com/display/TN/Set+Up+and+Use+ProctorCache • Organizations may set up multiple ProctorCache machines.

  23. ProctorCache System Requirements and Recommendations (continued) • Whenever possible, minimize the physical distance between ProctorCache machines and student testing devices. • Recommended: Set up proctor caching machines locally (i.e., at schools) rather than centrally (at a district office). • The default password for the ProctorCache software is t35t1n6. • Recommended versions for spring 2019 testing: • For Windows: ProctorCache Version 2018.11. If you have an old version of ProctorCache software on your machine, it is recommended you uninstall the old version prior to installing the new version. • For Mac: ProctorCache Version 2017.16. If you need assistance with downloading ProctorCache for Mac, call the MCAS Service Center.

  24. ProctorCache Setup – Download and Installation

  25. ProctorCache Setup – TestNav Configuration • TestNav configuration for ProctorCache is available: • For infrastructure trials,use the training site: • http://trng-mcas.pearsonaccessnext.com • For operational testing, use the operational site: • http://mcas.pearsonaccessnext.com • Configurations set up in the training site can be exported and then imported directly into the operational site.

  26. TestNav Configuration

  27. Precaching By Test • Precaching is available through the training site and can be found by selecting the Setup dropdown and selecting Precache by Test. • Precaching by Test needs to be done only once per test administration per caching server.

  28. Precache By Test prior to Creating Student Tests • Precaching for the Infrastructure Trial can be done now. • Precaching for operational testing will be available approximately two weeks before each testing window. • For grades 3–8: Schools should not precache the operational tests until two weeks prior to the start of their testing window: • Operational test content available on or around March 18 • High schools: • Precache operational grade 10 ELA content: March 12–25 • Precache operational grade 10 Math content: May 7–20 • Precache field test content for Biology and Intro Physics: May 10–24

  29. ProctorCache Setup – Precaching • TestNav configurations can be set up at the school or district level. • Recommended: Configure at the school level. • If a school does not have a configuration set up, the district configuration will be automatically selected. • An organization can only have one configuration. • However, each configuration can have multiple precaching computers set up.

  30. ProctorCache Admin Page Tests Tab: Clients Tab:

  31. Frequently Asked Questions • How do I verify my content is cached? • To find out if ProctorCache is working as expected, you may enter the following URL to confirm whether forms have been correctly precached: http://[Caching Computer’s IP Address]:4480 (i.e., http://192.168.100.50:4480) • How do I check whether the clients are connecting to the ProctorCache computer? • On the Sign In Screen on the TestNav app, there is a User Icon on the top, right-hand side of the screen with an App Check option. • Enter the Configuration Identifier found in PearsonAccess Next found at Setup > TestNav Configurations > select your configuration > Create/Edit Configurations. There will be an Configuration Identifier for each computer set up in that Configuration.

  32. Frequently Asked Questions (continued) • When should I purge test content? • Schools and districts that administered CBT in 2018 should purge previous test content and uninstall existing ProctorCache software before installing updated software for spring 2019. • Note: If using a 2018 version of ProctorCache for Mac, the software may be installed (there are currently no updates to the ProctorCache software for Mac). • At the end of the spring 2019 testing window, it is expected that schools and districts purge test content for security purposes (and to reduce the amount of data stored on the caching machine).

  33. Demonstrations: ProctorCache • Admin page “Clients” tab • Check for proxy version • PAN precache by test • Config page

  34. Questions & Answers (Use the “Questions” feature to ask questions.)

  35. Technology Staff Responsibilities during Infrastructure Trials 03

  36. Introduction • Purpose of an Infrastructure Trial: an opportunity for districts, schools, and students to prepare for the computer-based tests by simulating day of test network utilization • It will provide final confirmation that: • TestNav is configured correctly • Devices can successfully run TestNav • Networks will bear the full load during operational testing • Participating staff know what to do for computer-based testing • Who should participate: test coordinators, technology coordinators, test administrators, students • Two sessions on infrastructure trials: Feb. 13 and 15; register at www.doe.mass.edu/mcas/training.html.

  37. Getting Started • Download the Infrastructure Trial Readiness Guide from the MCAS Resource Center: http://mcas.pearsonsupport.com/manuals/ (Click on the “PearsonAccess Next Guidance” dropdown.) • Review the training modules on the MCAS Resource Center: http://mcas.pearsonsupport.com/training/

  38. Training Site for PearsonAccess Next • Infrastructure trials are done through the PAN training site: trng-mcas.pearsonaccessnext.com/customer/index.action • Usernames and passwords are always the same between the operational (live) and the training sites. If you reset a password on one site, passwords will be reset on both sites. • User accounts for operational and training sites are created separately. • If you need access to PAN, contact your District or School Test Coordinator.

  39. Before Conducting the Trial • TestNav should already be downloaded and installed on all student devices • Common applications are configured to not launch during testing • ProctorCache should already be downloaded and installed (recommended) • Configure internet firewalls, content filters, and spam filters • ProctorCache should be configured with TestNav in the PAN training site • Test content for the Infrastructure Trial should be precached to the ProctorCache machine(s)

  40. Before the Infrastructure Trial • Recommended: Before students participate in the trial, perform a preliminary system test to confirm whether you can connect to the ProctorCache computer from the student devices: • Create a small number of sample student records. • Create a PAN session and add the sample students. • Print student testing tickets and log into TestNav. • See the Infrastructure Trial Readiness Guide for instructions on creating sample student records and sessions, and for testing tickets: http://mcas.pearsonsupport.com/manuals/

  41. Managing and Monitoring the Infrastructure Trial • Test content can only be accessed through TestNav with a student testing ticket. • Testing tickets contain secure student log-in information and each student has a unique username and a session password. • Testing tickets are found in PearsonAccess Next on the Students in Sessions screen, under the Resources dropdown. • During operational testing, testing tickets are considered secure materials.

  42. Conducting the Trial • Test coordinator responsibilities (before the trial): • Creating sample student records in the training site • Moving the sample students into PAN Sessions • Printing student testing tickets • During the trial, technology coordinators will be responsible for: • Ensuring ProctorCache software is running • Monitoring LAN performance and Internet usage for bandwidth concerns • Troubleshooting as needed • Documenting any technical issues as they arise

  43. After The Infrastructure Trial • Document and report any technical issues • Meet with test coordinators and test administrators to debrief successes and areas to improve for live testing • Purge test content • Recommended: export the TestNav configuration from the training site and import it into the operational test administration on the live site • Setup > TestNavConfigurations > Import/Export TestNav Configurations • It is strongly recommended that schools do not make changes to their infrastructure in the time period between conducting a successful trial and the end of the computer-based testing window.

  44. Troubleshooting 04

  45. Expected Behaviors in TestNav • Not all problems have error messages, and not all problems are technical issues. • Users may encounter issues in TestNav that are different than anticipated or TestNav tools that do not appear to be working properly, but are actually working as designed. For example: • The Notepad cannot be resized. • The Exhibits cannot be resized (i.e., reference sheets). • Students cannot copy/paste text from secure test content (reading passages or test questions). They can only copy/paste text they write themselves. • A question appears as Not Answered in the Review menu until all parts of the question have been answered.

  46. TestNav Sign-In Error Codes • 9058: “The username or password you entered is incorrect.” • Ensure that the Username and Password are entered correctly, and that the student has the appropriate test ticket. • Ensure that the student is on the correct login page on the TestNav app. • Making sure that “Massachusetts” is displayed above the login area. • To get on the correct login page, click the User icon in the top right and select “Choose a different customer.”, then choose the correct page from the Apps Home Screen. Massachusetts Department of Elementary and Secondary Education

  47. Common Testing Error Codes • 1001: “Your test has been saved. Please notify your test administrator.” • Early Warning System initial message, does not indicate the issue, another error code will follow • 1009: “Unable to download test content” • Network connection issue between the testing device and Pearson servers. • 3005: “TestNav has detected that another application attempted to become the active window” • This could be caused by pop-ups in the background, power saving features, or system key combinations like ctrl+alt+del • 8026: “Unable to connect to the proctor caching computer. Please contact your administrator.” • Network connection issue between the testing device and the local Proctor Caching device

  48. Additional Common Testing Error Codes • 1008: “Unable to send final responses.” • The connection with the testing server was interrupted while the student was attempting to exit or submit the test, and TestNav was unable to upload responses to the testing server. See page 74 of the Principal’s Administration Manual for steps to take. • 1017/1018: “Primary/Alternate SRF location is not writable…” • TestNav displays this error when it tries to write to the SRF secondary location but fails. Check the path and verify it is valid, accessible, and that write access is granted. See page 75 of the Principal’s Administration Manual for steps to take. • TestNav Error Codes: https://support.assessment.pearson.com/display/TN/Error+Codes

  49. Steps for Technology Coordinators to Resolve Error Codes • If possible, do not power the device off until the student has exited TestNav. • If students power off the device without logging out first, they will remain in Active status in PearsonAccess Next and would need to be exited prior to being resumed. • If you only have a primary save location set for the device, do not move a student to another testing device. • This helps prevent student responses from becoming more difficult to retrieve. • If you set up a network secondary save location in the TestNav Configuration for all of the devices, this step can be ignored. • TestNav will always look in the primary and secondary save locations for a Student Response File when the student logs into the test. • Documentation can be found online for: • Principal’s Administration Manual Appendix A:http://mcas.pearsonsupport.com/resources/manuals/MCAS_Spring19_PAM.pdf • EWS Triggers: https://support.assessment.pearson.com/display/TN/Early+Warning+System+Triggers • SRF and Log Files: https://support.assessment.pearson.com/display/TN/Find+SRF+and+Log+Files

  50. Saved Response Files (SRFs) 05

More Related