INUVIKA OPEN VIRTUAL DESKTOP FOUNDATION SERVER

Transcription

1 INUVIKA OPEN VIRTUAL DESKTOP FOUNDATION SERVER INSTALLATION AND CONFIGURATION GUIDE Mathieu SCHIRES Version: Published July 26, 2016

2 Contents 1 INTRODUCTION PRE-REQUISITES Ubuntu (Trusty Tahr) sudo Repository RHEL and Centos SELinux Repository RHEL 6 and CentOS Adding an additional repository on RHEL RHEL 7 and CentOS Adding an additional repository on RHEL Clearing cache Firewall and ports OVD SESSION MANAGER (OSM) INSTALLATION AND CONFIGURATION Requirements Installing on Ubuntu (Trusty Tahr) Installing MySQL Package Installation Configuration Installing on RHEL 6 and CentOS Installing MySQL Package Installation Configuration PHP Settings Installing on RHEL 7 and CentOS Installing MySQL Package Installation Configuration PHP Settings OVD APPLICATION SERVER (OAS) INSTALLATION AND CONFIGURATION Requirements Windows Linux Page 1

3 4.2 Installing on Microsoft Windows Installing on Ubuntu (Trusty Tahr) Installing on RHEL 6 and CentOS Installing on RHEL 7 and CentOS Registering the Server and Publishing Applications Launching a Session Internal System Examining the Windows Agent Log OVD FILE SERVER (OFS) INSTALLATION AND CONFIGURATION Requirements Installing on Ubuntu (Trusty Tahr) Installing on RHEL 6 and CentOS Installing on RHEL 7 and CentOS OVD WEB ACCESS (OWA) INSTALLATION AND CONFIGURATION Requirements Installing on Ubuntu (Trusty Tahr) Installing on RHEL 6 and CentOS Installing on RHEL 7 and CentOS All-in-one installation on CentOS Installing the Java Applet Module Installing on Ubuntu (Trusty Tahr) Installing on RHEL 6 and CentOS Installing on RHEL 7 and CentOS Advanced Settings Description Page 2

4 1. INTRODUCTION The purpose of this document is to describe how the different server roles of Inuvika OVD can be installed on all the supported operating systems. The OVD servers roles can be installed on separate servers. This is recommended with an OVD farm in production To install all the components described in this guide, follow sections 1-6. To perform OVD Session Manager installation, follow steps in sections 1, 2 and 3. To perform OVD Application Server, follow steps in sections 1, 2 and 4. To perform OVD File Server installation, follow steps in sections 1, 2 and 5. To perform OVD Web Access installation, follow steps in sections 1, 2 and 6. Page 3

5 2. PRE-REQUISITES When installing the Linux distribution on the server, please ensure that the Server version is installed and not the Desktop version. Any required software packages will be installed when the OVD component is installed. Do not manually install a Graphical User Interface for desktop use or an X window environment. Failing to follow these recommendations may lead to poor system performance. In this document, we are using sm.test.demo for the OSM resource name, aps.test.demo for the OAS and web.test.demo for the OVD Web Access. You need to use the resource name that is configured for your own environment. The resource name can be the FQDN or hostname. It cannot be a URI context, protocol or port. 2.1 UBUNTU (TRUSTY TAHR) SUDO On an Ubuntu system, we do not use the super user (root) to install packages. It is recommended to use sudo before each command you enter. Of course, you can choose to log in as root if you wish using: $ sudo -s REPOSITORY Ubuntu (Trusty Tahr) is a Debian-based system which uses the same packaging system and tools as Debian: apt-get. For each server you plan to install, you need to have an internet connection on your Ubuntu (Trusty Tahr) system and add the Inuvika Debian repository to your system. Edit the /etc/apt/sources.list.d/ovd.list file to add the following line: deb trusty main Completing the Installation Process Install the keyring package to validate the repository using gpg: # wget -O- " apt-key add - Update the package database: # apt-get update Page 4

6 2.2 RHEL AND CENTOS SELINUX Inuvika OVD is not compatible with SELinux. So, if you have SELinux installed and enabled on your system, you will have to disable it. To disable SELinux: Edit the /etc/selinux/config file and set the SELINUX variable to disabled. SELINUX=disabled Reboot your system # reboot Check SELinux is now disabled # sestatus SELinux status: disabled REPOSITORY RHEL uses the RPM packaging system. For each server you plan to install, you will need to have an Internet connection on your RHEL system. The first step is to configure yum to enable the Inuvika RPM repository. Create the file /etc/yum.repos.d/ovd.repo as follows: RHEL 6 AND CENTOS 6 Adding the OVD repository. [ovd-2.0.0] name=inuvika OVD baseurl= enabled=1 gpgcheck=1 gpgkey= Adding an additional repository on RHEL 6 As pre-requisites, the following repository channel must be added using the command below: # yum-config-manager --enable rhel-6-server-optional-rpms RHEL 7 AND CENTOS 7 Adding the OVD repository. [ovd-2.0.0] name=inuvika OVD baseurl= enabled=1 gpgcheck=1 gpgkey= Page 5

7 Adding an additional repository on RHEL 7 As pre-requisites, the following repository channel must be added using the command below: # subscription-manager repos --enable=rhel-7-server-optional-rpms # yum clean all CLEARING CACHE Cleaning repositories caches to retrieve Inuvika OVD packages. 2.3 FIREWALL AND PORTS OVD requires the following ports to be open for different servers roles. Firewall rules need to be added for the incoming and outgoing traffic. OVD Session Manager: 80 (HTTP): for communication with a browser for the OVD Administration Console 443 (HTTPS): for communication with a browser for the OVD Administration Console 1111 (HTTP): for communication with an OVD Application Server OVD Web Access: 80 (HTTP): for communication with an end user s browser 443 (HTTPS): for communication with an end user s browser OVD Application Server: 1112 (HTTP): for communication with the OVD Session Manager 3389 (RDP): for communication with an end user s browser (with the Java access) or the OVD Enterprise Client OVD File Server: 1112 (HTTP): for communication with the OVD Session Manager 1113 (HTTP): for communication with an OVD Application Server 445 (CIFS): for communication with an OVD Application Server Inuvika Enterprise Secure Gateway: 1112 (HTTP): for communication with the OVD Session Manager 443 (HTTPS): for communication with an end user s browser 3389 (RDP): for communication with an OVD Application Server Page 6

8 3. OVD SESSION MANAGER (OSM) INSTALLATION AND CONFIGURA- TION This server is the central piece of an Inuvika OVD server farm and is always required. It manages the session establishment from a client, hosts the administration console and provides centralized management of all the OVD server resources. The OSM should be installed prior to any other server. Inuvika provides various Linux packages for installing the OSM on a Linux server. Inuvika does not provide a Windows installer version of OSM. 3.1 REQUIREMENTS All of the following Operating Systems are supported: RHEL 6.x / Centos 6.x 64 bits RHEL 7.x / Centos 7.x 64 bits Ubuntu server (LTS version only) 64 bits Minimum hardware configuration: CPU: 2 Cores recommended as a minimum Memory: 4 GB recommended as a minimum Storage: 20 GB Network: 1 GB NIC (2 for failover) 3.2 INSTALLING ON UBUNTU (TRUSTY TAHR) INSTALLING MYSQL The OSM needs access to a MySQL database. We advise you to setup the MySQL server on the same machine as the OSM to minimize network access time. Install the mysql-server package: # apt-get install mysql-server A password for root will be requested. Now login to mysql and create a database: # mysql -u root -p -e 'create database ovd' PACKAGE INSTALLATION Install the following OVD packages: # apt-get install inuvika-ovd-session-manager inuvika-ovd-administration-\ console The installer will require the resource name of the OVD Session Manager (ie. sm.test.demo) Page 7

9 The installer will prompt whether to enable HTTPS access to the Administration Console if it detects that HTTPS access is not already enabled on the system. If HTTPS access is enabled, after completing the installation, both HTTP and HTTPS access to the Administration Console will be available. The installer will prompt for an admin login and a password, and for confirmation of the password. The server is now installed but not configured. To configure the SM, open test.demo/ovd/admin in a web browser CONFIGURATION The first step is to go to and authenticate yourself with the admin login and password you provided during installation. The first time you log in, the system detects that it is not configured so you are redirected to a basic setup page which will save a default configuration. On this page, you setup the MySQL configuration. For example, if you installed MySQL on the same host as described above, you would use the following configuration: Database Type: MySQL Database host address: Database username: root Database password: [root_password] Database name: ovd Table prefix: ovd_ The OSM is now configured for basic use. 3.3 INSTALLING ON RHEL 6 AND CENTOS INSTALLING MYSQL The OSM needs access to a MySQL database. We advise you to setup the MySQL server on the same machine as the OSM to minimize network access time. Install the mysql package: # yum install mysql mysql-server To automatically start MySQL when the system boots up # chkconfig mysqld on Start the service # service mysqld start Define the mysql root password # mysqladmin -u root password 'mysql_root_password' Page 8

10 Now login to mysql and create a database: # mysql -u root -p -e 'create database ovd' PACKAGE INSTALLATION As prequisites, install the php-mbstring package: # yum install php-mbstring Install the following OVD packages: # yum install inuvika-ovd-session-manager inuvika-ovd-administration-\ console Launch the configuration tool # ovd-session-manager-config Admin login: admin Password: Retype password: Is this correct? [Y/n] Launch the Administration Console configuration tool # ovd-administration-console-config Session Manager address [ ]: Select whether to enable HTTPS access to the Administration Console. This message is displayed only if HTTPS access is not already enabled on the system. If HTTPS access is enabled, after completing the configuration, both HTTP and HTTPS access to the Administration Console will be available. Enable HTTPS support [yes] (yes or no): Configure and start apache service # chkconfig httpd on # service httpd restart CONFIGURATION The first step is to go to and authenticate yourself with the admin login and password you provided during installation. The first time you log in, the system detects that it is not configured so you are redirected to a basic setup page which will save a default configuration. On this page, you setup the MySQL configuration. For example, if you installed MySQL on the same host as described above, you would use the following configuration: Database Type: MySQL Database host address: Database username: root Page 9

11 Database password: [root_password] Database name: ovd Table prefix: ovd_ PHP SETTINGS You have to set the timezone setting located in the PHP configuration file. Edit the PHP configuration file # vi /etc/php.ini Change the setting to match the value you want (the possible values can be found here date.timezone = Europe/Paris Restart the Apache server # service httpd restart The OSM is now configured for basic use. 3.4 INSTALLING ON RHEL 7 AND CENTOS INSTALLING MYSQL The OSM needs access to a MySQL database. On RHEL 7 and CentOS 7, the mysql database package is provided by mariadb. We advise you to setup the MySQL server on the same machine as the OSM to minimize network access time. Install the mysql package: # yum install mariadb mariadb-server To automatically start MySQL when the system boots up # chkconfig mariadb on Start the service # service mariadb start Define the mysql root password # mysqladmin -u root password 'mysql_root_password' Now login to mysql and create a database: # mysql -u root -p -e 'create database ovd' Page 10

12 3.4.2 PACKAGE INSTALLATION As prequisites, install the php-mbstring package: # yum install php-mbstring Install the following OVD packages: # yum install inuvika-ovd-session-manager inuvika-ovd-administration-\ console Launch the configuration tool # ovd-session-manager-config Admin login: admin Password: Retype password: Is this correct? [Y/n] Launch the Administration Console configuration tool # ovd-administration-console-config Session Manager address [ ]: Select whether to enable HTTPS access to the Administration Console. This message is displayed only if HTTPS access is not already enabled on the system. If HTTPS access is enabled, after completing the configuration, both HTTP and HTTPS access to the Administration Console will be available. Enable HTTPS support [yes] (yes or no): Configure and start apache service # chkconfig httpd on # service httpd restart CONFIGURATION The first step is to go to and authenticate yourself with the admin login and password you provided during installation. The first time you log in, the system detects that it is not configured so you are redirected to a basic setup page which will save a default configuration. On this page, you setup the MySQL configuration. For example, if you installed MySQL on the same host as described above, you would use the following configuration: Database Type: MySQL Database host address: Database username: root Database password: [root_password] Database name: ovd Table prefix: ovd_ Page 11

13 3.4.4 PHP SETTINGS You have to set the timezone setting located in the PHP configuration file. Edit the PHP configuration file # vi /etc/php.ini Change the setting to match the value you want (the possible values can be found here date.timezone = Europe/Paris Restart the Apache server # service httpd restart The OSM is now configured for basic use. Page 12

14 4. OVD APPLICATION SERVER (OAS) INSTALLATION AND CONFIGU- RATION Inuvika OVD is an application and desktop delivery solution. The OAS in the OVD solution is the server that hosts and serves the end user applications and desktops It is accessed from an OVD client using an enhanced Remote Display Protocol. An Application Server can be either a Linux system or a Windows system depending on the type of applications and desktops you want to deliver. Of course, you can mix Linux and Windows machines in an Inuvika OVD farm to deliver applications seamlessly to the end user from different application servers. The user load will be load-balanced by the OSM among the available application servers to provide a better distribution of server resources. Inuvika OVD Foundation Server limits the number of OAS servers that can be registered in an OVD farm to one application server (either Linux or Windows). In order to register more than one application server, the OVD farm needs to be upgraded to Inuvika OVD Enterprise. For further information on upgrading Inuvika OVD Foundation Server to Inuvika OVD Enterprise please refer to the Enterprise Activation Guide that is included with this documentation. 4.1 REQUIREMENTS WINDOWS All of the following Operating Systems are supported: Windows 2008 R2 SP1 with Remote Desktop Services Windows 2012 / 2012 R2 with Remote Desktop Services Minimum hardware configuration: CPU: 4 cores recommended as a minimum Memory: 8 GB recommended as a minimum Storage: 50+ GB. High speed disks with RAID-1 (15krpm, SSDs or SAN disks). Network: 1 GB NIC LINUX All of the following Operating Systems are supported: RHEL 6.x / Centos 6.x 64 bits RHEL 7.x / Centos 7.x 64 bits Ubuntu server (LTS version only) 64 bits Minimum hardware configuration: CPU: 4 cores recommended as a minimum Memory: 8 GB recommended as a minimum Storage: 50+ GB. High speed disks with RAID-1 (15krpm, SSDs or SAN disks). Network: 1 GB NIC Page 13

15 4.2 INSTALLING ON MICROSOFT WINDOWS Microsoft Remote Desktop Services (2008R2 and 2012R2) role must be deployed, configured and properly licensed (See Microsoft RDS licensing for more information). The Windows server may run in a workgroup or be a member of an Active Directory domain but must not run as a domain controller. Disable the Network Level Authentication for Remote Desktop. Before installing the OAS, the Inuvika OVD Session Manager (OSM) must be installed and running. Furthermore if the RDS role has been installed, the server must be rebooted before installing the OAS. Download the OAS installer from this location: Copy the OAS installer to the Windows Server machine you wish to install it on and run it. The only installation data required is resource name of the OVD Session Manager. (We use sm.test.demo here as an example, but of course, you have to specify your own domain name). When the installation is complete, the Windows OVD service should be configured and running. To check go to the Windows Services, browse to Inuvika Open Virtual Desktop agent and look at the status. Page 14

16 The server should appear in the list of Unregistered Servers in the OVD Administration Console. If your server does not show up in the list, you might have a DNS configuration issue. Ensure that the firewall is correctly configured for the ports (Refer to section 2.3 "Firewalls and Ports") required by OVD 4.3 INSTALLING ON UBUNTU (TRUSTY TAHR) Some cloud based environments do not provide an Ubuntu system with all the required packages. The OVD Application Server requires the relevant linux-image-extra package to be installed on Ubuntu for it to work correctly. Check if the package is installed and if not install it using the following command: # apt-get install linux-image-extra-$(uname -r) Install the OAS packages: # apt-get install inuvika-ovd-slaveserver-role-aps inuvika-ovd-desktop The only information required is the resource name where the OSM can be accessed (we use sm.test.demo in this example, but of course, you have to use your own resource name). If you choose to install OAS on the same machine as OSM, enter for the resource name. The server should appear in the list of Unregistered Servers in the OVD Administration Console. If your server does not show up in the list, you might have a DNS configuration issue. Ensure that the firewall is correctly configured for the ports (Refer to section 2.3 "Firewalls and Ports") required by OVD 4.4 INSTALLING ON RHEL 6 AND CENTOS 6 Install a missing depedency # yum install librecode.so.0 Add the repository which provides Xfce support on RHEL/CentOS: Page 15

17 # yum install latest-6.noarch.rpm Install the cups package: # yum install cups Configure and start the cups service # chkconfig cups on # service cups restart Install the OAS packages: # yum install inuvika-ovd-slaveserver-role-aps inuvika-ovd-desktop Launch the configuration tool and configure the Session Manager address # ovd-slaveserver-config --sm-address sm.test.demo If you choose to install OAS on the same machine as OSM, enter for the resource name. Configure and the start the ovd-slaveserver service # chkconfig ovd-slaveserver on # service ovd-slaveserver restart The server should appear in the list of Unregistered Servers in the OVD Administration Console. If your server does not show up in the list, you might have a DNS configuration issue. Ensure that the firewall is correctly configured for the ports (Refer to section 2.3 "Firewalls and Ports") required by OVD 4.5 INSTALLING ON RHEL 7 AND CENTOS 7 Add the repository which provides Xfce support on RHEL/CentOS: # yum install latest-7.noarch.rpm If the system has been installed by using the minimal installation, the firewall is enabled by default. You can flush the policy chain or turn off the firewall. Flush the policy chain # iptables -F Page 16

18 Stop the firewall # systemctl stop firewalld Install the cups package: # yum install cups Configure and start the cups service # chkconfig cups on # service cups restart Install the OAS packages: # yum install inuvika-ovd-slaveserver-role-aps inuvika-ovd-desktop Launch the configuration tool and configure the Session Manager address # ovd-slaveserver-config --sm-address sm.test.demo If you choose to install OAS on the same machine as OSM, enter for the resource name. Configure and the start the ovd-slaveserver service # chkconfig ovd-slaveserver on # service ovd-slaveserver restart The server should appear in the list of Unregistered Servers in the OVD Administration Console. If your server does not show up in the list, you might have a DNS configuration issue. Ensure that the firewall is correctly configured for the ports (Refer to section 2.3 "Firewalls and Ports") required by OVD 4.6 REGISTERING THE SERVER AND PUBLISHING APPLICATIONS In the Administration Console, click register to register your application server and switch it from "maintenance" to "production" mode. Any applications that were available on the server should now be listed in the Administration Console. You can enter the desired Display name of the server which is the field used in the Administration Console to identify the server. The next step is to create the required publications so that authorized users can access the applications they require. A publication links an application group to a user group so that Page 17

19 users in the user group have access to the applications in the application group. You should plan how best to allocate your publications but to get started try adding some applications to an existing Application Group so that users will be authorized to run those applications. If you do not have any existing Application Groups, please refer to the Inuvika OVD Administration Guide first. 4.7 LAUNCHING A SESSION If you launch a session, you should be able to access to your applications from the application menu and from desktop icons if you did not disable that option in the Administration Console. 4.8 INTERNAL SYSTEM EXAMINING THE WINDOWS AGENT LOG In a default Windows installation, the log file can be found at: Windows 2008: C:\ProgramData\OVD\slaveserver\log. Windows 2012R2: C:\ProgramData\OVD\slaveserver\log. It s also possible to read view messages in the Windows Event Viewer (in the Application section). Page 18

20 5. OVD FILE SERVER (OFS) INSTALLATION AND CONFIGURATION Within Inuvika OVD, the OFS provides a centralized file management system that enables users to access the same files independently of which application server is used to provide the application. OFS provides a network file system that the OAS Servers are able to access when users are running sessions. It is used to provide access to both user profiles, and data folders and files. The OFS is available for Linux based servers only. In a small OVD server farm, the OFS may reside on the same physical machine as the OAS. In larger installations, the OFS would typically be installed on dedicated hardware. 5.1 REQUIREMENTS All of the following Operating Systems are supported: RHEL 6.x / Centos 6.x 64 bits RHEL 7.x / Centos 7.x 64 bits Ubuntu server (LTS version only) 64 bits Minimum hardware configuration: CPU: 2 cores (4 cores recommended) Memory: 2 GB (4 GB recommended) Storage: 100+ GB. High speed disks with RAID-1 (15krpm, SSDs or SAN disks). Network: 1 GB NIC 5.2 INSTALLING ON UBUNTU (TRUSTY TAHR) Install the OFS package: # apt-get install inuvika-ovd-slaveserver-role-fs The only information required is the resource name where the OSM can be accessed (we use sm.test.demo here for the example, but of course, you have to set your own domain name). If you choose to install OFS on the same machine as OSM, enter for the resource name. The server should appear in the list of Unregistered Servers in the OVD Administration Console. If your server does not show up in the list, you might have a DNS configuration issue. Ensure that the firewall is correctly configured for the ports (Refer to section 2.3 "Firewalls and Ports") required by OVD Page 19

21 5.3 INSTALLING ON RHEL 6 AND CENTOS 6 Install the samba package: # yum install samba Configure and start the samba service # chkconfig smb on # service smb restart Install the OFS package: # yum install inuvika-ovd-slaveserver-role-fs Launch the configuration tool and configure the Session Manager address # ovd-slaveserver-config --sm-address sm.test.demo If you choose to install OAS on the same machine as OSM, enter for the resource name. Configure and the start the ovd-slaveserver service # chkconfig ovd-slaveserver on # service ovd-slaveserver restart The server should appear in the list of Unregistered Servers in the OVD Administration Console. If your server does not show up in the list, you might have a DNS configuration issue. Ensure that the firewall is correctly configured for the ports (Refer to section 2.3 "Firewalls and Ports") required by OVD 5.4 INSTALLING ON RHEL 7 AND CENTOS 7 Install the samba package: # yum install samba Configure and start the samba service # chkconfig smb on # service smb restart Install the OFS package: # yum install inuvika-ovd-slaveserver-role-fs Page 20

22 Launch the configuration tool and configure the Session Manager address # ovd-slaveserver-config --sm-address sm.test.demo If you choose to install OAS on the same machine as OSM, enter for the resource name. Configure and the start the ovd-slaveserver service # chkconfig ovd-slaveserver on # service ovd-slaveserver restart On CentOS 7, the server must be rebooted. The server should appear in the list of Unregistered Servers in the OVD Administration Console. If your server does not show up in the list, you might have a DNS configuration issue. Ensure that the firewall is correctly configured for the ports (Refer to section 2.3 "Firewalls and Ports") required by OVD Page 21

23 6. OVD WEB ACCESS (OWA) INSTALLATION AND CONFIGURATION The OWA server is responsible for managing browser-based client sessions. In Inuvika OVD, there are two types of browser-based sessions available. The first type of browser session requires an HTML5 compliant browser on the client machine but no software needs to be installed on the client machine. The second type of browser session uses a Java applet within the browser to communicate with the OWA. In this case, the OWA will install the Java applet if it is not already available in the browser. In both cases, the OVD session can be tunneled over an SSL session for secure data transmission. For small installations, it is possible to install OWA on the same machine as the OSM. For larger installations it is recommended to install one or more OWA systems on their OWA server and to load-balance the servers for optimal performance. In this example, we are using web.test.demo as the OWA resource name 6.1 REQUIREMENTS All of the following Operating Systems are supported: RHEL 6.x / Centos 6.x 64 bits RHEL 7.x / Centos 7.x 64 bits Ubuntu server (LTS version only) 64 bits Minimum hardware configuration: CPU: 2 cores recommended as a minimum Memory: 4 GB recommended as a minimum Storage: 20 GB Network: 1 GB NIC (2 for failover) 6.2 INSTALLING ON UBUNTU (TRUSTY TAHR) Install the OWA package: # apt-get install inuvika-ovd-web-access During the installation, you will be asked if you want to connect the OWA to an existing OSM. If you answered "yes" for the previous question, you will be prompted to enter the resource name of the OSM. In our example: sm.test.demo. The installer will prompt whether to enable HTTPS access to the OWA if it detects that HTTPS access is not already enabled on the system. If HTTPS access is enabled, after completing the installation, both HTTP and HTTPS access to the OWA will be available. To test whether the system is running, enter the OWA resource name (prefixed by HTTP or HTTPS) in your browser and you should see the OVD login page Page 22

24 6.3 INSTALLING ON RHEL 6 AND CENTOS 6 Install the EPEL repository. The EPEL repository is a separate repository which provides many additional software packages not provided by the default CentOS repositories. # yum install latest-6.noarch.rpm Install the OWA package: # yum install inuvika-ovd-web-access The HTML5 client is enabled by default and is configured to use a Tomcat server Launch the configuration tool and set the IP for the OSM # ovd-web-access-config Session Manager address [ ]: Select whether to enable HTTPS access to the OWA. This message is displayed only if HTTPS access is not already enabled on the system. If HTTPS access is enabled, after completing the installation, both HTTP and HTTPS access to the OWA will be available. Enable HTTPS support [yes] (yes or no): Configure and then start the Tomcat service # chkconfig tomcat on # service tomcat restart Configure and then start the guacd service # chkconfig guacd on # service guacd restart To test whether the system is running, enter the OWA resource name (prefixed by HTTP or HTTPS) in your browser and you should see the OVD login page 6.4 INSTALLING ON RHEL 7 AND CENTOS 7 Install the EPEL repository. The EPEL repository is a separate repository which provides many additional software packages not provided by the default CentOS repositories. # yum install latest-7.noarch.rpm Install the OWA package: # yum install inuvika-ovd-web-access The HTML5 client is enabled by default and is configured to use a Tomcat server Page 23

25 Launch the configuration tool and set the IP for the OSM # ovd-web-access-config Session Manager address [ ]: Select whether to enable HTTPS access to the OWA. This message is displayed only if HTTPS access is not already enabled on the system. If HTTPS access is enabled, after completing the installation, both HTTP and HTTPS access to the OWA will be available. Enable HTTPS support [yes] (yes or no): Configure and then start the Tomcat service # chkconfig tomcat on # service tomcat restart Configure and then start the guacd service # chkconfig guacd on # service guacd restart Restart the Apache service # service httpd restart To test whether the system is running, enter the OWA resource name (prefixed by HTTP or HTTPS) in your browser and you should see the OVD login page 6.5 ALL-IN-ONE INSTALLATION ON CENTOS 6 A complete installation with all the OVD roles on a CentOS server may raise a problem. Refer to the "All-in-One" article on the Inuvika Knowledge Base at for further details. 6.6 INSTALLING THE JAVA APPLET MODULE OWA offers two differents modes: HTML5 and Java applet. The Java applet mode is disabled by default. The Inuvika OVD Java applet will be deprecated in a future release. Browser manufacturers have announced that they will remove support for Java applet plugins which means that the OVD Java applet will no longer be available at that time INSTALLING ON UBUNTU (TRUSTY TAHR) To use the Java applet in this version of OVD, the Java applet module for your system must first be installed on the OWA and then the configuration file for the OWA modified to enable the Java module. # apt-get install inuvika-ovd-applets INSTALLING ON RHEL 6 AND CENTOS 6 To use the Java applet in this version of OVD, the Java applet module for your system must first be installed on the OWA and then the configuration file for the OWA modified to enable the Java module. # yum install inuvika-ovd-applets Page 24

26 6.6.3 INSTALLING ON RHEL 7 AND CENTOS 7 To use the Java applet in this version of OVD, the Java applet module for your system must first be installed on the OWA and then the configuration file for the OWA modified to enable the Java module. # yum install inuvika-ovd-applets 6.7 ADVANCED SETTINGS DESCRIPTION In the login window, the user can set advanced parameters by clicking the "Advanced settings" button. Mode: This option allows you to pick which session mode you want to use. Desktop: The OWA will display a full desktop with OVD applications integrated within it. Portal: The OWA will display a window with a list of available OVD applications. This mode will provide a seamless user experience in which the user can interact with the applications as though they were installed and running locally subject to the security limitations imposed by HTML5. Type: This option allows you to switch between HTML5 or Java Java: Launch an OVD session using the Java applet (disabled by default with a fresh install). The Java mode can be enabled by modifying the OWA configuration file /etc/ovd/webaccess/config.inc.php. Further details are available in the Inuvika OVD Administration Guide. HTML5: Launch an OVD session using an HTML5 compliant browser Language: This option allows you to pick which language your OVD session will use. Page 25