https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&user=Tcasey&feedformat=atomUMIACS - User contributions [en]2024-03-29T13:05:51ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms&diff=7389ConferenceRooms2017-04-28T18:21:00Z<p>Tcasey: Tcasey moved page ConferenceRooms/ to ConferenceRooms</p>
<hr />
<div>#REDIRECT [[ConferenceRooms]]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=File:Filesettings.png&diff=7343File:Filesettings.png2017-03-31T18:26:04Z<p>Tcasey: </p>
<hr />
<div></div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms/ATL3100C&diff=7280ConferenceRooms/ATL3100C2017-02-03T15:52:24Z<p>Tcasey: </p>
<hr />
<div><br />
= QuICS Small VTC Conference Rooms (CSS 3100 C and D) =<br />
;Room Capabilities<br />
: Ability to host Skype conferences<br />
: Display video from room PC, or user laptop at table via HDMI & VGA inputs<br />
: Capture room audio and video at room PC or user laptop<br />
<br />
== Room Notes ==<br />
*CSS3100C and CSS3100D are identical in setup<br />
*There are no projection capabilities, there is only a display present</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms/ATL3100C&diff=7279ConferenceRooms/ATL3100C2017-02-03T15:51:47Z<p>Tcasey: </p>
<hr />
<div><br />
= QuICS Small VTC Conference Rooms (CSS 3100 C and D) =<br />
;Room Capabilities<br />
: Ability to host Skype conferences<br />
: Display video from room PC, or user laptop at table via HDMI & VGA inputs<br />
: Capture room audio and video at room PC or user laptop<br />
<br />
== Room Notes ==<br />
CSS3100C and CSS3100D are identical in setup<br />
There are no projection capabilities, there is only a display present</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms/ATL3100C&diff=7277ConferenceRooms/ATL3100C2017-02-03T15:49:43Z<p>Tcasey: Created page with " = QuICS Small VTC Conference Rooms (CSS 3100 C and D) = ;Room Capabilities : Ability to host Skype conferences : Display video from room PC, or user laptop at table via HDMI..."</p>
<hr />
<div><br />
= QuICS Small VTC Conference Rooms (CSS 3100 C and D) =<br />
;Room Capabilities<br />
: Ability to host Skype conferences<br />
: Display video from room PC, or user laptop at table via HDMI & VGA inputs<br />
: Capture room audio and video at room PC or user laptop<br />
<br />
== Room Notes ==<br />
There are no projection capabilities, there is only a display present</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms/ATL3100A&diff=7276ConferenceRooms/ATL3100A2017-02-03T15:46:29Z<p>Tcasey: </p>
<hr />
<div>=QuICS large Conference room= <br />
This room is designed as a presentation area and does not have videoconferencing systems present. There are direct HDMI and VGA inputs available to the left of the screen.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms/ATL3100A&diff=7275ConferenceRooms/ATL3100A2017-02-03T15:46:11Z<p>Tcasey: </p>
<hr />
<div>=QuICS large Conference room= <br />
This room is designed as a presentation area and does not have videoconferencing systems present. There are direst HDMI and VGA inputs available to the left of the screen.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms/ATL3100A&diff=7274ConferenceRooms/ATL3100A2017-02-03T15:44:58Z<p>Tcasey: </p>
<hr />
<div>[[Category:ConferenceRooms]]<br />
=QuICS large Conference room= <br />
This room is designed as a presentation area and does not have videoconferencing systems present. There are direst HDMI and VGA inputs available to the left of the screen.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=ConferenceRooms/ATL3100A&diff=7273ConferenceRooms/ATL3100A2017-02-03T15:44:48Z<p>Tcasey: Created page with "Category:Conference Rooms =QuICS large Conference room= This room is designed as a presentation area and does not have videoconferencing systems present. There are direst..."</p>
<hr />
<div>[[Category:Conference Rooms]]<br />
=QuICS large Conference room= <br />
This room is designed as a presentation area and does not have videoconferencing systems present. There are direst HDMI and VGA inputs available to the left of the screen.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Printing&diff=7220Printing2016-11-03T14:23:53Z<p>Tcasey: </p>
<hr />
<div>==Printing==<br />
*'''Operating Specific printing guides:'''<br />
:* [[WindowsPrinting|Windows Printing Guide]]<br />
:* [[OSXPrinting|macOS Printing Guide]]<br />
:* [[CUPS|Linux Printing Guide (RHEL and Ubuntu)]]<br />
:* [[UbuntuPrinting|Self supported Ubuntu Printing Guide]]<br />
<br />
* Printing from the wireless or Non-UMIACS Networks<br />
** UMIACS account holders: Connect to the UMIACS [[VPN]]. Afterwards, follow the instructions in [[WindowsPrinting]] for Windows or [[macOSPrinting]] for Mac.<br />
** UMIACS guests and self-supported systems may print using the [[Windows7PrintingNonUMIACS | open print server]]<br />
<br />
* [[PrinterQueueNaming|Selecting A Print Queue (Color, Banners, etc)]]<br />
<br />
* [[UNIXPrinting|Legacy UNIX Printing Guide (Linux and Solaris)]]<br />
<br />
* [[Umiacs_Public_Printers | Umiacs Public Printers]]<br />
<br />
*[[PrinterTroubleshooting | Printer troubleshooting]]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=OSXPrinting&diff=7219OSXPrinting2016-11-03T14:22:40Z<p>Tcasey: Tcasey moved page OSXPrinting to MacOSPrinting</p>
<hr />
<div>#REDIRECT [[MacOSPrinting]]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MacOSPrinting&diff=7218MacOSPrinting2016-11-03T14:22:40Z<p>Tcasey: Tcasey moved page OSXPrinting to MacOSPrinting</p>
<hr />
<div>__NOTOC__<br />
We support printing from user managed macOS 10.8 or later machines. Please note that you have to be on a UMIACS network directly or connected to the [[VPN]].<br />
<br />
[[Image:Osx-print00.png|right|100px]]<br />
=System Preferences=<br />
To start, open your System Preferences from the Dock or Applications folder. Once you have opened it, click '''Printers & Scanners'''.<br />
<br />
[[Image:osx-print01.png|right|100px]]<br />
<br />
=Print & Fax=<br />
When the '''Printers & Scanners''' window appears, create a new local printer by clicking the '''+''' icon in the lower left corner of the first pane in the window.<br />
<br />
=Add Printer=<br />
This will bring up a Add Printer dialog. Please ensure that you have selected IP.<br />
<br />
<br />
'''Note:''' If you just want basic printing, use the steps below. If you would like to enable all the advanced options for the printer, jump over this section to '''"Enabling Advanced Printer Options"'''.<br />
<br />
<br />
* Set Protocol to '''Internet Printing Protocol - IPP'''<br />
* Set Address to '''print.umiacs.umd.edu'''<br />
* Set the Queue to printers/queue; in this example for cps3142 it would be '''printers/cps3142'''. You have to make sure the queue is prefixed by '''printers/'''. For clarification, the queue is typically the printer name.<br />
* Set Name to the name of the printer you are trying to use. This makes it easily Identifiable in your list of printers.<br />
* It will always select '''Generic Postscript Printer'''. If you need to access the more advanced features of a queue/printer you will need take extra steps, please see the Advanced section at the bottom of this page.<br />
* Select Add<br />
* You will be asked about enabling duplex. If you know the printer has the option, which is true for most of our printers, go ahead and enable it. Then hit OK. If you're not sure, just leave it disabled. You can always enable it after the queue is added.<br />
<br />
[[Image:osx-print02.png]]<br />
<br />
You should now be able to print to this printer/queue from any macOS print menu.<br />
<br />
=Enabling Advanced Printer Features=<br />
Some printers may have features not accessible with the default drivers provided above. If this is the case, follow the guide below to identify, and install your print drivers from their manufacturer.<br />
<br />
<br />
'''Note:''' If you already installed the printer with generic drivers, you will need to highlight the printer and click '''-''', before attempting to add it again. You may also need a system update to get the latest drivers from Apple, if your printer does not have software drivers listed in the next steps.<br />
<br />
<br />
'''Step 1:''' Locate your printers name and search for its Make and Model here: http://print.umiacs.umd.edu/printers/<br />
<br />
<br />
'''Step 2:''' Follow the '''Add Printer''' steps above until you get to '''Generic Postscript Printer'''. Select '''Software''', then '''Add'''.<br />
<br />
<br />
[[Image:PrinterSoftwareSelection.png|600px]]<br />
<br />
<br />
'''Step 3:''' A window labeled "Printer Software" will now pop up. Scroll thru the list to find your specific make and model of printer. Click on it, and hit Ok.<br />
<br />
[[Image:PrinterSoftwareList.png]]<br />
<br />
'''Step 4:''' Click Add on the next window and it should install your printers software suite. You should have a list of options (if they are available) that looks similar this:<br />
<br />
[[Image:AdvPrinterOptions.png]]<br />
<br />
'''Final Step:''' Enable the Options you wish to use, Click '''OK'''. You should now be able to print to this printer/queue from any macOS print menu.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=MacOSPrinting&diff=7217MacOSPrinting2016-11-03T14:22:28Z<p>Tcasey: </p>
<hr />
<div>__NOTOC__<br />
We support printing from user managed macOS 10.8 or later machines. Please note that you have to be on a UMIACS network directly or connected to the [[VPN]].<br />
<br />
[[Image:Osx-print00.png|right|100px]]<br />
=System Preferences=<br />
To start, open your System Preferences from the Dock or Applications folder. Once you have opened it, click '''Printers & Scanners'''.<br />
<br />
[[Image:osx-print01.png|right|100px]]<br />
<br />
=Print & Fax=<br />
When the '''Printers & Scanners''' window appears, create a new local printer by clicking the '''+''' icon in the lower left corner of the first pane in the window.<br />
<br />
=Add Printer=<br />
This will bring up a Add Printer dialog. Please ensure that you have selected IP.<br />
<br />
<br />
'''Note:''' If you just want basic printing, use the steps below. If you would like to enable all the advanced options for the printer, jump over this section to '''"Enabling Advanced Printer Options"'''.<br />
<br />
<br />
* Set Protocol to '''Internet Printing Protocol - IPP'''<br />
* Set Address to '''print.umiacs.umd.edu'''<br />
* Set the Queue to printers/queue; in this example for cps3142 it would be '''printers/cps3142'''. You have to make sure the queue is prefixed by '''printers/'''. For clarification, the queue is typically the printer name.<br />
* Set Name to the name of the printer you are trying to use. This makes it easily Identifiable in your list of printers.<br />
* It will always select '''Generic Postscript Printer'''. If you need to access the more advanced features of a queue/printer you will need take extra steps, please see the Advanced section at the bottom of this page.<br />
* Select Add<br />
* You will be asked about enabling duplex. If you know the printer has the option, which is true for most of our printers, go ahead and enable it. Then hit OK. If you're not sure, just leave it disabled. You can always enable it after the queue is added.<br />
<br />
[[Image:osx-print02.png]]<br />
<br />
You should now be able to print to this printer/queue from any macOS print menu.<br />
<br />
=Enabling Advanced Printer Features=<br />
Some printers may have features not accessible with the default drivers provided above. If this is the case, follow the guide below to identify, and install your print drivers from their manufacturer.<br />
<br />
<br />
'''Note:''' If you already installed the printer with generic drivers, you will need to highlight the printer and click '''-''', before attempting to add it again. You may also need a system update to get the latest drivers from Apple, if your printer does not have software drivers listed in the next steps.<br />
<br />
<br />
'''Step 1:''' Locate your printers name and search for its Make and Model here: http://print.umiacs.umd.edu/printers/<br />
<br />
<br />
'''Step 2:''' Follow the '''Add Printer''' steps above until you get to '''Generic Postscript Printer'''. Select '''Software''', then '''Add'''.<br />
<br />
<br />
[[Image:PrinterSoftwareSelection.png|600px]]<br />
<br />
<br />
'''Step 3:''' A window labeled "Printer Software" will now pop up. Scroll thru the list to find your specific make and model of printer. Click on it, and hit Ok.<br />
<br />
[[Image:PrinterSoftwareList.png]]<br />
<br />
'''Step 4:''' Click Add on the next window and it should install your printers software suite. You should have a list of options (if they are available) that looks similar this:<br />
<br />
[[Image:AdvPrinterOptions.png]]<br />
<br />
'''Final Step:''' Enable the Options you wish to use, Click '''OK'''. You should now be able to print to this printer/queue from any macOS print menu.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=FTP/OSX/Finder&diff=7216FTP/OSX/Finder2016-11-03T14:21:05Z<p>Tcasey: Tcasey moved page FTP/OSX/Finder to FTP/macOS/Finder</p>
<hr />
<div>#REDIRECT [[FTP/macOS/Finder]]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=FTP/macOS/Finder&diff=7215FTP/macOS/Finder2016-11-03T14:21:05Z<p>Tcasey: Tcasey moved page FTP/OSX/Finder to FTP/macOS/Finder</p>
<hr />
<div>[[FTP]] services can be accessed from supported machines running macOS. This is a guide on how to access the UMIACS FTP service using macOS Finder.<br />
<br />
==Opening up macOS Finder==<br />
<br />
To open up macOS Finder, click on the macOS Finder icon on the dock at the bottom of your desktop.<br />
[[Image:OS X Dock.png|thumb|left|700px|The Finder icon is highlighted with a red square]]<br />
<br style="clear: both"/><br />
<br />
==Accessing The Incoming Folder in FTP==<br />
The owner of the incoming folder can receive and modify their incoming files from any supported machine. External collaborators can only drop data into the FTP incoming folder.<br />
<br />
===Access as an owner===<br />
The owner of an incoming folder can access it by following the steps below.<br />
<br />
First, bring up the address bar in macOS Finder by pressing <kbd>Command + Shift + G</kbd> on your keyboard.<br />
[[Image:OS X Finder Path Empty.png|thumb|left|700px|Bring up the "go to the folder"]]<br />
<br style="clear: both"/><br />
<br />
Then, type the following into the address bar and click the "Go" button.<br />
<pre>/fs/ftp/incoming/<username> - where <username> should be replaced with your username</pre><br />
[[Image:OS X FTP Path Entered.png|thumb|left|600px|Enter the path to access the incoming folder]]<br />
<br style="clear: both"/><br />
There is a configuration of tmpwatch[http://linux.die.net/man/8/tmpwatch] in place on our FTP service that will remove any files, regardless of owner or permissions, from any /fs/ftp/incoming/ directory that have not been accessed in 30 days.<br />
<br />
===Access as a collaborator===<br />
As an external collaborator you can drop files into a user's incoming folder. In order to do so, follow the steps below.<br />
<br />
First, open up the Finder's "Connect to Server" feature by pressing the <kbd>Command + K</kbd> keys.<br />
[[Image:OS X Open Finder Connect.png|thumb|left|600px|Open the "Connect to Server" window]]<br />
<br style="clear: both"/><br />
Then, enter the following address into the server address bar and then click on the "Connect" button.<br />
<pre>ftp://ftp.umiacs.umd.edu/incoming/<username> - where <username> should be replaced with the collaborator's username</pre><br />
[[Image:OS X Finder Connect Incoming.png|thumb|left|600px]]<br />
<br style="clear: both"/><br />
After that you will be prompted with a window where you should choose to connect as a guest and then click "Connect" once more.<br />
[[Image:OS X Finder Select Guest.png|thumb|left|600px|Select Guest]]<br />
<br style="clear: both"/><br />
[[Image:OS X Finder Connect Guest.png|thumb|left|600px|Click Connect]]<br />
<br style="clear: both"/><br />
<br />
==Accessing The Pubic Folder in FTP==<br />
The owner of the public folder can publish and modify files from a supported machine. External collaborators can only download files published by the owner. <br />
<br />
===Access as an owner===<br />
First, bring up the address bar in macOS Finder by pressing Command + Shift + G.<br />
[[Image:OS X Finder Path Empty.png|thumb|left|700px|Bring up the "go to the folder"]]<br />
<br style="clear: both"/> <br />
In order to access your public folder,<br />
type in the following into the address bar of Finder:<br />
<pre>/fs/ftp/pub/<username> - where <username> should be replaced with your username</pre><br />
[[Image:OS X FTP Pub Path.png|thumb|left|600px|Enter the path to access the pub folder]]<br />
<br style="clear: both"/><br />
<br />
===Access as a collaborator===<br />
External collaborators can access the public folders through the Finder's "Connect to Server" feature. The "Connect to Server" window can be opened by pressing <kbd>Command + K</kbd> on your keyboard.<br />
[[Image:OS X Open Finder Connect.png|thumb|left|600px|Open the "Connect to Server" window]]<br />
<br style="clear: both"/><br />
Then, enter the following address into the server address bar and then click on the "Connect" button.<br />
<pre>ftp://ftp.umiacs.umd.edu/pub/<username> - where <username> should be replaced with the desired collaborator's username</pre><br />
[[Image:OS X Finder Connect Address.png|thumb|left|600px|Enter the path to access the public folder]]<br />
<br style="clear: both"/><br />
After that you will be prompted with a window where you should choose to connect as a guest and then click "Connect" once more.<br />
[[Image:OS X Finder Select Guest.png|thumb|left|600px|Select Guest]]<br />
<br style="clear: both"/><br />
[[Image:OS X Finder Connect Guest.png|thumb|left|600px|Click Connect]]<br />
<br style="clear: both"/></div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=FTP/macOS/Finder&diff=7214FTP/macOS/Finder2016-11-03T14:20:17Z<p>Tcasey: </p>
<hr />
<div>[[FTP]] services can be accessed from supported machines running macOS. This is a guide on how to access the UMIACS FTP service using macOS Finder.<br />
<br />
==Opening up macOS Finder==<br />
<br />
To open up macOS Finder, click on the macOS Finder icon on the dock at the bottom of your desktop.<br />
[[Image:OS X Dock.png|thumb|left|700px|The Finder icon is highlighted with a red square]]<br />
<br style="clear: both"/><br />
<br />
==Accessing The Incoming Folder in FTP==<br />
The owner of the incoming folder can receive and modify their incoming files from any supported machine. External collaborators can only drop data into the FTP incoming folder.<br />
<br />
===Access as an owner===<br />
The owner of an incoming folder can access it by following the steps below.<br />
<br />
First, bring up the address bar in macOS Finder by pressing <kbd>Command + Shift + G</kbd> on your keyboard.<br />
[[Image:OS X Finder Path Empty.png|thumb|left|700px|Bring up the "go to the folder"]]<br />
<br style="clear: both"/><br />
<br />
Then, type the following into the address bar and click the "Go" button.<br />
<pre>/fs/ftp/incoming/<username> - where <username> should be replaced with your username</pre><br />
[[Image:OS X FTP Path Entered.png|thumb|left|600px|Enter the path to access the incoming folder]]<br />
<br style="clear: both"/><br />
There is a configuration of tmpwatch[http://linux.die.net/man/8/tmpwatch] in place on our FTP service that will remove any files, regardless of owner or permissions, from any /fs/ftp/incoming/ directory that have not been accessed in 30 days.<br />
<br />
===Access as a collaborator===<br />
As an external collaborator you can drop files into a user's incoming folder. In order to do so, follow the steps below.<br />
<br />
First, open up the Finder's "Connect to Server" feature by pressing the <kbd>Command + K</kbd> keys.<br />
[[Image:OS X Open Finder Connect.png|thumb|left|600px|Open the "Connect to Server" window]]<br />
<br style="clear: both"/><br />
Then, enter the following address into the server address bar and then click on the "Connect" button.<br />
<pre>ftp://ftp.umiacs.umd.edu/incoming/<username> - where <username> should be replaced with the collaborator's username</pre><br />
[[Image:OS X Finder Connect Incoming.png|thumb|left|600px]]<br />
<br style="clear: both"/><br />
After that you will be prompted with a window where you should choose to connect as a guest and then click "Connect" once more.<br />
[[Image:OS X Finder Select Guest.png|thumb|left|600px|Select Guest]]<br />
<br style="clear: both"/><br />
[[Image:OS X Finder Connect Guest.png|thumb|left|600px|Click Connect]]<br />
<br style="clear: both"/><br />
<br />
==Accessing The Pubic Folder in FTP==<br />
The owner of the public folder can publish and modify files from a supported machine. External collaborators can only download files published by the owner. <br />
<br />
===Access as an owner===<br />
First, bring up the address bar in macOS Finder by pressing Command + Shift + G.<br />
[[Image:OS X Finder Path Empty.png|thumb|left|700px|Bring up the "go to the folder"]]<br />
<br style="clear: both"/> <br />
In order to access your public folder,<br />
type in the following into the address bar of Finder:<br />
<pre>/fs/ftp/pub/<username> - where <username> should be replaced with your username</pre><br />
[[Image:OS X FTP Pub Path.png|thumb|left|600px|Enter the path to access the pub folder]]<br />
<br style="clear: both"/><br />
<br />
===Access as a collaborator===<br />
External collaborators can access the public folders through the Finder's "Connect to Server" feature. The "Connect to Server" window can be opened by pressing <kbd>Command + K</kbd> on your keyboard.<br />
[[Image:OS X Open Finder Connect.png|thumb|left|600px|Open the "Connect to Server" window]]<br />
<br style="clear: both"/><br />
Then, enter the following address into the server address bar and then click on the "Connect" button.<br />
<pre>ftp://ftp.umiacs.umd.edu/pub/<username> - where <username> should be replaced with the desired collaborator's username</pre><br />
[[Image:OS X Finder Connect Address.png|thumb|left|600px|Enter the path to access the public folder]]<br />
<br style="clear: both"/><br />
After that you will be prompted with a window where you should choose to connect as a guest and then click "Connect" once more.<br />
[[Image:OS X Finder Select Guest.png|thumb|left|600px|Select Guest]]<br />
<br style="clear: both"/><br />
[[Image:OS X Finder Connect Guest.png|thumb|left|600px|Click Connect]]<br />
<br style="clear: both"/></div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Network/VPN/macOS&diff=7213Network/VPN/macOS2016-11-03T14:18:03Z<p>Tcasey: </p>
<hr />
<div>'''Please note that this tutorial assumes you already have a network connection established.'''<br />
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory you already have access.'''<br />
<br />
The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a web browser.<br />
<br />
== Connecting through the Pulse Secure client ==<br />
#'''Download the client:'''<br />
#:[[Media:JunosPulse.dmg|macOS Pulse Secure Client]]<br style="clear:both"/><br />
#:''Upon starting the client for the first time it will ask to upgrade the client. This will pull an up-to-date version of the client with the most recent configuration.''<br />
#'''Open the client and click 'Add' (+) under the connection section.'''<br />
#:[[Image:JunosOSX.png|thumb|left|510px|[macOS] Click the 'Add' (+) button to create a new connection]]<br style="clear:both"/><br />
#'''In the 'Name' field, enter a descriptive name for this vpn Connection.'''<br />
#'''In the 'Server URL' enter 'vpn.umiacs.umd.edu'''' <br />
#:[[Image:JunosOSXSettings.png|thumb|left|510px|[macOS] Enter the name of the vpn server]]<br style="clear:both"/><br />
#'''Enter your UMIACS windows login credentials and hit connect.''' <br />
#:[[Image:JunosOSXLogin.png|thumb|left|510px|[macOS] Enter UMIACS Windows Credentials]]<br />
<br />
<br style="clear:both"/><br />
<br />
You should now be connected to the UMIACS VPN.<br />
==Checking VPN Status==<br />
# In the top right hand corner, on your status bar, you should see an S icon in a black circle. If there's a green arrow, that means you are connected! If there is nothing, that means you are not. <br />
#: [[Image:Check the Status of your ConnectionOSX1.png|thumb|left|610px|[macOS] The top image is connected, the bottom image is not.]]<br style="clear:both"/><br />
# You can click this icon, as well, and it will show you the status of your connection.<br />
#:[[Image:AreYouConnected2.png|thumb|left|610px|[macOS] The Pulse drop down menu.]]<br style="clear:both"/><br />
# If the icon is not in the status bar, you can find Pulse Secure in your Applications folder. There you will see a list of connections.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=(N/A)Network/VPN/OSX&diff=7212(N/A)Network/VPN/OSX2016-11-03T14:16:32Z<p>Tcasey: Tcasey moved page Network/VPN/OSX to Network/VPN/macOS</p>
<hr />
<div>#REDIRECT [[Network/VPN/macOS]]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Network/VPN/macOS&diff=7211Network/VPN/macOS2016-11-03T14:16:31Z<p>Tcasey: Tcasey moved page Network/VPN/OSX to Network/VPN/macOS</p>
<hr />
<div>'''Please note that this tutorial assumes you already have a network connection established.'''<br />
'''Authentication is handled via the Windows domain. If you have an account in the PC Active Directory you already have access.'''<br />
<br />
The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a web browser.<br />
<br />
== Connecting through the Pulse Secure client ==<br />
#'''Download the client:'''<br />
#:[[Media:JunosPulse.dmg|OSX Pulse Secure Client]]<br style="clear:both"/><br />
#:''Upon starting the client for the first time it will ask to upgrade the client. This will pull an up-to-date version of the client with the most recent configuration.''<br />
#'''Open the client and click 'Add' (+) under the connection section.'''<br />
#:[[Image:JunosOSX.png|thumb|left|510px|[OSX] Click the 'Add' (+) button to create a new connection]]<br style="clear:both"/><br />
#'''In the 'Name' field, enter a descriptive name for this vpn Connection.'''<br />
#'''In the 'Server URL' enter 'vpn.umiacs.umd.edu'''' <br />
#:[[Image:JunosOSXSettings.png|thumb|left|510px|[OSX] Enter the name of the vpn server]]<br style="clear:both"/><br />
#'''Enter your UMIACS windows login credentials and hit connect.''' <br />
#:[[Image:JunosOSXLogin.png|thumb|left|510px|[OSX] Enter UMIACS Windows Credentials]]<br />
<br />
<br style="clear:both"/><br />
<br />
You should now be connected to the UMIACS VPN.<br />
==Checking VPN Status==<br />
# In the top right hand corner, on your status bar, you should see an S icon in a black circle. If there's a green arrow, that means you are connected! If there is nothing, that means you are not. <br />
#: [[Image:Check the Status of your ConnectionOSX1.png|thumb|left|610px|[OSX] The top image is connected, the bottom image is not.]]<br style="clear:both"/><br />
# You can click this icon, as well, and it will show you the status of your connection.<br />
#:[[Image:AreYouConnected2.png|thumb|left|610px|[OSX] The Pulse drop down menu.]]<br style="clear:both"/><br />
# If the icon is not in the status bar, you can find Pulse Secure in your Applications folder. There you will see a list of connections.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=UMIACS_Public_Printers&diff=7201UMIACS Public Printers2016-10-31T14:13:15Z<p>Tcasey: </p>
<hr />
<div>==Access to Public Printers==<br />
If you need to print but there are no printers accessible in your lab, we have two locations with publicly accessible printers. These rooms are accessible only with your university ID key card. If you are not able to access these rooms with your key card, please see Edna in room 2119 to get this access granted to your card.<br />
<br />
=====Help Desk Printers in room 3142=====<br />
Color Printer: '''cps3142'''<br/><br />
Black/White Printer: '''ps3142'''<br />
<br />
=====Public Printers in room 4430=====<br />
Color Printer: '''cps4430a'''<br/><br />
Black/White Printer: '''ps4430b'''<br />
<br />
==How to Print==<br />
If you are unsure of how to connect to these printers, please see our other articles on printing in UMIACS.<br/><br />
[[PrinterQueueNaming | Selecting A Print Queue (Color, Banners, etc)]]<br/><br />
[[CUPS | UNIX Printing Guide (Linux and Solaris)]]<br/><br />
[[WindowsPrinting | Windows Printing Guide]]<br/><br />
[[OSXPrinting | macOS Printing Guide]]<br/><br />
[[WirelessPrinting | Printing from the wireless or Non-UMIACS Networks]]<br/></div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=UpdatingMozillaSoftware&diff=7200UpdatingMozillaSoftware2016-10-31T14:12:45Z<p>Tcasey: </p>
<hr />
<div>__FORCETOC__<br />
Like most applications, it is important to keep your browser and email clients up-to-date to combat security flaws and gain new functionality. The instructions on this page should help you update Mozilla Firefox and Thunderbird.<br />
<br />
You can also find installers and documentation for the latest versions of Firefox and Thunderbird here:<br />
*Firefox: http://www.getfirefox.com<br />
*Thunderbird: http://www.getthunderbird.com<br />
<br />
== Determining the Installed Version ==<br />
<br />
You can find out what version of Firefox or Thunderbird you have installed on you computer by opening up the application and choosing:<br />
*"Help > About Mozilla [application]" from the menu bar on Windows<br />
*"Firefox > About [application]" from the menu bar on macOS<br />
where [application] is either "Firefox" or "Thunderbird".<br />
<br />
== Updating Mozilla Firefox (Windows & Mac) ==<br />
*By default Mozilla Firefox will automatically update by itself. If it is currently disabled it can be enable with the following steps:<br />
#First navigate to options (Windows) or preferences (Mac).<br />
#Once in the options (Windows) or preferences (Mac) you navigate to the advanced tab.<br />
#Once on the advanced Tab you navigate to Updates.<br />
#*Once in the updates tab you will see an option to “Automatically install updates”. If this is not already enabled it is recommended to enable this.<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-firefox1.png|thumb|left|300pxx300px|Step 1: Navigate to options (Windows)]]<br />
[[Image:mac-firefox1.png|thumb|300px|Step 1: Navigate to preferences (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox2.png|thumb|left|300px|Step 2: Navigate to advanced tab (Windows)]]<br />
[[Image:mac-firefox2.png|thumb|300px|Step 2: Navigate to advanced tab (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox3.png|thumb|left|300px|Step 3: Navigate to updates (Windows)]]<br />
[[Image:mac-firefox3.png|thumb|300px|Step 3: Navigate to updates (Mac)]]<br />
<br style="clear: both" /><br />
<br />
*If you do not want to have Mozilla Firefox auto-update you can check manually for updates with the following steps:<br />
#First navigate to help->about Firefox (Windows) and about Firefox (Mac)<br />
#Click check for updates button (Windows and Mac)<br />
#If an update is available click “Update to “Version”’ Button (Windows and Mac)<br />
#Click “Restart to Update” button (Windows and Mac)<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-firefox4.png|thumb|left|300pxx300px|Step 1: Navigate to Help (Windows)]]<br />
[[Image:windows-firefox5.png|thumb|left|300pxx300px|Step 2: Navigate to about Firefox (Windows)]]<br />
[[Image:mac-firefox4.png|thumb|300px|Step 1: Navigate to about Firefox (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox6.png|thumb|left|300px|Step 3: Click “Check for Updates” button (Windows)]]<br />
[[Image:mac-firefox5.png|thumb|300px|Step 2: Click “Check for Updates” button (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-firefox7.png|thumb|left|300px|Step 4: Click “Update to “Version’” button (Windows)]]<br />
[[Image:mac-firefox6.png|thumb|300px|Step 3:Click “Update to “Version’” button (Mac)]]<br />
[[Image:windows-firefox8.png|thumb|left|300px|Step 5: Click “Restart to Update" button (Windows)]]<br />
[[Image:mac-firefox7.png|thumb|300px|Step 4:Click “Restart to Update" button (Mac)]]<br />
<br style="clear: both" /><br />
<br />
== Updating Mozilla Thunderbird (Windows & Mac) ==<br />
*By default Mozilla Thunderbird will automatically update by itself. If it is currently disabled it can be enable with the following steps.<br />
#First navigate to options->options(Windows) or preferences(Mac).<br />
#Once in the options(Windows) or preferences(Mac) you navigate to the advanced tab.<br />
#Once on the advanced Tab you navigate to Updates.<br />
#*Once in the updates tab you will see an option to “Automatically install updates”. If this is not already enabled it is recommended to enable this.<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird1.png|thumb|left|300px|Step 2: Navigate to options->options (Windows)]]<br />
[[Image:mac-thunderbird1.png|thumb|300px|Step 1: Navigate to preferences (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird2.png|thumb|left|300px|Step 2: Navigate to advanced tab (Windows)]]<br />
[[Image:mac-thunderbird2.png|thumb|300px|Step 2: Navigate to advanced tab (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird3.png|thumb|left|300px|Step 3: Navigate to updates(Windows)]]<br />
[[Image:mac-thunderbird3.png|thumb|300px|Step 3: Navigate to updates (Mac)]]<br />
<br style="clear: both" /><br />
<br />
*If you do not want to have Mozilla Thunderbird auto-update you can check manually for updates with the following steps:<br />
#First navigate to help->about Thunderbird (Windows) and about Thunderbird (Mac).<br />
#Click the check for updates button (Windows and Mac).<br />
#Click “Update & Restart” button (Windows) and “Restart to Update” button (Mac).<br />
<br />
''Click on pictures to enlarge them''<br />
<br style="clear: both" /><br />
[[Image:windows-Thunderbird4.png|thumb|left|300px|Step 1: Navigate to Help (Windows)]]<br />
[[Image:windows-Thunderbird5.png|thumb|left|300px|Step 2: Navigate to about Thunderbird (Windows)]]<br />
[[Image:mac-Thunderbird4.png|thumb|300px|Step 1: Navigate to about Thunderbird (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird6.png|thumb|left|300px|Step 3: Click “Check for Updates” button (Windows)]]<br />
[[Image:mac-thunderbird5.png|thumb|300px|Step 2: Click “Check for Updates” button (Mac)]]<br />
<br style="clear: both" /><br />
[[Image:windows-thunderbird7.png|thumb|left|300px|Step 4: Click “Update & Restart" button (Windows)]]<br />
[[Image:mac-thunderbird6.png|thumb|300px|Step 3:Click “Restart to Update" button (Mac)]]<br />
<br style="clear: both" /><br />
<br />
== Troubleshooting ==<br />
If for some reason Firefox or Thunderbird refuses to update using the methods described above, please stop by the [[HelpDesk]] and have a technician assist you.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureCopy&diff=7199SecureCopy2016-10-31T14:12:12Z<p>Tcasey: </p>
<hr />
<div>Secure Copy (or [http://en.wikipedia.org/wiki/Secure_Shell SCP]) is a way of copying data between two computers using [[SSH]].<br />
<br />
==Using SCP==<br />
The following commands work under Red Hat Enterprise Linux, Ubuntu Linux, and macOS. <br />
<br />
This command, when run from a terminal, will copy the file "source_file.txt" from the local machine to a folder inside the user's OpenLab account and give it the name "target_file.txt".<br />
wing:~ Ben$ scp source_file.txt bkirz@openlab.umiacs.umd.edu:target_file.txt<br />
<br />
This command, when run from a terminal, will copy the file "source_file.txt" from the user's OpenLab account into the current local directory and give it the name "target_file.txt".<br />
wing:~ Ben$ scp bkirz@openlab.umiacs.umd.edu:source_file.txt target_file.txt<br />
<br />
Note how the syntax of scp is very similar to that of the UNIX command cp with the addition of a hostname and username.<br />
<br />
For UMIACS supported Windows hosts, WinSCP (available for download [http://winscp.net/eng/download.php here]) is already installed. <br />
<br />
==Further Information==<br />
* [http://www.openssh.org/ OpenSSH]<br />
* [http://winscp.net WinSCP]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&diff=7198SSHFileTransferProtocol2016-10-31T14:11:41Z<p>Tcasey: </p>
<hr />
<div>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.<br />
<br />
'''Warning:''' running interactive programs in your shell initialization files, such as starting another shell, causes SFTP to fail. See [[Shell]] on how to correctly change the shell you are using<br />
<br />
==Connecting to an SFTP Server==<br />
Under Under Red Hat Enterprise Linux, Ubuntu Linux, and macOS, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].<br />
<br />
wing:~ bkirz$ sftp bkirz@openlab.umiacs.umd.edu<br />
<br />
For UMIACS supported Windows hosts, a SFTP client is already installed. For other hosts, you can download and install [http://winscp.net/eng/download.php winSCP], which will enable SSH and SFTP access.<br />
<br />
==Further Information==<br />
<br />
More information about SFTP can be found at [http://www.openssh.org/ http://www.openssh.org/].</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Printing&diff=7197Printing2016-10-31T14:10:46Z<p>Tcasey: </p>
<hr />
<div>==Printing==<br />
*'''Operating Specific printing guides:'''<br />
:* [[WindowsPrinting|Windows Printing Guide]]<br />
:* [[OSXPrinting|macOS Printing Guide]]<br />
:* [[CUPS|Linux Printing Guide (RHEL and Ubuntu)]]<br />
:* [[UbuntuPrinting|Self supported Ubuntu Printing Guide]]<br />
<br />
* Printing from the wireless or Non-UMIACS Networks<br />
** UMIACS account holders: Connect to the UMIACS [[VPN]]. Afterwards, follow the instructions in [[WindowsPrinting]] for Windows or [[OSXPrinting]] for Mac.<br />
** UMIACS guests and self-supported systems may print using the [[Windows7PrintingNonUMIACS | open print server]]<br />
<br />
* [[PrinterQueueNaming|Selecting A Print Queue (Color, Banners, etc)]]<br />
<br />
* [[UNIXPrinting|Legacy UNIX Printing Guide (Linux and Solaris)]]<br />
<br />
* [[Umiacs_Public_Printers | Umiacs Public Printers]]<br />
<br />
*[[PrinterTroubleshooting | Printer troubleshooting]]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SecureShell&diff=7196SecureShell2016-10-31T14:10:08Z<p>Tcasey: </p>
<hr />
<div>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]].<br />
<br />
==Connecting to an SSH Server==<br />
Under Linux and macOS the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]].<br />
# ssh bkirz@openlab.umiacs.umd.edu<br />
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.<br />
<br />
All UMIACS Windows hosts are installed with SSH Secure Shell Client. Alternatively, users can install these software on their personal machines:<br />
<br />
* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]<br />
* [http://ttssh2.sourceforge.jp/ ttssh2]<br />
<br />
Alternatively, all users can launch terminal sessions [[JuniperVPNTerminalSession| through the Juniper VPN web interface.]]<br />
<br />
==X11 Forwarding==<br />
By default, SSH only gives the user shell access to a host. Enabling X11 Forwarding allows users to run applications with Graphical User Interfaces.<br />
<br />
Under Linux and macOS, the following command from a terminal will connect a client computer to the UMIACS [[OpenLAB]] using X11 Forwarding.<br />
# ssh '''-Y''' bkirz@openlab.umiacs.umd.edu<br />
<br />
Under macOS, [http://xquartz.macosforge.org/landing/ xQuartz] is required on the client machine to forward X sessions from the remote session.<br />
<br />
If you do not have Cygwin, you will need to forward X through <br />
[http://sourceforge.net/projects/vcxsrv/ VcXsrv] or<br />
[http://www.straightrunning.com/XmingNotes/ Xming].<br />
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.<br />
<br />
[[Image:sshXForward.jpg]]<br />
<br />
Next, click save in the main ssh appication window to save this setting.<br />
<br />
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.<br />
Now, you will be able to use Xwindow programs from your ssh client.<br />
<br />
==SSH Tunneling==<br />
<br />
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.<br />
<br />
Please see the [[SecureShellTunneling]] page for more information.<br />
<br />
==SSH Keys (and Passwordless SSH)==<br />
<br />
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. <br />
To setup passwordless ssh, do the following.<br />
<br />
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 '''[enter]''', you will never be prompted for a password when ssh'ing which can lead to security problems.<br />
<br />
# To create a '''''passwordless''''' key, type the following, and then hit enter to place the keys in the default directory. '''NOTE: This is ''REQUIRED'' for our [[ClusterGuide|TORQUE/MAUI]]-based clusters!''' <pre> # ssh-keygen -N ""</pre><br />
#: Alternatively, to create a '''''passphrase-protected''''' (more-secure) key, type the following. Do not use this option if you plan to use any of our [[ClusterGuide|TORQUE/MAUI]]-based clusters.<pre> # ssh-keygen</pre><br />
#This will produce two files, '''id_rsa''' and '''id_rsa.pub''', the private and public keys, respectively. The default location will be ~/.ssh/. For the purposes of this tutorial we'll assume this default. Once you've created the keys, you will need to put them into place as follows: <br />
# chmod 700 ~/.ssh <br />
# chmod 600 ~/.ssh/id_rsa <br />
# touch ~/.ssh/authorized_keys2<br />
# chmod 600 ~/.ssh/authorized_keys2<br />
# cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys2<br />
# rm ~/.ssh/id_rsa.pub <br />
<br />
*It is '''very''' important that you keep your private key secure! Ensure that it is chmod'd to 600 and that you do not put it anywhere visible to other users!<br />
*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'd to 750 or 700 to make sure of this. If the group write bit is set, your ssh keys '''WILL NOT WORK'''<br />
<br />
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:<br />
<br />
# ssh-agent [SHELL]<br />
# ssh-add -t [TIME]<br />
<br />
In this case, "[SHELL]" is your preferred shell and "[TIME]" is the amount of time you'd like the key to be active in seconds. So, the following would start a bash shell with passwordless ssh active for 30 minutes:<br />
<br />
# ssh-agent bash<br />
# ssh-add -t 1800<br />
<br />
You will be prompted for your passphrase and, when entered correctly, you will be able to ssh without entering a password.<br />
<br />
To disable this functionality, simply delete your private key file ('''~/.ssh/id_rsa''') and remove the public key from your '''~/.ssh/authorized_keys2''' file.<br />
<br />
==Long Running Processes==<br />
If you are dealing with a long running process that is inhibiting your ability to work regularly, you may want to run your processes inside a screen on the host that you're connecting to. This way, if the connection is dropped for any reason the screen session will automatically detach on the host and will continue running so that you can reattach it at a later time when you've connected again. Please see our documentation on [[Screen | GNU Screen]] for more information.<br />
<br />
==Further Information==<br />
[http://www.openssh.org/ OpenSSH]<br />
<br />
[http://www.openssh.com/windows.html Windows Clients]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Network/VPN&diff=7195Network/VPN2016-10-31T14:09:15Z<p>Tcasey: </p>
<hr />
<div>UMIACS current provides VPN access through a Pulse Secure SSL VPN.<br />
<br />
==Getting Connected==<br />
* [[Network/VPN/Windows|Configuring a Windows SSL VPN Connection]] <br />
* [[Network/VPN/OSX|Configuring a macOS VPN Connection]]<br />
* '''Mobile Devices:'''<br />
:* [[Network/VPN/IOS | Configuring an iOS device]]<br />
Once connected to the VPN you can use the [[Remote_Desktop| Remote Desktop client]] to access a Windows machine, as well as access other UMIACS resources.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LaTeX&diff=7194LaTeX2016-10-31T14:08:09Z<p>Tcasey: </p>
<hr />
<div>==Background==<br />
<br />
From the main [http://www.latex-project.org Project Page]:<br />
<br />
LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the <i>de facto</i> standard for the communication and publication of scientific documents.<br />
<br />
==LaTeX on Windows==<br />
<br />
In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.<br />
<br />
==LaTeX on Linux/UNIX==<br />
<br />
As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with macOS support made available in [https://www.tug.org/mactex/ MacTeX]<br />
<br />
Most of our supported Linux systems should already have the LaTeX command-line utilities, as well as TeX Live, installed. Here is a example of using these to receive output as a PDF:<br />
<br />
* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:<br />
<br />
<pre><br />
\documentclass[12pt]{article}<br />
\usepackage{amsmath}<br />
\title{\LaTeX}<br />
\date{}<br />
\begin{document}<br />
\maketitle<br />
\LaTeX{} is a document preparation system for the \TeX{}<br />
typesetting program. It offers programmable desktop<br />
publishing features and extensive facilities for<br />
automating most aspects of typesetting and desktop<br />
publishing, including numbering and cross-referencing,<br />
tables and figures, page layout, bibliographies, and<br />
much more. \LaTeX{} was originally written in 1984 by<br />
Leslie Lamport and has become the dominant method for<br />
using \TeX; few people write in plain \TeX{} anymore.<br />
The current version is \LaTeXe.<br />
<br />
% This is a comment, not shown in final output.<br />
% The following shows typesetting power of LaTeX:<br />
\begin{align}<br />
E_0 &= mc^2 \\<br />
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}<br />
\end{align}<br />
\end{document}<br />
</pre><br />
<br />
* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:<br />
<br />
<pre><br />
[jlent@opensub01 example]$ latex example.tex <br />
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)<br />
[...]<br />
[1] (./example.aux) )<br />
Output written on example.dvi (1 page, 1692 bytes).<br />
Transcript written on example.log.<br />
</pre><br />
<br />
* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:<br />
<br />
* Option 1: Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:<br />
<pre><br />
[jlent@opensub01 example]$ dvips example.dvi <br />
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)<br />
' TeX output 2014.07.24:1013' -> example.ps<br />
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro><br />
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>. <br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb><br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb><br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb><br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb><br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb><br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb><br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb><br />
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb><br />
[1] <br />
[jlent@opensub01 example]$ ps2pdf example.ps <br />
[jlent@opensub01 example]$ <br />
</pre><br />
<br />
* Option 2: Using <tt>dvipdf</tt>:<br />
<pre><br />
[jlent@opensub01 example]$ dvipdf example.dvi <br />
[jlent@opensub01 example]$ <br />
</pre><br />
<br />
* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory. If your output PDF does not look quite right, you may need to use different conversion tools. Your workflow may necessarily vary depending on the contents of your document and how they are formatted and rendered.<br />
<br />
==Further Reading==<br />
<br />
* [http://latex-project.org/guides LaTeX project documentation page]<br />
* [http://mintaka.sdsu.edu/GF/bibliog/latex/LaTeXtoPDF.html More LaTex to PDF options]</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Network/Troubleshooting/DNS&diff=7193Network/Troubleshooting/DNS2016-10-31T14:07:35Z<p>Tcasey: </p>
<hr />
<div>We have experienced in the past a number of issues with home internet providers not correctly handling DNS resolution for UMIACS hostnames that can seem to be affecting connectivity to UMIACS.<br />
<br />
In the face of this, here are a few last-resort options for bypassing problematic DNS services...<br />
<br />
===[http://en.wikipedia.org/wiki/Google_Public_DNS Google DNS]===<br />
<br />
IP Addresses:<br />
* 8.8.8.8<br />
* 8.8.4.4<br />
<br />
===[http://en.wikipedia.org/wiki/OpenDNS OpenDNS]===<br />
<br />
IP Addresses:<br />
* 208.67.222.222<br />
* 208.67.220.220<br />
* 208.67.222.220<br />
* 208.67.220.222<br />
<br />
===How to change your default DNS servers===<br />
* '''Windows Vista/7/8/10:''' Under Control Panel > Network and Internet > Network and Sharing Center<br />
::# Click "Change adapter settings" on the left. <br />
::# Right click on the network adapter you're using, choose "Properties" from the context menu.<br />
::# Select "Internet Protocol Version 4 (TCP/IPv4)" and click on the "Properties" button.<br />
::# If not selected, choose "Use the following DNS server addresses:"<br />
::# Enter the public DNS addresses you desire to use.<br />
::# click OK, and close the remaining windows<br />
<br />
* '''macOS:''' System Preferences > Network > Advanced > DNS<br />
<br />
* '''Linux:''' edit your /etc/resolv.conf file and change the ip addresses after "nameserver" to any of those listed above.<br />
<br />
===Manual Lookup===<br />
If you are having problems getting to UMIACS hosts you can use our name servers to resolve those specific host names then connect using the IP addresses you lookup. Our name servers are 128.8.120.19, 128.8.120.50, and 128.8.132.75 to use this information to get the ip address of the host somehost.umiacs.umd.edu you would use the command "nslookup somehost.umiacs.umd.edu 128.8.120.19", from a linux, windows, or mac command prompt.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Subversion&diff=7191Subversion2016-10-31T13:58:31Z<p>Tcasey: </p>
<hr />
<div>This page is maintained for legacy reasons and it is suggested to use [[GitLab]] for version control.<br />
<br />
UMIACS provides a centrally managed [[Subversion]] service.<br />
<br />
To have a [[Subversion]] repository created you need to just email [mailto:staff@umiacs.umd.edu staff] and provide the name of your repository and how much initial space you think you will need.<br />
<br />
We will give you a [[URL]] back with the server https://subversion.umiacs.umd.edu in it.<br />
<br />
By default we will configure all repositories to be private and require authentication for both reading and writing to the [[Subversion]] repository. Authentication is done against our [[LDAP]] and if requested we can enable a UMIACS user to manage the [[ApplicationResource|AR]] with our [[ApplicationResourceUtil]] found at https://intranet.umiacs.umd.edu/arutil.<br />
<br />
=Getting Started with Subversion=<br />
<br />
You will first need to check out your repository,<br />
<br />
svn co https://subversion.umiacs.umd.edu/my_url<br />
<br />
This will create a directory in your current working directory with the name of the last part of the URL you just checked out.<br />
<br />
cd my_url<br />
<br />
You can now add files by the '''svn import''' command, '''svn add''' can be used to add file that you have created but is not under revision control yet.<br />
<br />
For more information please see the defacto book on [[Subversion]] in [http://svnbook.red-bean.com/en/1.4/svn-book.html HTML] or [http://svnbook.red-bean.com/en/1.4/svn-book.pdf PDF]<br />
<br />
=Clients=<br />
<br />
Most Linux distributions include subversion clients in the distribution including all our [[OSSupport|Red Hat Enterprise Linux]] clients.<br />
<br />
==Collab.net Subversion Packages==<br />
<br />
These are well packaged subversion command line packages. You can find ones for Windows, macOS and Solaris. Please see the community downloads for macOS.<br />
<br />
http://www.open.collab.net/downloads<br />
<br />
==Security Considerations==<br />
Command line subversions store your password be default on linux, so you should be careful. In order to disable password caching completely, add the line: "store-passwords = no" to the subversion configuration file on your machine. In order to disable caching for a one time command you can pass the --no-auth-cache option.<br />
<br />
==Server Certificate Verification on macOS==<br />
The command-line svn tool that is bundled with macOS through Xcode does not correctly handle the UMIACS subversion server certificate. In order to verify that you are actually connecting to UMIACS, verify that the following fingerprint matches:<br />
<br />
Fingerprint: cb:4f:c6:74:3e:1a:27:d3:55:e7:4b:5a:89:af:e4:c4:95:ce:fe:32<br />
<br />
If this fingerprint matches, you can safely accept the certificate. <br />
<br />
==Graphical Clients==<br />
<br />
===OS Integration===<br />
<br />
* Windows - http://tortoisesvn.tigris.org<br />
* macOS - http://scplugin.tigris.org<br />
<br />
===Other Clients===<br />
<br />
http://subversion.tigris.org/links.html#clients</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Remote_Desktop&diff=7190Remote Desktop2016-10-31T13:54:40Z<p>Tcasey: </p>
<hr />
<div>=Introduction=<br />
<br />
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. <br />
<br />
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.<br />
<br />
=How to Connect=<br />
*'''Prerequisites:'''<br />
**Connected to the [[VPN | UMIACS VPN]] or be within the UMIACS network border.<br />
**Be a member of the 'Remote Desktop Users' group on the remote machine.<br />
==Windows==<br />
For connecting to Windows client over RDP, we recommend the native Windows 'Remote Desktop Connection' client.<br />
#To start the RDC client, click the "Start'" or "Windows" button on the taskbar. In the menu, navigate to "All Programs," "Accessories," then select "Remote Desktop Connection". Alternatively, you can search for "Remote Desktop Connection" in the Start menu's search field. <br />
#Once RDC client starts, type the name of the RDP/Windows host you are trying to access. The name should be the Fully Qualified Domain Name (FDQN), i.e. "somepc.'''pc.umiacs.umd.edu'''". At this point, click "Connect" to initiate the RDP session. <br />
#*[[File:RemoteDesktop-ConnectMenu.jpg]]<br />
#After the connection is started, a warning message may alert you to an identity verification failure. For UMIACS machines, you can ignore this and proceed by selecting "Yes"<br />
#*[[File:RemoteDesktop-SecurityWarning.jpg]]<br />
#Upon reaching the Windows Security prompt, enter your PC credentials. If the username is either not correct or not the desired account, select "Use another account". Click "Ok" when you are done. <br />
#*[[File:RemoteDesktop-CredentialsPrompt.jpg]]<br />
#You should now be viewing the remote computer. To terminate the session, you should logout of Windows. <br />
<br />
To switch between your current host and the remote host, click the minimize or "-" button on the top connection bar. With RDC, the clipboard can be transferred between the remote and current host while the RDC client is running and logged in.<br />
<br />
==macOS==<br />
For connecting to Windows client over RDP, we recommend the 'Microsoft Remote Desktop' application. Another, although less preferred options is the CoRD client.<br />
#Open the 'Microsoft Remote Desktop Application' and select '+ New' to create a new device profile<br />
#Fill in the 'Connection Name' and 'PC Name' fields with the name of the host remote host you wish to connect to. Then close the window.<br />
#*[[File:OSX_MRD_addClient.png |300px]]<br />
#You will now see the device listed in the 'My Desktops' section of the 'Microsoft Remote Desktop' Application. Double click it to start the connection.<br />
#*[[File:OSX_MRD.png | 300px]]<br />
<br />
==UNIX==<br />
===freerdp===<br />
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. <br />
<br />
To use rdesktop, open a shell prompt and type the following command, replacing any $REPLACEME with the requested value. <br />
<br />
<pre> rdesktop -r clipboard:CLIPBOARD -g $GEOMETRY -d PC -u $USERNAME $HOSTNAME </pre><br />
<br />
Key: <br />
<br />
* <b><tt>$GEOMETRY</tt></b>: Percent of remote host's screen to mirror on the client<br />
* <b><tt>$USERNAME</tt></b>: Your UMIACS username (Do not include domain name)<br />
* <b><tt>$HOSTNAME</tt></b>: Fully Qualified Domain Name (FDQN) of the desired remote host<br />
<br />
Once you have connected, you will be directed to a Windows login screen where you can complete the login process.<br />
<br />
===xfreerdp===<br />
<br />
Xfreerdp is the replacement for rdesktop included with newer Linux hosts, starting with RHEL7 and Ubuntu 12.04/14.04. Xfreerdp also has RHEL6. You should use the xfreerdp client from the command line. This is preinstalled on these newer hosts. <br />
<br />
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: <br />
<br />
<pre> xfreerdp -d PC -u $USERNAME --plugin cliprdr -g $GEOMETRY $HOSTNAME </pre><br />
<br />
Similar to rdesktop, here is an explanation of the values above:<br />
<br />
* <b><tt>$GEOMETRY</tt></b>: Percent of remote host's screen to mirror on the client<br />
* <b><tt>$USERNAME</tt></b>: Your UMIACS username (Do not include domain name)<br />
* <b><tt>$HOSTNAME</tt></b>: Fully Qualified Domain Name (FDQN) of the desired remote host<br />
<br />
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.</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=AddingUMIACSCertificateAuthority&diff=7189AddingUMIACSCertificateAuthority2016-10-31T13:53:51Z<p>Tcasey: </p>
<hr />
<div>===Introduction===<br />
<br />
When you visit webpages encrypted with SSL, you may be presented with a warning about the site's security certificate not being trusted. These are normally important screens to pay attention to on the internet as a whole and UMIACS goes to great lengths to maintain a secure environment for our users. However, it is not cost effective to provide commercial certs for all our public facing certificates. In order to keep costs down we provide a UMIACS CA (certificate authority) that enables your web browser to trust our secure webpages. The following steps explain how to import this certificate based on your preferred web browser.<br />
<br />
===Mozilla Firefox (cross-platform)===<br />
<br />
Mozilla Firefox contains its own method of managing certificate authorities independent of your operating system. These are the steps required if you are using Firefox:<br />
<br />
* Visit http://intranet.umiacs.umd.edu<br />
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". <br />[[Image:UMIACSCA_IE_1.png]]<br />Firefox should open a "Downloading Certificate" dialog box automatically. It may look slightly different depending on your operating system or version of Firefox:<br />[[Image:UMIACSCA_Firefox_1.png|458px]]<br />
* Check all three boxes indicating that you fully trust this certificate authority<br />
* Click ok.<br />
* You may need to restart your browser for the change to take effect.<br />
<br />
===Internet Explorer and Google Chrome (Windows)===<br />
<br />
For most Windows browsers (excluding Firefox), certificate authorities are handled by Windows itself. These are the steps required to accept the certificate:<br />
<br />
* Visit http://intranet.umiacs.umd.edu<br />
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". Download and open this file<br />[[Image:UMIACSCA_IE_1.png|border]]<br />
* Click "Install Certificate..." towards the bottom of the dialog box<br />[[Image:UMIACSCA_IE_2.png|376px]]<br />
* Click Next<br />
* Choose "Place all certificates in the following store"<br />
* Choose "Trusted Root Certification Authorities" and click ok<br />[[Image:UMIACSCA_IE_3.png|644px]]<br />
* Click next and then finished. You should receive a success message similar to the following:<br />[[Image:UMIACSCA_IE_4.png|200px]]<br />
* You may need to restart your browser for the change to take effect.<br />
<br />
===Safari and Google Chrome (Mac macOS)===<br />
<br />
For most macOS browsers (excluding Firefox), certificate authorities are handled by macOS itself. This process requires administrator access. If you do not have administrator access and you are using a UMIACS-supported Mac, please contact [[HelpDesk|Staff]]. Otherwise, here are the steps required to accept the certificate:<br />
<br />
* Visit http://intranet.umiacs.umd.edu<br />
* Scroll to the bottom and click "UMIACS CA Root Certificate (CRT - Most Browsers)". Download and open this file by double-clicking it<br />[[Image:UMIACSCA_1.png|500px]]<br />
* The previous step will add the certificate for your own account, but it will not be trusted by macOS itself. If you have administrative access on your Mac, choose Always Trust:<br />[[Image:UMIACSCA_2.png|500px]]<br />
* Enter the administrator credentials to add this certificate for all users of the system:<br />[[Image:UMIACSCA_3.png|500px]]<br />
* Close the keychain access window.<br />
* You may need to restart your browser for the change to take effect.<br />
<br />
===Other Browsers (Unix)===<br />
<br />
If you are using a browser other than Firefox in Unix, the process is more complicated than the above methods and may depend on your particular Unix distribution. If you need assistance with this please contact [[HelpDesk|UMIACS Staff]].</div>Tcaseyhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Matlab&diff=7188Matlab2016-10-31T13:52:44Z<p>Tcasey: </p>
<hr />
<div>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]<br />
<br />
==Linux==<br />
Below are the different versions 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].<br />
<br />
[[Modules | Modules]] is the preferred way to interact with Matlab and the page will provide information on adding Matlab into your environment and using it.<br />
<br />
===RHEL5===<br />
* /opt/matlab-r2007b<br />
* /opt/matlab-r2008a<br />
* /opt/matlab-r2008b<br />
* /opt/matlab-r2009b<br />
* /opt/matlab-r2010a<br />
* /opt/matlab-r2010b<br />
* /opt/matlab-r2011a<br />
* /opt/matlab-r2011b<br />
* /opt/matlab-r2012a<br />
* /opt/matlab-r2012b<br />
* '''/opt/matlab-r2013a''' <br />
<br />
===RHEL6,7/Ubuntu===<br />
<br />
* /opt/common/matlab-r2007b<br />
* /opt/common/matlab-r2008a<br />
* /opt/common/matlab-r2008b<br />
* /opt/common/matlab-r2009b<br />
* /opt/common/matlab-r2010a<br />
* /opt/common/matlab-r2010b<br />
* /opt/common/matlab-r2011a<br />
* /opt/common/matlab-r2011b<br />
* /opt/common/matlab-r2012a<br />
* /opt/common/matlab-r2012b<br />
* /opt/common/matlab-r2013a<br />
* /opt/common/matlab-r2013b<br />
* /opt/common/matlab-r2014a<br />
* /opt/common/matlab-r2014b<br />
* '''/opt/common/matlab-r2015a'''<br />
<br />
==Windows==<br />
Below are the different locations of Matlab available for university-owned machines running Windows. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2007a<br />
* Matlab r2007b<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009a<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011a<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a<br />
* Matlab r2013b<br />
* Matlab r2014a<br />
* Matlab r2014b<br />
* Matlab r2015a<br />
* '''Matlab r2016a'''<br />
<br />
==macOS==<br />
Below are the different locations of Matlab available for university-owned machines running macOS. We expect that all versions should run on macOS 10.8 and newer. The one in bold is the latest version we have available:<br />
<br />
* Matlab r2008a<br />
* Matlab r2008b<br />
* Matlab r2009b<br />
* Matlab r2010a<br />
* Matlab r2010b<br />
* Matlab r2011b<br />
* Matlab r2012a<br />
* Matlab r2012b<br />
* Matlab r2013a (macOS 10.8+)<br />
* '''Matlab r2013b''' (macOS 10.8+)<br />
<br />
==License Troubleshooting==<br />
<br />
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's necessary to check the number of toolbox licenses available.<br />
<br />
===Windows License Troubleshooting===<br />
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. "win64" needs to be adjusted to "win32" on a 32-bit installation:<br />
$MATLAB_PATH\etc\win64\lmutil lmstat -c "$MATLAB_PATH\licenses\network.lic" -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2012b on a 64-bit Windows 7 host for the Aerospace Blockset Toolbox: <br />
"C:\Program Files\matlab\r2012b\etc\win64\lmutil.exe" lmstat -c "C:\Program Files\matlab\r2012b\licenses\network.lic" -f Aerospace_Blockset<br />
<br />
===Unix License Troubleshooting===<br />
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. "glnxa64" needs to adjusted to "glnx86" on a 32-bit installation::<br />
$MATLAB_PATH/bin/glnxa64/lmutil lmstat -c $MATLAB_PATH/licenses/network.lic -f $TOOLBOX_SHORTNAME<br />
<br />
As an example, here is how to query Matlab r2010b on our 64-bit RHEL5 hosts for the Parallel Computing Toolbox:<br />
/opt/matlab-r2010b/bin/glnxa64/lmutil lmstat -c /opt/matlab-r2010b/licenses/network.lic -f Distrib_Computing_Toolbox<br />
<br />
===Toolbox Shortnames===<br />
The toolbox names themselves don'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:<br />
<br />
Aerospace_Blockset <br />
Aerospace_Toolbox <br />
Bioinformatics_Toolbox <br />
Communication_Blocks <br />
Communication_Toolbox <br />
Compiler <br />
Control_Toolbox <br />
Curve_Fitting_Toolbox <br />
Data_Acq_Toolbox <br />
Database_Toolbox <br />
Datafeed_Toolbox <br />
Distrib_Computing_Toolbox <br />
Econometrics_Toolbox <br />
Excel_Link <br />
Fin_Derivatives_Toolbox <br />
Financial_Toolbox <br />
Fixed_Income_Toolbox <br />
Fixed_Point_Toolbox <br />
GADS_Toolbox <br />
Identification_Toolbox <br />
Image_Acquisition_Toolbox <br />
Image_Toolbox <br />
Instr_Control_Toolbox <br />
MAP_Toolbox <br />
MATLAB <br />
MATLAB_Builder_for_Java <br />
MATLAB_Coder <br />
MATLAB_Excel_Builder <br />
MATLAB_Report_Gen <br />
MPC_Toolbox <br />
Neural_Network_Toolbox <br />
Optimization_Toolbox <br />
PDE_Toolbox <br />
Real-Time_Workshop <br />
Robust_Toolbox <br />
Signal_Blocks <br />
Signal_Toolbox <br />
SimMechanics <br />
Simscape <br />
SIMULINK <br />
Simulink_Control_Design <br />
Stateflow <br />
Stateflow_Coder <br />
Statistics_Toolbox <br />
Symbolic_Toolbox <br />
Video_and_Image_Blockset <br />
Virtual_Reality_Toolbox <br />
Wavelet_Toolbox<br />
<br />
If you are having problems, feel free to contact [[HelpDesk | UMIACS Staff]], however please note that the Matlab license servers are hosted by campus' Division of Information Technology.<br />
<br />
==Matlab Customizations==<br />
<br />
You can tweak your Matlab experience using a file "startup.m". 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:<br />
<br />
* [http://www.mathworks.com/help/matlab/ref/matlabrc.html Mathworks: Startup.m]<br />
* [http://www.mathworks.com/help/matlab/matlab_env/startup-folder-for-the-matlab-program.html#bs6j57e-5 Mathworks: Userpath function]</div>Tcasey