UMIACS - User contributions [en]

UbuntuPrinting

2017-04-12T14:54:46Z

Ccramer: removing references to Ubuntu 12.04

==Overview==
Printing from your personal Ubuntu laptop or desktop is supported. If you are sitting at a supported UMIACS Ubuntu LTS desktop then please see our common UNIX/Linux printing documentation for [[CUPS]]. This documentation may not work for all versions of Ubuntu.

===Printer Accessibility===
In order to print you will '''need to be on the UMIACS internal network,''' either via a wired proxy drop or an [https://wiki.umiacs.umd.edu/umiacs/index.php/SecureShellTunneling SSH tunnel].

==Connecting to a printer==
In order for printing to function properly, you must complete '''ALL''' of the following steps:
#Open the 'Printing' dialog box and click 'Add'.
#Expand the 'Network Printer' dropdown list, and select 'Find Network Printer'.
#In the host field type "print.umiacs.umd.edu" and click find.
#:[[Image:UbuntuPrint01.png|thumb|none|300px|[3] Type 'print.umiacs.umd.edu' into the 'Host:' field and then click Find]]
#Select the print queue you wish to print to, click forward. If you are unsure which queue to use, see the [[PrinterQueueNaming| selecting a print queue]] page.
#:[[Image:UbuntuPrint02.png|thumb|none|300px|[4] Select the queue you wish to print too]]
#Name the printer. '''Take note of the model name listed in the Description. This will be used later!''' Then click 'Apply'
#:[[Image:UbuntuPrint03.png|thumb|none|300px|[5] Take note of the printer description, this will be used in later steps!]]
#In the printing dialog box, right click the newly added printer and select properties.
#In the 'Make and Model' line, click 'change'
#:[[Image:UbuntuPrint04.png|thumb|none|300px|[7] Click 'change' next the 'Make and Model' field.]]
#Ubuntu will now load a list of printers models (This will take a few moments). From that list, select the brand of the printer you are connecting to as noted in step 5.
#:[[Image:UbuntuPrint05.png|thumb|none|300px|[8] Select the brand of the printer as you noted in step 5]]
#Select the specific model of the printer as noted in step 5. Then click forward.
#:[[Image:UbuntuPrint06.png|thumb|none|300px|[9] Select the model of the printer as you noted in step 5]]
#Leave the "try to copy the option settings over from the old PPD" option selected and click forward.
#Select any additional features available for the printer (i.e. duplexing), and then click forward.
#Verify this process by printing a test page. You should get the default Ubuntu test page. If you just get a page with a string of text then the printer is not properly configured, and you should verify the settings.

CCompilers

2017-04-12T14:51:25Z

Ccramer:

We currently have the following C/C++ compilers on the following platforms:

===RHEL5===

* gcc 4.1.2 - /usr/bin/gcc
* gcc 3.4.6 - /usr/bin/gcc34
* gcc 3.3.6 - /usr/local/stow/gcc-3.3.6
* gcc 4.0.4 - /usr/local/stow/gcc-4.0.4
* gcc 4.2.4 - /usr/local/stow/gcc-4.2.4
* gcc 4.5.1 - /usr/local/stow/gcc-4.5.1
* gcc 4.6.0 - /usr/local/stow/gcc-4.6.0
* gcc 4.7.2 - /usr/local/stow/gcc-4.7.2
* gcc 4.8.0 - /usr/local/stow/gcc-4.8.0
* gcc 4.8.1 - /usr/local/stow/gcc-4.8.1
* gcc 4.8.3 - /usr/local/stow/gcc-4.8.3
* [[IntelCompilers|Intel Compilers]]
* [[PGICompilers|Portland Group Compilers]]

===RHEL6===

* gcc 4.4.7 - /usr/bin/gcc
* gcc 4.6.0 - /opt/local/stow/gcc-4.6.0
* gcc 4.7.2 - /opt/local/stow/gcc-4.7.2
* gcc 4.8.0 - /opt/local/stow/gcc-4.8.0
* gcc 4.8.1 - /opt/local/stow/gcc-4.8.1
* gcc 4.8.3 - /opt/local/stow/gcc-4.8.3
* [[IntelCompilers|Intel Compilers]]
* [[PGICompilers|Portland Group Compilers]]

In order to load different versions of gcc into your environment, you can use [[Modules|Modules]], which provides a way to add and later if needed remove environmental variables that provide access to UMIACS large set of software we offer. Please see our [[Modules|Modules page]] for more information on how to use Modules.

Also see: [[CDebuggers]]

CDebuggers

2017-04-12T14:50:22Z

Ccramer:

We currently have the following C/C++ debuggers on the following platforms:

===RHEL5===

* gdb 7.0.1-42.el5 - /usr/bin/gdb
* valgrind 3.5.0 - /usr/bin/valgrind

===RHEL6===

* gdb 7.2-50.el6 - /usr/bin/gdb
* valgrind 3.6.0 - /usr/bin/valgrind

Also see: [[CCompilers]]

Remote Desktop

2017-04-12T14:48:57Z

Ccramer:

=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 [[VPN | UMIACS VPN]] or be within the UMIACS network border.
**Be a member of the 'Remote Desktop Users' group on the remote machine.
==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.
#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]]
#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]]
#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.

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.

==macOS==
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]]

==UNIX==
===freerdp===
If you are trying to access a Windows host via RDP on a RHEL6 or Ubuntu 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.

<pre> rdesktop -r clipboard:CLIPBOARD -g $GEOMETRY -d PC -u $USERNAME $HOSTNAME </pre>

Key:

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: 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. Xfreerdp also has RHEL6. 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:

<pre> xfreerdp -d PC -u $USERNAME --plugin cliprdr -g $GEOMETRY $HOSTNAME </pre>

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

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: 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.