It could be quarantined.

If you have a RAPID virtual machine (VM) that you can’t access, first, login to: https://rtoolkits.web.duke.edu/ and verify that the VM is powered on. Next, be sure to have the University VPN active (unless you’re physically on campus) before attempting to SSH or RDP to the VM. If it is powered on, and you still can’t access it, your virtual machine could be quarantined due to security concerns.


RAPID VM owners are responsible for ensuring their VM is up to date for patching and has a supported Operating System (note: Ubuntu 14.04 and 16.04 are both now end of life). If you have missed the automatic updates or skipped the prompts to upgrade while logging in, your VM could automatically be placed into quarantine through Duke’s end point management processes (see https://sites.duke.edu/endpoints/getstarted/).

If quarantined, you can simply delete your existing vm and create a new one. All new images available for RAPID VMs meet current standards.

If you would like to first retrieve data or configurations from your existing VM, or upgrade it (instead of recreating), you can obtain a temporary “reprieve” from quarantine by emailing security@duke.edu with your request and a brief description of why the “reprieve” is required.

If you decide to upgrade your VM be sure to:

  1. Download and install the Duke University BigFix Agent for Windows or the Planisphere self-reporting tool for Linux.
  2. Download and install the Duke University CrowdStrike Agent for your operating system.

Once you upgrade and install the additional software, your VM will be removed from quarantine automatically.

If you suspect your VM has been quarantined, need assistance with initiating a reprieve, or have questions, please contact rescomputing@duke.edu for assistance.