Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

NIDA provides remote desktop servers in order to access licensed software as well as allowing access to on-site resources while working remotely.

Prerequisites

You must have Microsoft Authenticator set up as your default Multi-Factor Authentication method in order to access these remote desktop servers while off site.
See this page for instructions: Microsoft Authenticator App Setup

Remote Desktop Servers

Connection Timeout

You will automatically be disconnected from the remote desktop if no user input is received for the specified time. This means you will need to re-authenticate in order to connect back into the server. While disconnected, any running applications will remain open.

Session Timeout

If you disconnect from your remote desktop without signing out, the server will keep your applications running until the specified session timeout is reached. When the timeout is reached, the server will sign the user out and any unsaved work will be lost. Ensure you save your work and manually sign out when possible.

Server

Access For

Connection
Timeout

Session
Timeout

Purpose

KENRDS00

Staff and Students

3 hours

8 hours

For more demanding apps such as CAD and multimedia

KENRDS01

Staff

8 hours

5 days

General staff apps

Connecting to the Remote Desktop Servers

  1. Download the pre-configured settings for one of the server you wish to connect to

    1. KENRDS01 - Staff: Here

    2. KENRDS00 - Students and Staff: Here

  2. Double click on the downloaded rdp file to initiate a connection

  3. Enter your NIDA email address and password when prompted

  4. If you are connecting from off-site, you will need to then open the Microsoft Authenticator app on your mobile device and tap on the “Approve” button in order to approve the sign in. You will have 30 seconds to perform the approval.

    If you are having trouble approving the requests, cancel the connection and wait 1 minute before trying again from step 2. Cancel any approvals that may show up prior to trying again.

  • No labels