INUVIKA TECHNICAL GUIDE

Transcription

1 INUVIKA TECHNICAL GUIDE ENTERPRISE EVALUATION GUIDE OVD Enterprise External Document Version 1.1 Published Passing on or copying of this document, use and communication of its content not permitted without Inuvika written approval

2 PREFACE The purpose of this document is to simplify the process of evaluating Inuvika OVD 1.X Enterprise. It also describes how to implement an Inuvika OVD Enterprise evaluation environment to avoid the pitfalls of an evaluation without having in-depth training on the product. The methodology used in this document is for evaluation purposes only and should not be used for a production environment. Page 2

3 HISTORY Version Date Author Comments yy-mm-dd Roy Heaton/Richard Tang Updated document and added Demo Appliance information Agostinho Tavares Published the first version of the document Page 3

4 TABLE OF CONTENTS 1. INTRODUCTION Overview OVD Concepts OVD Demo appliance OVD Evaluation Platform Components Deploying the Evaluation Platform Pre-Requisites Related Documentation DEPLOYING THE DEMO APPLIANCE Importing the Demo Appliance into Virtual Box Changing the Network Configuration for the Appliance OVD Console Menu Options Configure the Network Configure the Keyboard Update the System Reboot the System Open a root console Exit Connecting to the Demo Appliance Enabling Enterprise Features ACCESSING OVD COMPONENTS Web Access HTML 5 Access Java Access Access URL Advanced settings Enterprise Desktop Client Pre-Requisites Client Installation Running The Enterprise Desktop Client Linux Applications and Desktop Evaluation Web Access Enterprise Client Adding a New Linux Application Command Line Installation Publishing a New Application Page 4

5 3.4.3 Command Line Installation Using the GUI USING A WINDOWS OVD APPLICATION SERVER Deploying the RDSH Role on Windows 2012 / 2008R Windows server Windows 2008 R Installing The OVD Application Server Agent Registering the Windows OAS Installing an Application on the Windows OAS Publishing Applications WIDE AREA NETWORK ACCESS Pre-Requisites Virtual Machine Setup Create a Virtual Box VM Installing an Ubuntu Server Configuring the Ubuntu Server Installing the Enterprise Secure Gateway Role Configuring ESG for use with Inuvika OWA Connecting to the Inuvika OVD Environment via the Internet OVD EVALUATION USING A FULL OVD INSTALLATION Evaluation Using An Ubuntu Server Installing the Ubuntu Server Configuring the Ubuntu Server Installing the OVD Components Enabling the Enterprise Features Evaluation and Other OVD Roles BIBLIOGRAPHY Page 5

6 CONVENTIONS The table below shows the typing conventions used in this document. These conventions denote a special type of information. Typing convention Information type Bold-face text Dialog Fields Commands Buttons File names Italics Document References Double Quotes Menu Options Page 6

7 1. INTRODUCTION 1.1 OVERVIEW This document aims to simplify the evaluation of Inuvika OVD 1.x Enterprise. It describes how to set-up an environment to properly evaluate the features offered by Inuvika OVD Enterprise. To ease the evaluation implementation, it is recommended to use a virtual platform, which can be either an Oracle Virtual Box, a VMware Workstation/Player or an ESXi/vSphere environment. Other virtualization technologies are also supported and can be used when performing a full product installation. To learn more about the installation process, refer to Chapter 0 OVD Evaluation Using a Full OVD Installation. Note: In this guide, the virtualization technology used is Oracle Virtual Box. Virtual Box needs to be installed prior to evaluating the Inuvika OVD Enterprise product. For a complete list of Inuvika OVD Enterprise features, refer to Inuvika OVD FS Overview, available at Figure 1: Inuvika OVD 1.x Evaluation Platform 1.2 OVD CONCEPTS OVD comprises of components. The collection of components that make up a full end-to-end working virtual desktop system is referred to as the OVD Farm. The minimum amount of components to make a functional OVD Farm consist of: OVD Session manager, OVD Administration Console, at least 1 OVD Application Server, and an OVD Web Access. The OVD Page 7

8 Farm can be extended, provided that the Enterprise licensing is applied, with more components for added extensibility, resiliency and more features. Please refer to section 1.4 below for more detail of these enterprise components. 1.3 OVD DEMO APPLIANCE There are two versions of OVD. Foundation Server is the basic OVD setup and allows one to evaluate OVD using one Application Server. The OVD Demo Appliance provides the functionality of the OVD Foundation Server packaged as an appliance. It can be upgraded to OVD Enterprise to allow an evaluation of the complete set of OVD features and to be able to connect multiple Application Servers. For a description of the features available in each version please refer to the Feature Summary document available on the Inuvika web site. 1.4 OVD EVALUATION PLATFORM COMPONENTS The components involved in the OVD Evaluation Platform are described below: 1. OVD Demo Appliance (ODA): Mandatory. The ODA is a ready-to-use virtual machine containing all the required OVD Linux components. This is in an OVA format, which is an importable Virtual Machine format that is compatible with VirtualBox, VMWare Player and ESXi. This Demo Appliance contains all of the components of OVD which one would normally install on separate servers. The Demo appliance contains these OVD components: o OSM: OVD Session Manager o OAC: OVD Administration Console o Linux OAS: Linux Application Server. This is a Linux server that will host applications which OVD can serve. o OFS: OVD File Server o OWA: OVD Web Access 2. Windows OAS: Windows Application Server. This is a Windows server that will host applications which OVD can serve. This is not contained in the OVD Demo Appliance. 3. ESG: Enterprise Secure Gateway. This is required only when evaluating Inuvika OVD from outside the corporate firewall via the Internet. This is not contained in the OVD Demo Appliance. Note: The IP addresses and/or Fully Qualified Names (FQDN) used in this documentation are for demonstration purposes only. Please use your own information that corresponds to your network configuration. Page 8

9 1.5 DEPLOYING THE EVALUATION PLATFORM The deployment instructions for the evaluation platform are described in the following chapters and allow the evaluator to use the OVD under these circumstances: 1. Local Network (LAN) access. The Demo Appliance assumes it is deployed in an internal LAN and that the one would be accessing it from within the LAN and same subnet. o Linux Applications only (by default). The Demo Appliance is based on a Linux operating system and so any applications which will be served will be Linux applications. o Windows Applications only (optional). Since the Demo Appliance is a Linux operating system, a separate Windows server (a separate VM) will be needed in order to provision Windows Applications via OVD o Both Linux and Windows applications 2. Internet Access (optional) 3. Installation from product repositories (optional). Should one want to install additional applications to be served by OVD, the Demo Appliance must have access to the repositories or Internet sources to successfully install them. Note: If there is no requirement to evaluate Windows application support, skip the Windows Applications step. If there is no requirement to access the system via the Internet, then the Internet Access step is not required. 1.6 PRE-REQUISITES This document will provide specific steps/recommendations to setup the Demo Appliance VM using Virtual Box. 1. Virtualization Layer: The latest available Virtual Box software must be installed with the default settings on your host system. Guest Virtual Machines will be configured to use network bridging (using the Host s LAN resources). 2. OVD Demo Appliance (ODA): This is self-contained VM in OVA format. The latest ODA version can be downloaded at The filename for the ODA is of the form Inuvika-OVD-1.x.x-Demo-Appliance.ova. Before starting the appliance, set the memory configuration to 4GB RAM. 3. Host Operating System (Virtual Box host): A modern Windows, MAC OSX or Linux system is required with 12GB or more RAM, a fast CPU with four multi-cores from Intel and a fast disk subsystem (preferably SSD) with a minimum of 100GB free storage available. The Host must be able to connect to the LAN environment and have access to the Internet. Page 9

10 4. Enterprise Secure Gateway (ESG): Optional component on a Linux server. However when evaluating it, ensure the Linux system has these minimum settings: 1 GB RAM, 1 vcpu, 10 GB storage (thin provisioning) Ubuntu server ISO 5. Windows OAS: Optional. A Windows Server is needed to be on and in the same LAN and be able to communicate with the Demo Appliance. Windows Server 2012 R2 ISO is required. The virtual machine must have: 4GB RAM or more 1vCPU or more 100GB disk space (thin provisioning) For the Windows Server ISO, follow the procedure mentioned by Microsoft TechNet Evaluation Center (Microsoft, 2015). 6. Web Access (OWA): OVD is accessible by a web browser using this component. Ensure that the user device meets the minimum requirements to connect using a web browser. For the minimum required configuration specifications, refer to Architecture Overview and System Requirements at RELATED DOCUMENTATION Inuvika provides access to all documentation for OVD at The following Foundation Server documents provide relevant reference information for the evaluation. This documentation is available at Architecture Overview and System Requirements Enterprise Activation Guide Installation and Configuration Guide Inuvika OVD FS Overview Additionally, the following OVD Enterprise document provides reference information for the Enterprise Desktop and Mobile Clients. Enterprise Client Guide Inuvika OVD Administration Guide Enterprise Secure Gateway Guide Page 10

11 2. DEPLOYING THE DEMO APPLIANCE Download the Inuvika ODA file (filetype OVA) from the Inuvika archive repository available at IMPORTING THE DEMO APPLIANCE INTO VIRTUAL BOX 1. Run Virtual Box on a Host that is in your Local Area Network. 2. From the Virtual Box File menu, choose Import Appliance. Navigate to the downloaded OVA file location. Figure 2: Appliance Settings 3. Click Import and Accept the License Agreement. Figure 3: Importing Demo Appliance Page 11

12 4. Once the import is finished, you will see the screen below indicating that the VM has been imported and can be run. The VM settings are preset from the import process. It assumes a physical network connection. Click Start. Figure 4: Inuvika OVD Demo Appliance 5. Ensure the Network Adaptor is enabled, and attached to Bridged Adaptor. The Name must match the type of network adapter that is connected to your LAN. For example if you are running it from a Laptop/Desktop that has no physical network cable attached to your LAN, and it is connected wirelessly, choose the Wireless adapter. Figure 5: Demo Appliance-Settings NOTE: If the error shown in Figure 6 pops-up, edit the VM settings/network configuration and verify it is using the correct network settings. Page 12

13 Figure 6: Error Message 6. Start the VM. Select the keyboard settings that match your system when prompted. Note: This is required only if you want to change the appliance configuration Figure 7: Keyboard Settings 7. After clicking OK, the OVD Demo Appliance console (ODA Console) will appear. The Appliance is connected to your LAN when the IP is displayed and corresponds to your network s LAN. DHCP is assumed. If your network does not have a DHCP server than the Demo Appliance network needs to be configured to use an unused static IP. To set the IP manually follow the instructions in section below. Page 13

14 Figure 8: ODA console 2.2 CHANGING THE NETWORK CONFIGURATION FOR THE APPLIANCE If the ODA Console as shown in Figure 8 above displays an IP address of the form , the DHCP (Dynamic Host Configuration Protocol) configuration is working correctly and the following steps 1-6 can be skipped. Note: For evaluations of a longer duration, it is recommended to use a Static Network Configuration. 1. Login to the ODA and open a root console with the default login and password (inuvika/inuvika). On the next screen, highlight Open a root console and click OK. Page 14

15 Figure 9: Console 2. A command prompt will then appear, similar to the screen below: Figure 10: Demo Appliance Command Prompt 3. Edit the network interfaces file by typing the below command: nano /etc/network/interfaces Note: nano is a Linux text editor. You can choose your own preferred text editor. Page 15

16 4. The primary network interface information will be displayed: Figure 11: Demo Appliance Network Interface Details 5. Change the settings so that they correspond to your own environment. Save the file (CTRL-w) and exit the editor (CTRL-x). 6. Reboot the system by entering the reboot command. Upon reboot, the console will display the access IP address. If it does not display the access information, it is recommended to change your network settings. 2.3 OVD CONSOLE MENU OPTIONS The Inuvika OVD Demo Appliance has 6 configuration tools as shown in figure 12 below: Figure 12: Inuvika Configuration Tools Page 16

17 2.3.1 CONFIGURE THE NETWORK Configure the Network option has 3 network settings that you can choose: Figure 13: Configure the Network-Network Settings ENABLE DHCP This option will configure the network to use DHCP and then ask you to reboot your system to activate the change. Figure 14: Enable DHCP Page 17

18 MANUAL IP This option can be used to configure a static network. The IP address, netmask, gateway and DNS information can be entered. After saving the information, the system will prompt for a reboot to activate the changes. Figure 15: Configure Static Network BACK Returns to the higher level menu item CONFIGURE THE KEYBOARD This option configures keyboard layout to be used in the demo appliance Figure 16: Keyboard Settings Page 18

19 2.3.3 UPDATE THE SYSTEM This option will perform an update of the entire system REBOOT THE SYSTEM This option will reboot the demo appliance OPEN A ROOT CONSOLE This option opens a root console command prompt EXIT Exit the Inuvika Configuration Tools 2.4 CONNECTING TO THE DEMO APPLIANCE Once the networking has been set and the Appliance is connected to the network, attempt to view the Welcome page. Open a web browser and enter the IP of your demo appliance. The browser should display the Inuvika Demo Appliance welcome page similar to the screenshot in figure 17 below: Figure 17: OVD Demo Appliance Main Page Page 19

20 To familiarize oneself with the OVD configuration, go to the OVD Administration Console page. Click the Administration Console using the mouse and click to select. A screen similar to the image below will be presented in a new browser tab: Figure 18: OVD Administration Console Login Refer to the Inuvika OVD Administration Guide for a description of the Administration Console functionality. 2.5 ENABLING ENTERPRISE FEATURES By default, the ODA is pre-configured with Inuvika OVD Foundation Server. The Foundation Server provides the basis for running an OVD farm but does not provide all the functionalities described in this evaluation guide. To create an evaluation environment with the Enterprise features enabled, follow the steps below: Request an evaluation key at Follow the steps described in the Enterprise Activation Guide to complete the activation of the OVD Enterprise features. The document is available at Page 20

21 3. ACCESSING OVD COMPONENTS In this chapter, we will evaluate Inuvika OVD from within the firewall and access the system using a browser from within the LAN. The evaluation process will begin with the Linux Application Server as this is provided out-of-box with the ODA. After this, we will add a Windows Server to the OVD evaluation platform. Figure 19: Inuvika OVD 1.x Evaluation Platform 3.1 WEB ACCESS OVD is versatile and can establish a virtual desktop in many ways. The web access is the most popular way, and one can establish a Virtual Desktop session by using a web browser to access OVD. The web access URL is IP]/ovd/ Note: Before accessing the OVD farm, ensure that the user device meets the minimum requirements to connect using a web browser. Refer to the Architecture Overview and System Requirements document HTML 5 ACCESS HTML5 access requires a modern web browser and is supported across all client platforms and devices without the need to install any additional software on the client device. Users will get the same user experience from a tablet as from a Windows 8 platform. The HTML5 client for OVD has some limitations regarding access to local resources when compared to the OVD Java applet, specifically smartcard support and limited printer support JAVA ACCESS The OVD Java Applet is able to provide an evaluation of all the OVD features that require access to local resources such as the local disk. The user system must have a Java runtime installed in Page 21

22 order to connect to in this mode. A check is performed when accessing the OVD Web Access URL for the first time, to detect whether Java is available on the user s device. If Java is not available, the Web Access uses HTML5 access by default. If Java is available, then the OVD Java Applet will be downloaded and installed in the browser. The user will be prompted to confirm access by the security settings of the Java runtime. Browser manufacturers are gradually phasing out support for Java Applets as HTML5 becomes more prevalent ACCESS URL Open your web browser and enter the URL Replace the IP address with the address corresponding to your own environment Note: The password for a user is the same as the login. Figure 20: Login Screen ADVANCED SETTINGS The advanced settings allow the user to select various session settings to be used for the session as described below: Figure 21: Advanced Settings Page 22

23 DESKTOP MODE AND PORTAL MODE There are 2 access modes available when accessing OVD using a web browser. In Desktop Mode, application icons are dynamically created within a Linux or Windows virtual desktop. Figure 22: Desktop Mode In Portal Mode, the published applications are presented as a multi-column list contained in a web portal together with a web based file management application. This provides a seamless presentation just as if they were installed and running locally. Note: In Java applet mode, applications run seamlessly out of the web browser. In HTML5 mode, applications run embedded in the web browser window. Page 23

24 Figure 23: Portal Mode TYPE The user may select either to start a Java based session or an HTML5 session FULL SCREEN The user may select to the session in full screen mode LANGUAGE The user may select a different language to be used for the session. Page 24

25 3.2 ENTERPRISE DESKTOP CLIENT The Enterprise Desktop Client provides the best option for corporate managed workstations. Windows, Linux and MAC OSX platforms are supported. The software can be fully integrated into the local operating system. It is possible to configure the client with a single sign-on (SSO). Thus it does not require an additional authentication other than the ones used to open a local operating system session (Not covered in this documentation. This requires strong Linux skills for set-up). The Enterprise Desktop client can be run with additional command line parameters for a better integration PRE-REQUISITES This client requires Inuvika OVD Enterprise to be activated and the client installed on the workstation CLIENT INSTALLATION Download the corresponding archive file from For the MAC, download and install the dmg file, for Linux use the tar.gz file and for Windows use the.exe file. For detailed installation information, refer to the Enterprise Clients Guide RUNNING THE ENTERPRISE DESKTOP CLIENT Login Screen: With More Options: Figures 24: Enterprise Client Login Screen Page 25

26 This client offers two connection modes: Desktop mode: This is the recommended mode for legacy workstations or thin client devices coupled with full screen configuration. Application mode: This is the recommended connection method on most configurations as applications are integrated seamlessly into the local operating systems. 3.3 LINUX APPLICATIONS AND DESKTOP EVALUATION The Inuvika Demo Appliance (ODA) is delivered with the latest OVD software and ready for evaluation with a set of common Linux applications already installed and Inuvika OVD set-up with test user accounts. It is then possible to evaluate Inuvika OVD 1.x with further configurations. The ODA runs the main Linux Inuvika OVD roles (on the same machine), which are: OSM: Inuvika OVD Session Manager OAS: Inuvika OVD Applications Server (Linux) OFS: Inuvika OVD File Server OWA: Inuvika OVD Web Access (provides user access via a modern web browser) OAC: Inuvika OVD Administration Console WEB ACCESS Connect to the virtual appliance Web Access URL with your favorite web browser. In the scenario being described this would be replace the IP address with the IP address of your demo appliance ENTERPRISE CLIENT Enter the login name of a user that can be seen on the OVD Administration Console (Users page). Enter the IP address of the demo appliance as the server, which is in our scenario. 3.4 ADDING A NEW LINUX APPLICATION Adding applications to the Linux OAS server is specific to each Linux distribution. In this documentation, we will cover Ubuntu LTS (64bit) but the principals apply to other distributions. Page 26

27 In Linux, application set-up may require command line installation or it may require a GUI for installation COMMAND LINE INSTALLATION Note: GUI stands for Graphical User Interface In this example, we will install LibreCAD (a comprehensive 2D CAD drawing tool based on the community edition of QCAD). 1. Login to the Linux OAS (in the OVD Evaluation Platform the Linux OAS is installed on the OVD virtual appliance) o Login: inuvika o Password: inuvika 2. Select menu item no. 5 (Open a root console) 3. Run the following commands to install the software package: apt-get install software-properties-common add-apt-repository ppa:librecad-dev/librecad-daily apt-get update apt-get install librecad PUBLISHING A NEW APPLICATION To publish a new application follow the steps below: 1. Connect to the OVD Administration Console at (using your own IP address) and enter admin as the login and password 2. Navigate to the applications page and verify that the application (LibreCAD) is listed. Note: Refreshing the browser may be required (pressing F5 on the keyboard) to display the newly added application(s). 3. After locating LibreCAD, click on the LibreCAD application name. The system will display the details for the application similar to the details shown in Figure 25. Page 27

28 Figure 25: LibreCAD Application Page 4. Click the Add to this group button. This will publish the application to the some applications Applications Group and make it available for users who have access to that Application Group which by default on the demo appliance is all the users COMMAND LINE INSTALLATION USING THE GUI The Demo Appliance is an amalgamation of OVD components. This appliance is useful to show how easy and versatile it is to manage your own OVD Farm, which its components would normally be distributed among multiple servers. In the following exercise we demonstrate how one would install programs using a GUI on the application server: 1. Login to the Linux OAS (which is running on the Demo Appliance for the OVD Evaluation Platform) o Login: inuvika o Password: inuvika 2. Select menu No 5 (Run a root console) 3. Install the xfce terminal application. apt-get update apt-get install xfce4-t 4. Publish the terminal application. See the previous section for information on how to publish the application Terminal Emulator. 5. Define a password for user root. passwd root Page 28

29 6. Use a web browser to connect to OVD as a normal user o Login: Enter the login for one of the available users. o Password: same as login 7. Click on Advanced Settings and make sure the mode is set to Desktop. Figure 26: Advanced Settings Page 8. Connect to the user session 9. Run the terminal application from the user desktop 10. Run the following command and enter the password for the user root su root 11. Install the application as recommended by the vendor. Page 29

30 4. USING A WINDOWS OVD APPLICATION SERVER OVD is not limited to publishing Linux programs to the Virtual Desktop. It also supports publishing Windows applications. A Windows Application Server simply needs to be installed on the same LAN and registered as an active Application Server in your OVD Farm. Inuvika OVD Windows Applications Server (OAS) can be run on Windows 2003 SP2/R2 (32 or 64 bit), Windows 2008 R2 SP1 and Windows 2012 R2. Note: The Windows Application server cannot be a domain controller Windows 2003 R2 SP1 must be running Terminal Services in application server mode Windows 2008/2012 must have the Remote Desktop Session Host role deployed Note: A grace period runs from the first TS/RDS installation. In some scenarios, the TS/RDS licensing service will have to be installed and properly licensed for OVD to run with Windows OAS. To avoid any unforeseeable complications, it is recommended that the Windows server be a fresh installation with no other services/roles installed other than those required by OVD. 4.1 DEPLOYING THE RDSH ROLE ON WINDOWS 2012 / 2008R2 Note: In this document, we will document using Windows Server 2008 R2 and 2012 R2 but not Windows 2003 server. For all Windows operating systems, it is important that the Windows server is a fresh installation with only the default settings WINDOWS SERVER 2012 Follow the steps below to install the RDSH role on Windows Server 2012: Run the Server Manager and select Local Server From the Manage menu, select Add Roles and Features Select Role-based or feature-based installation from the Installation option Select Remote Desktop Services from Server Roles page click Next from features page Select ONLY Remote Desktop Session Host on the Role Services page From the associated features page, accept all and click Add Features Tick the box for server restart after role deployment and click Install Page 30

31 After completing the installation, the system will need rebooting. After reboot Run the Server Manager and select the Local Server Click the Windows Firewall. From the Windows Firewall page: o Click Turn Windows Firewall on or off o Click Turn off Windows Firewall for Private, Public and Domain (if apply) network settings o Close Windows Firewall properties page Click the Remote Desktop link o Uncheck the box Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended) o Press OK and close the Window WINDOWS 2008 R2 Follow the steps below to install the RDSH role on Windows Server 2008: Run Server manager if not already started. Select Roles from the left pane. Then select Add Roles from the right pane. Select only Remote Desktop Services then click Next Select only Remote Desktop Session Host then click Next Select Do not require Network Level Authentication and click Next in the Authentication method Select Configure later then click Next in Licensing mode Click Next on Users or Groups selection Click Next on the clients experience Click Install Restart when prompted After completing the installation, the system will need rebooting. After Reboot Run start/control panel/system and security Then from the right pane Windows Firewall configuration, Check Firewall status then Turn Windows Firewall on or off from the left pane. Turn off the Windows Firewall for any location then click OK. Page 31

32 4.2 INSTALLING THE OVD APPLICATION SERVER AGENT To allow a Windows Server to become part of the OVD Evaluation Platform, the OVD Windows Application Server Agent must be installed. The steps below document the procedure to follow: Download the agent (Inuvika-OVD-1.x.x-ApplicationServer.exe) from to the Windows server. Run the installer on the Windows server Accept the license agreement Accept the default installation path Enter the OSM IP address (in our scenario this will be ) A security popup will show up regarding the Inuvika printer, click the Install button Click Finish and allow it to restart the server. The OVD Agent service will automatically start and communicate with your OVD Farm. You can now set the new server as an active application server in your OVD Farm. For more information, refer to the Installation and Configuration Guide available at REGISTERING THE WINDOWS OAS Once the Windows OAS has restarted with the Inuvika OVD agent installed, you must register the Windows OAS in the OVD Administration Console. 1. Connect to the OVD Administration Console at (using your own IP address) and enter admin as the login and password 2. Click the Servers page and then the Unregistered Servers tab 3. Click Register on the Windows server that is displayed. The system will now register the server and the applications available on the server. 4. When the registration is complete, the Servers page will be displayed. Click Switch to production to set the server to production mode The Windows OAS is now ready for use. 4.4 INSTALLING AN APPLICATION ON THE WINDOWS OAS Windows applications developed for end users of your system must be installed properly on one or more OAS servers so they can be accessed remotely. To install an end-user application on a RD Session Host server, the RD Session Host server must first be switched into a special install mode called RD-Install to ensure that the application will be able to run in a multi-user environment. After your applications have been installed on your Page 32

33 RD Session Host server, you must switch the server back into execution mode (RD-Execute) before users can remotely connect to your server. You can switch between the RD-install and RD-execute modes from the command line using these commands: change user /install change user /execute 1. Open a cmd.exe window 2. Run the following command: change user /install 3. Proceed with the application installation 4. When the application installation is finished and before rebooting the server (if required), run the command below: change user /execute 5. Reboot server (if required) 4.5 PUBLISHING APPLICATIONS 1. Connect to the OVD Administration Console at (using your own IP address) and enter admin as the login and password 2. Navigate to the Applications page. Note: If the newly installed application does not show up, press F5 on the keyboard to refresh the list of applications. 3. Click on the application link. The details for the application will be displayed similar to figure 27 below. Page 33

34 Figure 27: Application Details 4. Click the Add to this group button. This will publish the application to the some applications Applications Group and make it available for users who have access to that Application Group which by default on the demo appliance is all the users. 5. Connect to OVD as a user and run the Windows application Page 34

35 5. WIDE AREA NETWORK ACCESS This chapter presents an overview on how to access Inuvika OVD securely from outside the network. The Inuvika Enterprise Secure Gateway (ESG) provides secure access to Inuvika OVD using SSL tunneling technology and is required when accessing OVD from an Enterprise Client or using the Java Applet within the browser via the Internet. It may also be used with the HTML5 client but is not required since the OWA may be configured to provide access via SSL. In this example, the ESG will be configured to work with the HTML5 client. The ESG is specifically tailored to provide secure access to an OVD server farm and offers a secure entry point to OVD from outside the firewall. The ESG requires the use of port 443 only and firewalls will normally have the TCP 443 port open so no further firewall configuration is required. The Inuvika Enterprise Secure Gateway (ESG) requires a dedicated Linux server (physical or virtual). In this guide, we will use an Ubuntu x Linux server to deploy the ESG. Figure 28: Evaluation Platform 5.1 PRE-REQUISITES The Enterprise Secure Gateway is a component to be installed on a new separate Linux instance. 1. Download the server ISO from Ubuntu available at: Inuvika OVD 1.x is supported on Ubuntu x LTS. 2. Set-up an incoming TCP rule on your firewall. This rule must allow incoming TCP 443 traffic and forward the traffic to the ESG server. Inuvika OVD requires TCP 443 to be open on the firewall. Consult your system administrator to enable/activate this rule. Page 35

36 5.2 VIRTUAL MACHINE SETUP The ESG server will be installed on an Ubuntu x server. Assuming your evaluation is on Virtual Box, please follow the steps laid out in section Adjust the steps to match your virtual host environment (eg VMWare workstation/esxi). Note: If you prefer using RHEL/CentOS, contact your sales representative at Inuvika CREATE A VIRTUAL BOX VM From the Virtual Box GUI, create a new virtual machine. 1. Name and Operating System Name: ESG or any name you prefer Type: Linux Version: Ubuntu (64 bit) 2. Memory size Set 1024MB or more 3. Hard Drive Type Accept the default (create a virtual hard drive now with 8GB) Select VDI as the hard drive type (or your preferred one) Select dynamically allocated File location and size: accept the default 4. Select the newly created VM and click the settings button Storage : o Select the CD/DVD icon from the left Storage tree o Click the CD/DVD icon from the Attributes menu and browse for the Ubuntu ISO Network : Set the Adapter 1 to Bridge Adapter ( NAT by default) INSTALLING AN UBUNTU SERVER Follow the steps below to install the Ubuntu server. 1. Select the ESG VM then click Start from the Virtual Box GUI 2. Select your preferred language then press enter 3. Select Install Ubuntu Server 4. Select the installation language 5. Select the location 6. Skip keyboard detection unless you need it 7. Select the appropriate keyboard from the list 8. Configure the network settings Page 36

37 Enter the hostname. We will use esg in our example Enter a username for your account. We will use inuvika in our example Enter a password. We will use inuvika in our example Accept weak password: Select yes unless you set a strong password Encrypt your home directory: Select no Accept the time zone 9. Partition the disks Accept the default (guided use entire disk and set up LVM) Press enter for the disk partition that is displayed Write changes to the disks and configure LVM? : Select yes (use TAB key) and press enter For the partition size, accept the default and press ENTER. Write changes to disks : Select yes (using the TAB key) then press ENTER 10. Configure package manager HTTP proxy: Put in relevant configuration if required and select continue using the TAB key Automatic updates: Accept the default no automatic updates and press ENTER Software selection: Check OpenSSH server only (using the SPACE bar) and use the TAB key to select continue Install GRUB boot manager: Default yes, press ENTER Finish Installation The server will be rebooted automatically CONFIGURING THE UBUNTU SERVER By default, the Ubuntu server is configured to use an IP from the DHCP server (if available). If you are ok with this IP, continue to next. 1. Login to the Ubuntu server console Login: inuvika Password: Inuvika 2. Run the following command: sudo edit /etc/network/interfaces Enter the password inuvika when requested Page 37

38 3. Change: # The primary network interface auto eth0 iface eth0 inet dhcp To: # The primary network interface auto eth0 iface eth0 inet static address netmask gateway dns-nameservers dns-search inuvika.demo Your configuration will be different, change your network settings accordingly 4. Reboot the server for changes to take effect by entering the following command: # reboot 5.3 INSTALLING THE ENTERPRISE SECURE GATEWAY ROLE 1. Login to the Ubuntu server console: Login: inuvika Password: inuvika 2. Edit/create the repository file: sudo nano /etc/apt/sources.list.d/ovd.list Enter the password inuvika when requested. 3. Add the following repository: deb trusty main Page 38

39 4. Save the edits and exit the editor 5. Install the keyring for the OVD packages: sudo wget -O- " apt-key add - Enter the password inuvika if requested 6. Update the package database: apt-get update 7. Install the ESG server role sudo apt-get install inuvika-ovd-slaveserver-role-gateway 8. Enter the Session Manager FQDN or IP address. In this example we are using The ESG Gateway is now installed but does not have a link to the OWA CONFIGURING ESG FOR USE WITH INUVIKA OWA This section describes the configuration required for using the OWA through the ESG. 1. Edit the gateway configuration file sudo nano /etc/ovd/slaveserver/slaveserver.conf 2. In the Gateway section, add the lines below where is the address of the OWA server. Replace this address with the address in your environment. This is the IP of the OVD Demo Appliance. [Gateway] # web_client = http[s]://ip[:port]/ web_client = Page 39

40 3. Save the changes and exit the editor. 4. Restart the ESG service sudo /etc/init.d/ovd-slaveserver restart Enter your password if requested Note: The Inuvika ESG runs with an auto-generated SSL certificate. In a production environment, a signed certificate should be installed. 5.4 CONNECTING TO THE INUVIKA OVD ENVIRONMENT VIA THE INTERNET Inuvika OVD access from the Internet requires that the ESG server be accessible through TCP 443. OVD clients (Web Access, Enterprise client, tablet clients ) will connect to the FQDN/Public IP address of the ESG server over HTTPS. Web Access portal: Enterprise Client & Tablet Clients: In the server field, enter the public IP address or FQDN of the ESG server. Note: For user convenience, it is best to associate the public IP address with a properly registered fully qualified domain name (FQDN). Note: Users will have a certificate warning similar to the one below, as the certificate is not signed by a public certification authority (a self-signed certificate). Page 40

41 Figure 29: Untrusted Connection 6. OVD EVALUATION USING A FULL OVD INSTALLATION By following the previous chapters, the example illustrates how the OVD Demo Appliance can be used to evaluate Enterprise features and components. In a real production scenario, one would not use the Demo Appliance -- A full OVD Farm with its componenets separately installed on dedicate Linux servers is recommended for highavailability, fault-tolerance, and maximum performance and security. As with any enterprise product, the following considerations need to be made: No compatible virtualization layer (Oracle Virtual Box or VMware) to support the deployment of the Inuvika Demo Appliance (ODA) eg the deployment is targeted on XenServer, Microsoft Hyper-V or other solutions Deciding to use physical servers Evaluation without the provided ODM platform The diagram below depicts the standard Inuvika OVD Evaluation Platform. Page 41

42 Figure 30: Evaluation Platform A compatible operating system must be installed prior to Inuvika OVD server components that meets the Inuvika OVD pre-requisites. See Architecture Overview and System Requirements for details. For the evaluation platform we will use: 1. OSM server: A Vanilla Ubuntu x server installation is recommended. The following Inuvika OVD server roles will be deployed on that server: a. OSM b. OWA c. OAC d. OFS e. Linux OAS 2. Windows OAS server (optional): If Windows applications and Desktops are to be evaluated 3. ESG server (optional): If Internet access is to be evaluated. Note: For the OSM server, the other roles, particularly the Linux OAS role may be optionally deployed on a separate server with the same pre-requisites. 6.1 EVALUATION USING AN UBUNTU SERVER The steps below describe how to install an Ubuntu server on the OSM server with the hostname osm. Page 42

43 6.1.1 INSTALLING THE UBUNTU SERVER Insert the Ubuntu server ISO into the server (virtual machine or appliance) 1. Run the Ubuntu Server installation 2. Select your preferred language then press enter 3. Select Install Ubuntu Server 4. Select the installation language 5. Select the location 6. Skip keyboard detection unless you need it 7. Select the appropriate keyboard from the list 8. Configure the network settings Enter the hostname. We will use osm in our example Enter a username for your account. We will use inuvika in our example Enter a password. We will use inuvika in our example Accept weak password: Select yes unless you set a strong password Encrypt your home directory: Select no Accept the time zone 9. Partition disks. Accept the default (guided use entire disk and set up LVM) Press enter for the disk partition that is displayed Write changes to the disks and configure LVM? : Select yes (use TAB key) and press enter For the partition size, accept the default and press ENTER. Write changes to disks : Select yes (using the TAB key) then press ENTER 10. Configure package manager HTTP proxy: Put in relevant configuration if required and select continue using the TAB key Automatic updates: Accept the default no automatic updates and press ENTER Software selection: Check OpenSSH server only (using the SPACE bar) and use the TAB key to select continue Install GRUB boot manager: Default yes, press ENTER 11. Finish installation The server will be rebooted automatically. Note: Do not install Apache, MySQL etc Any packages required by OVD will be installed when installing the OVD package. Page 43

44 6.1.2 CONFIGURING THE UBUNTU SERVER By default, the Ubuntu server is configured to use an IP from the DHCP server (if available). If you are ok with this IP, continue to next. 1. Login to the Ubuntu server console Login: inuvika Password: Inuvika 2. Run the following command: sudo edit /etc/network/interfaces Enter the password inuvika when requested 3. Change: # The primary network interface auto eth0 iface eth0 inet dhcp To: # The primary network interface auto eth0 iface eth0 inet static address netmask gateway dns-nameservers dns-search inuvika.demo Change the network settings to comply with your environment 4. Reboot the server for changes to take effect by entering the following command: # reboot Page 44

45 6.1.3 INSTALLING THE OVD COMPONENTS This section describes how to install the OVD components on the OSM server. 1. Open a session on the Ubuntu server either on the appliance console or using SSH 2. Enter the user credentials: Login: inuvika Password: inuvika 3. Follow the instructions for Ubuntu in the Installation and Configuration Guide documentation for each component. The following roles should be installed: OSM OAC OAS OFS OWA ENABLING THE ENTERPRISE FEATURES To enable OVD Enterprise, first request an evaluation key using the web form at and once the key has been received, follow the steps in the Enterprise Activation Guide to enable the Enterprises features. 6.2 EVALUATION AND OTHER OVD ROLES To install the ESG Component, refer to the information in the document Enterprise Secure Gateway Guide Page 45

46 7. BIBLIOGRAPHY Microsoft. (2015, 06 24). Windows Server Evaluations. Retrieved from TechNet Evaluation Center: Oracle. (2015, 07 09). Virtual Box 5.0. Retrieved from VMWare. (2015, 08 08). VMWare Vsphere. Retrieved from Products/Vsphere: Page 46