Transcript Infrastructure Readiness Training

Infrastructure
Readiness Training
Infrastructure Readiness
Training Agenda

Welcome and Introductions



Overview
Parking Lot
Configuring the Infrastructure Trial Environment

Network and System Configurations







Proctor Caching





Downloading and Installing the Proctor Caching Software for Windows
Downloading and Installing the Proctor Caching Software for Mac
TestNav


System Specifications
Proctor Caching Overview
TestNav Overview
Wireless Best Practices
TestNav Configuration Best Practices
TestNav System Check Tool
Downloading TestNav 6.9
Installing TestNav 6.9
TestNav Early Warning System
Common Errors and Solutions
Infrastructure Readiness
Training Agenda (cont.)

PearsonAccess Training Center



Logging into the PearsonAccess Training Center
Creating Sample Students
Session Management









Creating a Session
Adding Students to a Session
Printing Authorization Tickets
Monitoring Sessions
Caching Test Content Starting a Session
Stopping a Session
Conducting the Infrastructure Trial at a School
Common Administrative Errors and Solutions
Launching TestNav



Logging in to the Infrastructure Trial
Exiting The Infrastructure Trial
Infrastructure Trial Survey
Infrastructure Readiness
Training Agenda (cont.)

Support Information

Where to find Support Resources





TestNav Technology Guidelines
TestNav Early Warning System Reference Manual
Proctor Caching Guide
Infrastructure Readiness Guide
Contacting Pearson Support
System Specifications
Proctor Caching –
Network Diagram
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.
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.
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.
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.
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.
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.
Local Installation vs.
File Share Installation
Pros
Cons
File Share + Single point of installation and - Adds a potential point of failure
configuration changes
+ Easier to implement in a
large-scale testing environment
+ Centralized location for log
files
Local
+ Quicker launch time
+ Limits potential points of
failure
- Increases installation time (Note:
System automation tools, such as
SMS [Windows] and Apple Remote
Desktop [Mac] can make local
installs much easier)
- Requires that configuration
changes be made on each
machine
Wireless Networks
Best Practices

DO use a local installation of TestNav



File Share installations will work fine, but 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.
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
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.
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.
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.
Enable Student Read/Write-Access



Students must have read-access to the TestNav
installation directory.
Students must have read/write access to the
TestNav/Logs and TestNav/Temp directory.
Students must have read/write access to the Student
Response File save locations whether they are located
on the workstation or on a network share.
TestNav Installation
Best Practices (contd.)
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.
Screen resolution



All tests are authored to a screen resolution of 1024 x 768 so
make sure that your testing machines are capable of 1024 x 768
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.
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.
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.
System Check for TestNav
(contd.)


Select the appropriate Test Administration from the
drop-down box.
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.
System Check for TestNav
(contd.)

Click the Testing Volume Calculator tab. This tool will
be used to estimate how many users can be tested
with the bandwidth that is available.
System Check for TestNav



Select the correct test administration
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.
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.
System Check for TestNav


In order for the Infrastructure Trial 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.
Demonstration
Proctor Caching


Downloading Proctor Caching
Installing Proctor Caching



Windows
Mac
Testing if Proctor Caching is running
TestNav


Downloading TestNav
Installing TestNav 6.9
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.

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.


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.
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.
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.
Early Warning – Screenshots
(contd.)
Invalid
Save
Locations
Early Warning – Screenshots
(contd.)
Invalid
Save
Locations
Early Warning – Screenshots
(contd.)
Unable to
download
test content
Early Warning – Screenshots
(contd.)
Unable to
download
test content
Early Warning – Screenshots
(contd.)
Unable to
upload
responses
Early Warning – Screenshots
(contd.)
Unable to
upload
responses
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
Questions?
PearsonAccess Training Center


All administrative actions required for the Infrastructure Trial
will be carried out through the PearsonAccess Training
Center.
A Training Center account can be set up by contacting your
district assessment coordinator.
Logging in to the
Training Center

Logging in for the first time

An email will be sent with your initial login credentials






Click on the link within the email.
Create a password. You will be prompted to enter it twice.
Read and accept the confidentiality agreement.
Upon logging in you will be prompted to select an
administration. Choose “Florida Training Administration.”
Click Logout when finished or just close the browser.
To return to the Training Center, go to
www.pearsonaccess.com/fl and click the Training Center tab
and then “Log into PearsonAccess Training Site.
*You have only five chances to enter your username and password
correctly before your account is locked.
Sample Students

Sample students must be created in order to carry
out the Infrastructure Trial.

To create sample students, go to the home page in
the Training Center and click Create Students.
Sample Students (contd.)

You will be prompted to select your organization.
Select your organization and click Next.

Next, a page will be displayed with fields that must
be populated.
Sample Students (contd.)



Click Create Students and you will be prompted to
confirm you want to create them. Once confirmed,
the sample students will have been created.
Repeat these steps until you have created enough
sample students for the Infrastructure Trial.
Number of sample students to be created is based on
the maximum number of computers that will be used
concurrently during testing, plus approximately 10%
to account for errors or additional tickets.
Creating a Sample Session


A sample test session will need to be created in order to
administer the Infrastructure Trial.
To create a sample session


Go to the Test Management tab in the Training Center and click
Manage Test Sessions.
Click New Session.
Creating a Sample Session
(contd.)

A screen will appear with fields that must be
populated to create the session.

Once the fields are populated, click Save to create
the session.
Adding Students to a Session

Return to Manage Test Sessions and select the session you
just created.

Click Add Students.
Adding Students (contd.)


Students can be added either by class or by individual
student. For the purpose of the trial we’ll add students by
class.
To add students by class, select View By: Classes and check
the box beside the class to be added. Then click Add to
Session.
Authorization Tickets

To print authorization tickets select Authorizations >
Student Authorizations.

Authorization tickets can be printed in three formats: Detail
View, List View, and Grid View.
Monitoring Sessions
Student Status Key
Status
Description
Ready
The student has not logged into the session yet and is ready
to be logged in.
Active
The student is currently in the session.
Exited
The student has exited the session, but has not submitted
their responses yet.
Completed
The student has completed the test and has successfully
submitted their responses.
Marked Complete
The student’s responses have been submitted manually.
Resumed
Resumed-Upload
The student is ready to log back into the session.
The student is ready to log back into the session with saved
responses.
Resuming a Student


If a student needs to be resumed, go to the session
page and check the student(s) to be resumed and
click Resume Test.
A confirmation will be displayed once the student is
resumed.
Caching Test Content


Test content must be cached in order to carry out the
Infrastructure Trial.
To cache test content


Start the Proctor Caching service on the Proctor Caching
computer by going to Start > All Programs > Proctor
Caching > Proctor_Caching.
A window will open with the status of the Proctor Cache and
test content is now ready to be cached.
Caching Test Content (contd.)



When the content is ready to be cached,
use a computer that is not the caching
computer to cache content.
In order to cache content, the proxy
settings within the browser will need to
be changed.
Caching test content using Internet
Explorer (Windows only):




Open Internet Explorer and go to Tools
> Internet Options.
Click on the Connections tab and then
LAN Settings.
Select “Use a proxy server for your LAN”
and enter the IP address of the Proctor
Caching computer and port 4480.
Click OK in both windows and restart the
browser for the new settings to be
applied.
Caching Test Content (contd.)

Caching test content using Mozilla Firefox (Windows and Mac):



Go to Tools > Options > Advanced and click Settings under the
Network tab.
Select Manual Proxy Configuration and enter the IP address of the
Proctor Caching computer in the HTTP Proxy box followed by port 4480.
Once the settings are entered, select OK in both windows and restart the
browser for the settings to be applied.
Caching Test Content (contd.)

Caching test content using Safari (Mac only):




Go to Safari > Preferences > Advanced and click Settings the
Proxies: Change Settings button.
Select the Web Proxy (HTTP) check box, enter the IP address
and port of the Proctor Caching computer in the Web Proxy
Server boxes, and click Apply Now.
Close the System Preferences window and the Safari Preferences
window.
Close all browser windows and restart the browser for the new
changes to take effect.
Caching Test Content
(Windows and Mac)


When test content is ready to be cached, log in to
the Training Center and navigate to Test
Management > Manage Test Sessions.
Select the session to be cached and click Proctor
Caching in the top yellow bar.
Caching Test Content
(Windows and Mac – contd.)



Once Proctor
Caching is selected,
a page will be
displayed with the
contents to be
cached. Click Next.
A page will now be
displayed showing
the progress of the
caching process.
Once the content
has been 100%
cached, the
Infrastructure Trial
can be started.
Starting a Session

Before students can be logged in to the
Infrastructure Trial, the session must be started.

To start a session, click Start in the top left corner of the
session page.

A confirmation page will be displayed.
Stopping a Session

Before a session can be stopped, students must be either
in “Completed” or “Marked Complete” status. To stop the
session, select Stop in the top left corner of the session
page.
Conducting the Infrastructure
Trial at a School


Schools conduct the Trial using the maximum number
of computers that will be tested concurrently during
the spring administration.
Volunteers log in to complete the Trial test.






Students or adult volunteers can be used - not necessary
that computer-based testing students are used.
Trial is not appropriate for student practice.
One volunteer can run multiple computers because
volunteers supply a random answer every 10 seconds.
Volunteers will log issues on Student Authorization Tickets.
Use the script provided in the Infrastructure
Readiness Guide.
Estimated time for Trial is approximately 30 minutes.
Launching TestNav



TestNav is launched by
double-clicking the
TestNav icon on the
desktop.
Enter the URL for the
Infrastructure Trial in the
Address line. This URL can
be found on the student
authorization tickets.
Click Go and TestNav will
present a login page.
Logging in to the
Infrastructure Trial

Enter the Login ID and Test Code and click Login.
Logging in to the
Infrastructure Trial (contd.)


TestNav will load the test items and the welcome
screen will appear.
The process for administering the Infrastructure Trial
can be found within the Infrastructure Readiness
Guide located on PearsonAccess under Support >
Additional Resources.
Exiting the Infrastructure Trial



Once all test items have been viewed and tools have
been tested in the Infrastructure Trial, the test can be
submitted.
Submit the test by clicking Submit on the review
page.
Responses will now be submitted and the student
status will show as “Completed” on the session page.
Infrastructure Trial Survey





Completed once by each school and each district.
Go to http://tinyurl.com/infrastructuretrial (survey
will be live November 24).
Please complete by December 8, 2010.
School representative will review all notes and
Student Authorization Tickets to provide school-level
response.
District representative will review all school-level
surveys and notes and provide district-level response.
Support Information


Support resources for the Infrastructure Trial can be
located on the PearsonAccess Florida page under
Support > Additional Resources.
These resources include downloads for:




Infrastructure Readiness Guide (required)
TestNav Technology Guidelines (optional)
Early Warning System Reference Manual (optional)
Proctor Caching User Guide (optional)
Contacting Pearson Support


If technical assistance is needed at any point during
the Infrastructure Trial, contact Pearson Support at
877-847-3043 or at [email protected].
The following slides provide information that should
be gathered prior to contacting Pearson to help
diagnose technical issues.
Contacting Pearson About
PearsonAccess





Are you using a PC or a Mac?
What is your user role? (District Assessment Coordinator,
District Technology Coordinator, School Assessment
Coordinator, or School Technology Coordinator)
What screen are you on? Provide the path if possible.
What task were you trying to complete when you
encountered an error?
What was the error message? If there wasn’t an error
message, what are you unable to do?
Contacting Pearson About
TestNav







Are you using a PC or a Mac?
What task were you trying to complete in TestNav
when you encountered an error?
What is the session name?
Did an error code or message appear?
Can you provide a log file?
Do you use a proxy server and if so, what is the IP
address?
Have the TestNav URLs been allowed through your
Firewall/Content Filter?
Contacting Pearson About
Proctor Caching





Are you using a PC or a Mac?
Were you setting up Proctor Caching on a
workstation or a server?
Have you installed the Proctor Caching software?
Did you start the Proctor Caching software prior to
attempting to cache test content?
Have the TestNav URLs been allowed through your
Firewall/Content Filter?
Contact

Pearson Computer-Based Testing Team




Kaitlynn Griffith ([email protected])
Aleksandra Edlemon ([email protected])
Brett Miller ([email protected])
FLDOE K-12 Assessment Administration Team







Susie Lee, Director ([email protected])
Daphne Csonka, Supervisor ([email protected])
Tara Gardner (Dedicated to CBT) ([email protected] or
850.245.0742)
Jenny Black (Dedicated to CBT) ([email protected] or
850.245.9470)
Kira Sullivan ([email protected])
Tamika Brinson ([email protected])
Molly Hand ([email protected])
Questions?