https://wiki.umiacs.umd.edu/umiacs/api.php?action=feedcontributions&user=Seliseev&feedformat=atomUMIACS - User contributions [en]2024-03-29T01:06:54ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/umiacs/index.php?title=Perl&diff=7048Perl2016-07-13T21:09:52Z<p>Seliseev: </p>
<hr />
<div>Perl is a general-purpose programming language originally developed for text manipulation and now used for a wide range of tasks including system administration, web development, network programming, GUI development, and more.<br />
The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal). Its major features are that it's easy to use, supports both procedural and object-oriented (OO) programming, has powerful built-in support for text processing, and has one of the world's most impressive collections of third-party modules.<br />
<br />
==Perl Versions==<br />
While most modern operating systems ship with a version of Perl, UMIACS also maintains multiple versions.<br />
<br />
===RHEL===<br />
:For RHEL, different versions of Perl can be found via [[Modules | GNU Modules.]]<br />
:The versions in /usr have PerlLocalLib support to allow users an easy way to install and maintain their own perl modules:<br />
:* RHEL 5<br />
:** /usr/bin/perl - 5.8.8<br />
:** /usr/local/stow/perl-5.14.2 - 5.14.2<br />
<br />
:* RHEL 6<br />
:** /usr/bin/perl - 5.10.1<br />
:** /opt/local/stow/perl-5.14.2 - 5.14.2<br />
<br />
===Ubuntu===<br />
:For Ubuntu hosts, different version of Perl can be install through the [[Ubuntu/SoftwareCenter | Ubuntu Software Center ]]<br />
:The versions in /usr and /opthave PerlLocalLib support to allow users an easy way to install and maintain their own perl modules:<br />
:* Ubuntu Precise 12.04<br />
:** /usr/bin/perl - 5.14.2<br />
<br />
:* Ubuntu Trusty 14.04<br />
:** /usr/bin/perl - 5.18.2<br />
<br />
===WIN32===<br />
:ActiveState Perl can be installed on your PC upon request. Contact [mailto:staff@umiacs.umd.edu staff] for details.<br />
<br />
If you find that you need a version of Perl that is not readily available, you can always build it from [http://www.cpan.org/src/ source.]<br />
<br />
==Installing Modules==<br />
In order to ensure backwards compatibility and functionality, we prefer that users create their own installations of perl modules so that we can keep the central versions of Perl as vanilla as possible. The following instructions will show you how to [[Perl/Environment | setup and install local copies of Perl Modules.]]<br />
<br />
==Documentation==<br />
You can find full documentation for any version of Perl at http://www.cpan.org/modules/INSTALL.html. You can also find Perl tutorials (which can be fonud under the Manuals menu).</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Perl/Environment&diff=7047Perl/Environment2016-07-13T21:04:01Z<p>Seliseev: /* Installing Modules */</p>
<hr />
<div>We recommend using local::lib to create your own directory of Perl packages downloaded from CPAN. This will create an isolated collection of packages, that will not affect the system version of Perl. This allows users to quickly bootstrap a local Perl Module library.<br />
<br />
<br />
==Creating an Environment==<br />
*You will first need to download a copy of local::lib. This can be found by searching local::lib at http://search.cpan.org/<br />
<br />
*Decompress and extract the package:<br />
<pre>-bash-3.2$ gunzip local-lib-2.000019.tar.gz<br />
-bash-3.2$ tar xvf local-lib-2.000019.tar<br />
</pre><br />
<br />
*Configure and then install the environment:<br />
<pre>-bash-3.2$ cd local-lib-2.000019<br />
-bash-3.2$ perl Makefile.PL --bootstrap<br />
-bash-3.2$ make test && make install<br />
</pre><br />
<br />
*Add the newly created environment to your initialization scripts. After this step is complete, you will need to start a new shell.<br />
<pre>echo 'eval $(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib)' >>~/.bashrc</pre><br />
'''Note:''' Depending on your current initialization script setup, you may need to add the line generated by the above command to your .bash_profile as well. (Or the tcsh equivalent)<br />
<br />
==Module Management==<br />
===Installing Modules===<br />
Once your environment has been created and properly sourced, you can then install packages with cpan as your normally would:<br />
<pre><br />
-bash-3.2$ cpan -i Date::Tolkien::Shire;<br />
</pre><br />
For more information on module installation, see http://www.cpan.org/modules/INSTALL.html<br />
<br />
===Listing Installed Modules===<br />
The following command will list all the Perl Modules installed in the currently sourced environment:<br />
<pre><br />
-bash-3.2$ perldoc perllocal<br />
</pre><br />
<br />
==Creating additional Environments==<br />
By default your environment will be created in the ~/perl5 directory. It is possible to create multiple environments by specifying a directory in when building the environment:<br />
<pre>-bash-3.2$ cd local-lib-2.000019<br />
-bash-3.2$ perl Makefile.PL --bootstrap=/Path/to/Second/Environment<br />
-bash-3.2$ make test && make install<br />
</pre><br />
<br />
It is important to keep in mind that you will need to adjust the line in your initialization scrips to reflect the location of the Environment you wish to use.</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Perl&diff=7045Perl2016-07-13T19:11:57Z<p>Seliseev: /* Perl Versions */</p>
<hr />
<div>Perl is a general-purpose programming language originally developed for text manipulation and now used for a wide range of tasks including system administration, web development, network programming, GUI development, and more.<br />
The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal). Its major features are that it's easy to use, supports both procedural and object-oriented (OO) programming, has powerful built-in support for text processing, and has one of the world's most impressive collections of third-party modules.<br />
<br />
==Perl Versions==<br />
While most modern operating systems ship with a version of Perl, UMIACS also maintains multiple versions.<br />
<br />
===RHEL===<br />
:For RHEL, different versions of Perl can be found via [[Modules | GNU Modules.]]<br />
:The versions in /usr have PerlLocalLib support to allow users an easy way to install and maintain their own perl modules:<br />
:* RHEL 5<br />
:** /usr/bin/perl - 5.8.8<br />
:** /usr/local/stow/perl-5.14.2 - 5.14.2<br />
<br />
:* RHEL 6<br />
:** /usr/bin/perl - 5.10.1<br />
:** /opt/local/stow/perl-5.14.2 - 5.14.2<br />
<br />
===Ubuntu===<br />
:For Ubuntu hosts, different version of Perl can be install through the [[Ubuntu/SoftwareCenter | Ubuntu Software Center ]]<br />
:The versions in /usr and /opthave PerlLocalLib support to allow users an easy way to install and maintain their own perl modules:<br />
:* Ubuntu Precise 12.04<br />
:** /usr/bin/perl - 5.14.2<br />
<br />
:* Ubuntu Trusty 14.04<br />
:** /usr/bin/perl - 5.18.2<br />
<br />
===WIN32===<br />
:ActiveState Perl can be installed on your PC upon request. Contact [mailto:staff@umiacs.umd.edu staff] for details.<br />
<br />
If you find that you need a version of Perl that is not readily available, you can always build it from [http://www.cpan.org/src/ source.]<br />
<br />
==Installing Modules==<br />
In order to ensure backwards compatibility and functionality, we prefer that users create their own installations of perl modules so that we can keep the central versions of Perl as vanilla as possible. The following instructions will show you how to [[Perl/Environment | setup and install local copies of Perl Modules.]]</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=7042GitLab2016-07-13T18:43:51Z<p>Seliseev: </p>
<hr />
<div>GitLab is source code collaboration software based on [[Git]] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS Krb5 credentials in the LDAP tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help. <b>Note:</b> you will need to log in to view this page.<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/permissions/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/markdown/markdown.md<br />
<br />
==Repository URLs== <br />
Users can download and clone directories from the remote repository using git clone. There are two different URLs that can be used: HTTPS and SSH. <br />
You can view the URL underneath the Project title in the Project tab. Change the displayed URL by clicking on the URL type you want to see. <br />
===SSH===<br />
The SSH URL is more direct, though it is harder to set up. In order to do so, you will have to add an SSH key to your Gitlab account. Instructions to do so can be found [https://gitlab.umiacs.umd.edu/help/ssh/README here]. Once you have the SSH key added, you can log in without having to enter any credentials from the machine and account for which you created the SSH key. <br />
===HTTPS===<br />
The HTTPS URL is easier to set up- you just clone directly from the repository using the HTTPS URL. However, you will have to re-enter your credentials for GitLab every single time that you attempt to commit to, push to, pull from, or otherwise access the remote repository.</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=CollaboratorAccount&diff=6966CollaboratorAccount2016-06-27T19:40:18Z<p>Seliseev: /* UMIACS Collaborator Account */</p>
<hr />
<div>=UMIACS Collaborator Account=<br />
<br />
UMIACS provides a application only account that provides collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our [[GitLab]] source code and project management, our [[OBJbox | ObjectStore]] , Wiki's and other web based application platforms. These accounts do not have any storage and any access to [[GitLab]] repositories, [[OBJbox | ObjectStore]] buckets, etc. fall under their account sponser and/or the PI. We also have a new more flexible Security Group that will replace our UMIACS Application Resources, the new Security Groups are managed in our [https://intranet.umiacs.umd.edu/directory/groups/ UMIACS Directory Application].<br />
<br />
==How do I create a Collaborator Account?==<br />
A UMIACS Account holder has to sponsor the Collaborator Account. This is done in our [https://intranet.umiacs.umd.edu/requests/accounts/collaborators/new UMIACS Requests Application]. This will generate a token and send email to the Collaborator to set their details (including a username and password). Once the Collaborator has created the account a email will be sent to the account sponsor, staff and Collaborator that the account is ready to use.<br />
<br />
==How do you reset a Collaborator Account password?==<br />
This is done by the account sponsor through the Collaborator account list in the [https://intranet.umiacs.umd.edu/requests/accounts/collaborators UMIACS Requests Application]. The account sponsor will generate a token and send email to the Collaborator with a link to reset their password.<br />
<br />
==What happened to Gitlab Collaborator Accounts?==<br />
These were superseded with the new UMIACS Collaborator Account. All Gitlab Collaborator Accounts will be contacted and be transitioned to the new UMIACS Collaborator Account.<br />
<br />
==What is the difference between a UMIACS Application Resource account and the new UMIACS Collaborator Account?==<br />
UMIACS Application Resource accounts are being deprecated in favor of the new UMIACS Collaborator Account. Each Application Resource will need all its accounts converted and the applications reconfigured to use the new Security Group framework. Staff will work with our AR owners to make this transition.</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Services/Collaboration&diff=6965Services/Collaboration2016-06-27T19:39:33Z<p>Seliseev: /* Current Offerings */</p>
<hr />
<div>Collaboration tools are designed to improve the ease of sharing and modifying data with a group of people.<br />
<br />
==Current Offerings==<br />
;[[GitLab | GitLab]]<br />
: Web-based git repository manager with wiki and issue tracking features.<br />
;[[OBJbox| Object Storage]]<br />
: Block storage</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Services/Data&diff=6964Services/Data2016-06-27T19:39:11Z<p>Seliseev: /* Current Offerings */</p>
<hr />
<div>==Current Offerings==<br />
;[[OBJbox | Object Storage]]<br />
: Block storage<br />
;[[Druva | Mobile Device Backups]]<br />
: Data backups for mobile devices and personal machines.<br />
;Network Attached Storage<br />
: Home directories, Lab fileshares<br />
;Data Archiving<br />
: Long term storage of data<br />
;Data Distribution<br />
: FTP service.</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Windows/LaptopSupport&diff=6962Windows/LaptopSupport2016-06-27T18:14:40Z<p>Seliseev: /* UMIACS Base Laptop Support */</p>
<hr />
<div>==UMIACS Windows Laptop Support==<br />
In order to meet the demanding requirements of mobile computing best practices and security policies, UMIACS provides a range of supported laptop options. In order to qualify for UMIACS support the laptop must meet the following <br />
[[#Hardware Base Requirements | Base Requirements]].<br />
<br />
==Support Levels==<br />
===UMIACS Enterprise Laptop Support===<br />
The UMIACS Enterprise laptop support provides a secure computing platform with automated backups and security updates. This option is ideal for those dealing with sensitive data, or those who want a worry-free experience.<br />
*'''What we provide:'''<br />
:*Operating System Installation and Maintenance<br />
:*University Licensed Software<br />
:*Security Updates [[LANDesk | (LANDesk)]]<br />
:*Data Backups [[Druva | (Druva)]]<br />
:*Data Protection [[BitLocker | (BitLocker)]]<br />
:*Hardware Diagnostics and Support<br />
<br />
===UMIACS Base Laptop Support===<br />
The UMIACS base laptop support serves as a primer for a development laptop. Staff will install an Enterprise version of Microsoft Windows, as well as a range of software suites including F-Secure Anti-virus, Microsoft Office, and MATLAB. You are then responsible for the maintenance and upkeep of the Operating System and any data stored on the computer.<br />
*'''What we provide:'''<br />
:*Operating System Installation<br />
:*University Licensed Software<br />
:*Hardware Diagnostics and Support<br />
*'''What's left for you:'''<br />
:*Data Backups<br />
:*Security Updates<br />
:*Operating System Maintenance<br />
<br />
In order to help users operate securely and help protect their data, UMIACS offers a range of laptop services.<br />
<br />
===UMIACS Hardware Support===<br />
The UMIACS hardware support provides basic hardware diagnostics and warranty repairs, while allowing the user to have full control over the software and data stored on their laptop.<br />
*'''What we provide:'''<br />
:*Hardware Diagnostics and Support<br />
*'''What's left for you:'''<br />
:*Everything else.<br />
<br />
==Hardware Base Requirements==<br />
In order to qualify for UMIACS laptop support, the hardware must meet the following requirements:<br />
*University Owned Hardware<br />
*Non-consumer model from a tier one vendor (Dell, Microsoft)<br />
*3 years OEM warranty/support<br />
*Readily available manufacturer diagnostic tools<br />
*Readily available hardware drivers<br />
Other hardware platforms may be considered on a case-by-case basis, subject to staff evaluation.</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=GitLab&diff=6960GitLab2016-06-27T16:52:40Z<p>Seliseev: </p>
<hr />
<div>GitLab is source code collaboration software based on [[Git]] source control management. It allows users to create their own repositories and share them with other users/groups or publicly. It supports built-in project wikis, code review, and issue tracking for each project. A full list of features can be found on the [https://www.gitlab.com/gitlab-ce GitLab] website.<br />
<br />
All code is hosted on-site on UMIACS servers and is backed up nightly. We give all UMIACS users 5 projects with a soft limit of 400Mb per project. Projects that you create inside of a group namespace still count towards your project limit. UMIACS Staff can help create Lab groups (called namespaces) and delegate authority to manage the group to one or more faculty members. Permissions are assigned within GitLab. The UMIACS [[ApplicationResource|AR]] system is '''not''' used with GitLab.<br />
<br />
To get started, navigate to the following URL in your browser and enter your UMIACS Krb5 credentials in the LDAP tab:<br />
<br />
https://gitlab.umiacs.umd.edu<br />
<br />
==GitLab Offsite Collaborators==<br />
Any UMIACS user can now create an unlimited number of offsite<br />
collaborator accounts for our Security Groups, GitLab and Object Store. These accounts can not create<br />
repositories or groups, but may be given access to your repositories or<br />
groups. You can find this utility in our [https://intranet.umiacs.umd.edu/requests Requests] application under [https://intranet.umiacs.umd.edu/requests/accounts UMIACS Collaborators].<br />
<br />
==User Documentation==<br />
GitLab provides user documentation that can be accessed at https://gitlab.umiacs.umd.edu/help. <b>Note:</b> you will need to log in to view this page.<br />
<br />
Some of the most useful sections include:<br />
* Permissions and user roles - https://gitlab.umiacs.umd.edu/help/permissions/permissions.md<br />
* GitLab markdown for wikis and READMEs - https://gitlab.umiacs.umd.edu/help/markdown/markdown.md</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=NFShomes&diff=6959NFShomes2016-06-27T16:38:58Z<p>Seliseev: </p>
<hr />
<div>===/nfshomes===<br />
<br />
Automounted NFS file system that houses users' [[OpenLAB]] home directories.<br />
<br />
Found on supported [[OSSupport#UNIX | UNIX]] and [[OSSupport#MacOSX | MacOSX]] systems as <br />
<br />
/nfshomes/username<br />
<br />
Please note that since [[NFS]] is insecure the scope is limited to which machines can mount this file system. If you need additional access you can mount this file system using [[CIFS]] from many operating systems (including Windows) by accessing it as (substituting $username with your UMIACS username)<br />
<br />
\\umdisk.umiacs.umd.edu\$username\openlab<br />
<br />
[[CIFS]] access is limited to machines in the domain so please use the [[VPN]] if you need access from outside UMIACS networks (including the wireless).<br />
<br />
This file system has regular backups with our [[TSM]] service and has [[Snapshots:NetApp|Snapshots]] for easy user restores.</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&diff=6939SSHFileTransferProtocol2016-06-15T17:53:10Z<p>Seliseev: /* Connecting to an SFTP Server */</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 Mac OS X, 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>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&diff=6938SSHFileTransferProtocol2016-06-15T17:52:08Z<p>Seliseev: /* Connecting to an SFTP Server */</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 Mac OS X, 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>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=SSHFileTransferProtocol&diff=6926SSHFileTransferProtocol2016-06-14T21:23:02Z<p>Seliseev: </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 Mac OS X, 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/index.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>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=LabFacilities&diff=6922LabFacilities2016-06-14T19:24:15Z<p>Seliseev: </p>
<hr />
<div>* [[OpenLAB]]<br />
* [https://wiki.umiacs.umd.edu/cbcb-private/index.php/Compute Center for Bioinformatics and Computational Biology] (CBCB) http://www.cbcb.umd.edu<br />
* Center for Digital International Government (CDIG) http://www.umiacs.umd.edu/research/CDIG<br />
* Center for Automation Research (CFAR) http://www.cfar.umd.edu<br />
* Center for Human Enhanced Secure Systems (CHESS) http://chess.umiacs.umd.edu/<br />
* Computational Linguistics and Information Processing (CLIP) https://wiki.umiacs.umd.edu/clip/index.php/Main_Page<br />
* Computer Vision Laboratory (CVL) http://www.cfar.umd.edu/cvl/<br />
* Distributed Systems Software Laboratory (DSSL) http://www.cs.umd.edu/projects/dssl<br />
* Fraunhofer Center at Maryland (FCMD) http://fc-md.umd.edu/<br />
* Global Land Cover Facility (GLCF) http://www.glcf.umiacs.umd.edu<br />
* Graphics and Visual Informatics Laboratory (GVIL) http://www.cs.umd.edu/gvil/<br />
* Human Computer Interaction Laboratory (HCIL) http://www.cs.umd.edu/hcil<br />
* Language and Media Processing Laboratory (LAMP) http://lamp.cfar.umd.edu<br />
* Laboratory for Computational Cultural Dynamics (LCCD) http://www.umiacs.umd.edu/research/LCCD/<br />
* Laboratory for Parallel and Distributed Computing (LPDC) http://www.umiacs.umd.edu/research/LPDC<br />
* Maryland Information and Network Dynamics Lab (MIND) http://mindlab.umd.edu/<br />
* [https://wiki.umiacs.umd.edu/maxwell/index.php/Main_Page MaxWell - WiMaX Forum Applications Laboratory] (MaxWell) http://www.umiacs.umd.edu/research/maxwell/<br />
* Perceptual Interfaces and Reality Laboratory (PIRL) http://pirl.umd.edu/</div>Seliseevhttps://wiki.umiacs.umd.edu/umiacs/index.php?title=Remote_Desktop&diff=6902Remote Desktop2016-06-13T14:19:44Z<p>Seliseev: /* UNIX */</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 />
==OSX==<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>Seliseev