Remote Desktop: Difference between revisions

From UMIACS
Jump to navigation Jump to search
(This is a complete renovation of the Remote Desktop)
No edit summary
Line 1: Line 1:
==Introduction==
=Introduction=


Remote Desktop allows you to connect to another computer from a network that is compatible. Currently, at UMIACS, this feature is only supported for Windows hosts using the Remote Desktop Protocol (RDP). If you need to remotely connect to a UNIX host, please see [[SecureShell]]. With RDP, you can control your Windows desktop environment through a graphical user interface. Mouse and keyboard movements are transferred over a network to a Windows host running an RDP server, which sends screen refreshes back.  
Remote Desktop allows you to connect to another computer from a network that is compatible. Currently, at UMIACS, this feature is only supported for Windows hosts using the Remote Desktop Protocol (RDP). If you need to remotely connect to a UNIX host, please see [[SecureShell]]. With RDP, you can control your Windows desktop environment through a graphical user interface. Mouse and keyboard movements are transferred over a network to a Windows host running an RDP server, which sends screen refreshes back.  
Line 5: Line 5:
To access an RDP enabled machine, you must be on the UMIACS physical network or [[VPN]]. You must also be authorized to access and remotely control the host you are requesting. If a remote session is active, it is not possible for another user to log onto the console in-person. Attempting to use RDP when a computer is in use by another user could force the existing user to logoff and lose their work. You should always quit RDP by logging off of the remote computer. Simply quitting the RDP client can cause you to stay logged in and prevent other users from accessing the remote host, even at the physical console.
To access an RDP enabled machine, you must be on the UMIACS physical network or [[VPN]]. You must also be authorized to access and remotely control the host you are requesting. If a remote session is active, it is not possible for another user to log onto the console in-person. Attempting to use RDP when a computer is in use by another user could force the existing user to logoff and lose their work. You should always quit RDP by logging off of the remote computer. Simply quitting the RDP client can cause you to stay logged in and prevent other users from accessing the remote host, even at the physical console.


==Remote Clients/Viewers==
=How to Connect=
 
*'''Prerequisites:'''
There are a variety of tools available for accessing RDP enabled hosts. The following are the tools currently supported by UMIACS.
**Connected to the [[VPN | UMIACS VPN]] or be within the UMIACS network border.
 
==Windows==
===Windows===
For connecting to Windows client over RDP, we recommend the native Windows 'Remote Desktop Connection' client.
 
#To start the RDC client, click the "Start'" or "Windows" button on the taskbar. In the menu, navigate to "All Programs," "Accessories," then select "Remote Desktop Connection". Alternatively, you can search for "Remote Desktop Connection" in the Start menu's search field.  
Microsoft Remote Desktop Connection (RDC) is the included client for Windows machines. If you are using a Windows machine to access a host through RDP, this is the tool you should use.  
#Once RDC client starts, type the name of the RDP/Windows host you are trying to access. The name should be the Fully Qualified Domain Name (FDQN), i.e. "somepc.'''pc.umiacs.umd.edu'''". At this point, click "Connect" to initiate the RDP session.  
 
#*[[File:RemoteDesktop-ConnectMenu.jpg]]
====Using RDC====
#After the connection is started, a warning message may alert you to an identity verification failure. For UMIACS machines, you can ignore this and proceed by selecting "Yes"
 
#*[[File:RemoteDesktop-SecurityWarning.jpg]]
1) To start the RDC client, click the "Start'" or "Windows" button on the taskbar. In the menu, navigate to "All Programs," "Accessories," then select "Remote Desktop Connection". Alternatively, you can search for "Remote Desktop Connection" in the Start menu's search field.  
#Upon reaching the Windows Security prompt, enter your PC credentials. If the username is either not correct or not the desired account, select "Use another account". Click "Ok" when you are done.  
 
#*[[File:RemoteDesktop-CredentialsPrompt.jpg]]
 
#You should now be viewing the remote computer. To terminate the session, you should logout of Windows.  
2) Once RDC client starts, type the name of the RDP/Windows host you are trying to access. The name should be the Fully Qualified Domain Name (FDQN), i.e. "somepc.'''pc.umiacs.umd.edu'''". At this point, click "Connect" to initiate the RDP session.  
 
[[File:RemoteDesktop-ConnectMenu.jpg]]
 
 
3) After the connection is started, a warning message may alert you to an identity verification failure. For UMIACS machines, you can ignore this and proceed by selecting "Yes"
 
[[File:RemoteDesktop-SecurityWarning.jpg]]
 
4) Upon reaching the Windows Security prompt, enter your PC credentials. If the username is either not correct or not the desired account, select "Use another account". Click "Ok" when you are done.  
 
[[File:RemoteDesktop-CredentialsPrompt.jpg]]
 
5) You should now be viewing the remote computer. To terminate the session, you should logout of Windows.  


To switch between your current host and the remote host, click the minimize or "-" button on the top connection bar. With RDC, the clipboard can be transferred between the remote and current host while the RDC client is running and logged in.
To switch between your current host and the remote host, click the minimize or "-" button on the top connection bar. With RDC, the clipboard can be transferred between the remote and current host while the RDC client is running and logged in.


===UNIX Hosts===
==OSX==
Given the diversity among our UNIX hosts, different RDP clients work best with different Operating Systems. See their descriptions or the table at the bottom of this page for compatibility details.  
For connecting to Windows client over RDP, we recommend the 'Microsoft Remote Desktop' application.  Another, although less preferred options is the CoRD client.
#Open the 'Microsoft Remote Desktop Application' and select '+ New' to create a new device profile
#Fill in the 'Connection Name' and 'PC Name' fields with the name of the host remote host you wish to connect to.  Then close the window.
#*[[File:OSX_MRD_addClient.png  |300px]]
#You will now see the device listed in the 'My Desktops' section of the 'Microsoft Remote Desktop' Application.  Double click it to start the connection.
#*[[File:OSX_MRD.png | 300px]]


====CoRD====
==UNIX==
If you are trying to access a Windows host via RDP on a Mac, you should use CoRD. The binary can be downloaded from by clicking [http://cord.sourceforge.net/  http://cord.sourceforge.net/].
===rdesktop===
 
To install CoRD, drag the app from it's download folder to the Applications folder.
 
1) With CoRD installed, launch the app from the Applications folder. At this time, you may wish to right click (CTRL+CLICK) on the Dock icon, hover over 'Options,' and select "Keep in Dock."
 
[[File:RemoteDesktop-KeepInDock.png]]
 
2) Under the "File" menu, press "New Server...".
 
[[File:RemoteDesktop-NewServer.png]]
 
3) On the New Server pop up, fill out the appropriate information. The ''Address'' should be the Fully Qualified Domain Name of the RDP remote server (i.e. somepc'''.pc.umiacs.umd.edu'''). For the ''Username'' field, type your UMIACS username, then type "PC" in the ''Domain'' field. You may select a desired screen resolution or leave the default, whichever you prefer. You may also choose a name for this connection under the ''label'' field. When you are done creating the RDP connection, close the new connection popup.
 
[[File:RemoteDesktop-SetupCoOrd.png]]
 
4)  Go to the "Servers" menu on the top bar and select "Servers." Choose the name you gave your connection in step 3.
 
[[File:RemoteDesktop-RunServer.png]]
 
5) As with Microsoft Remote Desktop Connection, enter your password credentials at the login prompt. Be sure to quit by using the Windows logoff function when you are ready.
 
====rdesktop====
If you are trying to access a Windows host via RDP on a RHEL6 or Ubuntu 12.04/14.04 machine, you should use the rdesktop client from the command line. This should be preinstalled, so there is no configuration that needs to happen.  
If you are trying to access a Windows host via RDP on a RHEL6 or Ubuntu 12.04/14.04 machine, you should use the rdesktop client from the command line. This should be preinstalled, so there is no configuration that needs to happen.  


Line 76: Line 45:
Once you have connected, you will be directed to a  Windows login screen where you can complete the login process.
Once you have connected, you will be directed to a  Windows login screen where you can complete the login process.


====xfreerdp====
===xfreerdp===


Xfreerdp is the replacement for rdesktop included with newer Linux hosts, starting with RHEL7 and Ubuntu 12.04/14.04. You should use the xfreerdp client from the command line. This is preinstalled on these newer hosts.  
Xfreerdp is the replacement for rdesktop included with newer Linux hosts, starting with RHEL7 and Ubuntu 12.04/14.04. You should use the xfreerdp client from the command line. This is preinstalled on these newer hosts.  
Line 91: Line 60:


As with any of these RDP solutions, closing xfreerdp (using the top bar or using CTRL+C) without logging out could cause considerable problems for other users of the workstation. Please be sure to logout after you are finished with the remote machine using the Start menu.
As with any of these RDP solutions, closing xfreerdp (using the top bar or using CTRL+C) without logging out could cause considerable problems for other users of the workstation. Please be sure to logout after you are finished with the remote machine using the Start menu.
===Comparison Table===
{|style="color:green;background-color:#ffffcc;" cellpadding="10" cellspacing="0" border="1"
|-style="color:black;"
|
|Windows 7
|RHEL 5
|RHEL6
|RHEL7
|Ubuntu 12.04
|Ubuntu 14.04
|Mac OS X
|-
|RDC
|Yes
|
|
|
|
|
|
|-
|CoRD
|
|
|
|
|
|
|Yes
|-
|rdesktop
|
|Yes
|Yes
|
|Yes
| Yes
|
|-
|xfreerdp
|
|
|
|Yes
| Yes
| Yes
|
|}

Revision as of 14:01, 23 February 2015

Introduction

Remote Desktop allows you to connect to another computer from a network that is compatible. Currently, at UMIACS, this feature is only supported for Windows hosts using the Remote Desktop Protocol (RDP). If you need to remotely connect to a UNIX host, please see SecureShell. With RDP, you can control your Windows desktop environment through a graphical user interface. Mouse and keyboard movements are transferred over a network to a Windows host running an RDP server, which sends screen refreshes back.

To access an RDP enabled machine, you must be on the UMIACS physical network or VPN. You must also be authorized to access and remotely control the host you are requesting. If a remote session is active, it is not possible for another user to log onto the console in-person. Attempting to use RDP when a computer is in use by another user could force the existing user to logoff and lose their work. You should always quit RDP by logging off of the remote computer. Simply quitting the RDP client can cause you to stay logged in and prevent other users from accessing the remote host, even at the physical console.

How to Connect

  • Prerequisites:
    • Connected to the UMIACS VPN or be within the UMIACS network border.

Windows

For connecting to Windows client over RDP, we recommend the native Windows 'Remote Desktop Connection' client.

  1. To start the RDC client, click the "Start'" or "Windows" button on the taskbar. In the menu, navigate to "All Programs," "Accessories," then select "Remote Desktop Connection". Alternatively, you can search for "Remote Desktop Connection" in the Start menu's search field.
  2. Once RDC client starts, type the name of the RDP/Windows host you are trying to access. The name should be the Fully Qualified Domain Name (FDQN), i.e. "somepc.pc.umiacs.umd.edu". At this point, click "Connect" to initiate the RDP session.
  3. After the connection is started, a warning message may alert you to an identity verification failure. For UMIACS machines, you can ignore this and proceed by selecting "Yes"
    • RemoteDesktop-SecurityWarning.jpg
  4. Upon reaching the Windows Security prompt, enter your PC credentials. If the username is either not correct or not the desired account, select "Use another account". Click "Ok" when you are done.
  5. You should now be viewing the remote computer. To terminate the session, you should logout of Windows.

To switch between your current host and the remote host, click the minimize or "-" button on the top connection bar. With RDC, the clipboard can be transferred between the remote and current host while the RDC client is running and logged in.

OSX

For connecting to Windows client over RDP, we recommend the 'Microsoft Remote Desktop' application. Another, although less preferred options is the CoRD client.

  1. Open the 'Microsoft Remote Desktop Application' and select '+ New' to create a new device profile
  2. Fill in the 'Connection Name' and 'PC Name' fields with the name of the host remote host you wish to connect to. Then close the window.
  3. You will now see the device listed in the 'My Desktops' section of the 'Microsoft Remote Desktop' Application. Double click it to start the connection.

UNIX

rdesktop

If you are trying to access a Windows host via RDP on a RHEL6 or Ubuntu 12.04/14.04 machine, you should use the rdesktop client from the command line. This should be preinstalled, so there is no configuration that needs to happen.

To use rdesktop, open a shell prompt and type the following command, replacing any $REPLACEME with the requested value. 

 rdesktop -r clipboard:CLIPBOARD -g $GEOMETRY -d PC -u $USERNAME  $HOSTNAME

Key:

  • $GEOMETRY: Percent of remote host's screen to mirror on the client
  • $USERNAME: Your UMIACS username (Do not include domain name)
  • $HOSTNAME: Fully Qualified Domain Name (FDQN) of the desired remote host

Once you have connected, you will be directed to a Windows login screen where you can complete the login process.

xfreerdp

Xfreerdp is the replacement for rdesktop included with newer Linux hosts, starting with RHEL7 and Ubuntu 12.04/14.04. You should use the xfreerdp client from the command line. This is preinstalled on these newer hosts.

The command for xfreerdp is a bit different than rdesktop. To connect via RDP to a remote host with xfreerdp, type the following command, replacing values as appropriate: 

 xfreerdp -d PC -u $USERNAME --plugin cliprdr -g $GEOMETRY $HOSTNAME

Similar to rdesktop, here is an explanation of the values above:

  • $GEOMETRY: Percent of remote host's screen to mirror on the client
  • $USERNAME: Your UMIACS username (Do not include domain name)
  • $HOSTNAME: Fully Qualified Domain Name (FDQN) of the desired remote host

As with any of these RDP solutions, closing xfreerdp (using the top bar or using CTRL+C) without logging out could cause considerable problems for other users of the workstation. Please be sure to logout after you are finished with the remote machine using the Start menu.

Retrieved from "https://wiki.umiacs.umd.edu/umiacs/index.php?title=Remote_Desktop&oldid=6476"