<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rleimens</id>
	<title>UMIACS - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rleimens"/>
	<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php/Special:Contributions/Rleimens"/>
	<updated>2026-06-01T18:40:33Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.7</generator>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Jira&amp;diff=8159</id>
		<title>Jira</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Jira&amp;diff=8159"/>
		<updated>2019-02-25T16:24:09Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;JIRA is a request and bug tracker that UMIACS uses to provide our [[HelpDesk]] functionality to our users. It can be accessed [https://intranet.umiacs.umd.edu/jira here].&lt;br /&gt;
&lt;br /&gt;
It is a web based ticketing system that allows both users and staff to maintain greater control over their tickets and makes communication and resolution of issues a seamless process. &lt;br /&gt;
&lt;br /&gt;
== Using JIRA ==&lt;br /&gt;
JIRA automatically creates accounts for UMIACS Account holders. &#039;&#039;&#039;If you have a UMIACS account, you can log in to JIRA using the UMIACS Single Sign On service&#039;&#039;. Otherwise, when you email JIRA, a ticket is created, and the email address your mail was sent from is added as a participant to the ticket -- this means that if you create a ticket using a non-UMIACS email address, you&#039;ll have to login to JIRA using that email address to see the ticket.&lt;br /&gt;
&lt;br /&gt;
===If you have a UMIACS account===&lt;br /&gt;
&lt;br /&gt;
Simply login to Jira&#039;s Customer Portal [0] and select the UMIACS Single Single Sign On to login with your UMIACS credentials.&lt;br /&gt;
&lt;br /&gt;
[0] https://intranet.umiacs.umd.edu/jira/servicedesk/customer/portal/&lt;br /&gt;
&lt;br /&gt;
===If you do not have a UMIACS account or submitted a ticket with a non-UMIACS address===&lt;br /&gt;
The first time you use a new address to submit a ticket you will get an automated email containing a link to set a password for the newly-created Jira account. After you have set your full name and password, you can log in with this email address and password at the external user page [1].&lt;br /&gt;
&lt;br /&gt;
[1] https://intranet.umiacs.umd.edu/jira/servicedesk/customer/user/login?nosso&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Jira_offsite.png]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Jira&amp;diff=8122</id>
		<title>Jira</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Jira&amp;diff=8122"/>
		<updated>2019-02-01T16:03:04Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: /* Using JIRA */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;JIRA is a request and bug tracker that UMIACS uses to provide our [[HelpDesk]] functionality to our users. It can be accessed [https://intranet.umiacs.umd.edu/jira here].&lt;br /&gt;
&lt;br /&gt;
It is a web based ticketing system that allows both users and staff to maintain greater control over their tickets and makes communication and resolution of issues a seamless process. &lt;br /&gt;
&lt;br /&gt;
== Using JIRA ==&lt;br /&gt;
JIRA automatically creates accounts for UMIACS Account holders. &#039;&#039;&#039;If you have a UMIACS account, you can log in to JIRA using the UMIACS Single Sign On service&#039;&#039;. Otherwise, when you email JIRA, a ticket is created, and the email address your mail was sent from is added as a participant to the ticket -- this means that if you create a ticket using a non-UMIACS email address, you&#039;ll have to login to JIRA using that email address to see the ticket.&lt;br /&gt;
&lt;br /&gt;
===If you have a UMIACS account===&lt;br /&gt;
&lt;br /&gt;
Simply login to Jira&#039;s Customer Portal [0] and you will be redirected to the UMIACS Single Single Sign On to login with your UMIACS credentials.&lt;br /&gt;
&lt;br /&gt;
[0] https://intranet.umiacs.umd.edu/jira/servicedesk/customer/portal/&lt;br /&gt;
&lt;br /&gt;
===If you do not have a UMIACS account or submitted a ticket with a non-UMIACS address===&lt;br /&gt;
The first time you use a new address to submit a ticket you will get an automated email containing a link to set a password for the newly-created Jira account. After you have set your full name and password, you can log in with this email address and password at the external user page [1].&lt;br /&gt;
&lt;br /&gt;
[1] https://intranet.umiacs.umd.edu/jira/servicedesk/customer/user/login?nosso&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Jira_offsite.png]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Network/VPN/Windows&amp;diff=7446</id>
		<title>Network/VPN/Windows</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Network/VPN/Windows&amp;diff=7446"/>
		<updated>2017-07-03T16:37:55Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: /* Connecting through the Pulse Secure client */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Please note that this tutorial assumes you already have a network connection established.&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&#039;Authentication is handled via the Windows domain.  If you have an account in the PC Active Directory, you already have access.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The UMIACS VPN is accessible through the Pulse Secure Client.  Alternatively, you can establish a connection through a web browser.&lt;br /&gt;
&lt;br /&gt;
== Connecting through the Pulse Secure client ==&lt;br /&gt;
#&#039;&#039;&#039;Download the client:&#039;&#039;&#039;&lt;br /&gt;
#:[[Media:PulseSecure.x64.msi|Windows 64 bit Pulse Secure Client]]&amp;lt;br style=&amp;quot;clear:both&amp;quot;/&amp;gt;&lt;br /&gt;
#:[[Media:PulseSecure.x86.msi|Windows 32 bit Pulse Secure Client]]&amp;lt;br style=&amp;quot;clear:both&amp;quot;/&amp;gt;&lt;br /&gt;
#:&#039;&#039;Upon starting the client for the first time it may ask to upgrade the client.  This will pull an up to date version of the client with the most recent configuration.&#039;&#039;&lt;br /&gt;
#&#039;&#039;&#039;Start the client if it is not already running - it usually starts by default on bootup.&#039;&#039;&#039;&lt;br /&gt;
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu.]]&lt;br /&gt;
#&#039;&#039;&#039;If the client is already running, double click its icon from the status bar.&#039;&#039;&#039;&lt;br /&gt;
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click its status icon to open.]]&lt;br /&gt;
#&#039;&#039;&#039;and click &#039;Add&#039; (+) under the connection section.&#039;&#039;&#039;&lt;br /&gt;
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the &#039;Add&#039; (+) button to create a new connection.]]&lt;br /&gt;
#&#039;&#039;&#039;Enter a name for your VPN connection and the server URL &#039;vpn.umiacs.umd.edu&#039;&#039;&#039;&#039; &lt;br /&gt;
#:[[Image:Pulse Connections.jpg|thumb|center|280px|[Windows] Enter the name of the VPN server.]]&lt;br /&gt;
#&#039;&#039;&#039;Enter your UMIACS Windows side credentials and hit connect.&#039;&#039;&#039; &lt;br /&gt;
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS Windows credentials.]]&lt;br /&gt;
&lt;br /&gt;
You should now be connected to the UMIACS VPN.&lt;br /&gt;
&lt;br /&gt;
==Checking VPN Status==&lt;br /&gt;
# In the bottom right hand corner, in your status bar, you should see an S icon. If there&#039;s a green arrow, that means you are connected! If there is nothing, that means you are not. &lt;br /&gt;
#:[[Image:Pulseicon2.png|thumb|center|500px|]]&lt;br /&gt;
# You can hover over this icon and it will show you the status of your connection.&lt;br /&gt;
#:[[Image:PulseStatus2.png|thumb|center|500px|]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=HelpDesk&amp;diff=7427</id>
		<title>HelpDesk</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=HelpDesk&amp;diff=7427"/>
		<updated>2017-06-25T21:24:19Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The UMIACS Help Desk provides Technical Support and Equipment procurement.&lt;br /&gt;
&lt;br /&gt;
; Help Desk Location&lt;br /&gt;
: 3142 A.V. Williams Building&lt;br /&gt;
; Help Desk Hours&lt;br /&gt;
: 9:00am - 5:00pm Monday - Friday. (Excluding University Holidays)&lt;br /&gt;
&lt;br /&gt;
==How to Contact Support==&lt;br /&gt;
; Email&lt;br /&gt;
: [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]&lt;br /&gt;
; Telephone&lt;br /&gt;
: 301-405-1775&lt;br /&gt;
; [[Jira | JIRA Request Tracker]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=HelpDesk&amp;diff=7426</id>
		<title>HelpDesk</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=HelpDesk&amp;diff=7426"/>
		<updated>2017-06-25T21:24:10Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The UMIACS Help Desk provides Technical Support and Equipment procurement.&lt;br /&gt;
&lt;br /&gt;
; Help Desk Location&lt;br /&gt;
: 3142 A.V. Williams Building&lt;br /&gt;
; Help Desk Hours&lt;br /&gt;
: 9:00am - 5:00pm Monday - Friday. (Excluding University Holidays)&lt;br /&gt;
&lt;br /&gt;
==How to Contact Support==&lt;br /&gt;
; Email&lt;br /&gt;
: [mailto:staff@umiacs.umd.edu staff@umiacs.umd.edu]&lt;br /&gt;
; Telephone&lt;br /&gt;
: 301-405-1775&lt;br /&gt;
; [[Jira | JIRA Request Tracker]]&lt;br /&gt;
&lt;br /&gt;
Test&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=7160</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=7160"/>
		<updated>2016-10-07T15:50:01Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A tentative list of maintenance windows for 2016 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;October 20th 2016&#039;&#039;&#039;&lt;br /&gt;
* November 17th 2016&lt;br /&gt;
* December 22nd 2016&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;br /&gt;
* February 19th 2015&lt;br /&gt;
* March 19th 2015&lt;br /&gt;
* May 21st 2015&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;br /&gt;
* November 19th 2015&lt;br /&gt;
* December 17th 2015&lt;br /&gt;
* January 21st 2016&lt;br /&gt;
* February 18th 2016&lt;br /&gt;
* March 12th 2016 (Adjusted date for AVW power outage)&lt;br /&gt;
* April 21st 2016&lt;br /&gt;
* May 19th 2016&lt;br /&gt;
* June 23rd 2016&lt;br /&gt;
* July 21st 2016&lt;br /&gt;
* August 18th 2016&lt;br /&gt;
* September 22nd 2016&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=7159</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=7159"/>
		<updated>2016-10-07T15:49:44Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A tentative list of maintenance windows for 2016 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;October 20th 2016&#039;&#039;&#039;&lt;br /&gt;
* November 17th 2016&lt;br /&gt;
* December 22nd 2016&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;br /&gt;
* February 19th 2015&lt;br /&gt;
* March 19th 2015&lt;br /&gt;
* May 21st 2015&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;br /&gt;
* November 19th 2015&lt;br /&gt;
* December 17th 2015&lt;br /&gt;
* January 21st 2016&lt;br /&gt;
* February 18th 2016&lt;br /&gt;
* March 12th 2016 (Adjusted date for AVW power outage)&lt;br /&gt;
* April 21st 2016&lt;br /&gt;
* May 19th 2016&lt;br /&gt;
* June 23rd 2016&lt;br /&gt;
* July 21st 2016&lt;br /&gt;
* August 18th 2016&lt;br /&gt;
* September 21st 2016&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=7158</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=7158"/>
		<updated>2016-10-07T15:49:12Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A tentative list of maintenance windows for 2016 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;October 20th 2016&#039;&#039;&#039;&lt;br /&gt;
* November 17th 2016&lt;br /&gt;
* December 22nd 2016&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;br /&gt;
* February 19th 2015&lt;br /&gt;
* March 19th 2015&lt;br /&gt;
* May 21st 2015&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;br /&gt;
* November 19th 2015&lt;br /&gt;
* December 17th 2015&lt;br /&gt;
* January 21st 2016&lt;br /&gt;
* February 18th 2016&lt;br /&gt;
* March 12th 2016 (Adjusted date for AVW power outage)&lt;br /&gt;
* April 21st 2016&lt;br /&gt;
* May 19th 2016&lt;br /&gt;
* June 23rd 2016&lt;br /&gt;
* July 21st 2016&lt;br /&gt;
* August 18th 2016&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6852</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6852"/>
		<updated>2016-03-09T21:17:27Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A tentative list of maintenance windows for 2016 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;March 12th 2016&#039;&#039;&#039; (Adjusted date for AVW power outage)&lt;br /&gt;
* April 21st 2016&lt;br /&gt;
* May 19th 2016&lt;br /&gt;
* June 23rd 2016&lt;br /&gt;
* July 21st 2016&lt;br /&gt;
* August 18th 2016&lt;br /&gt;
* September 22nd 2016&lt;br /&gt;
* October 20th 2016&lt;br /&gt;
* November 17th 2016&lt;br /&gt;
* December 22nd 2016&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;br /&gt;
* February 19th 2015&lt;br /&gt;
* March 19th 2015&lt;br /&gt;
* May 21st 2015&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;br /&gt;
* November 19th 2015&lt;br /&gt;
* December 17th 2015&lt;br /&gt;
* January 21st 2016&lt;br /&gt;
* February 18th 2016&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6686</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6686"/>
		<updated>2015-10-23T04:12:27Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A list of maintenance windows for 2015 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;November 19th, 2015&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;br /&gt;
* February 19th 2015&lt;br /&gt;
* March 19th 2015&lt;br /&gt;
* May 21st 2015&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6514</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6514"/>
		<updated>2015-05-20T14:38:06Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A list of maintenance windows for 2015 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;May 21st 2015&#039;&#039;&#039;&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;br /&gt;
* November 19th, 2015&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;br /&gt;
* February 19th 2015&lt;br /&gt;
* March 19th 2015&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6480</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6480"/>
		<updated>2015-03-23T00:56:23Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A list of maintenance windows for 2015 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;April 23rd 2015&#039;&#039;&#039;&lt;br /&gt;
* May 21st 2015&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;br /&gt;
* November 19th, 2015&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;br /&gt;
* February 19th 2015&lt;br /&gt;
* March 19th 2015&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6471</id>
		<title>MonthlyMaintenanceWindow</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MonthlyMaintenanceWindow&amp;diff=6471"/>
		<updated>2015-02-12T15:18:56Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS takes a monthly maintenance window to patch and reboot our hosts.  This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.&lt;br /&gt;
&lt;br /&gt;
The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft&#039;s Patch Tuesday].  This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month&#039;s window.&lt;br /&gt;
&lt;br /&gt;
The window is always going to be on a &#039;&#039;&#039;Thursday&#039;&#039;&#039; from &#039;&#039;&#039;8pm-12am&#039;&#039;&#039;.  A list of maintenance windows for 2015 is as follows with the upcoming window in bold.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;February 19th 2015&#039;&#039;&#039;&lt;br /&gt;
* March 19th 2015&lt;br /&gt;
* April 23rd 2015&lt;br /&gt;
* May 21st 2015&lt;br /&gt;
* June 18th 2015&lt;br /&gt;
* July 23rd 2015&lt;br /&gt;
* August 20th 2015&lt;br /&gt;
* September 17th 2015&lt;br /&gt;
* October 22nd 2015&lt;br /&gt;
* November 19th, 2015&lt;br /&gt;
&lt;br /&gt;
==Archives==&lt;br /&gt;
* January 17th 2013&lt;br /&gt;
* February 21st 2013&lt;br /&gt;
* March 21st 2013&lt;br /&gt;
* April 18th 2013&lt;br /&gt;
* May 23rd 2013&lt;br /&gt;
* June 20th 2013&lt;br /&gt;
* July 18th 2013&lt;br /&gt;
* August 22nd 2013&lt;br /&gt;
* September 19th 2013&lt;br /&gt;
* October 17th 2013&lt;br /&gt;
* December 19th 2013&lt;br /&gt;
* January 23rd 2014&lt;br /&gt;
* February 20th 2014&lt;br /&gt;
* March 20th 2014&lt;br /&gt;
* April 17th 2014&lt;br /&gt;
* May 22nd 2014&lt;br /&gt;
* June 19th 2014&lt;br /&gt;
* July 17th 2014&lt;br /&gt;
* August 21st 2014&lt;br /&gt;
* September 18th 2014&lt;br /&gt;
* October 23rd 2014&lt;br /&gt;
* November 20th 2014&lt;br /&gt;
* December 18th 2014&lt;br /&gt;
* January 22nd 2015&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&amp;diff=6400</id>
		<title>Matlab</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&amp;diff=6400"/>
		<updated>2014-12-03T22:19:56Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS has [[Matlab]] licenses that cover Linux, Windows and Mac.  To access them you have to be using a university owned computer. If you would like to run Matlab on a machine that is not University-owned, you can check the pricing through OIT/SLIC [http://www.oit.umd.edu/units/slic/products/mathworks/matlab.html here]&lt;br /&gt;
&lt;br /&gt;
==Linux==&lt;br /&gt;
Below are the different locations of Matlab across our supported linux workstations and servers.  The one in bold is our latest version. RHEL5 is no longer supported as of R2013b, and 32-bit Linux distributions are no longer supported as of R2012b. For more information, please see [http://www.mathworks.com/support/sysreq/roadmap.html this page].&lt;br /&gt;
&lt;br /&gt;
===RHEL5===&lt;br /&gt;
* /opt/matlab-r2007b&lt;br /&gt;
* /opt/matlab-r2008a&lt;br /&gt;
* /opt/matlab-r2008b&lt;br /&gt;
* /opt/matlab-r2009b&lt;br /&gt;
* /opt/matlab-r2010a&lt;br /&gt;
* /opt/matlab-r2010b&lt;br /&gt;
* /opt/matlab-r2011a&lt;br /&gt;
* /opt/matlab-r2011b&lt;br /&gt;
* /opt/matlab-r2012a&lt;br /&gt;
* /opt/matlab-r2012b&lt;br /&gt;
* &#039;&#039;&#039;/opt/matlab-r2013a&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
===RHEL6,7/Ubuntu===&lt;br /&gt;
&lt;br /&gt;
* /opt/common/matlab-r2007b&lt;br /&gt;
* /opt/common/matlab-r2008a&lt;br /&gt;
* /opt/common/matlab-r2008b&lt;br /&gt;
* /opt/common/matlab-r2009b&lt;br /&gt;
* /opt/common/matlab-r2010a&lt;br /&gt;
* /opt/common/matlab-r2010b&lt;br /&gt;
* /opt/common/matlab-r2011a&lt;br /&gt;
* /opt/common/matlab-r2011b&lt;br /&gt;
* /opt/common/matlab-r2012a&lt;br /&gt;
* /opt/common/matlab-r2012b&lt;br /&gt;
* /opt/common/matlab-r2013a&lt;br /&gt;
* /opt/common/matlab-r2013b&lt;br /&gt;
* /opt/common/matlab-r2014a&lt;br /&gt;
* &#039;&#039;&#039;/opt/common/matlab-r2014b&#039;&#039;&#039;&lt;br /&gt;
==Windows==&lt;br /&gt;
Below are the different locations of Matlab available for university-owned machines running Windows 7. The one in bold is the latest version we have available:&lt;br /&gt;
&lt;br /&gt;
* Matlab r2007a&lt;br /&gt;
* Matlab r2007b&lt;br /&gt;
* Matlab r2008a&lt;br /&gt;
* Matlab r2008b&lt;br /&gt;
* Matlab r2009a&lt;br /&gt;
* Matlab r2009b&lt;br /&gt;
* Matlab r2010a&lt;br /&gt;
* Matlab r2010b&lt;br /&gt;
* Matlab r2011a&lt;br /&gt;
* Matlab r2011b&lt;br /&gt;
* Matlab r2012a&lt;br /&gt;
* Matlab r2012b&lt;br /&gt;
* Matlab r2013a&lt;br /&gt;
* &#039;&#039;&#039;Matlab r2013b&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==OSX==&lt;br /&gt;
Below are the different locations of Matlab available for university-owned machines running OSX. We expect that all versions should run on OSX 10.8 and newer. The one in bold is the latest version we have available:&lt;br /&gt;
&lt;br /&gt;
* Matlab r2008a&lt;br /&gt;
* Matlab r2008b&lt;br /&gt;
* Matlab r2009b&lt;br /&gt;
* Matlab r2010a&lt;br /&gt;
* Matlab r2010b&lt;br /&gt;
* Matlab r2011b&lt;br /&gt;
* Matlab r2012a&lt;br /&gt;
* Matlab r2012b&lt;br /&gt;
* Matlab r2013a (OSX 10.8+)&lt;br /&gt;
* &#039;&#039;&#039;Matlab r2013b&#039;&#039;&#039; (OSX 10.8+)&lt;br /&gt;
&lt;br /&gt;
==License Troubleshooting==&lt;br /&gt;
&lt;br /&gt;
Campus has a limited number of seats for Matlab itself, as well as the various toolboxes. When calling functions in a toolbox, Matlab will automatically check out a license, making it temporarily unavailable to other users. Sometimes it&#039;s necessary to check the number of toolbox licenses available.&lt;br /&gt;
&lt;br /&gt;
===Windows License Troubleshooting===&lt;br /&gt;
On Windows machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. &amp;quot;win64&amp;quot; needs to be adjusted to &amp;quot;win32&amp;quot; on a 32-bit installation:&lt;br /&gt;
 $MATLAB_PATH\etc\win64\lmutil lmstat -c &amp;quot;$MATLAB_PATH\licenses\network.lic&amp;quot; -f $TOOLBOX_SHORTNAME&lt;br /&gt;
&lt;br /&gt;
As an example, here is how to query Matlab r2012b on a 64-bit Windows 7 host for the Aerospace Blockset Toolbox: &lt;br /&gt;
 &amp;quot;C:\Program Files\matlab\r2012b\etc\win64\lmutil.exe&amp;quot; lmstat -c &amp;quot;C:\Program Files\matlab\r2012b\licenses\network.lic&amp;quot; -f Aerospace_Blockset&lt;br /&gt;
&lt;br /&gt;
===Unix License Troubleshooting===&lt;br /&gt;
On Unix machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. &amp;quot;glnxa64&amp;quot; needs to adjusted to &amp;quot;glnx86&amp;quot; on a 32-bit installation::&lt;br /&gt;
 $MATLAB_PATH/bin/glnxa64/lmutil lmstat -c $MATLAB_PATH/licenses/network.lic -f $TOOLBOX_SHORTNAME&lt;br /&gt;
&lt;br /&gt;
As an example, here is how to query Matlab r2010b on our 64-bit RHEL5 hosts for the Parallel Computing Toolbox:&lt;br /&gt;
 /opt/matlab-r2010b/bin/glnxa64/lmutil lmstat -c /opt/matlab-r2010b/licenses/network.lic -f Distrib_Computing_Toolbox&lt;br /&gt;
&lt;br /&gt;
===Toolbox Shortnames===&lt;br /&gt;
The toolbox names themselves don&#039;t always work with this command; Rather, Matlab has a set of shortnames which can be passed to the lmstat command. The following are all the valid shortnames:&lt;br /&gt;
&lt;br /&gt;
 Aerospace_Blockset   &lt;br /&gt;
 Aerospace_Toolbox  &lt;br /&gt;
 Bioinformatics_Toolbox  &lt;br /&gt;
 Communication_Blocks  &lt;br /&gt;
 Communication_Toolbox  &lt;br /&gt;
 Compiler  &lt;br /&gt;
 Control_Toolbox  &lt;br /&gt;
 Curve_Fitting_Toolbox  &lt;br /&gt;
 Data_Acq_Toolbox  &lt;br /&gt;
 Database_Toolbox  &lt;br /&gt;
 Datafeed_Toolbox  &lt;br /&gt;
 Distrib_Computing_Toolbox  &lt;br /&gt;
 Econometrics_Toolbox  &lt;br /&gt;
 Excel_Link  &lt;br /&gt;
 Fin_Derivatives_Toolbox  &lt;br /&gt;
 Financial_Toolbox  &lt;br /&gt;
 Fixed_Income_Toolbox  &lt;br /&gt;
 Fixed_Point_Toolbox  &lt;br /&gt;
 GADS_Toolbox  &lt;br /&gt;
 Identification_Toolbox  &lt;br /&gt;
 Image_Acquisition_Toolbox  &lt;br /&gt;
 Image_Toolbox  &lt;br /&gt;
 Instr_Control_Toolbox  &lt;br /&gt;
 MAP_Toolbox  &lt;br /&gt;
 MATLAB  &lt;br /&gt;
 MATLAB_Builder_for_Java  &lt;br /&gt;
 MATLAB_Coder  &lt;br /&gt;
 MATLAB_Excel_Builder  &lt;br /&gt;
 MATLAB_Report_Gen  &lt;br /&gt;
 MPC_Toolbox  &lt;br /&gt;
 Neural_Network_Toolbox  &lt;br /&gt;
 Optimization_Toolbox  &lt;br /&gt;
 PDE_Toolbox  &lt;br /&gt;
 Real-Time_Workshop  &lt;br /&gt;
 Robust_Toolbox  &lt;br /&gt;
 Signal_Blocks  &lt;br /&gt;
 Signal_Toolbox  &lt;br /&gt;
 SimMechanics  &lt;br /&gt;
 Simscape  &lt;br /&gt;
 SIMULINK  &lt;br /&gt;
 Simulink_Control_Design  &lt;br /&gt;
 Stateflow  &lt;br /&gt;
 Stateflow_Coder  &lt;br /&gt;
 Statistics_Toolbox  &lt;br /&gt;
 Symbolic_Toolbox  &lt;br /&gt;
 Video_and_Image_Blockset  &lt;br /&gt;
 Virtual_Reality_Toolbox  &lt;br /&gt;
 Wavelet_Toolbox&lt;br /&gt;
&lt;br /&gt;
If you are having problems, feel free to contact [[HelpDesk | UMIACS Staff]], however please note that the Matlab license servers are hosted by campus&#039; Division of Information Technology.&lt;br /&gt;
&lt;br /&gt;
==Matlab Customizations==&lt;br /&gt;
&lt;br /&gt;
You can tweak your Matlab experience using a file &amp;quot;startup.m&amp;quot;. If this file is present in the current working directory where you launch Matlab, it will be executed. You can perform a variety of tasks using this file. These include (but are not limited to) customizing the window environment, setting variables for later use, and enabling use of 3rd party toolboxes. Alternatively, you can use the userpath env variable to set a path other than the current working directory for startup and 3rd party toolbox locations. Please see the following links for more information:&lt;br /&gt;
&lt;br /&gt;
* [http://www.mathworks.com/help/matlab/ref/matlabrc.html Mathworks: Startup.m]&lt;br /&gt;
* [http://www.mathworks.com/help/matlab/matlab_env/startup-folder-for-the-matlab-program.html#bs6j57e-5 Mathworks: Userpath function]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrintingUMIACS&amp;diff=6279</id>
		<title>WindowsPrintingUMIACS</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrintingUMIACS&amp;diff=6279"/>
		<updated>2014-08-29T17:38:15Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: /* Installation of printer queue */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
&lt;br /&gt;
This will guide you through the process of installing and using the printers available within UMIACS.&lt;br /&gt;
&lt;br /&gt;
==Printing Outside of UMIACS / Laptop Printing==&lt;br /&gt;
&lt;br /&gt;
In order to print from outside the UMIACS network, you must first connect to the [[VPN]] on [[Windows7VPN|Windows]]. After you are connected, follow the instructions for adding a printer queue below. Please note that you must be on the VPN whenever your print.&lt;br /&gt;
&lt;br /&gt;
==Pre-Installation Knowledge on Printing at UMIACS==&lt;br /&gt;
&lt;br /&gt;
[[PrinterQueueNaming| Printer Queue Naming]]&lt;br /&gt;
&lt;br /&gt;
==Installation of printer queue==&lt;br /&gt;
&lt;br /&gt;
Please note that this applies to machines on any UMIACS network. This includes all proxy networks, the vast majority of machines in the labs, and machines connected to the UMIACS VPN but not the wireless network alone. &lt;br /&gt;
&lt;br /&gt;
To add printer queues:&lt;br /&gt;
&lt;br /&gt;
Go to start, click and type in “\\printers.pc.umiacs.umd.edu” in the search box. &lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc1.jpg]] [[Image:Win7doc2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you are on the [[WindowsJuniperVPN | Junos VPN]]&#039;&#039;&#039;, you may be prompted with a box for authentication.  Make sure to use your Windows Domain credentials, with &#039;pc\&#039; prefixed to your username.  (For example, if your username was &#039;johndoe&#039; you would enter &#039;pc\johndoe&#039; in the username box)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:UMIACS Printing.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A list of printer queues will appear. Select your desired printer by double clicking on the queue. Once you have double clicked on the queue a box will immediately pop up to show you the status of the printer driver installation. Once that is complete you can start using the printer.&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc3.jpg]]&lt;br /&gt;
&lt;br /&gt;
==Duplex Printing==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Many printers in UMIACS support duplex (2 sided) printing. To make the duplex printing default, first make sure the appropriate printer queue is installed via the directions above. Afterwards, go to start, then “Devices and Printers.”&lt;br /&gt;
Once the printer has been installed proceed by right clicking on the queue then selecting “Printing preferences.”&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc4.jpg]]&lt;br /&gt;
&lt;br /&gt;
After a few seconds the following menu will come up. Make sure you are on the “Printing Shortcuts” tab and select the “Eco-Print (Two-sided Printing)” option then click on okay. This modification will allow you to print 2-sided whenever you choose to use this printer.&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc5.jpg]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrintingUMIACS&amp;diff=6252</id>
		<title>WindowsPrintingUMIACS</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrintingUMIACS&amp;diff=6252"/>
		<updated>2014-08-06T16:28:16Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: /* Printing Outside of UMIACS / Laptop Printing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
&lt;br /&gt;
This will guide you through the process of installing and using the printers available within UMIACS.&lt;br /&gt;
&lt;br /&gt;
==Printing Outside of UMIACS / Laptop Printing==&lt;br /&gt;
&lt;br /&gt;
In order to print from outside the UMIACS network, you must first connect to the [[VPN]] on [[Windows7VPN|Windows]]. After you are connected, follow the instructions for adding a printer queue below. Please note that you must be on the VPN whenever your print.&lt;br /&gt;
&lt;br /&gt;
==Pre-Installation Knowledge on Printing at UMIACS==&lt;br /&gt;
&lt;br /&gt;
[[PrinterQueueNaming| Printer Queue Naming]]&lt;br /&gt;
&lt;br /&gt;
==Installation of printer queue==&lt;br /&gt;
&lt;br /&gt;
Please note that this applies to machines on any UMIACS network. This includes all proxy networks, the vast majority of machines in the labs, and machines connected to the UMIACS VPN but not the wireless network alone. &lt;br /&gt;
&lt;br /&gt;
To add printer queues:&lt;br /&gt;
&lt;br /&gt;
Go to start, click and type in “\\printers.pc.umiacs.umd.edu” in the search box. &lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc1.jpg]] [[Image:Win7doc2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you are on the VPN&#039;&#039;&#039;, you may be prompted with a box for authentication.  Make sure to use your Windows Domain credentials, with &#039;pc\&#039; prefixed to your username.  (For example, if your username was &#039;johndoe&#039; you would enter &#039;pc\johndoe&#039; in the username box)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:UMIACS Printing.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A list of printer queues will appear. Select your desired printer by double clicking on the queue. Once you have double clicked on the queue a box will immediately pop up to show you the status of the printer driver installation. Once that is complete you can start using the printer.&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc3.jpg]]&lt;br /&gt;
&lt;br /&gt;
==Duplex Printing==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Many printers in UMIACS support duplex (2 sided) printing. To make the duplex printing default, first make sure the appropriate printer queue is installed via the directions above. Afterwards, go to start, then “Devices and Printers.”&lt;br /&gt;
Once the printer has been installed proceed by right clicking on the queue then selecting “Printing preferences.”&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc4.jpg]]&lt;br /&gt;
&lt;br /&gt;
After a few seconds the following menu will come up. Make sure you are on the “Printing Shortcuts” tab and select the “Eco-Print (Two-sided Printing)” option then click on okay. This modification will allow you to print 2-sided whenever you choose to use this printer.&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc5.jpg]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrintingUMIACS&amp;diff=6251</id>
		<title>WindowsPrintingUMIACS</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrintingUMIACS&amp;diff=6251"/>
		<updated>2014-08-06T16:28:00Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: /* Printing Outside of UMIACS / Laptop Printing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
&lt;br /&gt;
This will guide you through the process of installing and using the printers available within UMIACS.&lt;br /&gt;
&lt;br /&gt;
==Printing Outside of UMIACS / Laptop Printing==&lt;br /&gt;
&lt;br /&gt;
In order to print from outside the UMIACS network, you must first connect to the [[VPN]] for [[Windows7VPN|Windows]]. After you are connected, follow the instructions for adding a printer queue below. Please note that you must be on the VPN whenever your print.&lt;br /&gt;
&lt;br /&gt;
==Pre-Installation Knowledge on Printing at UMIACS==&lt;br /&gt;
&lt;br /&gt;
[[PrinterQueueNaming| Printer Queue Naming]]&lt;br /&gt;
&lt;br /&gt;
==Installation of printer queue==&lt;br /&gt;
&lt;br /&gt;
Please note that this applies to machines on any UMIACS network. This includes all proxy networks, the vast majority of machines in the labs, and machines connected to the UMIACS VPN but not the wireless network alone. &lt;br /&gt;
&lt;br /&gt;
To add printer queues:&lt;br /&gt;
&lt;br /&gt;
Go to start, click and type in “\\printers.pc.umiacs.umd.edu” in the search box. &lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc1.jpg]] [[Image:Win7doc2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you are on the VPN&#039;&#039;&#039;, you may be prompted with a box for authentication.  Make sure to use your Windows Domain credentials, with &#039;pc\&#039; prefixed to your username.  (For example, if your username was &#039;johndoe&#039; you would enter &#039;pc\johndoe&#039; in the username box)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:UMIACS Printing.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A list of printer queues will appear. Select your desired printer by double clicking on the queue. Once you have double clicked on the queue a box will immediately pop up to show you the status of the printer driver installation. Once that is complete you can start using the printer.&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc3.jpg]]&lt;br /&gt;
&lt;br /&gt;
==Duplex Printing==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Many printers in UMIACS support duplex (2 sided) printing. To make the duplex printing default, first make sure the appropriate printer queue is installed via the directions above. Afterwards, go to start, then “Devices and Printers.”&lt;br /&gt;
Once the printer has been installed proceed by right clicking on the queue then selecting “Printing preferences.”&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc4.jpg]]&lt;br /&gt;
&lt;br /&gt;
After a few seconds the following menu will come up. Make sure you are on the “Printing Shortcuts” tab and select the “Eco-Print (Two-sided Printing)” option then click on okay. This modification will allow you to print 2-sided whenever you choose to use this printer.&lt;br /&gt;
&lt;br /&gt;
[[Image:Win7doc5.jpg]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Remote_Desktop&amp;diff=6208</id>
		<title>Remote Desktop</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Remote_Desktop&amp;diff=6208"/>
		<updated>2014-07-10T14:54:01Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: This is a complete renovation of the Remote Desktop&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Remote Clients/Viewers==&lt;br /&gt;
&lt;br /&gt;
There are a variety of tools available for accessing RDP enabled hosts. The following are the tools currently supported by UMIACS.&lt;br /&gt;
&lt;br /&gt;
===Windows===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
====Using RDC====&lt;br /&gt;
&lt;br /&gt;
1) To start the RDC client, click the &amp;quot;Start&#039;&amp;quot; or &amp;quot;Windows&amp;quot; button on the taskbar. In the menu, navigate to &amp;quot;All Programs,&amp;quot; &amp;quot;Accessories,&amp;quot; then select &amp;quot;Remote Desktop Connection&amp;quot;. Alternatively, you can search for &amp;quot;Remote Desktop Connection&amp;quot; in the Start menu&#039;s search field. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &amp;quot;somepc.&#039;&#039;&#039;pc.umiacs.umd.edu&#039;&#039;&#039;&amp;quot;. At this point, click &amp;quot;Connect&amp;quot; to initiate the RDP session. &lt;br /&gt;
&lt;br /&gt;
[[File:RemoteDesktop-ConnectMenu.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Yes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[File:RemoteDesktop-SecurityWarning.jpg]]&lt;br /&gt;
&lt;br /&gt;
4) Upon reaching the Windows Security prompt, enter your PC credentials. If the username is either not correct or not the desired account, select &amp;quot;Use another account&amp;quot;. Click &amp;quot;Ok&amp;quot; when you are done. &lt;br /&gt;
&lt;br /&gt;
[[File:RemoteDesktop-CredentialsPrompt.jpg]]&lt;br /&gt;
&lt;br /&gt;
5) You should now be viewing the remote computer. To terminate the session, you should logout of Windows. &lt;br /&gt;
&lt;br /&gt;
To switch between your current host and the remote host, click the minimize or &amp;quot;-&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
===UNIX Hosts===&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
====CoRD====&lt;br /&gt;
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/]. &lt;br /&gt;
&lt;br /&gt;
To install CoRD, drag the app from it&#039;s download folder to the Applications folder.&lt;br /&gt;
&lt;br /&gt;
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 &#039;Options,&#039; and select &amp;quot;Keep in Dock.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[File:RemoteDesktop-KeepInDock.png]]&lt;br /&gt;
&lt;br /&gt;
2) Under the &amp;quot;File&amp;quot; menu, press &amp;quot;New Server...&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
[[File:RemoteDesktop-NewServer.png]]&lt;br /&gt;
&lt;br /&gt;
3) On the New Server pop up, fill out the appropriate information. The &#039;&#039;Address&#039;&#039; should be the Fully Qualified Domain Name of the RDP remote server (i.e. somepc&#039;&#039;&#039;.pc.umiacs.umd.edu&#039;&#039;&#039;). For the &#039;&#039;Username&#039;&#039; field, type your UMIACS username, then type &amp;quot;PC&amp;quot; in the &#039;&#039;Domain&#039;&#039; 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 &#039;&#039;label&#039;&#039; field. When you are done creating the RDP connection, close the new connection popup.&lt;br /&gt;
&lt;br /&gt;
[[File:RemoteDesktop-SetupCoOrd.png]]&lt;br /&gt;
&lt;br /&gt;
4)  Go to the &amp;quot;Servers&amp;quot; menu on the top bar and select &amp;quot;Servers.&amp;quot; Choose the name you gave your connection in step 3. &lt;br /&gt;
&lt;br /&gt;
[[File:RemoteDesktop-RunServer.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
====rdesktop====&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
To use rdesktop, open a shell prompt and type the following command, replacing any $REPLACEME with the requested value. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; rdesktop -r clipboard:CLIPBOARD -g $GEOMETRY -d PC -u $USERNAME  $HOSTNAME &amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Key: &lt;br /&gt;
&lt;br /&gt;
* &amp;lt;b&amp;gt;&amp;lt;tt&amp;gt;$GEOMETRY&amp;lt;/tt&amp;gt;&amp;lt;/b&amp;gt;: Percent of remote host&#039;s screen to mirror on the client&lt;br /&gt;
* &amp;lt;b&amp;gt;&amp;lt;tt&amp;gt;$USERNAME&amp;lt;/tt&amp;gt;&amp;lt;/b&amp;gt;: Your UMIACS username (Do not include domain name)&lt;br /&gt;
* &amp;lt;b&amp;gt;&amp;lt;tt&amp;gt;$HOSTNAME&amp;lt;/tt&amp;gt;&amp;lt;/b&amp;gt;: Fully Qualified Domain Name (FDQN) of the desired remote host&lt;br /&gt;
&lt;br /&gt;
Once you have connected, you will be directed to a  Windows login screen where you can complete the login process.&lt;br /&gt;
&lt;br /&gt;
====xfreerdp====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; xfreerdp -d PC -u $USERNAME --plugin cliprdr -g $GEOMETRY $HOSTNAME &amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Similar to rdesktop, here is an explanation of the values above:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;b&amp;gt;&amp;lt;tt&amp;gt;$GEOMETRY&amp;lt;/tt&amp;gt;&amp;lt;/b&amp;gt;: Percent of remote host&#039;s screen to mirror on the client&lt;br /&gt;
* &amp;lt;b&amp;gt;&amp;lt;tt&amp;gt;$USERNAME&amp;lt;/tt&amp;gt;&amp;lt;/b&amp;gt;: Your UMIACS username (Do not include domain name)&lt;br /&gt;
* &amp;lt;b&amp;gt;&amp;lt;tt&amp;gt;$HOSTNAME&amp;lt;/tt&amp;gt;&amp;lt;/b&amp;gt;: Fully Qualified Domain Name (FDQN) of the desired remote host&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Comparison Table===&lt;br /&gt;
&lt;br /&gt;
{|style=&amp;quot;color:green;background-color:#ffffcc;&amp;quot; cellpadding=&amp;quot;10&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-style=&amp;quot;color:black;&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
|Windows 7&lt;br /&gt;
|RHEL 5&lt;br /&gt;
|RHEL6&lt;br /&gt;
|RHEL7&lt;br /&gt;
|Ubuntu 12.04&lt;br /&gt;
|Ubuntu 14.04&lt;br /&gt;
|Mac OS X&lt;br /&gt;
|-&lt;br /&gt;
|RDC&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|CoRD&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|Yes&lt;br /&gt;
|-&lt;br /&gt;
|rdesktop&lt;br /&gt;
|&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|Yes&lt;br /&gt;
| Yes&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|xfreerdp&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|Yes&lt;br /&gt;
| Yes&lt;br /&gt;
| Yes&lt;br /&gt;
|&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:RemoteDesktop-SecurityWarning.jpg&amp;diff=6206</id>
		<title>File:RemoteDesktop-SecurityWarning.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:RemoteDesktop-SecurityWarning.jpg&amp;diff=6206"/>
		<updated>2014-07-10T14:51:10Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6152</id>
		<title>WebSpace</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6152"/>
		<updated>2014-06-23T15:18:22Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS provides web space hosting for research/lab pages and user pages.&lt;br /&gt;
&lt;br /&gt;
==Main Website and Lab Pages==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access the main website and lab sites for editing in two ways:&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
Faculty members and authorized users can modify their own public profiles on the main UMIACS homepage. For instructions, see [[ContentManagement]].&lt;br /&gt;
&lt;br /&gt;
==Personal Web Space==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu/~username&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access their website for editing two ways:&lt;br /&gt;
&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-users - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
In general, large datasets related to a Labs research should go into the specific lab&#039;s web tree, not the individual users.  Remember that users&#039; webpage is not permanently maintained once the user leaves UMIACS.&lt;br /&gt;
&lt;br /&gt;
==Adding A Password Protected Folder To Your Web Space==&lt;br /&gt;
&lt;br /&gt;
1) Create the directory you want to password protect or &amp;lt;tt&amp;gt;cd&amp;lt;/tt&amp;gt; into the directory you want to password protect&lt;br /&gt;
&lt;br /&gt;
2) Create a file called &#039;&#039;.htaccess&#039;&#039; (&amp;lt;tt&amp;gt; vi .htaccess&amp;lt;/tt&amp;gt;) in the directory you wish to password protect.&lt;br /&gt;
&lt;br /&gt;
3) In the file you just created type the following lines &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;AuthUserFile &amp;quot;/your/directory/here/&amp;quot;.htpasswd&lt;br /&gt;
AuthName &amp;quot;Secure Document&amp;quot;&lt;br /&gt;
AuthType Basic&lt;br /&gt;
require user username&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, if you were going to protect the &amp;lt;tt&amp;gt;/fs/www-users/username/private&amp;lt;/tt&amp;gt; directory and you want the required name to be  &amp;lt;tt&amp;gt;class239&amp;lt;/tt&amp;gt;, then your file would look like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
AuthUserFile /fs/www-users/username/private/.htpasswd&lt;br /&gt;
AuthName &amp;quot;Secure Document&amp;quot;&lt;br /&gt;
AuthType Basic&lt;br /&gt;
require user class239&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Create a file called &#039;&#039;.htpasswd&#039;&#039; in the same directory as &#039;&#039;.htaccess&#039;&#039;. You create this file by typing in &amp;lt;tt&amp;gt;htpasswd -c .htpasswd &#039;&#039;username&#039;&#039;&amp;lt;/tt&amp;gt; in the directory area to be protected.&lt;br /&gt;
&lt;br /&gt;
In the example above, the username is &amp;lt;tt&amp;gt;class239&amp;lt;/tt&amp;gt; so you would type &amp;lt;tt&amp;gt;htpasswd -c .htpasswd class239&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You will be prompted to enter the password you want. The &#039;&#039;.htpasswd&#039;&#039; file will be created in the current directory and will contain an encrypted version of the password.&lt;br /&gt;
&lt;br /&gt;
To later change the username, edit the &#039;&#039;.htaccess&#039;&#039; file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6151</id>
		<title>WebSpace</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6151"/>
		<updated>2014-06-23T15:14:24Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: /* Adding A Password Protected Folder To Your Web Space */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS provides web space hosting for research/lab pages and user pages.&lt;br /&gt;
&lt;br /&gt;
==Main Website and Lab Pages==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access the main website and lab sites for editing in two ways:&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
Faculty members and authorized users can modify their own public profiles on the main UMIACS webpage. For instructions, see [[ContentManagement]].&lt;br /&gt;
&lt;br /&gt;
==Personal Web Space==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu/~username&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access their website for editing two ways:&lt;br /&gt;
&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-users - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
In general, large datasets related to a Labs research should go into the specific lab&#039;s web tree, not the individual users.  Remember that users&#039; webpage is not permanently maintained once the user leaves UMIACS.&lt;br /&gt;
&lt;br /&gt;
==Adding A Password Protected Folder To Your Web Space==&lt;br /&gt;
&lt;br /&gt;
1) Create the directory you want to password protect or &amp;lt;tt&amp;gt;cd&amp;lt;/tt&amp;gt; into the directory you want to password protect&lt;br /&gt;
&lt;br /&gt;
2) Create a file called &#039;&#039;.htaccess&#039;&#039; (&amp;lt;tt&amp;gt; vi .htaccess&amp;lt;/tt&amp;gt;) in the directory you wish to password protect.&lt;br /&gt;
&lt;br /&gt;
3) In the file you just created type the following lines &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;AuthUserFile &amp;quot;/your/directory/here/&amp;quot;.htpasswd&lt;br /&gt;
AuthName &amp;quot;Secure Document&amp;quot;&lt;br /&gt;
AuthType Basic&lt;br /&gt;
require user username&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example, if you were going to protect the &amp;lt;tt&amp;gt;/fs/www-users/username/private&amp;lt;/tt&amp;gt; directory and you want the required name to be  &amp;lt;tt&amp;gt;class239&amp;lt;/tt&amp;gt;, then your file would look like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
AuthUserFile /fs/www-users/username/private/.htpasswd&lt;br /&gt;
AuthName &amp;quot;Secure Document&amp;quot;&lt;br /&gt;
AuthType Basic&lt;br /&gt;
require user class239&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Create a file called &#039;&#039;.htpasswd&#039;&#039; in the same directory as &#039;&#039;.htaccess&#039;&#039;. You create this file by typing in &amp;lt;tt&amp;gt;htpasswd -c .htpasswd &#039;&#039;username&#039;&#039;&amp;lt;/tt&amp;gt; in the directory area to be protected.&lt;br /&gt;
&lt;br /&gt;
In the example above, the username is &amp;lt;tt&amp;gt;class239&amp;lt;/tt&amp;gt; so you would type &amp;lt;tt&amp;gt;htpasswd -c .htpasswd class239&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You will be prompted to enter the password you want. The &#039;&#039;.htpasswd&#039;&#039; file will be created in the current directory and will contain an encrypted version of the password.&lt;br /&gt;
&lt;br /&gt;
To later change the username, edit the &#039;&#039;.htaccess&#039;&#039; file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6150</id>
		<title>WebSpace</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6150"/>
		<updated>2014-06-23T14:11:26Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS provides web space hosting for research/lab pages and user pages.&lt;br /&gt;
&lt;br /&gt;
==Main Website and Lab Pages==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access the main website and lab sites for editing in two ways:&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
Faculty members and authorized users can modify their own public profiles on the main UMIACS webpage. For instructions, see [[ContentManagement]].&lt;br /&gt;
&lt;br /&gt;
==Personal Web Space==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu/~username&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access their website for editing two ways:&lt;br /&gt;
&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-users - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
In general, large datasets related to a Labs research should go into the specific lab&#039;s web tree, not the individual users.  Remember that users&#039; webpage is not permanently maintained once the user leaves UMIACS.&lt;br /&gt;
&lt;br /&gt;
==Adding A Password Protected Folder To Your Web Space==&lt;br /&gt;
&lt;br /&gt;
1) Create the directory you want to password protect or &#039;&#039;&#039;cd&#039;&#039;&#039; into the directory you want to password protect&lt;br /&gt;
&lt;br /&gt;
2) Create a file called &#039;&#039;.htaccess&#039;&#039; (&#039;&#039;&#039;vi .htaccess&#039;&#039;&#039;) in the directory you wish to password protect.&lt;br /&gt;
&lt;br /&gt;
3) In the file you just created type the following lines&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthUserFile &#039;&#039;/your/directory/here/&#039;&#039;.htpasswd&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthName &amp;quot;Secure Document&amp;quot;&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthType Basic&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;require user username&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For example, if you were going to protect the &#039;&#039;&#039;/fs/www-users/username/private&#039;&#039;&#039; directory and you want the required name to be &#039;&#039;&#039;class239&#039;&#039;&#039;, then your file would look like this:&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthUserFile /fs/www-users/username/private/.htpasswd&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthName &amp;quot;Secure Document&amp;quot;&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthType Basic&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;require user class239&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
4) Create a file called &#039;&#039;.htpasswd&#039;&#039; in the same directory as &#039;&#039;.htaccess&#039;&#039;. You create this file by typing in &#039;&#039;&#039;htpasswd -c .htpasswd &#039;&#039;username&#039;&#039;&#039;&#039;&#039; in the directory area to be protected.&lt;br /&gt;
&lt;br /&gt;
In the example above, the username is &#039;&#039;&#039;class239&#039;&#039;&#039; so you would type &#039;&#039;&#039;htpasswd -c .htpasswd class239&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
You will be prompted to enter the password you want. The &#039;&#039;.htpasswd&#039;&#039; file will be created in the current directory and will contain an encrypted version of the password.&lt;br /&gt;
&lt;br /&gt;
To later change the username, edit the &#039;&#039;.htaccess&#039;&#039; file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6149</id>
		<title>WebSpace</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WebSpace&amp;diff=6149"/>
		<updated>2014-06-23T14:03:15Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS provides web space hosting for research/lab pages and user pages.&lt;br /&gt;
&lt;br /&gt;
==Main Website and Lab Pages==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access the main website and lab sites for editing in two ways:&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
Faculty members and authorized users can modify their own public profiles from a standard web browser. For instructions, see [[ContentManagement]].&lt;br /&gt;
&lt;br /&gt;
==Personal Web Space==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;http://www.umiacs.umd.edu/~username&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Users can access their website for editing two ways:&lt;br /&gt;
&lt;br /&gt;
* From &amp;lt;b&amp;gt;Unix&amp;lt;/b&amp;gt; as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])&lt;br /&gt;
* From &amp;lt;b&amp;gt;Windows&amp;lt;/b&amp;gt; as \\umiacs-webftp.umiacs.umd.edu\www-users - and remotely accessed by the same file share over the [[VPN]]&lt;br /&gt;
&lt;br /&gt;
In general, large datasets related to a Labs research should go into the specific lab&#039;s web tree, not the individual users.  Remember that users&#039; webpage is not permanently maintained once the user leaves UMIACS.&lt;br /&gt;
&lt;br /&gt;
==Adding A Password Protected Folder To Your Web Space==&lt;br /&gt;
&lt;br /&gt;
1) Create the directory you want to password protect or &#039;&#039;&#039;cd&#039;&#039;&#039; into the directory you want to password protect&lt;br /&gt;
&lt;br /&gt;
2) Create a file called &#039;&#039;.htaccess&#039;&#039; (&#039;&#039;&#039;vi .htaccess&#039;&#039;&#039;) in the directory you wish to password protect.&lt;br /&gt;
&lt;br /&gt;
3) In the file you just created type the following lines&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthUserFile &#039;&#039;/your/directory/here/&#039;&#039;.htpasswd&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthName &amp;quot;Secure Document&amp;quot;&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthType Basic&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;require user username&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For example, if you were going to protect the &#039;&#039;&#039;/fs/www-users/username/private&#039;&#039;&#039; directory and you want the required name to be &#039;&#039;&#039;class239&#039;&#039;&#039;, then your file would look like this:&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthUserFile /fs/www-users/username/private/.htpasswd&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthName &amp;quot;Secure Document&amp;quot;&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;AuthType Basic&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&#039;&#039;&#039;require user class239&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
4) Create a file called &#039;&#039;.htpasswd&#039;&#039; in the same directory as &#039;&#039;.htaccess&#039;&#039;. You create this file by typing in &#039;&#039;&#039;htpasswd -c .htpasswd &#039;&#039;username&#039;&#039;&#039;&#039;&#039; in the directory area to be protected.&lt;br /&gt;
&lt;br /&gt;
In the example above, the username is &#039;&#039;&#039;class239&#039;&#039;&#039; so you would type &#039;&#039;&#039;htpasswd -c .htpasswd class239&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
You will be prompted to enter the password you want. The &#039;&#039;.htpasswd&#039;&#039; file will be created in the current directory and will contain an encrypted version of the password.&lt;br /&gt;
&lt;br /&gt;
To later change the username, edit the &#039;&#039;.htaccess&#039;&#039; file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=MPATH&amp;diff=5989</id>
		<title>MPATH</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=MPATH&amp;diff=5989"/>
		<updated>2014-06-05T19:21:57Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Redirected page to EnvironmentalVariables&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT: [[EnvironmentalVariables]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Intranet&amp;diff=5987</id>
		<title>Intranet</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Intranet&amp;diff=5987"/>
		<updated>2014-06-05T14:51:52Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed references to Web SSH client&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Remote Access==&lt;br /&gt;
* [https://franklin.pc.umiacs.umd.edu/exchange Exchange Webmail] - For Exchange Server users.  &amp;lt;tt&amp;gt;Please enter &amp;quot;pc\username&amp;quot; as your username and your password when prompted.&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [https://webmail.umiacs.umd.edu/imapmail/src/login.php IMAP Webmail] - For IMAP and POP3 users on umiacs-mail.&lt;br /&gt;
&lt;br /&gt;
==Account Management==&lt;br /&gt;
&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/intranet/accountRequest Openlab Account] - New accounts, approve requests, etc.&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/directorysearch Search the Directory] - Search for e-mail addresses, telephone numbers, and room numbers of UMIACS employees.&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/chinfo Directory Update] - Update your UMIACS directory info and change e-mail forwarding options.&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/%7Ewebevent/cgi-bin/webevent.cgi Events Calendar] - Online calendars for UMIACS events and seminars series.&lt;br /&gt;
 &lt;br /&gt;
* [[Main_Page|Technical Reference]] - How-to&#039;s and FAQ&#039;s regarding UMIACS&#039;s computing facilities&lt;br /&gt;
	&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/intranet/equipmentReservation Equipment Reservation] - Reserve laptops and other equipment ahead of time.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShell&amp;diff=5986</id>
		<title>SecureShell</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShell&amp;diff=5986"/>
		<updated>2014-06-05T14:43:50Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed references to Web SFTP applet&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Secure Shell (or [http://en.wikipedia.org/wiki/Secure_Shell SSH]) is a network protocol allowing two computers to exchange data securely over an insecure network.  By default, use of SSH brings the user to a terminal, but the protocol can be used for other types of data transfer such as [[SFTP]] and [[SCP]].&lt;br /&gt;
&lt;br /&gt;
==Connecting to an SSH Server==&lt;br /&gt;
Under Linux and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].&lt;br /&gt;
 # ssh bkirz@openlab.umiacs.umd.edu&lt;br /&gt;
This will give you access to a terminal on any one of the [[OpenLAB]] servers.  Note that by default you will not have access to applications that require X11 to run.&lt;br /&gt;
&lt;br /&gt;
All UMIACS Windows hosts are installed with SSH Secure Shell Client. Alternatively, users can install these software on their personal machines:&lt;br /&gt;
&lt;br /&gt;
* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]&lt;br /&gt;
* [http://ttssh2.sourceforge.jp/ ttssh2]&lt;br /&gt;
&lt;br /&gt;
Alternatively, all users can launch terminal sessions [[JuniperVPNTerminalSession| through the Juniper VPN web interface.]]&lt;br /&gt;
&lt;br /&gt;
==X11 Forwarding==&lt;br /&gt;
By default, SSH only gives the user shell access to a host.  Enabling X11 Forwarding allows users to run applications with Graphical User Interfaces.&lt;br /&gt;
&lt;br /&gt;
Under Linux and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.&lt;br /&gt;
 # ssh &#039;&#039;&#039;-Y&#039;&#039;&#039; bkirz@openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
If you do not have Cygwin, you will need to forward X through &lt;br /&gt;
[http://sourceforge.net/projects/vcxsrv/ VcXsrv] or&lt;br /&gt;
[http://www.straightrunning.com/XmingNotes/ Xming].&lt;br /&gt;
First, enable X forwarding on your secure ssh client. The option is under tunneling in the ssh client settings, shown below. This only has to be done once.&lt;br /&gt;
&lt;br /&gt;
[[Image:sshXForward.jpg]]&lt;br /&gt;
&lt;br /&gt;
Next, click save in the main ssh appication window to save this setting.&lt;br /&gt;
&lt;br /&gt;
After this has been done, every time you want to use X forwarding, you need to make sure VcXsrv or Xming has been started (it will appear in your task tray) through the start menu programs.&lt;br /&gt;
Now, you will be able to use Xwindow programs from your ssh client.&lt;br /&gt;
&lt;br /&gt;
==SSH Tunneling==&lt;br /&gt;
&lt;br /&gt;
You can tunnel one or more ports through an SSH connection such that your packets will look like they are coming from the host you are tunneling to.   This is helpful for services that you would be normally blocked by a firewall.&lt;br /&gt;
&lt;br /&gt;
Please see the [[SecureShellTunneling]] page for more information.&lt;br /&gt;
&lt;br /&gt;
==SSH Keys (and Passwordless SSH)==&lt;br /&gt;
&lt;br /&gt;
There are some situations where it is important to be able to ssh without entering a password.  This is mostly required when working in clusters.  This is done using ssh keys.  Instead of authenticating with a password, ssh can use a pre-defined set of encryption keys to establish an authorized connection. &lt;br /&gt;
To setup passwordless ssh, do the following.&lt;br /&gt;
&lt;br /&gt;
First, you will need to create a ssh [http://en.wikipedia.org/wiki/Key_pair key pair].  It is possible to use a password that you will need to enter at the beginning of your work session.  This is preferable as it is more secure but may cause problems for some clustered work, particularly our TORQUE/MAUI clusters.  If you simply hit &#039;&#039;&#039;[enter]&#039;&#039;&#039;, you will never be prompted for a password when ssh&#039;ing which can lead to security problems.&lt;br /&gt;
&lt;br /&gt;
# To create a &#039;&#039;&#039;&#039;&#039;passwordless&#039;&#039;&#039;&#039;&#039; key, type the following.  &#039;&#039;&#039;NOTE: This is &#039;&#039;REQUIRED&#039;&#039; for our [[ClusterGuide|TORQUE/MAUI]]-based clusters!&#039;&#039;&#039; &amp;lt;pre&amp;gt;  # ssh-keygen -N &amp;quot;&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
#: Alternatively, to create a &#039;&#039;&#039;&#039;&#039;passphrase-protected&#039;&#039;&#039;&#039;&#039; (more-secure) key, type the following.  Do not use this option if you plan to use any of our [[ClusterGuide|TORQUE/MAUI]]-based clusters.&amp;lt;pre&amp;gt;  # ssh-keygen&amp;lt;/pre&amp;gt;&lt;br /&gt;
#This will produce two files, &#039;&#039;&#039;id_rsa&#039;&#039;&#039; and &#039;&#039;&#039;id_rsa.pub&#039;&#039;&#039;, the private and public keys, respectively.  The default location will be ~/.ssh/. For the purposes of this tutorial we&#039;ll assume this default. Once you&#039;ve created the keys, you will need to put them into place as follows: &lt;br /&gt;
  # chmod 700 ~/.ssh &lt;br /&gt;
  # chmod 600 ~/.ssh/id_rsa &lt;br /&gt;
  # touch ~/.ssh/authorized_keys2&lt;br /&gt;
  # chmod 600 ~/.ssh/authorized_keys2&lt;br /&gt;
  # cat ~/.ssh/id_rsa.pub &amp;gt;&amp;gt; ~/.ssh/authorized_keys2&lt;br /&gt;
  # rm ~/.ssh/id_rsa.pub &lt;br /&gt;
&lt;br /&gt;
*It is &#039;&#039;&#039;very&#039;&#039;&#039; important that you keep your private key secure!  Ensure that it is chmod&#039;d to 600 and that you do not put it anywhere visible to other users!&lt;br /&gt;
*You must also make sure that no other users may write to your .ssh directory. This includes making sure that your home directory is not writable by group. Your home directory should be chmod&#039;d to 750 or 700 to make sure of this. If the group write bit is set, your ssh keys &#039;&#039;&#039;WILL NOT WORK&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you did not select a passphrase when you generated your keys, you can now ssh without a password.  If you did select a passphrase, you will need to activate the keys as follows:&lt;br /&gt;
&lt;br /&gt;
  # ssh-agent [SHELL]&lt;br /&gt;
  # ssh-add -t [TIME]&lt;br /&gt;
&lt;br /&gt;
In this case, &amp;quot;[SHELL]&amp;quot; is your preferred shell and &amp;quot;[TIME]&amp;quot; is the amount of time you&#039;d like the key to be active in seconds.  So, the following would start a bash shell with passwordless ssh active for 30 minutes:&lt;br /&gt;
&lt;br /&gt;
  # ssh-agent bash&lt;br /&gt;
  # ssh-add -t 1800&lt;br /&gt;
&lt;br /&gt;
You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.&lt;br /&gt;
&lt;br /&gt;
To disable this functionality, simply delete your private key file (&#039;&#039;&#039;~/.ssh/id_rsa&#039;&#039;&#039;) and remove the public key from your &#039;&#039;&#039;~/.ssh/authorized_keys2&#039;&#039;&#039; file.&lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
[http://www.openssh.org/ OpenSSH]&lt;br /&gt;
&lt;br /&gt;
[http://www.openssh.com/windows.html Windows Clients]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Intranet&amp;diff=5985</id>
		<title>Intranet</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Intranet&amp;diff=5985"/>
		<updated>2014-06-05T14:42:30Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed SFTP Applet link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Remote Access==&lt;br /&gt;
* [https://franklin.pc.umiacs.umd.edu/exchange Exchange Webmail] - For Exchange Server users.  &amp;lt;tt&amp;gt;Please enter &amp;quot;pc\username&amp;quot; as your username and your password when prompted.&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [https://webmail.umiacs.umd.edu/imapmail/src/login.php IMAP Webmail] - For IMAP and POP3 users on umiacs-mail.&lt;br /&gt;
&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/intranet/ssh SSH Web Client] - An SSH client right inside your browser, requires Java plug-in.&lt;br /&gt;
&lt;br /&gt;
==Account Management==&lt;br /&gt;
&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/intranet/accountRequest Openlab Account] - New accounts, approve requests, etc.&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/directorysearch Search the Directory] - Search for e-mail addresses, telephone numbers, and room numbers of UMIACS employees.&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/chinfo Directory Update] - Update your UMIACS directory info and change e-mail forwarding options.&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/%7Ewebevent/cgi-bin/webevent.cgi Events Calendar] - Online calendars for UMIACS events and seminars series.&lt;br /&gt;
 &lt;br /&gt;
* [[Main_Page|Technical Reference]] - How-to&#039;s and FAQ&#039;s regarding UMIACS&#039;s computing facilities&lt;br /&gt;
	&lt;br /&gt;
* [https://intranet.umiacs.umd.edu/intranet/equipmentReservation Equipment Reservation] - Reserve laptops and other equipment ahead of time.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5984</id>
		<title>SSHFileTransferProtocol</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5984"/>
		<updated>2014-06-05T14:41:12Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed references to Web SFTP applet&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems.  SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.&lt;br /&gt;
&lt;br /&gt;
==Connecting to an SFTP Server==&lt;br /&gt;
Under Under Red Hat Enterprise Linux, Ubuntu Linux, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].&lt;br /&gt;
&lt;br /&gt;
 wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
For UMIACS supported Windows hosts, a SFTP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SFTP access.  &lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
&lt;br /&gt;
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShellTunneling&amp;diff=5983</id>
		<title>SecureShellTunneling</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShellTunneling&amp;diff=5983"/>
		<updated>2014-06-04T21:17:50Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Linked RDP page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Port Forwarding==&lt;br /&gt;
&lt;br /&gt;
When you want to just forward a specific port locally to a remote port.   &lt;br /&gt;
&lt;br /&gt;
This example will create a local port 9999 that will be forwarded to the remote host webbserver.umiacs.umd.edu and its port 8000 through the host openlab.umiacs.umd.edu.&lt;br /&gt;
&lt;br /&gt;
* ssh -NfL 9999:webserver.umiacs.umd.edu:8000 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
This example will create a local port 13389 that will be forwarded to a remote host that is running a [[Remote Desktop |RDP]] client like Windows through the host openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
* ssh -L 13389:my-desktop.pc.umiacs.umd.edu:3389 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Socks Proxy==&lt;br /&gt;
&lt;br /&gt;
[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy.  Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command. &lt;br /&gt;
&lt;br /&gt;
* ssh -ND 7777 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy.  This can have performance implications.&lt;br /&gt;
&lt;br /&gt;
==Port Forwarding with PuTTY==&lt;br /&gt;
&lt;br /&gt;
Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under &amp;quot;Connection&amp;gt;SSH&amp;gt;Tunnels&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
[[Image:PuTTYWin7Tunnel.png]]&lt;br /&gt;
&lt;br /&gt;
This example will create a local port &#039;&#039;&#039;8889&#039;&#039;&#039; that is attached to the remote host &#039;&#039;&#039;clipsm301.umiacs.umd.edu&#039;&#039;&#039; on its port &#039;&#039;&#039;8000&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Socks Proxy with PuTTY==&lt;br /&gt;
&lt;br /&gt;
Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.&lt;br /&gt;
&lt;br /&gt;
In PuTTY under &amp;quot;Sessions&amp;quot; set the Host Name:&lt;br /&gt;
[[Image:Putty1.png]]&lt;br /&gt;
&lt;br /&gt;
Then under &amp;quot;Connection&amp;gt;SSH&amp;gt;Tunnels&amp;quot; enter a port number and set the type of forwarding to &amp;quot;Dynamic&amp;quot; and press add:&lt;br /&gt;
&lt;br /&gt;
[[Image:Putty2.png]]&lt;br /&gt;
&lt;br /&gt;
Click Open and log into the host.&lt;br /&gt;
As long as this PuTTY window is open and you are logged in, you can use the SOCKS proxy.&lt;br /&gt;
&lt;br /&gt;
Please note that when you configure proxy settings for a browser or your whole operating system, all the traffic for that browser or your OS will be sent through the proxy.  This can have performance implications.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShellTunneling&amp;diff=5981</id>
		<title>SecureShellTunneling</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShellTunneling&amp;diff=5981"/>
		<updated>2014-06-04T19:40:03Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed references to Windows versions XP and Vista, replacing with generic &amp;#039;Windows&amp;#039;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Port Forwarding==&lt;br /&gt;
&lt;br /&gt;
When you want to just forward a specific port locally to a remote port.   &lt;br /&gt;
&lt;br /&gt;
This example will create a local port 9999 that will be forwarded to the remote host webbserver.umiacs.umd.edu and its port 8000 through the host openlab.umiacs.umd.edu.&lt;br /&gt;
&lt;br /&gt;
* ssh -NfL 9999:webserver.umiacs.umd.edu:8000 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
This example will create a local port 13389 that will be forwarded to a remote host that is running a [[RDP]] client like Windows through the host openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
* ssh -L 13389:my-desktop.pc.umiacs.umd.edu:3389 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Socks Proxy==&lt;br /&gt;
&lt;br /&gt;
[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy.  Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command. &lt;br /&gt;
&lt;br /&gt;
* ssh -ND 7777 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy.  This can have performance implications.&lt;br /&gt;
&lt;br /&gt;
==Port Forwarding with PuTTY==&lt;br /&gt;
&lt;br /&gt;
Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under &amp;quot;Connection&amp;gt;SSH&amp;gt;Tunnels&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
[[Image:PuTTYWin7Tunnel.png]]&lt;br /&gt;
&lt;br /&gt;
This example will create a local port &#039;&#039;&#039;8889&#039;&#039;&#039; that is attached to the remote host &#039;&#039;&#039;clipsm301.umiacs.umd.edu&#039;&#039;&#039; on its port &#039;&#039;&#039;8000&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Socks Proxy with PuTTY==&lt;br /&gt;
&lt;br /&gt;
Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.&lt;br /&gt;
&lt;br /&gt;
In PuTTY under &amp;quot;Sessions&amp;quot; set the Host Name:&lt;br /&gt;
[[Image:Putty1.png]]&lt;br /&gt;
&lt;br /&gt;
Then under &amp;quot;Connection&amp;gt;SSH&amp;gt;Tunnels&amp;quot; enter a port number and set the type of forwarding to &amp;quot;Dynamic&amp;quot; and press add:&lt;br /&gt;
&lt;br /&gt;
[[Image:Putty2.png]]&lt;br /&gt;
&lt;br /&gt;
Click Open and log into the host.&lt;br /&gt;
As long as this PuTTY window is open and you are logged in, you can use the SOCKS proxy.&lt;br /&gt;
&lt;br /&gt;
Please note that when you configure proxy settings for a browser or your whole operating system, all the traffic for that browser or your OS will be sent through the proxy.  This can have performance implications.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:PuTTYWin7Tunnel.png&amp;diff=5968</id>
		<title>File:PuTTYWin7Tunnel.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:PuTTYWin7Tunnel.png&amp;diff=5968"/>
		<updated>2014-06-03T13:27:13Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Rleimens uploaded a new version of &amp;amp;quot;File:PuTTYWin7Tunnel.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Windows 7 PuTTY screenshot of Tunnel.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:PuTTYWin7Tunnel.png&amp;diff=5967</id>
		<title>File:PuTTYWin7Tunnel.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:PuTTYWin7Tunnel.png&amp;diff=5967"/>
		<updated>2014-06-03T13:22:58Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Rleimens uploaded a new version of &amp;amp;quot;File:PuTTYWin7Tunnel.png&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Windows 7 PuTTY screenshot of Tunnel.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShellTunneling&amp;diff=5966</id>
		<title>SecureShellTunneling</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShellTunneling&amp;diff=5966"/>
		<updated>2014-06-03T13:18:06Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Update screenshot for win7&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Port Forwarding==&lt;br /&gt;
&lt;br /&gt;
When you want to just forward a specific port locally to a remote port.   &lt;br /&gt;
&lt;br /&gt;
This example will create a local port 9999 that will be forwarded to the remote host webbserver.umiacs.umd.edu and its port 8000 through the host openlab.umiacs.umd.edu.&lt;br /&gt;
&lt;br /&gt;
* ssh -NfL 9999:webserver.umiacs.umd.edu:8000 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
This example will create a local port 13389 that will be forwarded to a remote host that is running a [[RDP]] client like Windows XP or Windows Vista through the host openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
* ssh -L 13389:my-desktop.pc.umiacs.umd.edu:3389 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Socks Proxy==&lt;br /&gt;
&lt;br /&gt;
[[SSH]] can also tunnel all traffic coming into a certain port through a SOCKS v5 proxy.  Many browsers and some operating systems can be setup to then connect to this proxy to allow them again to look like they are coming from the host name you specify in your [[SSH]] command. &lt;br /&gt;
&lt;br /&gt;
* ssh -ND 7777 openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
Please note: when you configure proxy settings for a browser (or your whole operating system) all the traffic for that browser (or the OS) will be sent through the proxy.  This can have performance implications.&lt;br /&gt;
&lt;br /&gt;
==Port Forwarding with PuTTY==&lt;br /&gt;
&lt;br /&gt;
Windows users can achieve the same types of tunnels using PuTTY or a similar SSH client. In PuTTY, the port forwarding configuration dialogue can be found under &amp;quot;Connection&amp;gt;SSH&amp;gt;Tunnels&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
[[Image:PuTTYWin7Tunnel.png]]&lt;br /&gt;
&lt;br /&gt;
This example will create a local port &#039;&#039;&#039;8889&#039;&#039;&#039; that is attached to the remote host &#039;&#039;&#039;clipsm301.umiacs.umd.edu&#039;&#039;&#039; on its port &#039;&#039;&#039;8000&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Socks Proxy with PuTTY==&lt;br /&gt;
&lt;br /&gt;
Windows users can tunnel traffic coming into a certain port through a SOCKS v5 proxy by using PuTTY or a similar SSH client. Many browsers and some operating systems can be setup to connect to this proxy to allow them to look like they are coming from the host name you specify.&lt;br /&gt;
&lt;br /&gt;
In PuTTY under &amp;quot;Sessions&amp;quot; set the Host Name:&lt;br /&gt;
[[Image:Putty1.png]]&lt;br /&gt;
&lt;br /&gt;
Then under &amp;quot;Connection&amp;gt;SSH&amp;gt;Tunnels&amp;quot; enter a port number and set the type of forwarding to &amp;quot;Dynamic&amp;quot; and press add:&lt;br /&gt;
&lt;br /&gt;
[[Image:Putty2.png]]&lt;br /&gt;
&lt;br /&gt;
Click Open and log into the host.&lt;br /&gt;
As long as this PuTTY window is open and you are logged in, you can use the SOCKS proxy.&lt;br /&gt;
&lt;br /&gt;
Please note that when you configure proxy settings for a browser or your whole operating system, all the traffic for that browser or your OS will be sent through the proxy.  This can have performance implications.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:PuTTYWin7Tunnel.png&amp;diff=5965</id>
		<title>File:PuTTYWin7Tunnel.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=File:PuTTYWin7Tunnel.png&amp;diff=5965"/>
		<updated>2014-06-03T13:17:29Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Windows 7 PuTTY screenshot of Tunnel.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Windows 7 PuTTY screenshot of Tunnel.&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureCopy&amp;diff=5959</id>
		<title>SecureCopy</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureCopy&amp;diff=5959"/>
		<updated>2014-06-03T12:46:09Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed references to explicit RHEL versions&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Secure Copy (or [http://en.wikipedia.org/wiki/Secure_Shell SCP]) is a way of copying data between two computers using [[SSH]].&lt;br /&gt;
&lt;br /&gt;
==Using SCP==&lt;br /&gt;
The following commands work under Red Hat Enterprise Linux, Ubuntu Linux, and Mac OS X. &lt;br /&gt;
&lt;br /&gt;
This command, when run from a terminal, will copy the file &amp;quot;source_file.txt&amp;quot; from the local machine to a folder inside the user&#039;s OpenLab account and give it the name &amp;quot;target_file.txt&amp;quot;.&lt;br /&gt;
 wing:~ Ben$ scp source_file.txt bkirz@openlab.umiacs.umd.edu:target_file.txt&lt;br /&gt;
&lt;br /&gt;
This command, when run from a terminal, will copy the file &amp;quot;source_file.txt&amp;quot; from the user&#039;s OpenLab account into the current local directory and give it the name &amp;quot;target_file.txt&amp;quot;.&lt;br /&gt;
 wing:~ Ben$ scp bkirz@openlab.umiacs.umd.edu:source_file.txt target_file.txt&lt;br /&gt;
&lt;br /&gt;
Note how the syntax of scp is very similar to that of the UNIX command cp with the addition of a hostname and username.&lt;br /&gt;
&lt;br /&gt;
For UMIACS supported Windows hosts, a SCP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SCP access. &lt;br /&gt;
&lt;br /&gt;
Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.&lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
* [http://www.openssh.org/ OpenSSH]&lt;br /&gt;
* [http://winscp.net WinSCP]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5958</id>
		<title>SSHFileTransferProtocol</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5958"/>
		<updated>2014-06-03T12:45:29Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed references to explicit RHEL versions&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems.  SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.&lt;br /&gt;
&lt;br /&gt;
==Connecting to an SFTP Server==&lt;br /&gt;
Under Under Red Hat Enterprise Linux, Ubuntu Linux, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].&lt;br /&gt;
&lt;br /&gt;
 wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
For UMIACS supported Windows hosts, a SFTP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SFTP access.  &lt;br /&gt;
&lt;br /&gt;
Alternatively, users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/sftp/ here] without installing any additional software.&lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
&lt;br /&gt;
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureCopy&amp;diff=5957</id>
		<title>SecureCopy</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureCopy&amp;diff=5957"/>
		<updated>2014-06-02T20:50:59Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Updated to remove Win7 hosts&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Secure Copy (or [http://en.wikipedia.org/wiki/Secure_Shell SCP]) is a way of copying data between two computers using [[SSH]].&lt;br /&gt;
&lt;br /&gt;
==Using SCP==&lt;br /&gt;
The following commands work under RedHat Linux 3, 4, 5, 6, and Mac OS X.&lt;br /&gt;
&lt;br /&gt;
This command, when run from a terminal, will copy the file &amp;quot;source_file.txt&amp;quot; from the local machine to a folder inside the user&#039;s OpenLab account and give it the name &amp;quot;target_file.txt&amp;quot;.&lt;br /&gt;
 wing:~ Ben$ scp source_file.txt bkirz@openlab.umiacs.umd.edu:target_file.txt&lt;br /&gt;
&lt;br /&gt;
This command, when run from a terminal, will copy the file &amp;quot;source_file.txt&amp;quot; from the user&#039;s OpenLab account into the current local directory and give it the name &amp;quot;target_file.txt&amp;quot;.&lt;br /&gt;
 wing:~ Ben$ scp bkirz@openlab.umiacs.umd.edu:source_file.txt target_file.txt&lt;br /&gt;
&lt;br /&gt;
Note how the syntax of scp is very similar to that of the UNIX command cp with the addition of a hostname and username.&lt;br /&gt;
&lt;br /&gt;
For UMIACS supported Windows hosts, a SCP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SCP access. &lt;br /&gt;
&lt;br /&gt;
Alternatively, all users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/ssh/ here] without installing any additional software.&lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
* [http://www.openssh.org/ OpenSSH]&lt;br /&gt;
* [http://winscp.net WinSCP]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5956</id>
		<title>SSHFileTransferProtocol</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5956"/>
		<updated>2014-06-02T20:49:40Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems.  SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.&lt;br /&gt;
&lt;br /&gt;
==Connecting to an SFTP Server==&lt;br /&gt;
Under RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].&lt;br /&gt;
&lt;br /&gt;
 wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
For UMIACS supported Windows hosts, a SFTP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SFTP access.  &lt;br /&gt;
&lt;br /&gt;
Alternatively, users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/sftp/ here] without installing any additional software.&lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
&lt;br /&gt;
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5955</id>
		<title>SSHFileTransferProtocol</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5955"/>
		<updated>2014-06-02T20:49:19Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems.  SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.&lt;br /&gt;
&lt;br /&gt;
==Connecting to an SFTP Server==&lt;br /&gt;
Under RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].&lt;br /&gt;
&lt;br /&gt;
 wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
For UMIACS supported Windows hosts, an SFTP client is already installed. For other hosts, you can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SFTP access.  &lt;br /&gt;
&lt;br /&gt;
Alternatively, users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/sftp/ here] without installing any additional software.&lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
&lt;br /&gt;
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&amp;diff=5954</id>
		<title>Matlab</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&amp;diff=5954"/>
		<updated>2014-06-02T20:42:04Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS has [[Matlab]] licenses that cover Linux, Windows and Mac.  To access them you have to be using a university owned computer. If you would like to run Matlab on a machine that is not University-owned, you can check the pricing through OIT/SLIC [http://www.oit.umd.edu/units/slic/products/mathworks/matlab.html here]&lt;br /&gt;
&lt;br /&gt;
==Linux==&lt;br /&gt;
Below are the different locations of Matlab across our supported linux workstations and servers.  The one in bold is our latest version. RHEL5 is no longer supported as of R2013b, and 32-bit Linux distributions are no longer supported as of R2012b. For more information, please see [http://www.mathworks.com/support/sysreq/roadmap.html this page].&lt;br /&gt;
&lt;br /&gt;
===RHEL5===&lt;br /&gt;
* /opt/matlab-r2007b&lt;br /&gt;
* /opt/matlab-r2008a&lt;br /&gt;
* /opt/matlab-r2008b&lt;br /&gt;
* /opt/matlab-r2009b&lt;br /&gt;
* /opt/matlab-r2010a&lt;br /&gt;
* /opt/matlab-r2010b&lt;br /&gt;
* /opt/matlab-r2011a&lt;br /&gt;
* /opt/matlab-r2011b&lt;br /&gt;
* /opt/matlab-r2012a&lt;br /&gt;
* /opt/matlab-r2012b&lt;br /&gt;
* &#039;&#039;&#039;/opt/matlab-r2013a&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
===RHEL6/Ubuntu===&lt;br /&gt;
&lt;br /&gt;
* /opt/common/matlab-r2007b&lt;br /&gt;
* /opt/common/matlab-r2008a&lt;br /&gt;
* /opt/common/matlab-r2008b&lt;br /&gt;
* /opt/common/matlab-r2009b&lt;br /&gt;
* /opt/common/matlab-r2010a&lt;br /&gt;
* /opt/common/matlab-r2010b&lt;br /&gt;
* /opt/common/matlab-r2011a&lt;br /&gt;
* /opt/common/matlab-r2011b&lt;br /&gt;
* /opt/common/matlab-r2012a&lt;br /&gt;
* /opt/common/matlab-r2012b&lt;br /&gt;
* /opt/common/matlab-r2013a&lt;br /&gt;
* /opt/common/matlab-r2013b&lt;br /&gt;
* &#039;&#039;&#039;/opt/common/matlab-r2014a&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Windows==&lt;br /&gt;
Below are the different locations of Matlab available for university-owned machines running Windows 7. The one in bold is the latest version we have available:&lt;br /&gt;
&lt;br /&gt;
* Matlab r2007a&lt;br /&gt;
* Matlab r2007b&lt;br /&gt;
* Matlab r2008a&lt;br /&gt;
* Matlab r2008b&lt;br /&gt;
* Matlab r2009a&lt;br /&gt;
* Matlab r2009b&lt;br /&gt;
* Matlab r2010a&lt;br /&gt;
* Matlab r2010b&lt;br /&gt;
* Matlab r2011a&lt;br /&gt;
* Matlab r2011b&lt;br /&gt;
* Matlab r2012a&lt;br /&gt;
* Matlab r2012b&lt;br /&gt;
* Matlab r2013a&lt;br /&gt;
* &#039;&#039;&#039;Matlab r2013b&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==OSX==&lt;br /&gt;
Below are the different locations of Matlab available for university-owned machines running OSX. We expect that all versions should run on OSX 10.6 and newer. The one in bold is the latest version we have available:&lt;br /&gt;
&lt;br /&gt;
* Matlab r2008a&lt;br /&gt;
* Matlab r2008b&lt;br /&gt;
* Matlab r2009b&lt;br /&gt;
* Matlab r2010a&lt;br /&gt;
* Matlab r2010b&lt;br /&gt;
* Matlab r2011b&lt;br /&gt;
* Matlab r2012a&lt;br /&gt;
* Matlab r2012b&lt;br /&gt;
* Matlab r2013a (OSX 10.7+)&lt;br /&gt;
* &#039;&#039;&#039;Matlab r2013b&#039;&#039;&#039; (OSX 10.7+)&lt;br /&gt;
&lt;br /&gt;
==License Troubleshooting==&lt;br /&gt;
&lt;br /&gt;
Campus has a limited number of seats for Matlab itself, as well as the various toolboxes. When calling functions in a toolbox, Matlab will automatically check out a license, making it temporarily unavailable to other users. Sometimes it&#039;s necessary to check the number of toolbox licenses available.&lt;br /&gt;
&lt;br /&gt;
===Windows License Troubleshooting===&lt;br /&gt;
On Windows machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. &amp;quot;win64&amp;quot; needs to adjusted to &amp;quot;win32&amp;quot; on a 32-bit installation:&lt;br /&gt;
 $MATLAB_PATH\bin\win64\lmutil lmstat -c &amp;quot;$MATLAB_PATH\licenses\network.lic&amp;quot; -f $TOOLBOX_SHORTNAME&lt;br /&gt;
&lt;br /&gt;
As an example, here is how to query Matlab r2009b on a 64-bit Windows XP host for the Aerospace Blockset Toolbox: &lt;br /&gt;
 C:\Program Files\matlab7.9r2009b\bin\win64\lmutil.exe lmstat -c &amp;quot;C:\Program Files\matlab7.9r2009b\licenses\network.lic&amp;quot; -f Aerospace_Blockset&lt;br /&gt;
&lt;br /&gt;
===Unix License Troubleshooting===&lt;br /&gt;
On Unix machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. &amp;quot;glnxa64&amp;quot; needs to adjusted to &amp;quot;glnx86&amp;quot; on a 32-bit installation::&lt;br /&gt;
 $MATLAB_PATH/bin/glnxa64/lmutil lmstat -c $MATLAB_PATH/licenses/network.lic -f $TOOLBOX_SHORTNAME&lt;br /&gt;
&lt;br /&gt;
As an example, here is how to query Matlab r2010b on our 64-bit RHEL5 hosts for the Parallel Computing Toolbox:&lt;br /&gt;
 /opt/matlab-r2010b/bin/glnxa64/lmutil lmstat -c /opt/matlab-r2010b/licenses/network.lic -f Distrib_Computing_Toolbox&lt;br /&gt;
&lt;br /&gt;
===Toolbox Shortnames===&lt;br /&gt;
The toolbox names themselves don&#039;t always work with this command; Rather, Matlab has a set of shortnames which can be passed to the lmstat command. The following are all the valid shortnames:&lt;br /&gt;
&lt;br /&gt;
 Aerospace_Blockset   &lt;br /&gt;
 Aerospace_Toolbox  &lt;br /&gt;
 Bioinformatics_Toolbox  &lt;br /&gt;
 Communication_Blocks  &lt;br /&gt;
 Communication_Toolbox  &lt;br /&gt;
 Compiler  &lt;br /&gt;
 Control_Toolbox  &lt;br /&gt;
 Curve_Fitting_Toolbox  &lt;br /&gt;
 Data_Acq_Toolbox  &lt;br /&gt;
 Database_Toolbox  &lt;br /&gt;
 Datafeed_Toolbox  &lt;br /&gt;
 Distrib_Computing_Toolbox  &lt;br /&gt;
 Econometrics_Toolbox  &lt;br /&gt;
 Excel_Link  &lt;br /&gt;
 Fin_Derivatives_Toolbox  &lt;br /&gt;
 Financial_Toolbox  &lt;br /&gt;
 Fixed_Income_Toolbox  &lt;br /&gt;
 Fixed_Point_Toolbox  &lt;br /&gt;
 GADS_Toolbox  &lt;br /&gt;
 Identification_Toolbox  &lt;br /&gt;
 Image_Acquisition_Toolbox  &lt;br /&gt;
 Image_Toolbox  &lt;br /&gt;
 Instr_Control_Toolbox  &lt;br /&gt;
 MAP_Toolbox  &lt;br /&gt;
 MATLAB  &lt;br /&gt;
 MATLAB_Builder_for_Java  &lt;br /&gt;
 MATLAB_Coder  &lt;br /&gt;
 MATLAB_Excel_Builder  &lt;br /&gt;
 MATLAB_Report_Gen  &lt;br /&gt;
 MPC_Toolbox  &lt;br /&gt;
 Neural_Network_Toolbox  &lt;br /&gt;
 Optimization_Toolbox  &lt;br /&gt;
 PDE_Toolbox  &lt;br /&gt;
 Real-Time_Workshop  &lt;br /&gt;
 Robust_Toolbox  &lt;br /&gt;
 Signal_Blocks  &lt;br /&gt;
 Signal_Toolbox  &lt;br /&gt;
 SimMechanics  &lt;br /&gt;
 Simscape  &lt;br /&gt;
 SIMULINK  &lt;br /&gt;
 Simulink_Control_Design  &lt;br /&gt;
 Stateflow  &lt;br /&gt;
 Stateflow_Coder  &lt;br /&gt;
 Statistics_Toolbox  &lt;br /&gt;
 Symbolic_Toolbox  &lt;br /&gt;
 Video_and_Image_Blockset  &lt;br /&gt;
 Virtual_Reality_Toolbox  &lt;br /&gt;
 Wavelet_Toolbox&lt;br /&gt;
&lt;br /&gt;
If you are having problems, feel free to contact [[HelpDesk | UMIACS Staff]], however please note that the Matlab license servers are hosted by campus&#039; Division of Information Technology.&lt;br /&gt;
&lt;br /&gt;
==Matlab Customizations==&lt;br /&gt;
&lt;br /&gt;
You can tweak your Matlab experience using a file &amp;quot;startup.m&amp;quot;. If this file is present in the current working directory where you launch Matlab, it will be executed. You can perform a variety of tasks using this file. These include (but are not limited to) customizing the window environment, setting variables for later use, and enabling use of 3rd party toolboxes. Alternatively, you can use the userpath env variable to set a path other than the current working directory for startup and 3rd party toolbox locations. Please see the following links for more information:&lt;br /&gt;
&lt;br /&gt;
* [http://www.mathworks.com/help/matlab/ref/matlabrc.html Mathworks: Startup.m]&lt;br /&gt;
* [http://www.mathworks.com/help/matlab/matlab_env/startup-folder-for-the-matlab-program.html#bs6j57e-5 Mathworks: Userpath function]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&amp;diff=5953</id>
		<title>Matlab</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&amp;diff=5953"/>
		<updated>2014-06-02T20:37:50Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Remove WinXP References&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS has [[Matlab]] licenses that cover Linux, Windows and Mac.  To access them you have to be using a university owned computer. If you would like to run Matlab on a machine that is not University-owned, you can check the pricing through OIT/SLIC [http://www.oit.umd.edu/units/slic/products/mathworks/matlab.html here]&lt;br /&gt;
&lt;br /&gt;
==Linux==&lt;br /&gt;
Below are the different locations of Matlab across our supported linux workstations and servers.  The one in bold is our latest version. RHEL5 is no longer supported as of R2013b, and 32-bit Linux distributions are no longer supported as of R2012b. For more information, please see [http://www.mathworks.com/support/sysreq/roadmap.html this page].&lt;br /&gt;
&lt;br /&gt;
===RHEL5===&lt;br /&gt;
* /opt/matlab-r2007b&lt;br /&gt;
* /opt/matlab-r2008a&lt;br /&gt;
* /opt/matlab-r2008b&lt;br /&gt;
* /opt/matlab-r2009b&lt;br /&gt;
* /opt/matlab-r2010a&lt;br /&gt;
* /opt/matlab-r2010b&lt;br /&gt;
* /opt/matlab-r2011a&lt;br /&gt;
* /opt/matlab-r2011b&lt;br /&gt;
* /opt/matlab-r2012a&lt;br /&gt;
* /opt/matlab-r2012b&lt;br /&gt;
* &#039;&#039;&#039;/opt/matlab-r2013a&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
===RHEL6/Ubuntu===&lt;br /&gt;
&lt;br /&gt;
* /opt/common/matlab-r2007b&lt;br /&gt;
* /opt/common/matlab-r2008a&lt;br /&gt;
* /opt/common/matlab-r2008b&lt;br /&gt;
* /opt/common/matlab-r2009b&lt;br /&gt;
* /opt/common/matlab-r2010a&lt;br /&gt;
* /opt/common/matlab-r2010b&lt;br /&gt;
* /opt/common/matlab-r2011a&lt;br /&gt;
* /opt/common/matlab-r2011b&lt;br /&gt;
* /opt/common/matlab-r2012a&lt;br /&gt;
* /opt/common/matlab-r2012b&lt;br /&gt;
* /opt/common/matlab-r2013a&lt;br /&gt;
* /opt/common/matlab-r2013b&lt;br /&gt;
* &#039;&#039;&#039;/opt/common/matlab-r2014a&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Windows==&lt;br /&gt;
Below are the different locations of Matlab available for university-owned machines running Windows 7. The one in bold is the latest version we have available:&lt;br /&gt;
&lt;br /&gt;
* Matlab r2007a&lt;br /&gt;
* Matlab r2007b&lt;br /&gt;
* Matlab r2008a&lt;br /&gt;
* Matlab r2008b&lt;br /&gt;
* Matlab r2009a&lt;br /&gt;
* Matlab r2009b&lt;br /&gt;
* Matlab r2010a&lt;br /&gt;
* Matlab r2010b&lt;br /&gt;
* Matlab r2011a&lt;br /&gt;
* Matlab r2011b&lt;br /&gt;
* Matlab r2012a&lt;br /&gt;
* Matlab r2012b&lt;br /&gt;
* Matlab r2013a&lt;br /&gt;
* &#039;&#039;&#039;Matlab r2013b&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==OSX==&lt;br /&gt;
Below are the different locations of Matlab available for university-owned machines running OSX. We expect that all versions should run on OSX 10.6 and newer. The one in bold is the latest version we have available:&lt;br /&gt;
&lt;br /&gt;
* Matlab r2008a&lt;br /&gt;
* Matlab r2008b&lt;br /&gt;
* Matlab r2009b&lt;br /&gt;
* Matlab r2010a&lt;br /&gt;
* Matlab r2010b&lt;br /&gt;
* Matlab r2011b&lt;br /&gt;
* Matlab r2012a&lt;br /&gt;
* Matlab r2012b&lt;br /&gt;
* Matlab r2013a (OSX 10.7+)&lt;br /&gt;
* &#039;&#039;&#039;Matlab r2013b&#039;&#039;&#039; (OSX 10.7+)&lt;br /&gt;
&lt;br /&gt;
==License Troubleshooting==&lt;br /&gt;
&lt;br /&gt;
Campus has a limited number of seats for Matlab itself, as well as the various toolboxes. When calling functions in a toolbox, Matlab will automatically check out a license, making it temporarily unavailable to other users. Sometimes it&#039;s necessary to check the number of toolbox licenses available.&lt;br /&gt;
&lt;br /&gt;
===Windows License Troubleshooting===&lt;br /&gt;
On Windows machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. &amp;quot;win64&amp;quot; needs to adjusted to &amp;quot;win32&amp;quot; on a 32-bit installation:&lt;br /&gt;
 $MATLAB_PATH\bin\win64\lmutil lmstat -c &amp;quot;$MATLAB_PATH\licenses\network.lic&amp;quot; -f $TOOLBOX_SHORTNAME&lt;br /&gt;
&lt;br /&gt;
As an example, here is how to query Matlab r2009b on a 64-bit Windows 7 host for the Aerospace Blockset Toolbox: &lt;br /&gt;
 C:\Program Files\matlab7.9r2009b\bin\win64\lmutil.exe lmstat -c &amp;quot;C:\Program Files\matlab7.9r2009b\licenses\network.lic&amp;quot; -f Aerospace_Blockset&lt;br /&gt;
&lt;br /&gt;
===Unix License Troubleshooting===&lt;br /&gt;
On Unix machines, the necessary command is as follows. Please note that you may need to adjust the path to reflect the available Matlab versions and the installation path. Additionally, this assumes that you are using a 64-bit version. &amp;quot;glnxa64&amp;quot; needs to adjusted to &amp;quot;glnx86&amp;quot; on a 32-bit installation::&lt;br /&gt;
 $MATLAB_PATH/bin/glnxa64/lmutil lmstat -c $MATLAB_PATH/licenses/network.lic -f $TOOLBOX_SHORTNAME&lt;br /&gt;
&lt;br /&gt;
As an example, here is how to query Matlab r2010b on our 64-bit RHEL5 hosts for the Parallel Computing Toolbox:&lt;br /&gt;
 /opt/matlab-r2010b/bin/glnxa64/lmutil lmstat -c /opt/matlab-r2010b/licenses/network.lic -f Distrib_Computing_Toolbox&lt;br /&gt;
&lt;br /&gt;
===Toolbox Shortnames===&lt;br /&gt;
The toolbox names themselves don&#039;t always work with this command; Rather, Matlab has a set of shortnames which can be passed to the lmstat command. The following are all the valid shortnames:&lt;br /&gt;
&lt;br /&gt;
 Aerospace_Blockset   &lt;br /&gt;
 Aerospace_Toolbox  &lt;br /&gt;
 Bioinformatics_Toolbox  &lt;br /&gt;
 Communication_Blocks  &lt;br /&gt;
 Communication_Toolbox  &lt;br /&gt;
 Compiler  &lt;br /&gt;
 Control_Toolbox  &lt;br /&gt;
 Curve_Fitting_Toolbox  &lt;br /&gt;
 Data_Acq_Toolbox  &lt;br /&gt;
 Database_Toolbox  &lt;br /&gt;
 Datafeed_Toolbox  &lt;br /&gt;
 Distrib_Computing_Toolbox  &lt;br /&gt;
 Econometrics_Toolbox  &lt;br /&gt;
 Excel_Link  &lt;br /&gt;
 Fin_Derivatives_Toolbox  &lt;br /&gt;
 Financial_Toolbox  &lt;br /&gt;
 Fixed_Income_Toolbox  &lt;br /&gt;
 Fixed_Point_Toolbox  &lt;br /&gt;
 GADS_Toolbox  &lt;br /&gt;
 Identification_Toolbox  &lt;br /&gt;
 Image_Acquisition_Toolbox  &lt;br /&gt;
 Image_Toolbox  &lt;br /&gt;
 Instr_Control_Toolbox  &lt;br /&gt;
 MAP_Toolbox  &lt;br /&gt;
 MATLAB  &lt;br /&gt;
 MATLAB_Builder_for_Java  &lt;br /&gt;
 MATLAB_Coder  &lt;br /&gt;
 MATLAB_Excel_Builder  &lt;br /&gt;
 MATLAB_Report_Gen  &lt;br /&gt;
 MPC_Toolbox  &lt;br /&gt;
 Neural_Network_Toolbox  &lt;br /&gt;
 Optimization_Toolbox  &lt;br /&gt;
 PDE_Toolbox  &lt;br /&gt;
 Real-Time_Workshop  &lt;br /&gt;
 Robust_Toolbox  &lt;br /&gt;
 Signal_Blocks  &lt;br /&gt;
 Signal_Toolbox  &lt;br /&gt;
 SimMechanics  &lt;br /&gt;
 Simscape  &lt;br /&gt;
 SIMULINK  &lt;br /&gt;
 Simulink_Control_Design  &lt;br /&gt;
 Stateflow  &lt;br /&gt;
 Stateflow_Coder  &lt;br /&gt;
 Statistics_Toolbox  &lt;br /&gt;
 Symbolic_Toolbox  &lt;br /&gt;
 Video_and_Image_Blockset  &lt;br /&gt;
 Virtual_Reality_Toolbox  &lt;br /&gt;
 Wavelet_Toolbox&lt;br /&gt;
&lt;br /&gt;
If you are having problems, feel free to contact [[HelpDesk | UMIACS Staff]], however please note that the Matlab license servers are hosted by campus&#039; Division of Information Technology.&lt;br /&gt;
&lt;br /&gt;
==Matlab Customizations==&lt;br /&gt;
&lt;br /&gt;
You can tweak your Matlab experience using a file &amp;quot;startup.m&amp;quot;. If this file is present in the current working directory where you launch Matlab, it will be executed. You can perform a variety of tasks using this file. These include (but are not limited to) customizing the window environment, setting variables for later use, and enabling use of 3rd party toolboxes. Alternatively, you can use the userpath env variable to set a path other than the current working directory for startup and 3rd party toolbox locations. Please see the following links for more information:&lt;br /&gt;
&lt;br /&gt;
* [http://www.mathworks.com/help/matlab/ref/matlabrc.html Mathworks: Startup.m]&lt;br /&gt;
* [http://www.mathworks.com/help/matlab/matlab_env/startup-folder-for-the-matlab-program.html#bs6j57e-5 Mathworks: Userpath function]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5952</id>
		<title>SSHFileTransferProtocol</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&amp;diff=5952"/>
		<updated>2014-06-02T20:29:55Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Remove WinXP Support info&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;SSH File Transfer Protocol ([http://en.wikipedia.org/wiki/SSH_file_transfer_protocol SFTP]) is a network protocol used to securely transfer and manage files on remote systems.  SFTP is layered on top of the [[SSH]] protocol, and is preferred over [[FTP]] as a method of remote file transfer.&lt;br /&gt;
&lt;br /&gt;
==Connecting to an SFTP Server==&lt;br /&gt;
Under RedHat Linux 3, 4, and 5, and Mac OS X, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].&lt;br /&gt;
&lt;br /&gt;
 wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
For UMIACS supported Windows hosts, an SFTP client is already installed. Other hosts can download and install [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], which will enable SSH and SFTP access.&lt;br /&gt;
&lt;br /&gt;
Alternatively, users can use the UMIACS Intranet SFTP Web Applet located [https://intranet.umiacs.umd.edu/sftp/ here] without installing any additional software.&lt;br /&gt;
&lt;br /&gt;
==Further Information==&lt;br /&gt;
&lt;br /&gt;
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=OSSupport&amp;diff=5951</id>
		<title>OSSupport</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=OSSupport&amp;diff=5951"/>
		<updated>2014-06-02T18:36:47Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Remove WinXP reference&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UMIACS Supports the following Operating Systems&lt;br /&gt;
&lt;br /&gt;
==Linux==&lt;br /&gt;
&lt;br /&gt;
General [[LinuxFAQ]]&lt;br /&gt;
&lt;br /&gt;
* [[RHEL4|RedHat Enterprise Linux 4]]&lt;br /&gt;
* [[RHEL5|RedHat Enterprise Linux 5]]&lt;br /&gt;
* [[RHEL6|RedHat Enterprise Linux 6]]&lt;br /&gt;
* [[Ubuntu | Ubuntu Precise 12.04 LTS / Ubuntu Trusty 14.04 LTS]]&lt;br /&gt;
&lt;br /&gt;
==Windows==&lt;br /&gt;
* Windows Server 2003&lt;br /&gt;
* Windows Server 2008&lt;br /&gt;
*[[Windows_7_Activation|Windows 7]]&lt;br /&gt;
* [[Windows_Patch_Management|Windows Patch Management]]&lt;br /&gt;
&lt;br /&gt;
==MacOSX==&lt;br /&gt;
&lt;br /&gt;
* MacOSX10.4&lt;br /&gt;
* MacOSX10.5&lt;br /&gt;
* MacOSX10.6&lt;br /&gt;
* MacOSX10.7&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrinting&amp;diff=5950</id>
		<title>WindowsPrinting</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=WindowsPrinting&amp;diff=5950"/>
		<updated>2014-06-02T18:24:25Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Removed WinXP guide link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Supported Windows Printing Platforms==&lt;br /&gt;
&lt;br /&gt;
Windows 7 printing: [[Windows7Printing| Windows 7 Printing]]&lt;br /&gt;
&lt;br /&gt;
==Open Printing for Laptops and Non-UMIACS Systems==&lt;br /&gt;
&lt;br /&gt;
Windows 7 printing Non-UMIACS: [[Windows7PrintingNonUMIACS| Windows7 Printing Non UMIACS]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Remote_Desktop&amp;diff=5949</id>
		<title>Remote Desktop</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Remote_Desktop&amp;diff=5949"/>
		<updated>2014-06-02T18:11:27Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: Revised to eliminate WinXP references&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Remote Desktop==&lt;br /&gt;
&lt;br /&gt;
Remote Desktop is a protocol developed by Microsoft designed to allow a user the ability to remotely access a windows computer. This tool is included in most versions of Microsoft Windows starting with NT 4.0. You must be connected to the [[VPN|UMIACS VPN]] to use the Remote Desktop Client outside of our network.&lt;br /&gt;
&lt;br /&gt;
==Starting the Client on Windows 7==&lt;br /&gt;
There are two methods of starting the client in Windows 7. The first method involves searching for it using the search box within the start menu:&lt;br /&gt;
&lt;br /&gt;
[[Image:RDCpic1.jpg]]&lt;br /&gt;
&lt;br /&gt;
Alternatively, you can click on Start-&amp;gt; All Programs-&amp;gt; Accessories -&amp;gt; Remote Desktop Connection to start the client:&lt;br /&gt;
&lt;br /&gt;
[[Image:RDCpic2.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Connecting to the Machine==&lt;br /&gt;
Once you have opened the Remote Desktop Connection program, type in the name of the windows machine you would like to access and then click connect. For example, &amp;quot;jefferson.&#039;&#039;&#039;pc.umiacs.umd.edu&#039;&#039;&#039;&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
[[Image:RDCpic4.jpg]]&lt;br /&gt;
&lt;br /&gt;
If you are using Windows 7, upon first connection to a machine you may receive a pop up warning you must accept:&lt;br /&gt;
&lt;br /&gt;
[[Image:RDCpic5.jpg]]&lt;br /&gt;
&lt;br /&gt;
If you are connecting to a Windows 7 machine a window titled “Windows Security” will pop up which will require you to type in your credentials; then click OK.&lt;br /&gt;
&lt;br /&gt;
[[Image:RDCpic7.jpg]]&lt;br /&gt;
&lt;br /&gt;
If the screen above doesn’t show up and the one below comes up in place, then you either typed the machine name incorrectly or the machine you want to connect to isn’t on the PC domain.&lt;br /&gt;
&lt;br /&gt;
[[Image:RDCpic8.jpg]]&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Email&amp;diff=5948</id>
		<title>Email</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Email&amp;diff=5948"/>
		<updated>2014-06-02T15:14:14Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
===Introduction===&lt;br /&gt;
&lt;br /&gt;
Depending on the environment you&#039;ll be working in, you have two primary choices for mail. You can decide on our PC based solution Microsoft Exchange or a [[UNIXEmail|IMAP Email]] solution. Both provide scanning for Virus and Spam through our [[BarracudaSpamFirewall|Barracuda Spam Firewall]]&lt;br /&gt;
&lt;br /&gt;
Alternatively if you already have a Email provider you like we offer the ability to forward your Email.&lt;br /&gt;
&lt;br /&gt;
You can update your Email preference through our [https://intranet.umiacs.umd.edu/chinfo Directory Profile] Tool.&lt;br /&gt;
&lt;br /&gt;
===Microsoft Exchange Email===&lt;br /&gt;
If you are accustomed with Microsoft Outlook and/or need a shared calendar then we offer the UMIACS Exchange service.  If you work primarily on a PC, collaborate with primarily PC-based users, expect to email MIME attachments or just feel most comfortable with a PC based mail solution, the exchange mailserver is likely the best solution for you.  Among other things, it also supports IMAP, vacation (auto-response) and virus filtering capabilities.&lt;br /&gt;
&lt;br /&gt;
[[SettingUpOutlook2007/2010withExchange|Setting Up Outlook 2007/2010 with Exchange]]&lt;br /&gt;
&lt;br /&gt;
[[SettingUpOutlook2003withExchange|Setting Up Outlook 2003 with Exchange]]&lt;br /&gt;
&lt;br /&gt;
[[SettingupiPhoneAccesstoExchange|Setting Up iPhone Access with Exchange]]&lt;br /&gt;
&lt;br /&gt;
[[AccessingExchangeviaThunderbird|Setting Up Thunderbird with Exchange]]&lt;br /&gt;
&lt;br /&gt;
[[WorkingWithOutlook|Working with Outlook]]&lt;br /&gt;
&lt;br /&gt;
The link for the Exchange web interface is https://exchange.umiacs.umd.edu/owa.  It is also on the front page of our intranet site (https://intranet.umiacs.umd.edu).  Please note that the web interface works best in IE.&lt;br /&gt;
&lt;br /&gt;
===[[IMAPEmail|IMAP Email]]===&lt;br /&gt;
Our IMAP service is available as a simple multi-platform way of reading your mail.  It provides powerful server-side mail filtering and vacation support.  You can configure you own IMAP client (see below for a list of supported clients) or use our [[Webmail]] server to read your email.&lt;br /&gt;
&lt;br /&gt;
===Support Matrix===&lt;br /&gt;
&lt;br /&gt;
{|style=&amp;quot;color:green;background-color:#ffffcc;&amp;quot; cellpadding=&amp;quot;10&amp;quot; cellspacing=&amp;quot;0&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-style=&amp;quot;color:black;&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
|Pine&lt;br /&gt;
|Mutt&lt;br /&gt;
|Thunderbird&lt;br /&gt;
|Mail.app&lt;br /&gt;
|Outlook/Exchange&lt;br /&gt;
|-&lt;br /&gt;
|Windows 7&lt;br /&gt;
|Yes(1)&lt;br /&gt;
|&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|Yes&lt;br /&gt;
|-&lt;br /&gt;
|RHEL 5&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|Yes(2)&lt;br /&gt;
|-&lt;br /&gt;
|RHEL 6&lt;br /&gt;
|Yes (4)&lt;br /&gt;
|Yes (5)&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|Yes(2)&lt;br /&gt;
|-&lt;br /&gt;
|Ubuntu 12.04&lt;br /&gt;
|Yes (4)&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|Yes(2)&lt;br /&gt;
|-&lt;br /&gt;
|Ubuntu 14.04&lt;br /&gt;
|Yes (4)&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|&lt;br /&gt;
|Yes(2)&lt;br /&gt;
|-&lt;br /&gt;
|Mac OS X&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes&lt;br /&gt;
|Yes(3)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
# - We support pine on Windows through [http://www.washington.edu/pine/getpine/pcpine.html PC Pine]&lt;br /&gt;
# - Microsoft Exchange support is only available through the Outlook Web Access which is severely limited on non-IE browsers.&lt;br /&gt;
# - Microsoft Exchange support for Mail/Contacts/Calendar requirers Mac OS X 10.6 or later.&lt;br /&gt;
# - On later RHEL or Ubuntu hosts, pine is no longer supported, and has been replaced by alpine&lt;br /&gt;
# - On RHEL 6 hosts, Mutt is no longer installed by default. Please contact staff for install if need on host&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=BarracudaSpamFirewall&amp;diff=5947</id>
		<title>BarracudaSpamFirewall</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=BarracudaSpamFirewall&amp;diff=5947"/>
		<updated>2014-06-02T13:07:14Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Introduction===&lt;br /&gt;
&lt;br /&gt;
UMIACS has deployed a system with 3 Barracuda Networks spam firewalls. This allows for enterprise level Virus and Spam scoring and filtering for our email architecture.&lt;br /&gt;
&lt;br /&gt;
===Mail Flow Through Barracudas===&lt;br /&gt;
*Currently users that receive mail at Exchange or our new IMAP service will be serviced by the Barracudas. &lt;br /&gt;
&lt;br /&gt;
*The first time your mail flows through one of the Barracudas it will send you a mail with a new username and password. Subsequently you will receive every day (unless you configure otherwise) a mail at approx. 3:30 EST from the Barracuda with your quarantine summary.&lt;br /&gt;
&lt;br /&gt;
===Quarantine===&lt;br /&gt;
*Mail that has been deemed as spam will be kept on the Barracudas in quarantine.  It will not be delivered to your mailbox unless you configure the Barracudas to do so.&lt;br /&gt;
*Your quarantine will be preserved for &#039;&#039;&#039;21 days&#039;&#039;&#039;. If mail is held for longer, then it will be purged. At the bottom of your 3:30 quarantine mail you will see a link that will take you straight to your quarantine.&lt;br /&gt;
**If you receive a security warning in your browser after clicking this link, you may need to [[AddingUMIACSCertificateAuthority|add the UMIACS Certificate Authority]].&lt;br /&gt;
&lt;br /&gt;
===Whitelists, Blacklists &amp;amp; Bayesian Filtering===&lt;br /&gt;
*You may also setup whitelists, blacklists, and Bayesian filtering options through the Preferences tab at the top of the Barracuda web portal.&lt;br /&gt;
&lt;br /&gt;
===More Information===&lt;br /&gt;
*For more information on how to use the Barracuda please download the user&#039;s guide:&lt;br /&gt;
&lt;br /&gt;
https://wiki.umiacs.umd.edu/umiacs/images/5/5a/Barracuda_usersguide.pdf&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&amp;diff=5834</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/umiacs/index.php?title=Main_Page&amp;diff=5834"/>
		<updated>2014-05-27T13:02:20Z</updated>

		<summary type="html">&lt;p&gt;Rleimens: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Announcements==&lt;br /&gt;
&amp;lt;startFeed /&amp;gt;&lt;br /&gt;
=== [[Heartbleed2014|Heartbleed]] ===&lt;br /&gt;
As many of you are aware, a vulnerability called [http://heartbleed.com/ Heartbleed] has been discovered in a ubiquitous cryptography library, OpenSSL.  The bug has been in the code for almost 2 years and was reported publicly with patches available on Monday April 7th.  It has been demonstrated that the vulnerability can be used to expose both passwords and data that should have been secured with the SSL protocol.  &lt;br /&gt;
&lt;br /&gt;
UMIACS staff has patched all of the Institute&#039;s systems to secure this vulnerability. Due to the length of the time that our servers were vulnerable and the inability to detect any past exploitation, we are going to require all UMIACS [[Kerberos|Krb5]]  (UNIX) and [[ActiveDirectory]] (PC) credentials to be changed.&lt;br /&gt;
&lt;br /&gt;
Please change your password before &#039;&#039;&#039;May 1st 2014&#039;&#039;&#039;.  After May 1st, any passwords that are not reset will be locked and expired.  Any user that does not reset either their Krb5 or Active Directory passwords will be scheduled for archive and deletion.   Expired credentials will need to be reset with a photo ID in the UMIACS [[HelpDesk]].&lt;br /&gt;
&lt;br /&gt;
UMIACS passwords should be changed via https://intranet.umiacs.umd.edu/password.&lt;br /&gt;
&lt;br /&gt;
=== Condor Upgrade ===&lt;br /&gt;
&lt;br /&gt;
Staff has upgraded the UMIACS [[Condor]] pool to HTCondor 8. For most users, this should be a smooth transition. However, if you have the Condor 7 paths in your environment (e.g. &amp;lt;tt&amp;gt;/opt/UMcondor&amp;lt;/tt&amp;gt;), these should be removed. The Condor binaries now live in &amp;lt;tt&amp;gt;/usr/bin&amp;lt;/tt&amp;gt;. Please contact [[HelpDesk | staff]] with any questions or concerns.&lt;br /&gt;
&lt;br /&gt;
=== APC Surge Protector Recall ===&lt;br /&gt;
APC recently issued a recall of surge protectors manufactured before the year 2003 due to potential fire hazards when overheating as a result of abnormal electrical conditions. We will handle the recall process for any affected devices you may have. Please see [[APC | this page]] for more details.&lt;br /&gt;
&lt;br /&gt;
===Mavericks and Backups===&lt;br /&gt;
The most recent version of OSX, Mavericks, is incompatible with our deployed version of Druva.  Druva is our backup software and we have upgraded it to support Mavericks.  However, you will need to upgrade your Druva client.  You can get the latest version of the client [[Druva/setup#Getting_the_client | here]].  Alternatively you can bring your laptop to the helpdesk and we will upgrade it for you.&lt;br /&gt;
	&lt;br /&gt;
&amp;lt;endFeed /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Technical Reference==&lt;br /&gt;
&lt;br /&gt;
Welcome to UMIACS Wiki.  This is the main place to find documentation and information about your account and  the technical services that UMIACS offers.  If this is your first time please start here [[GettingStarted| Getting Started]].&lt;br /&gt;
&lt;br /&gt;
We provide many  [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].&lt;br /&gt;
&lt;br /&gt;
We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.&lt;br /&gt;
&lt;br /&gt;
Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].&lt;br /&gt;
&lt;br /&gt;
If you would like to open a support ticket, please contact the UMIACS [[HelpDesk]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;/div&gt;</summary>
		<author><name>Rleimens</name></author>
	</entry>
</feed>