Installing Parallels Client for Linux

28 users found this article helpful

Installation Procedure - GUI

Installation via GUI is only valid on DEB and RPM versions.

Download package from parallels.com/products/ras/download/links/ and store it locally.
Install package using the default package installer.

Download the deb package from parallels.com/products/ras/download/links/ and store it locally.
Switch to the root user.
To install type:
```
dpkg -i RASClient.deb
```
Note - If the installation fails because of missing dependencies, try installing these dependencies using the following command :
```
apt-get -f install
```
Client for Linux binaries are now installed under:
```
/opt/2X/Client/bin
```
Run the following command to launch Client:
```
/opt/2X/Client/bin/2XClient
```
You can also run the following commands to obtain a list of all usage parameters for Client session:
```
cd /opt/2X/Client/bin

./appserverclient -?
```

Download the rpm package from parallels.com/products/ras/download/links/ and store it locally.
Switch to the root user.
Input command as per below example depending on Client version you would like to install:
```
rpm –ivh RASClient-xx.xx.xxxx_x86_x64.rpm
```
If you experience dependencies error, please run the following command for installation and confirm dependencies fix:

yum install RASClient-xx.xx.xxxx_x86_x64.rpm

Client for Linux binaries are now installed under:
```
/opt/2X/Client/bin    
```
Run the following command to launch Client:
```
/opt/2X/Client/bin/2XClient
```
You can also run the following commands to obtain a list of all usage parameters for Client session:
```
cd /opt/2X/Client/bin

./appserverclient -?
```

Download the tar package from parallels.com/products/ras/download/links/ and store it locally.
Switch to the root user.
Switch to the directory containing Parallels Client, e.g.:
```
cd /home/<username>/Downloads
```
To install type:
```
tar jxvf RASClient.tar.bz2 -C /
```
Parallels Client for Linux binaries are now installed under:
```
/opt/2X/Client/bin
```
It is recommended that the post install script is launched in order to register icons, mimetypes, url schema and databases configurations. This script is located under: /opt/2X/Client/scripts/install.sh
Run the following command to launch Client:
```
/opt/2X/Client/bin/2XClient
```
You can also run the following commands to obtain a list of all usage parameters for Client session:
```
cd /opt/2X/Client/bin

./appserverclient -?
```
Note: To unregister the components registered during installation it is recommended to launch the uninstall script located under: /opt/2X/Client/scripts/uninstall.sh

Depending on the package used to install the Client, the SSO installation procedure may vary:

Already available with Client package:

Separate package to Client:

Debian package - Requires Client pre-installed. Install package using the default package installer.

Install pam_2xclient.so module to have Single Sign On for Client.

Note - this file is located under /opt/2X/Client/lib/security/pam_2xclient.so no matter the package used.
The module always returns true and will use an authentication token that will be provided by a higher authentication module.

Note: When a higher authentication module has been configured to SUFFICIENT, it will return on success immediately and pam_2Xclient.so won’t be called. Please change SUFFICIENT TO REQUIRED.
To install Client PAM module, add two lines to your session manage service (eg. /etc/pam d/gdm):
```
auth  optional pam_2xclient.so
password  optional pam_2xclient.so
```
Module arguments:

Debug: Debug trace will be written to /tmp/pam_2xclient.log. If the file cannot be opened, then syslog will be used.

You can use debug argument with all module types. EG. Session optional pam_2xclient.so debug
The module will create an SSO cookie only for well known session services.
You can change the list of services to allow: EG. auth optional pam_2xclient.so gdm kde kdm-kde4

Tell us how we can improve it.