Elsevier Secure Browser Faculty Training

What to Expect

Enhanced Security

• Screensharing is not allowed (the screen will show as black) and clipboard use is not allowed (copy/paste).
• Screen recording and screenshots are blocked, in addition to remote testing and proxy testing software.
• Testers cannot navigate away from the exam to interact with other applications or devices until they exit the secure browser.
• If students attempt a prohibited activity (e.g. using a blocked app or keyboard control), they will be alerted and disconnected from the exam.
• Background apps are not allowed and will be hidden or disabled. If the secure browser cannot hide or disable an app, it will send an error message noting the app preventing the launch. That app will need to be manually closed to proceed.
• Additional monitors and devices (including Bluetooth) are blocked. Bluetooth-linked headphones and mice are allowed but must be connected before launching the secure browser. Mice connected via USB are also allowed.

Testing on Lab or Institution-Owned Devices

1. For onsite devices/computer labs, please refer to the HESI System Requirements documents for both Mac and Windows to ensure your devices are compliant.
2. Use THIS LINK to download and test the secure browser on the institution’s devices prior to students testing.
   Note: If you get an error using this link, clear the cache or paste into an incognito browser

If you encounter any technical issues downloading or launching the secure browser, review the troubleshooting steps located in the last section of this page.

Testing on Personal Devices (Mac or Windows)

Before test day, ensure your test-takers review the system requirements, download the compatibility check, and complete the mock exam to ensure their devices can successfully run the secure browser.

1. Have testers download and run the HESI Compatibility Check prior to their exam using this link to complete the initial secure browser download and ensure system compatibility. The link provided in this guide is the verified access point and must be used by testers to successfully run the compatibility check and mock exam in the secure browser.
   Note: If they receive an error using this link, have your testers clear the cache or paste into an incognito browser.
   
2. The first time a tester downloads the secure browser, they will click the link in Step 1 to download the application. It may take up to a minute (dependent on network speed).
   Note: For Mac OS Sonoma users, there is a known bug for the subsequent step (step 3). Once the browser is opened from the desktop, it will immediately close itself. However, once downloaded it will work when launching from the HESI NG site in your Chrome, Edge, or Firefox browser.
3. Once the application has been downloaded to a device, students will return to the instructions page and hit “Begin.” This will open the exam in the secure browser. The secure browser will then close or hide any prohibited applications and lock down the tester’s device.

On test day, ensure testers have all apps not needed for testing closed, and they are not screen sharing or trying to use multiple monitors. As a best practice:

1. Have students restart their computers just before testing in order to start with a “clean” device.
2. Ask students to arrive with their devices fully charged. We highly recommend testers connect to a power source while testing if they have a device with an older battery.

For more details and step-by-step instructions about preparing for student testing with personal devices, click here.

Testing on Chromebooks

To download the Chromebook app, search “Elsevier Secure Browser” in the app store, or go to this link. 

1. To launch the exam, log into HESI NG as usual (via Evolve or LMS).
2. Register for the exam, if not yet completed.
3. Click on the exam link to get to the exam details page and launch the exam.

If the app is already installed on the device, “Open in App” should appear in the browser bar, OR, if “Remember this choice” had been previously selected, it will automatically open the app to the exam waiting room, where the student will input the access code.

If the App is not yet installed on the device, click the link to the Google Play Store listed in the instructions, click install, and follow the installation instructions.
Note: This may take a few minutes depending on the device and network strength.

For more details and step-by-step instructions about preparing for student testing with Chromebooks, click here.

Testing on iPads

Let us know if you will be testing on the new Elsevier Secure Browser iPad app so that we may enable a feature flag on the backend.

1. Use SAFARI to access HESI NG. You can log in using any faculty account.
2. Complete the Compatibility Check and it will prompt the user to download the Elsevier Secure Browser app from the App Store.
3. Once the app is downloaded, the landing page can be closed in order to re-access HESI NG and start an exam.

Testing with Virtual Machines

If your students will be testing with a computer lab that is managed through the use of virtual machines, your setup will need to be reconfigured. You will need to inform your Elsevier Customer Success Manager as soon as possible so we can change your organization’s configuration to allow virtual machines.

• If your school is proctoring fully onsite in computer labs, the configuration to allow virtual machines should only introduce a small amount of risk.
• If your school is proctoring with a mixture of computer lab devices, student-owned devices, and/or remote proctoring, it is highly recommended to not allow virtual machines, as it would introduce significant risk to the test security of their testing environment. This will mean that students are not able to test on the computer lab devices, but it will significantly reduce the risk of proxy testing.
  Note: Bad actors who are paid to take tests for students often do so via remote desktop software or virtual machines, which are blocked with the new secure browser.

Remote Desktop Software

Remote desktop software is not permitted and will automatically be blocked by the Elsevier Secure Browser. It is important to note:

• It cannot be used to enter access codes for students or monitor exams during testing.
• If you need access to remote desktop software to assist your students, an update to your proctoring and exam administration practices is required. Please contact your Elsevier Customer Success Manager if you would like advice or consultation on proctoring best practices.

Remote Proctoring

We have special configuration settings to allow testing via a remote proctor vendor to work with our new Elsevier Secure Browser. If your school is enabled for remote proctoring, this configuration will be automatically applied to those exams.

The preparation will be the same as onsite exams: download the Elsevier Secure Browser application to the student device and ensure it is working before taking an exam. Otherwise, the student will follow the same remote proctoring processes and flows as before. 

Troubleshooting Student Issues

If a student cannot open the secure browser or if it is taking longer than 2 minutes to load try the following steps:

1. Ensure the background apps are closed.
2. Have the student restart their device and try again.
   Note: If restarting on Mac, deselect the option to reopen windows and applications upon restart – https://support.apple.com/en-us/HT204005

If a student needs to exit the secure browser and there is no exit button (for example: on the loading screen), they can use keyboard control CTRL SHIFT Q.

Computer Lab FAQs

Q: Can the browser be installed for multiple users or user profiles at once?
A: The Elsevier Secure Browser application uses a ClickOnce installer, which is designed to install for one user at a time. ClickOnce installs applications in the user’s profile directory, not in a common location that can be shared across users on the same machine.

Q: Can the browser be installed as an administrator?
A: The browser can be installed with administrator rights, however, the ClickOnce installer requires the user’s profile to be the one used at the time of the install.

Q: Can the secure browser be installed on multiple devices at once via an MSI installer?
A: At present, we do not support this kind of installation. However, we are currently exploring this option.

Q: Does anything else need to be installed or allowed on the device for the secure browser to run?
A:  You must have Microsoft Edge Chromium or the WebView2 runtime installed on Windows devices.

Q: The system requirements indicate the latest version (-1) of JAWS is required. Do I need to install JAWS on the devices for the secure browser to work?
A: Older versions of JAWS may have issues with the new browser. It is not a requirement to have JAWS installed on the device to use the secure browser, however, we acknowledge that many users prefer JAWS, or that schools may have institutional contracts. Note that we do have a built-in text-to-speech tool within the secure browser to accommodate accessibility needs.

Testing FAQs and Support Information