Faculty looking for the Arch RemoteLab should click here.
Workflow
- Use SU's remote desktop service to remote into a virtual Windows desktop, which has access to the G drive, including any files you may keep on the desktop.
- Use the virtual Windows desktop to further remote into your office computer (called Double Hop).
Reasons why you may want to double hop
- You use special fonts, such as the school's Grotesque and Plantin.
- You use software that is not available on the virtual Windows desktop.
- You need better performance.
- You want to leave files open and programs running to return to later.
Reasons why you may not want to double hop
- You find the virtual Windows desktop is adequate for your work.
- You want to avoid the extra complexity of working two layers deep.
Steps
Step 1: Connect to an SU virtual Windows desktop.
You have two choices for how to connect. Each link will take you to a new page with instructions. After you connect to the virtual Windows desktop, return to this page and complete step 2 .
Which method is best? The web browser is more convenient, but you may notice a slight degradation in graphical fidelity and less options to tweak the connection.
a. Connect through a web browser.
b. Connect using a Remote Desktop App.
Step 2: Connect to the Arch RemoteLab from the virtual Windows desktop (double hop).
RDP Client Method
Troubleshooting - Connection Failure
- "This computer can't connect to the remote computer."
- This error could mean your office computer is off.
- If you get a black screen upon login to your office computer (double hop):
- Type CTRL-ALT-END (Windows) or CONTROL-OPTION-FN-LEFT ARROW (macOS) to bring up Task Manager on the remote office computer.
- In Task Manager click More Details, then click File > Run new task.
- Enter explorer.exe in the box and click Ok.
- This should bring back the desktop.
- If that doesn't help, again click File > Run new task.
- Enter shutdown -r in the box and click OK.
- This should restart the remote office computer. Close the remote computer window. Wait several minutes and try to connect again.