Technology Readiness Training Updated: 1/24/2018 Welcome to the Technology Readiness presentation. At the end of the presentation, you’ll receive contact information for Indiana Customer Service. We will pause at several points for questions. Remember to type your questions into the chat window and direct the questions to Host, Presenter and All Panelists. The PowerPoint for today’s presentation will be available on the Indiana ISTEP+ and IREAD-3 Resource Center at http://indiana.pearsonaccessnext.com.

Agenda New Technology Requirements Timeline of Important Events Overview of Technology Resources TestNav 8 Early Warning System ProctorCache Local Infrastructure Trial Support Here is today’s agenda. First let’s examine a summary of the new technology requirements. Next we will look at some key dates for the upcoming administration. We have an overview of the key technologies, then we’ll examine the various resources available on the Indiana ISTEP+ and IREAD-3 Resource Center. After that, we focus on TestNav8, the Early Warning System, and ProctorCache. Next, we will cover some information related to Local Infrastructure Trials, and finish with support information for contacting support.

New Technology Requirements Here is a quick glance at some new technology requirements.

New Technology Requirements TestNav 8 New version of TestNav Support for iOS versions 10.2, 10.2.1, 10.3.1 - 10.3.3, 11.1, 11.2 iOS 9.3.5 and earlier NOT supported iPad version 2 and 3 no longer supported ChromeOS versions 57- 63 now supported ChromeOS 56 and earlier NOT Supported Android 7.0 only supported Android OS OS X 10.9, 10.10, 10.11; macOS Sierra 10.12, 10.13 now supported TestNav app available in Windows 10 App Store ProctorCache New version of ProctorCache macOS 10.12 now supported OS X versions prior to 10.9 no longer supported Minimum required RAM now 2 GB (4 GB Recommend) TestNav and ProctorCache both have new versions. iOS versions 10.2, 10.2.1, 10.3.1 - 10.3.3, 11.1, 11.2 are supported. Previous versions are not. This means that iPad versions 2 and 3 are no longer supported. ChromeOS support now runs from versions 57 through 63, with earlier versions no longer supported. The current version of Android supported for TestNav is 7.0. macOS 10.9, 10.10, 10.11; macOS Sierra 10.12, 10.13 support has been added for both TestNav and ProctorCache. You may now download TestNav from the Windows 10 App Store. And ProctorCache hardware minimums have been raised to 2 GB RAM with 4 GB recommended. For up-to-date requirements check the TestNav Online Support under Technology Resources on the Indiana ISTEP+ and IREAD-3 Resource Center.

Timeline of Important Events Let’s begin with a look at some important events coming soon.

Timeline of Important Events Dates Pre-Statewide Readiness Test Question and Answer Sessions January 30 – February 1 Statewide Readiness Test (SRT) February 7, with February 15 as a backup, 10:00 a.m. (EST) Pre-Test Administration Q&A Part 1: 2/13/18 – 2/21/18 Part 2: 4/2/18 – 4/11/18 Practice Test Administration Window Part 1: 1/22/18 – 3/9/18 Online Part 2: 3/5/18 – 5/4/18 Paper Part 2: 3/5/18 – 5/2/18 Test Administration Window Part 1: 2/26/18 – 3/9/18 Part 2: 4/16/18 – 5/4/18 The timeline can be found in the Indiana Resource Center and has links to register for upcoming training sessions. Here are some key dates and tasks you should make note of. Pre-Statewide Readiness Test Q and A Sessions are January 30th to February 1st. And Statewide Readiness Test or SRT is February 7 with a backup date scheduled for February 15th

Overview of Technology Resources Next, let’s review some technology resources.

Computer-Based Testing Components PearsonAccessnext Assessment administration Manage student data, test sessions, access reports TestNav 8 Student test delivery engine Early warning system Computer-based assessments are comprised of three main technology components working together to securely deliver test content to students and preserve the security of student responses. Those components are PearsonAccessnext, TestNav 8, and ProctorCache. [CLICK] PearsonAccessnext is a system that administrators use to manage student data, set up and schedule computer-based tests, and manage test sessions. PearsonAccessnext is role-based, and users can be assigned specific roles that control which functions those roles can access, and what people serving in those roles can do in the system. [CLICK] TestNav 8 is the secure testing engine that students will use to interact with test items. Behind the scenes, an inner-component of TestNav called the Early Warning System maintains test security and checks for connectivity or content issues. The Early Warning System also maintains student responses. While a student is testing, the Early Warning System records student responses in a local encrypted saved response file. After a few questions are answered, TestNav bundles the answers into a packet and transmits them to our servers. TestNav then waits for a handshake acknowledgement that verifies we’ve successfully captured the responses on our side. This means that we control and verify the transmission of student responses to our servers. It also gives the added benefit of students being able to resume where they left off in the case of a connectivity or network failure. Another important note is when students submit their final answers, TestNav won’t completely finalize the student’s tests until it has received confirmation that the responses have been captured on our side. We want to be absolutely sure that we have all of the student’s answers before we wrap up the test. [CLICK] ProctorCache is free software that works with TestNav to reduce the overall bandwidth requirement for computer-based testing by pre-downloading the entire test content that your students need and storing it locally in an encrypted format. This feature allows you to serve test content at local speeds rather than Internet download speeds. The requirements are very flexible. This feature doesn’t have to be installed on a server-class operating system. In most cases, a single ProctorCache machine can be used to service many students. ProctorCache Works with TestNav to reduce bandwidth requirements

Overview of Technology Resources Your technical resources can be found on the Pearson Indiana ISTEP+ and IREAD-3 Resource Center. This is a central repository for information. There are links to Technology Resources, Training Resources, and Support. You can also link directly to PearsonAccessnext and other tools through this site. http://indiana.pearsonaccessnext.com

TestNav 8 Let’s continue with an examination of TestNav 8.

TestNav 8 Introduction Secure student testing application Corporation / School Test Coordinators should develop tracking plan TestNav is the secure application that students will use to participate in computer-based testing. Students will receive all of the information they need to access TestNav through a student authorization ticket that is printed from PearsonAccessnext. Corporation and School Test Coordinators (CTCs and STCs) should develop a plan for tracking which computers or devices each student uses to test. It’s best practice to have students resume on the same computer. For tablets and Chromebooks, students must resume testing on the same device. In an instance where a saved response file needs to be recovered for a student, the original device must be located.

TestNav 8 Support http://indiana.pearsonaccessnext.com Support can be found in a couple of places. Again, you can visit the Resource Center at the URL on the screen. As mentioned earlier, you will see a Technology Resources section, a Training Resources section, and a Support section on the home page. We recommend that you visit here first for Indiana-specific resources. You can also navigate to the Pearson support site directly for general product support information. http://indiana.pearsonaccessnext.com

TestNav 8 – Getting Started and Demonstration Training resources are available on the Indiana Resource Center. We recommend that you review this section for steps to help you get started. You can also access ProctorCache, which we’ll discuss later. [CLICK] Notice the green box for downloading the various TestNav 8 applications.

Secure Tests We have two types of tests that are used: secure tests and Experience Items. Secure tests require Kiosk Mode, which prevents students from accessing any other web pages or applications during testing. Secure tests include all operational tests and training center tests. The details of where to get the relevant version of TestNav are shown. We’ll cover these requirements and those from the next slide again shortly. I want to emphasize that you should not update your OS without verifying it is supported.

No Kiosk Mode Required Non-Kiosk Mode tests are used only for Experience Items. Experience Items will help parents and students familiarize themselves with content and format of online tests. They are not operational tests. The requirements are listed here for the different browsers.

TestNav App Installers The TestNav 8 app is accessible at download.testnav.com. Based on the platform that you will be using – Desktop or laptop, iPad, or Chromebook - download the app or apps that you’ll need for testing. We’ll talk more about iPads and Chromebooks shortly. If you’re installing TestNav for Desktop, there are options for Mac, Windows, and Linux. There are two options for Microsoft Windows: .msi and .exe. The .msi file is optimized for network installation as a group and pushing out to multiple computers. The .exe file is for downloading onto individual computers. For Windows 10, TestNav is also available on the Windows Store. There is a .dmg file for installing on Macs. In general, the Desktop installation takes only a few minutes on an individual computer. Network installations will vary depending on your environment. [CLICK] Please note the link on this page to TestNav System Requirements. The information on the next several slides will come from that location. http://download.testnav.com

Updating the TestNav App The new version of TestNav is required iOS has a new version that became available on August 8, 2017 Users will see an error message if a testing device does not have the updated version installed TestNav has been updated since the Spring and Summer 2017 ISTEP+ and IREAD-3 test administrations and will need to be reinstalled. You will need to install the new version of TestNav even if you’re using the same computers as last year. As a special note regarding iOS: Pearson updated its TestNav apps to align with the TestNav 8.9 release in July. Additional testing of the upcoming iOS release prompted Pearson to further update the iOS TestNav app. Schools and districts must take this update from the App Store, available after August 8, 2017.

Network Configuration Firewalls, content filters, spam filters and any other routing or blocking systems should be set to allow access to the following: *.testnav.com: 80 *.testnav.com: 443 *.pearsontestcontent.com *.thawte.com *.usertrust.com *.comodoca.com google-analytics.com (Optional) https://support.assessment.pearson.com/display/TN/Accessibilit y+Tools+and+PNP+Profile#AccessibilityToolsandPNPProfile- TestNavWhitelist Before you begin, firewalls and other filtering systems will need to be set to allow a small number of sites. A full list can be reached by clicking “TestNav System Requirements” from download.testnav.com. Please refer to the support site for TestNav System requirements.

Windows, OS X and Linux System Requirements OS X: 10.9, 10.10, 10.11; macOS Sierra 10.12, 10.13 Linux Fedora 24 (64-bit), Ubuntu 16.04 (64-bit) The installable TestNav app has a few minimum technology requirements. We’ll cover Windows, Mac OS X, and Linux now, and then discuss Chromebooks, iPads, and Android devices separately. Supported Mac OS versions are OS X 10.9, 10.10, 10.11; macOS Sierra 10.12, 10.13. Supported Windows version are Windows 7 to Windows 10. Linux is supported on Fedora 24 and Ubuntu 16.04.

Chromebook System Requirements Hardware and software requirements Memory requirements Operating system No Java or browser dependencies Chromebooks and ProctorCache Students testing on Chromebooks can gather cached content Chromebooks cannot be used as ProctorCache machines For Chromebooks, it’s important to note some highlights: Minimum and recommended memory requirements are listed here And TestNav requires Chrome OS 57 through 63 There are no Java or browser requirements for Chromebooks, as students will use the TestNav 8 app to access their test content. And while a Chromebook can take advantage of a ProctorCache setup, a Chromebook cannot be used as a ProctorCache machine.

Chromebooks – Setup Overview Two Setup Methods Managed Chromebooks Unmanaged Chromebooks Can be performed simultaneously on all Chromebooks in your domain Two main steps to complete Install TestNav 8 App and set it to run as a Kiosk App Preserve local data on Chromebook to retain SRF and log files on the device Steps have to be performed on each Chromebook Requires access to the administrator / owner account for each device Device will be backed up to cloud storage and wiped if you do not have access to the administrator account for the device Now let’s move into the setup details. Chromebooks can either be managed or unmanaged, which presents us with two different setup methods. For managed devices, all of the setup steps will be performed through the central administration, so all Chromebooks in a domain can be configured at once. When using managed devices, there are two main steps you’ll need to complete – install the TestNav 8 App and set it to run as a Kiosk App, and preserve the local data on the Chromebook to retain Saved Response Files (SRF) and log files on the device. For unmanaged devices, the setup steps will have to be performed on each device individually. This requires access to the administrator account for the device. If you don’t have access to the administrator account, the Chromebook will need to be backed up to cloud storage and wiped clean before you can continue. After testing, it can be restored from the cloud. Note: All devices used for testing need to have a secondary save location configured. All devices used for testing need to have a secondary save location configured.

Chromebook Tips Before Testing: Set up a secondary save location in PearsonAccessnext Check your managed Chromebook settings Make sure your wireless access points can support the number of Chromebooks used Please see the following sites for setup instructions and system requirements: https://support.assessment.pearson.com/display/TN/Set+Up+TestNav+on+Chrome+OS https://support.assessment.pearson.com/display/TN/TestNav+System+Requirements During Testing: Create a tracking log for testing devices Properly exit the test after completing sections Before wiping devices clean, ensure all tests are in completed status Here are some tips for Chromebooks. Creating a secondary save location is required. For Chromebooks this location will need to be an SFTP service. If the Response File Backup Location is not utilized, the student can continue testing, but if a failure occurs in hardware and the SRF is lost, no backup file will be available.  The student may receive an undetermined response. Prior to testing, check your managed Chromebook settings to ensure that everything is set for your environment and all student Chromebooks that will be used for testing are properly enrolled and managed. Be certain to ensure that your Chromebooks are not set to erase data when rebooted, as this could cause issues during testing, including erasing an SRF. If you’re noticing a large amount of connections being dropped or network connection errors, check to make sure that your Wireless Access Point can support the number of Chromebooks that are connecting to it at one time. Create a tracking log for testing devices, so you can always find the device each tester used. Whenever students will be away from their Chromebook after completing a section, be certain they properly exit the test by clicking on the account icon in the top right of the screen and choosing Sign Out. Before wiping devices clean at end of testing, ensure all tests are in completed status.

iPad System Requirements Hardware and software requirements Memory requirements Operating system External Keyboards are NOT required, but are recommended No Java or browser dependencies iPads and ProctorCache iPads cannot be used as ProctorCache machines iOS 10.2, 10.2.1, 10.3.1 - 10.3.3, 11.1, 11.2 supported The TestNav Desktop App must be updated from the App Store due to upcoming iOS releases. This became available on August 8, 2017 Let’s have a look at the system requirements for iPads. It’s important to note some highlights for the iPad: Minimum and recommended memory requirements are listed. External keyboards are recommended And your iPad requires 10.2, 10.2.1, 10.3.1 - 10.3.3, 11.1, 11.2 As mentioned earlier, you must update your TestNav app with the release available on August 8th. And while an iPad can take advantage of a ProctorCache setup, an iPad cannot be used as a ProctorCache machine. NOTE: All devices used for testing need to have a secondary save location configured. All devices used for testing need to have a secondary save location configured.

Set Up TestNav on iPad Install TestNav Select Indiana Allow Mic Access Run App Check Confirm App Self Lock Sign In to TestNav Now let’s move into the setup details. Download TestNav for iPads from the AppStore. [click] Select Indiana [click] Allow Microphone Access [click] Tap the user drop-down menu, and select App Check [click] Confirm App Self-lock [click] Complete App Check [click] Then, Students will then be able to use the device for online testing NOTE: Students that click or tap No cannot continue testing in the secure test.

Single App Mode Automatic Assessment Configuration (AAC) AAC ensures that the student cannot access other apps, pages, or features after Single App Mode starts Locked out features: Auto-correction Definitions Keyboard shortcuts Predictive keyboard Spell check Single App Mode is Automatic Assessment Configuration (AAC). It locks testers into TestNav, blocking several features they shouldn’t access during the testing process.

Android Device System Requirements Hardware and software requirements Memory requirements Operating system No Java or browser dependencies Android devices and ProctorCache Students testing on Android devices can gather cached content Android devices cannot be used as ProctorCache machines Let’s have a look at the system requirements for Android. It’s important to note some highlights, such as minimum and recommended memory requirements. TestNav requires Android 7.0. External keyboards are required for Android devices. There are no Java or browser requirements for Android devices, as students will use the TestNav 8 App to access their test content. And while an Android device can take advantage of a ProctorCache setup, allowing TestNav to gather cached content, an Android device cannot be used as the actual ProctorCache machine. All devices used for testing need to have a secondary save location configured.

Android Devices – Setup Overview Two Setup Methods Google Play for Education Mobile Device Manager (MDM) Install app using your Google Play for Education account Add names or email addresses of the users who will need to access TestNav; can also use Google Group or contact group Google tips: https://support.google.com/edu/pla y/?hl=en#topic=6068591 TestNav App can be installed using an MDM that supports Device Owner Unmanaged Devices Install using Google Play Store app Enter TestNav in the search field Select TestNav, then select Install When launching TestNav, it will display the Screen Pin dialog. Tap Yes. Tap Start Test Now. Now let’s move into the setup details. Android devices can be installed with a Google Play for Education account with a school license required, or by using a mobile device manager that supports Device Owner. To install on Android devices, you can use your Google Play for Education account to download the app. You’ll need to add the names or email addresses of those you want to access the TestNav app. Alternatively, you can use Google Group addresses or a contact group. You can find tips for sending content to students on the Google support site. You also have the ability to install the TestNav app using a mobile device management (MDM) system that supports Device Owner. You can install TestNav on unmanaged Android devices by following the link on download.testnav.com

Saved Response File (SRF) on Tablets and Chromebooks Primary saved response file location is managed by the TestNav 8 App A secondary save location needs to be configured to ensure all devices have a backup save location Pearson support site provides steps and instructions to find SRF and log files on the TestNav System Requirements page With TestNav Desktop and browser-based TestNav, the primary save location for Saved Response Files (SRF) and TestNav log files is managed by your TestNav Configuration in PearsonAccessnext, which we’ll examine in a few minutes. With tablets and Chromebooks, the primary location is hardware storage space that is reserved and managed by the TestNav 8 app. Creating a secondary save location is a critical step in preparing for a successful online testing experience. CTCs must confirm with local IT staff that a secondary save location has been configured prior to the test administration to ensure successful capture of student responses. The Pearson Support site provides steps and instructions to assist you, should you need to locate the SRF and log files on any student testing computer. This can be found from the TestNav System Requirements page.

Early Warning System Before we move on, let’s pause for questions. Remember to type your questions into the chat window and direct the questions to Host, Presenter and All Panelists. Next we’ll discuss the Early Warning System, the integrated functionality of TestNav that monitors network connection and student response data submission.

Early Warning System (EWS) The Early Warning System (EWS) is integrated functionality in TestNav that provides additional fail-safes in the event of unexpected network disruptions during computer-based testing The Early Warning System (EWS) is integrated functionality in TestNav that runs silently in the background. EWS alerts you to any issues that arise during the test administration, such as an interruption in network connectivity or other applications attempting to take control of the desktop. Early Warning System notifications often involve IT staff, so it’s important for technical staff, as well as administrators and test proctors, to have an idea of how it works and what will trigger an on-screen message.

Saved Response File (SRF) The EWS writes continuously in the background to the saved response file (SRF). A combination of the student authorization letter and the test session is used to uniquely identify an SRF. The SRF has a response data threshold that, once reached, triggers TestNav to send response data to Pearson servers. Uploading of response data is continuous. If an upload to the Pearson servers fails, student responses continue to be saved locally while TestNav cycles and attempts another upload. If the response data upload is successful, TestNav creates a new empty SRF and begins the process again. TestNav deletes an SRF only after it is successfully uploaded to the Pearson servers. TestNav can identify the correct SRF if a test is successfully resumed. Only the SRF from the student’s last test attempt can be used when the student resumes a test. The Early Warning System writes continuously in the background to the saved response file (or SRF). Some corporations may be concerned about students overwriting each other’s files, but TestNav ensures this will not happen by using a unique file name for each student’s test attempt. A combination of the student's unique login information and the test session is used to uniquely identify an SRF. The SRF has a response data threshold that, once reached, triggers TestNav to send response data to Pearson servers. This means that TestNav doesn’t upload each individual response immediately, but writes responses to the SRF until it has a batch of responses to upload. The uploading of response data is continuous. If an upload to the Pearson servers fails, student responses will continue to be saved locally. TestNav will continue to cycle and attempt another upload. If the data upload is successful, TestNav will create a new empty SRF and begin the process again. TestNav will delete an SRF only after it has been successfully uploaded to the Pearson servers. TestNav uses the student's unique login information to identify the correct SRF if a test is successfully resumed. TestNav will use only the SRF from the student’s last test attempt when a student resumes a test. If you find any SRFs are remaining on servers or devices, leave them until all testing is complete for this testing window. Response files can be left over in situations where students exit TestNav by clicking the X or shutting off their computers, and when they are resumed, the option to 'skip upload' is selected. Skipping upload often happens since either the student sees the prompt and just presses skip, or the proctor skips the upload to get the student into the test faster. If the upload is skipped, this would start the student off on the last question that we have on our side (usually within one or two questions, if not on the same question they were on when they were logged off). TestNav would create a new SRF file, but not delete the old one since it was not consumed. This is intended because the old SRF file likely contains outdated test data (if any). 

Early Warning System – Triggers The following will result in a “Test Proctor – Click Here” notification: Problems writing to save location: EWS will trigger if… The student does not have read / write access to the save location TestNav cannot locate the save location NEW! The student does not have read / write access to the secondary response file location Problems downloading test content: TestNav cannot connect to a ProctorCache workstation to retrieve test content The student workstation is no longer connected to the Internet Problems with saved response files (SRF): The SRF file is moved while the student is testing and TestNav cannot locate the active file An aggressive content filter corrupts the SRF file A technology coordinator attempts to load an incorrect SRF file for the student Now let’s review the specific events that trigger the Early Warning System. We’ll touch on each of the triggers briefly. First TestNav determines that the Saved Response File location is not viable when: Students do not have the proper read/write access to either of the designated save locations. TestNav cannot locate the save location. If the save location is on a network drive and the student is not connected to the network, TestNav cannot launch the test. And When a student logs in to a test if the Secondary Response File Location is not writable the system will provide a 1002 error indicating the teacher or test proctor needs to be notified. The proctor will have the choice of continuing or exiting the test. If the proctor continues with the test, the selection to continue will appear in the log files.  If the Response File Backup Location is not utilized, the student can continue testing, but if a failure occurs in hardware and the SRF is lost, no backup file will be available.  The student may receive an undetermined response. Second TestNav may be unable to download portions of the test if: TestNav cannot connect to a ProctorCache workstation to retrieve test content. A student workstation is no longer connected to the Internet while the student is testing and has reached the last item previously downloaded when the student was connected to the Internet. And finally TestNav is unable to upload student responses to Pearson if: The SRF file is moved while the student is testing and TestNav can no longer locate the active SRF file. If an aggressive content filter corrupts the SRF file. Some content filters are very aggressive in filtering data. To avoid this error message, you need to include the static IP address of your ProctorCache workstation in your content filter’s exception list to allow full pass-through without data corruption. If you have any questions about this process, please contact the support desk. Contact information for Indiana Customer Service will be provided at the end of today’s presentation. TestNav might also be unable to upload a student response if a technology coordinator attempts to load an incorrect SRF file for the student. TestNav keeps track of the student’s current SRF file so you cannot load a previously stored SRF for the student or any other student’s SRF using the current login credentials.

ProctorCache Let’s move on to ProctorCache.

ProctorCache Overview ProctorCache is Pearson-supplied software that: Allows you to pre-cache test content to your local network before a test Reduces the burden on your Internet Service Provider (ISP) by eliminating redundancy in requests for test content Stores an encrypted local copy of all pre-cached tests ProctorCache is required because of its benefits. ProctorCache is Pearson-supplied software that’s used in conjunction with TestNav to reduce bandwidth requirements and accelerate the delivery of test content. You pre-cache content before the test to your local network. You reduce or eliminate redundant downloads of test content, which will reduce the burden on your Internet Service Provider (ISP). And you can store an encrypted local copy of all precached tests and serve them at LAN speeds to students. ProctorCache is required by the IDOE because of the many benefits it provides.

ProctorCache System Requirements Runs on Windows and Mac OS X Utilizes TCP Ports 80, 443, 4480 and 4481 Requires a fixed internal IP address ProctorCache setup instructions can be found on the Indiana Resource Center site under Technology Resources: http://indiana.pearsonaccessnext.com/technology-resources/ The ProctorCache software must be installed, and it has a set of minimum requirements. The requirements are not robust, which gives corporations flexibility on what machines they use for ProctorCache. It doesn’t require an underlying server-based operating system, and it can run on desktop class hardware and operating systems. We recommend 4 GB RAM; however, it could potentially run on as little of 2 GB RAM. ProctorCache can run on both Windows and Mac OS X operating systems which include: Macintosh OS X 10.9, 10.10, 10.11 and macOS 10.12 and Windows 7, Windows 8, Windows 10, Windows Server 2008, or Windows Server 2012. ProctorCache uses TCP Ports 80 and 443 for communication between the ProctorCache machine and the Pearson servers, and ports 4480 and 4481 for communication between testing workstations and the ProctorCache machine. This means TCP ports 80, 443, 4480, and 4481 must be opened. 80 and 443 are also listed in the URL and ports configuration. You don’t have to perform this step twice. It’s possible to set custom ports for ProctorCache. In this case, those specific ports should be opened and not 4480 and 4481. Because testing workstations must know a predictable network location for the ProctorCache machine, ProctorCache requires a fixed internal IP address. Those corporations which require Internet traffic to pass through an upstream proxy server will have to configure ProctorCache to point to their proxy server. For details on setting up an upstream proxy, refer to the “Upstream Proxy Configuration” section in the ProctorCache setup instructions.

ProctorCache Diagram This diagram illustrates two network scenarios. The scenario on the left illustrates a network setup that doesn’t use ProctorCache. Each student is downloading a unique copy of the test content directly from the Pearson servers. The diagram shows that redundant test copies are being downloaded simultaneously over the corporation’s ISP connection, while students are waiting to test. This heavy use of bandwidth not only affects how quickly the test loads for students, but also the available bandwidth for all other Internet-related activities. The right side of the diagram shows the network traffic for a test environment successfully using ProctorCache. The test content is precached once in an encrypted format to a local workstation designated in the TestNav configuration setup as the ProctorCache computer. Students that are assigned to the ProctorCache computer will locally access the test content without utilizing your Internet bandwidth, thus decreasing overall network traffic for your corporation. The closer the configured computers are to the ProctorCache workstation, the faster the delivery of content. Corporations have the flexibility to decide where to implement ProctorCache in the network environment. Based on local network considerations, corporations can implement ProctorCache machines at the corporation level or at the school level. If implementing at a corporation level, we recommend considering the added complexity of the connection between the school and the central location. If ProctorCache computers are housed at the school where students are testing, then you don’t have to worry about an outside connection. Without ProctorCache, each testing computer must individually connect across the Internet to download test content. With ProctorCache, test content is mirrored on a local computer from which the testing computers download test content.

ProctorCache Setup Download installer Run installer and start service NEW! Updated versions of ProctorCache installers http://download.testnav.com Run installer and start service Service is normally started by default Shortcuts exist to start or stop the service, if necessary Verify service is running; purge old cached content Installing and verifying the ProctorCache service is very simple and only takes a few minutes. First, technology coordinators will download the ProctorCache installer for their system. These are NEW versions since last year, so if you have previously installed ProctorCache, you should purge your old content, uninstall your previous version, and then reinstall the updated software. The previous version of ProctorCache will function correctly, but it is recommended that the newest version is used. Run the installer; the InstallAnywhere wizard will prompt you through the installation process. After the installation is complete, start the service. This is normally started by default, but shortcuts are available to start or stop the service, if needed. Next, verify that the service is running by visiting the ProctorCache Diagnostics page; we’ll cover the Diagnostics page in more detail shortly. If you used ProctorCache for a previous test, please ensure that you have purged your previously cached test content. Instructions for purging cached content can be found in the Indiana Online Testing guide, which can be found on the Indiana Resource Center. The links for the downloads can also be found in the ProctorCache setup instructions and on download.testnav.com. The ProctorCache software is installed on only the designated ProctorCache machine and not on each of the student workstations. Also, the content only needs to be precached once during the test window. You can purge the content after the test window has ended. Once installed, your ProctorCache computers can be managed from PearsonAccessnext. Open ProctorCache Diagnostics screen Select old content and then Purge; password required to complete

TestNav Configurations Using TestNav Configurations, you can manage ProctorCache computer configurations and response file save locations To access administration of ProctorCache on PearsonAccessnext, log onto the site and select Setup, then TestNav Configurations. NOTE: TestNav configurations must be installed on both the Training Site and the Live Site of PearsonAccessnext.

TestNav Configurations Select Create / Edit TestNav Configurations from the start drop-down.

TestNav Configurations If creating a new configuration, click Select Tasks, Create / Edit TestNav Configurations. Then click Start. You can have only one configuration assigned to each organization. If you want multiple ProctorCache computers per organization, other computers may be added to an existing configuration. If you are creating a new configuration, create a recognizable name for it. Select Precaching Computer Override, if you want to utilize this fail over feature. This setting allows a computer that has already started testing to bypass a ProctorCache computer which suddenly becomes unavailable and to resume the test using test content downloaded directly from Pearson servers. Select the organization. Type in the computer name, IP Address, and port. The default ports are 4480 and 4481. Creating secondary save locations is a required step in preparing for a successful online testing experience. CTCs must confirm with local IT staff that secondary save locations have been configured prior to the test administration to ensure successful capture of student responses. For Windows, Mac, and Linux testing machines, you may use a network share or an server as your secondary response file location. For Android, iOS, or ChromeOS you must utilize an SFTP server for a SRF file location. If the Response File Backup Location is not utilized, the student can continue testing, but if a failure occurs in hardware and the SRF is lost, no backup file will be available.  The student may receive an undetermined response. NOTE: If you do not enter the Primary Location, Windows, Mac, and Linux will default to the user directory of the logged on user. If you want to verify locations, you can take a sample testing device, launch a practice test and answer a few questions. From another device, monitor the secondary save location. Verify that a file is created that contains as part of its name the student’s test login.

Configuration Details Selecting a configuration name allows review of the details and the addition of more precaching machines. Also note the Configuration Identifier. This unique ID can be entered when running App Check from a testing computer to verify connectivity to this specific ProctorCache computer.

Configuration Details With multiple pre-caching computers, note that you can delete the added ProctorCache configurations.

Import / Export TestNav Configurations defined in the Training Site also need to be manually added to the Operational Site or vice versa, which can be managed through Import / Export functionality. Under TestNav Configurations, you would simply choose to Export the configuration from where it was first created. Then, on the other site, you would import the file created.

ProctorCache Diagnostics Screen http://<Static IP Address>:4480 Or http://localhost:4480 http://127.0.0.1:4480 Tests: Provides information about test content and caching status Test Details displays status of individual test items Clients: Displays clients that have connected to TestNav by IP address Client Details displays details by computer Settings: Change password screen Buttons: Allows you to refresh or purge cached content On the ProctorCache computer, you can verify the status of the cached content by using the ProctorCache Diagnostics page. Depending on your installation preferences, you can access the Diagnostics screen from your Start menu on Windows machines, Finder on a Mac, or through desktop shortcuts. You will only see the Settings button if you access the diagnostics page using local host or the loopback address. You also can directly navigate to the ProctorCache Diagnostics page by typing in your browser the URL displayed on the screen, and hit Enter to view the ProctorCache interface. You will see three tabs: Select the Tests tab for information about Test Content and Caching Status. Selecting the Clients tab will allow you to monitor client Connectivity. Select the Settings tab to change your password The next row contains buttons to Refresh a test if a newer version is available. You can also conduct searches for specific tests, forms, statuses, entries, and cache dates.

Diagnostics Screen – Tests Tab Content displayed at test and form levels Functionality to refresh or purge selected content Clicking on a test name displays the Test Details screen, which shows cached content by item The default password is t35t1n6 On the Tests tab, you’ll see content displayed at the Test and Form levels. Functionality is available to Refresh or Purge selected test content if necessary, and it requires a password. The password is t35t1n6 The initial password is available in the ProctorCache setup instructions to protect against unauthorized deletion of cached content. You’ll also see status indicators for each row of cached test content. Clicking on a test name will display the Test Details screen, which displays individual items cached for the test. There, status indicators will appear next to each item.

Diagnostics Screen – Settings Tab Allows user to set a custom ProctorCache password Can only be accessed when visiting the Diagnostics screen from the ProctorCache machine The default password is t35t1n6 The Settings tab allows technology coordinators to set a custom ProctorCache password to perform the tasks of refreshing or purging cached content. The default password is shown again on this slide; however, Pearson strongly recommends that you create a custom password. You can change the default password at any time, but only from the Diagnostics screen from the ProctorCache machine. [CLICK] Enter the current password and then provide a new password and confirm your entry. Then click Submit to save the password. If you forget your password, the administrator can reset it following the directions in the ProctorCache setup instructions which are located in the Indiana Online Testing guide, which can be found on the Indiana Resource Center.

Tests Tab Status OK – Content is successfully cached Not Loaded – Content is not cached Waiting… – Content is waiting to be loaded Loading… – Content is currently loading Failed to load content – There was a failure to load content MD5 Check Invalid – MD5 comparison could not be completed MD5 Mismatch – MD5 comparison was completed, but files did not match Let’s look at the Test Tab Statuses. An OK status means the content is successfully cached. The yellow status indicators usually appear when the content is in the process of being cached. Red status indicators indicate problems with cached content. ProctorCache also performs an MD5 check once an item has been cached to compare the test content on the Pearson servers with the cached item. The MD5 check should show that the items are identical. In general, any status in red is a critical problem. Any content with a red status should be checked and reloaded. If the problem isn’t resolved, contact Pearson Customer Service for technical assistance. NOTE: In general, any status in Red is a critical problem. Any content with a red status should be checked and reloaded. If the problem is not resolved, contact the Pearson Help Desk.

Diagnostics Screen – Clients Tab The Clients tab provides visibility to the testing workstations that have requested test content from ProctorCache. Each testing workstation on the Clients tab also has a status indicator. Clicking on an IP address or name of a computer will show the details of the computer that connected to the ProctorCache machine to fetch test content. Clients that have connected to TestNav are listed by IP address Selecting a computer name displays a Details screen, which shows information regarding a particular computer

Clients Tab Status OK – Client is active Idle – 5 to 30 minutes since client was active Long Idle – 30 minutes to 12 hours since client was active NOTE: Clients are removed after 12 hours of inactivity. For the client statuses an OK status means the client is currently active. The yellow status indicators appear when the clients have gone idle. Idle means up to 30 minutes, Long Idle means 30 minutes to 12 hours. NOTE: Clients are removed after 12 hours of inactivity but will reappear on the list once they request test content again.

Local Infrastructure Trial Before we move on, let’s pause for questions. Remember to type your questions into the chat window and direct the questions to Host, Presenter and All Panelists. Let’s move on to Local Infrastructure Trials.

Local Infrastructure Trial and Statewide Readiness Test New! For the 2017-2018 school year, capacity for online testing was assessed through the completion of a Local Infrastructure Trial. The Statewide Readiness Test (SRT) is a final check of local technology configurations and devices prior to live testing for schools that are scheduled to test online. The SRT is not a factor in determining Paper-Pencil or online for testing status. All requests to test on paper were made this fall, following completion of a Local Infrastructure Trial. For the 2017-2018 school year, capacity for online testing was assessed through the completion of a Local Infrastructure Trial. In previous years the Statewide Readiness Test helped to determine online capacity. For the SRT, you should utilize every device that will be used for live testing. For Spring 2018 online testing, the Statewide Readiness Test is a final readiness check for all schools that are scheduled to test online. All devices that are going to be used for live testing should be included in the SRT.

What is a Local Infrastructure Trial? A Local Infrastructure Trial is a dress rehearsal of a computer-based assessment. It does not use real student information. This is a low stakes, dry run for final confirmation that: TestNav is configured correctly Devices can successfully run TestNav Participating staff know what to do for computer-based assessments A Local Infrastructure Trial is a dress rehearsal. The IDOE required participating in a Local Infrastructure Trial to prepare for computer-based testing. For a Local Infrastructure Trial, you should utilize a sample of every type of device used for testing. Unlike a live assessment, you won’t use real student information. Instead “sample” student information is used. This year Pearson will load sample students and generate test sessions for practice tests and the Statewide Readiness Test. All student data will be generic or generated randomly. Remember each school conducted a Local Infrastructure Trial for confirmation that your site has the capacity for online testing, including verification of the following items: • Your school has adequate capacity • TestNav 8 is configured correctly • Devices can successfully run TestNav 8 • And participating staff know what to do for the computer-based assessment

Local Infrastructure Trial A trial is conducted on the Training Site using sample test data, not on the live site. Notice the brown background on this slide, which indicates that we are on the Training Site. Make certain you select Infrastructure Trial as the administration across the top. Then select TestNav configurations under Setup. The same steps for setting up TestNav configurations mentioned previously will need to be done here. A step-by-step guide will be available in the Indiana Online Testing guide, which can be found on the Indiana Resource Center.

Local Infrastructure Trial Corporation Information Technology staff will need to complete some of the steps of a Local Infrastructure Trial before Test Coordinators can complete the remaining ones.

Local Infrastructure Trial This trial mirrors the entire process of testing, both verifying the technological resources and the knowledge of some key staff. Students are placed into sample sessions created for this purpose

Local Infrastructure Trial Tests are pre-cached for the sample sessions, verifying that process as well.

Local Infrastructure Trial Tests are started Practice tests are conducted by students or volunteer participants Tests get marked complete [CLICK] Take note of any technical issues. You can contact Indiana Customer Service with any questions. We’ll be providing that contact information shortly. Again, capacity for online testing was assessed through the completion of a Local Infrastructure Trial, NOT the Statewide Readiness Test as in previous years.

Wireless Local Infrastructure Trial Wireless access points – more are better Limit number of computers per wireless access point Distance – closer is better Limit obstructions Fully charged devices Another step for some environments is wireless testing, if your school uses wireless devices. Schools can test both wired and wireless at the same time. Here are some best practices when testing wirelessly: Ensure sufficient wireless access points and limit the number of computers per wireless access point for better performance. Computers located closer to wireless access points perform better than those that are farther away. Obstructions, such as walls and equipment, between testing workstations and wireless access points can disrupt connection and negatively affect performance. Set up a small number of workstations to measure performance on a wireless network before setting up a large number of workstations. Evaluate performance before scaling

Support Let’s pause one last time for questions. Remember to type your questions into the chat window and direct the questions to Host, Presenter and All Panelists. We will close todays presentation with support contact information.

Indiana Customer Support Indiana ISTEP+ and IREAD-3 Resource Center http://indiana.pearsonaccessnext.com/ Phone: 866-683-6668 Electronic request via the form below: http://indiana.pearsonaccessnext.com/pearsonaccessnext/# Monday – Friday 7:00 a.m. – 7:00 p.m. (EST) Indiana Department of Education Assessment IDOE Assessment Program Specialist (Technology): Jennifer Woo jwoo@doe.in.gov Phone: (317) 232-9050 or Toll-free: (888) 544-7837 INassessments@doe.in.gov This concludes our training. If you have any questions, you can contact Pearson’s Indiana Customer Service at the number on the screen from 7 a.m. to 7 p.m. Monday through Friday Eastern Time. By using the web link on PearsonAccessnext or the Indiana Resource Center. The IDOE Assessment Specialist for Technology is Jennifer Woo and she can be reached at the email address listed on the screen. Thank you for joining us today. [Live: At this time, I would like to give the floor back to ______________ (whomever is representing the IDOE) for some closing remarks.]