Lab and Institution Devices2026-06-06T22:51:55+00:00

Elsevier Secure Browser Faculty Guide: Student Testing on Lab or Institution-Owned Devices

This faculty readiness guide outlines the key steps and information faculty need to know about their test-takers accessing the Elsevier Secure Browser with lab or institution-owned devices. Review the instructions below for details about installing the secure browser and completing the compatibility check on lab or institution-owned devices.

Secure Browser Installation

Faculty proctoring their students’ HESI exams will not need to download the secure browser on the devices they will be using to proctor exams. The secure browser only needs to be installed on the devices used for test-taking. Included below are the key steps for installation that need to be completed for testing devices that are lab or institution-owned.

1. 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 student testing.
Note: If you get an error using this link, clear the cache or paste into an incognito browser.
3. After clicking the above link, you will be redirected to the corresponding download page for your appropriate operating system. Follow the instructions provided for your device. You can also click the links below to review more detailed instructions for each device type.

If you encounter any technical issues downloading or launching the secure browser, review the troubleshooting steps located in the last section of the Elsevier Secure Browser Faculty Training page.

Testing with Virtual Machines

Testing on virtual machines requires special configuration. Notify your Elsevier Customer Success Manager promptly to enable this for your organization. Please note the following information about testing with virtual machines.

  • Blocking virtual machines helps prevent proxy testing, which is common with remote desktop software.
  • Allowing virtual machines increases the risk of proxy testing. For fully onsite labs with trained proctors, there is less risk.
  • If using a mix of lab, student-owned, or remote proctoring devices, we highly discourage the use of virtual machines, as it poses significant security risks.

FAQs and Troubleshooting

For common FAQs and troubleshooting steps, review the Common Troubleshooting Scenarios and FAQs section on the Elsevier Secure Browser Faculty Training page.

Computer Lab FAQs

Review the frequently asked questions below for information regarding common questions about preparing and using computer lab or institution-owned devices. If you have questions about installing or running the secure browser on these devices, please review this information prior to contacting Support or your Customer Success Manager.

Computer Lab2026-03-17T16:50:17+00:00

Any faculty or exam administrators who are proctoring the exams do not need to install the secure browser onto the device(s) they will be using to administer the exams. The secure browser only needs to be installed on testing devices.

Windows: At this time, the ClickOnce installer is only designed to install for one user at a time (the user doing the install). However, we do have an MSI file available for mass installs. Please see the question in the FAQ, “Can the secure browser be installed via an MSI installer?” 

Mac: The Mac ap

Windows: The browser can be installed with admin rights, but it is not required. However, ClickOnce requires the user’s profile to be the one used at the time of the install.

Mac: Yes.

Windows: Yes, we have an MSI install option available. Follow the instructions below to complete the install. 

  1. Navigate to the direct link. Open your web browser and navigate to:  https://hesicdn-public.hesiinet.com/customer_notification/resources/ElsevierSecureBrowser.msi
  2. Download and launch the MSI file. Download the MSI file from the link. Once the download is complete, locate the file in your downloads. folder and double-click to launch it.
    Note: Although the file is signed, the browser may indicate that it is suspicious. This is because the file needs to go through a trial period with Microsoft before it is accepted. We assure you that the file is safe.
  3. Continue through the setup wizard. Follow the prompts in the setup wizard to proceed with the installation.
  4. Choose a target folder. When prompted to choose a target folder, select a location where the user has execute, read, and write permissions such as `C:/Users//Elsevier Secure Browser`
  5. Continue through the setup wizard. Continue following the prompts in the setup wizard and confirm the installation. 
  6. Close the setup wizard. Once the installation is complete, close the setup wizard. 

Important Notes
 •  Update Rights: Ensure that the installation allows update rights otherwise you are taking on a liability. The sites must not block the executable or any other components required for updates. If you do not allow update rights, an error message will be shown stating the secure browser doesn’t have rights to update itself.
•  Do not move the secure browser from the installed directory or it will not launch.  

Mac: Not applicable.

Virtual machines need to be enabled for you in advance. Please note, we can only enable your institution for virtual machines if:
1. All testing is done on-site on the institution-owned devices (i.e. there is no testing on student personal devices, nor remotely).
2. There are no other options (e.g. labs with physical machines).

If you meet this criteria, let us know and we can check to make sure you are enabled if you are not already.

Note: Virtual machines are enabled at the institution level, which opens up the possibility for proxy testing. We trust your computer labs are secure and that you adhere to our secure testing policies.

No, all remote desktop applications are blocked by the Elsevier Secure Browser. The secure browser blocks remoting technology and does not distinguish between “good” and “bad” use cases. Please reach out to your Customer Success Manager if you have further questions or concerns.

Windows: You must have Microsoft Edge Chromium or the WebView2 runtime to be installed on Windows devices.

Mac: No, there are no additional installation requirements.

Ideally, the application is installed as a persistent application and is able to be retained between users. If not, so long as there is not an admin key required to download and run the application, and you have ensured the devices are compatible with the secure browser in advance, there should be no issue with downloading the secure browser each time it is to be used.

Ideally, the application is installed as a persistent application and is able to be retained between users. If not, so long as there is not an admin key required to download and run the application, and you have ensured the devices are compatible with the secure browser in advance, there should be no issue with downloading the secure browser each time it is to be used.

If you can share that key with your users, then the users can download the secure browser themselves each time they test. If this is not possible, you are unable to secure other devices for testing that do not require an admin key, and you are not able to install the application in any way such that it persists across user profiles, please reach out to your Customer Success Manager as soon as possible for further assistance.

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. We do have a built-in text-to-speech tool within the secure browser to accommodate accessibility needs.

Need technical or product support? Visit our Evolve Support Center ↗

Go to Top