infrastructure readiness training. infrastructure readiness training agenda welcome and...
out of 70
Post on 26-Dec-2015
Embed Size (px)
- Slide 1
- Infrastructure Readiness Training
- Slide 2
- Infrastructure Readiness Training Agenda Welcome and Introductions Overview Parking Lot Configuring the Infrastructure Trial Environment Network and System Configurations System Specifications Proctor Caching Overview TestNav Overview Wireless Best Practices TestNav Configuration Best Practices TestNav System Check Tool Proctor Caching Downloading and Installing the Proctor Caching Software for Windows Downloading and Installing the Proctor Caching Software for Mac TestNav Downloading TestNav 6.9 Installing TestNav 6.9 TestNav Early Warning System Common Errors and Solutions
- Slide 3
- 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
- Slide 4
- 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
- Slide 5
- System Specifications
- Slide 6
- Proctor Caching Network Diagram
- Slide 7
- 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.
- Slide 8
- 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.
- Slide 9
- 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.
- Slide 10
- 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.
- Slide 11
- 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.
- Slide 12
- Local Installation vs. File Share Installation ProsCons File Share + Single point of installation and configuration changes + Easier to implement in a large-scale testing environment + Centralized location for log files - Adds a potential point of failure 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
- Slide 13
- 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.
- Slide 14
- 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
- Slide 15
- 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.
- Slide 16
- 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.
- Slide 17
- 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.
- Slide 18
- 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.
- Slide 19
- 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 www.pearsonaccess.com/fl 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.
- Slide 20
- 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.
- Slide 21
- 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.
- Slide 22
- 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.
- Slide 23
- 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.
- Slide 24
- 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 ban
View more >
The Army Physical Readiness Training Program (PRT) Army Physical Readiness Training Program ... Strength Training Circuit ... Army Physical Readiness Training Program Revision Date:
Physician Readiness for Expert Practice (PREP) Training ... ?· Physician Readiness for Expert Practice…
ICS Information Flow for the EPA OSC Readiness Training ... ?· the EPA OSC Readiness Training Program…
Expeditionary Readiness Training (ExpeRT) Course ?· Expeditionary Readiness Training (ExpeRT) Course…
Arkansas ELPA21 Interactive Demo, Training Modules ... ... . ... Training Modules, Administrator Roles Readiness
Training Readiness Checklist - Edesix viewTraining Readiness Checklist Page 1 Training Readiness Checklist Page 3 PRS Title Goes Here Training Readiness Checklist Page 7 +44 131 510 0232 sales@ Reg: SC235672 | VAT: GB 803 9042 51
Unlocking potential through infrastructure readiness Final ... Lack of budget 35% Legacy IT infrastructure