Connection Broker Managing User Connections to Workstations, Blades, VDI, and more. Installation Guide

Transcription

1 Connection Broker Managing User Connections to Workstations, Blades, VDI, and more Installation Guide Version 8.1 August 25, 2015

2 Contacting Leostream Leostream Corporation Waverley Oaks Rd Telephone: Suite 200 Fax: Waltham, MA USA To submit an enhancement request, To request product information or inquire about our future directions, Copyright Copyright by Leostream Corporation This software program and documentation are copyrighted by Leostream. The software described in this document is provided under a license agreement and may be used or copied only under the terms of this agreement. No part of this manual may be copied or reproduced in any form without prior written consent from Leostream. Trademarks The following are trademarks of Leostream Corporation. Leostream The Leostream graphical logo The absence of a product name or logo from this list does not constitute a waiver of the trademark or other intellectual property rights concerning that product, name, or logo by Leostream. HP is a registered trademark that belong to Hewlett-Packard Development Company, L.P. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. The OpenStack Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. Leostream is not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. Sun, Sun Microsystems, Sun Ray, and Java are trademarks or registered trademarks of Oracle and/or its affiliates. OpenLDAP is a trademark of The OpenLDAP Foundation. Microsoft, Active Directory, SQL Server, Hyper-V, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Other brand and product names are trademarks or registered trademarks of their respective holders. Leostream claims no right to use of these marks. Patents Leostream software is protected by U.S. Patent 8,417,796. 2

3 Installation Guide Contents CONTENTS... 3 CHAPTER 1: OVERVIEW... 5 LEOSTREAM COMPONENTS... 5 WHAT IS THE CONNECTION BROKER?... 5 HARDWARE REQUIREMENTS... 7 VIRTUALIZATION PLATFORM REQUIREMENTS... 8 CHAPTER 2: DOWNLOADING SOFTWARE AND MANUALS... 9 CHAPTER 3: INSTALLING THE CONNECTION BROKER INSTALLING INTO KVM-BASED OPENSTACK CLOUDS Required OpenStack Permissions Security Group Requirements Creating the Connection Broker Image Launching a Connection Broker Instance Assigning a Floating IP Address INSTALLING INTO VMWARE WORKSTATION INSTALLING USING VMWARE VSPHERE CLIENT INSTALLING INTO CITRIX XENSERVER 6.X INSTALLING INTO MICROSOFT HYPER-V SERVER INSTALLING INTO RED HAT ENTERPRISE VIRTUALIZATION STARTING THE CONNECTION BROKER VIRTUAL MACHINE MANUALLY CONFIGURING THE CONNECTION BROKER ADDRESS Entering the Connection Broker Address Restarting the Connection Broker Returning to the Connection Broker Welcome Screen CONFIGURING SECOND NETWORK ADAPTER FOR PCOIP USING FIREWALL PORTS CHAPTER 4: INSTALLING THE LEOSTREAM AGENT INSTALLING ON MICROSOFT WINDOWS OPERATING SYSTEMS Starting and Stopping the Leostream Agent Entering the Connection Broker IP Address Using the Leostream Agent with Microsoft Hyper-V Server Configuring the Leostream Agent for Citrix XenDesktop Support Configuring the Leostream Agent for Citrix XenApp Support INSTALLING ON LINUX OPERATING SYSTEMS Prerequisites for Installing USB over IP Support Prerequisites for Installing the Desktop Experience Using the Graphical Installer Silent Installations using XML-Files

4 Installing at the Console Starting the Leostream Agent Service Leostream Agent Files CHAPTER 5: INSTALLING LEOSTREAM CONNECT INSTALLING ON MICROSOFT WINDOWS OPERATING SYSTEMS Entering the Connection Broker IP Address INSTALLING ON LINUX AND APPLE MAC OPERATING SYSTEMS Prerequisites for Installing USB over IP Support Installation Instructions Leostream Connect Files Silent Installations using XML-Files INSTALLING LEOSTREAM CONNECT ON HP THIN CLIENTS CHAPTER 7: SETTING CONNECTION BROKER DNS SERVICE LOCATION (SRV) APPENDIX A: COMMAND LINE OPTIONS FOR WINDOWS VERSION OF LEOSTREAM CONNECT AND LEOSTREAM AGENT INSTALLING FROM THE COMMAND LINE UNINSTALLING FROM THE COMMAND LINE ENCODING THE CONNECTION BROKER ADDRESS

5 Installation Guide Chapter 1: Overview This installation guide provides instructions for installing the Connection Broker, Leostream Agent, and Leostream Connect. See the Quick Start Guides and Administrator s Guides for additional information on configuring these components after installation. Leostream Components The Leostream Connection Broker consists of the following four components. Connection Broker: The main virtual appliance that manages the hosted desktop infrastructure. The Connection Broker is the central management layer for configuring your deployment, including: inventorying desktops, applications, printers, and other resources, assigning these resources to users, and defining the end-user experience. Leostream Agent: When installed on the remote desktops, the Leostream Agent provides the Connection Broker with insight into the connection status of remote users. On remote desktops running a Microsoft Windows operating system, the Leostream Agent also controls the end-user experience with respect to USB device management and multimonitor support. Although optional, the Leostream Agent is a critical component when scaling out deployments to a large number of end users. Leostream Connect: A client provided by Leostream that allows users to log into desktops from fat or thin clients. Using Leostream Connect, you can repurpose existing fat desktops and laptops, lowering the cost of VDI deployments. Some thin clients provide built-in Leostream Connect clients. Database: The Connection Broker stores all information in an internal database. A typical installation requires 2 Gbyte of disk space for the internal database. Large scale deployments that require Connection Broker clusters must use an external Microsoft SQL Server 2012 or 2014 database. What is the Connection Broker? A connection broker lies at the heart of any VDI deployment, and is the key component for assigning resources to end users. The Leostream Connection Broker runs as a virtual appliance within a VMware, Citrix, Microsoft, or Red Hat virtualization layers or in OpenStack clouds, making it easy to install, maintain, and update. The Connection Broker provides end users with consistent, reliable access to desktops from a range of client devices. The Connection Broker also allows you to manage: Desktop sessions, to optimize resource and power consumption USB devices, to ensure data security End user experience, to provide the optimal working environment for your end users 5

6 Chapter 1: Overview Using the Connection Broker, you define: Authentication Servers: A server that provides authentication services to users logging into the Connection Broker. The Connection Broker supports Microsoft Active Directory, Novell edirectory, NIS, or OpenLDAP directory services. You can specify any number of (trusted or not-trusted) domains, using any combination of authentication server types. In addition, the Connection Broker allows you to manually define users without configuring an authentication server. Centers: The external systems from which the Connection Broker pulls resources, including desktops, applications, and printers. Centers can be created from the following systems: VMware ESX/ESXi, vsphere, and vcenter Server; Citrix XenDesktop, XenServer and XenApp; open source Xen; OpenStack clouds, including HP Helion OpenStack; Microsoft Hyper-V via System Center Virtual Machine Manager (SCVMM), Remote Desktop Services, and Active Directory. Resources: Desktops, applications, and printers available for assignment to an end user. Desktops: Virtual machines, physical machines, blades, and Microsoft Terminal Services to assign to end users. Desktops can be running either Windows or Linux operating systems. Applications: Applications and desktops hosted in a Citrix XenApp farm. Pools: Collections of desktops or applications, gathered from a single or multiple centers. Clients: An application or system used to access a remote desktop. The Connection Broker supports Linux and Windows fat clients and a variety of thin clients, as well as Web browsers. Locations: A group of clients, defined by client attributes such as manufacturer, device type, OS version, or IP address. You can define the end-user s experience, including the desktops, printers, and USB devices they can use, based on the location of their client. Plans: Common sets of rules that can be used as building blocks for defining the end user experience. There are two types of plans: pool-based plans such as protocol, power control, and release plans are applied to pools in a policy and define how the Connection Broker manages the desktops in that pool; location-based plans such as printer and registry plans are applied to desktops based on the location of the user s client device. Policies: Rules that assign desktops and applications to users, and define what occurs when the assignment is done. Policies assign plans to desktops based on the desktop s pool membership, and mange USB passthrough permissions. Roles: Permissions that control the actions an end user is allowed to take on their desktops and the level of access they have to the Connection Broker Administrator Web interface. 6

7 Installation Guide Administrator-defined access control rules that map end users to roles and policies, which determine: Which desktops and applications the Connection Broker offers the user The level of access each user has to the Connection Broker Administrator Web interface The Connection Broker maps users to these rules via their authentication server attributes and assigns desktops and applications from pools, as depicted in the following figure. Users can access their desktops from any of the following devices: A Web browser, including Microsoft Internet Explorer and Mozilla Firefox browsers A variety of thin clients, including Del Wyse, HP, IGEL, IRIS, and more A Windows or Linux laptop or desktop, using Leostream Connect. Hardware Requirements The Connection Broker requires virtual resources equivalent to the following hardware: 1500 MHz or faster Intel Pentium IV processor (or equivalent) 2.0 Gbytes of RAM 8 Gbytes of hard drive space Bridged Ethernet adapter, ideally with Internet connectivity 7

8 Chapter 1: Overview Virtualization Platform Requirements The Connection Broker runs as a virtual appliance within the following virtualization platforms: KVM-based OpenStack clouds VMware Workstation 9 and higher VMware vsphere 5 and 6 Citrix XenServer 6.x Microsoft Hyper-V Server 2012 and Windows Server 2012 R2 Hyper-V (requires SCVMM) Red Hat Enterprise Virtualization 3.0 8

9 Installation Guide Chapter 2: Downloading Software and Manuals You can obtain a trial license for the Leostream Connection Broker, as follows: 1. In your Web browser, go to the Leostream Web site 2. Click on the Free Trial link at the top-right of any page. 3. Fill in the required fields in the Trial Request Form, and submit the form. 4. After Leostream receives your request, you will receive an with a 30-day trial license key, and a link to the page containing the Connection Broker software. Click on the link to this page, or go to 5. In the Connection Broker download page, click on the Connection Broker link appropriate for your virtualization platform. The Resources section of the Leostream Web site contains additional information that you may find useful in getting started with your deployment. Go to the Downloads & Documentation page to download Leostream Connect, the Leostream Agent, or any Leostream documentation. Go to the Training page to download training presentations and videos showing how to get started with your Connection Broker. Go to the Frequently Asked Questions for a list of common tasks and issues. 9

10 Chapter 3: Installing the Connection Broker Chapter 3: Installing the Connection Broker Ensure that the location you are installing the Connection Broker into contains at least 2 Gbytes of free space. After you install the Connection Broker virtual appliance and upload your license key into the Connection Broker, Leostream recommends checking for the most recent update. Use the Check for updates option on the > System > Maintenance page to update your Connection Broker, at any time. See Updating the Connection Broker in the Connection Broker Administrator s Guide for complete instructions. Installing into KVM-based OpenStack Clouds Required OpenStack Permissions Leostream manages OpenStack clouds using the OpenStack APIs. Before you begin your Leostream deployment, ensure that you have access to a user account with the required permissions in OpenStack. In order to use all of the functionality in the Connection Broker, your user requires access to the following: In /etc/nova/policy.json compute:get_all compute:create compute:start compute:stop compute:reboot compute_extension:admin_actions:suspend compute_extension:floating_ips compute_extension:admin_actions:resume network:associate_floating_ip network:disassociate_floating_ip In /etc/glance/policy.json get_images Security Group Requirements Before creating your Connection Broker instances, ensure that you have an appropriate security group configured in OpenStack. Leostream requires the following ports be open for incoming traffic. 10

11 Installation Guide Port Required By Purpose and * 3389** Connection Broker Connection Broker Leostream Agent on the OpenStack Instances OpenStack Instances Creating the Connection Broker Image For SSH access to the Connection Broker. Alternatively, you can access the Connection Broker console via the Horizon Dashboard. For access to the Connection Broker web interface, and communication with the Leostream Agents and Leostream Connect. If you close port 80 on your Connection Broker, you may omit that port from the security group. Port for communications from the Connection Broker to the Leostream Agent. * The Leostream Agent port may be changed using the Leostream Agent Control Panel dialog. If you change the default Leostream Agent port, ensure that you open the associated port in the security group For RDP access to the OpenStack VDI/DaaS instances ** If you use a display protocol other than RDP, ensure that you open any ports required by that display protocol. After downloading the Connection Broker QCOW2-file, import it as an image into your OpenStack cloud. You can create the Connection Broker image using the Horizon Dashboard, as follows. 1. Go to the Images page inside the OpenStack project you want to contain your Connection Broker. 2. Click the Create Image button. 3. In the Create An Image form, enter a name for your Connection Broker image. 4. From the Image Source drop-down menu, select Image File. 5. In the Image File section, browse for the Connection Broker QCOW2-file. 6. Leave the remaining fields blank, as shown in the following figure, and click Create Image. 11

12 Chapter 3: Installing the Connection Broker After the image is saved, the Leostream Connection Broker appears in your image list, for example: Launching a Connection Broker Instance To launch a Connection Broker instance: 1. Go to the Instances page in a project with access to the Connection Broker image. 2. Click the Launch Instance button. 3. Enter a name for your Connection Broker in the Instance Name edit field. 4. Select m1.small from the Flavor drop-down menu. 5. Select Boot from image from the Instance Boot Source drop-down menu. 6. Select your Leostream Connection Broker image from the Image Name drop-down menu. The Launch Instance form looks similar to what is shown in the following figure. 12

13 Installation Guide 7. In the Launch Instance form, go to the Access & Security tab. 8. Confirm or set the correct key in the Key Pair drop-down menu. 9. Also in the Access & Security tab, select an appropriate security group (see Security Group Requirements), for example: 10. In the Launch Instance form, go to the Networking tab. 11. Add a network interface to the Connection Broker instance, for example: 13

14 Chapter 3: Installing the Connection Broker 12. Click Launch. After the spawning process for the instance completes, you can go to the instance Console page to watch the Connection Broker appliance boot. After the Connection Broker starts, the console displays the Connection Broker IP address, for example: The Connection Broker uses the IP address assigned by OpenStack on the network you selected when launching the instance. To configure the Connection Broker, you must be able to access the Connection Broker from a Web browser, which may require you to assign a public floating IP address to the Connection Broker (see Assigning a Floating IP Address). If you snapshot your Connection Broker and subsequently launch an instance from the snapshot, the network may not correctly start. In this case, log into the Connection Broker console using the following credentials: username: root password: leostream In the Linux shell, run the following commands: rm /etc/udev/rules.d/70-persistent-net.rule reboot The Connection Broker reboots with the network interface configured correctly. 14

15 Installation Guide Assigning a Floating IP Address If you cannot access the private IP address assigned to the Connection Broker, you can use the OpenStack Horizon Dashboard to associate a floating IP address with your Connection Broker instance, as follows. 1. Go to the Access & Security page in the OpenStack project that contains your Connection Broker. 2. If you do not have an available floating IP address, click the Allocate IP to Project button. Otherwise, skip to step Select public from the Pool drop down menu in the Allocate Floating IP form. 4. Click Allocate IP. 5. In the list of floating IPs, click the Associate button for an available IP address, for example: 6. In the Manage Floating IP Associations form, select your Leostream Connection Broker instance from the Port to be associated drop-down menu, for example: 7. Click Associate. You can now access the Connection Broker Administrator Web interface using the public floating IP address. 15

16 Chapter 3: Installing the Connection Broker Installing Into VMware Workstation The Connection Broker supports VMware Workstation 9 and higher, which contain the required support for CentOS Linux 5. Leostream does not recommend using VMware Workstation in a production environment. To install the Connection Broker into VMware Workstation: 1. Download and save the Connection Broker for VMware Workstation. You must have at least 700 Mbytes of free space. 2. Create a folder inside the directory that contains your virtual machine inventory, for example inside the C:\Virtual Machines directory. 3. Extract the Leostream Connection Broker files into the folder you created in step two. 4. Inside the folder you extracted in step 2, double-click on the LeostreamCB.vmx file. VMware Workstation automatically opens the virtual machine. This process may take a few minutes; Workstation displays a progress indicator similar to the message 5. After the virtual machine finishes opening, it should be shown as a new tab in VMware Workstation. You can now start the virtual machine. Once the Connection Broker virtual machine boots up, the remote console displays its IP address. You can point a Web browser to this IP address and configure your Connection Broker. See one of the Quick Start manuals for tutorials on configuring your Connection Broker. Installing using VMware vsphere Client The Connection Broker virtual appliance is packaged as an OVA-file. Use the vsphere Client to install the Connection Broker virtual appliance into vsphere 5 and 6, as described in the following steps. 1. Download and extract the Connection Broker virtual appliance for VMware vsphere. 2. Log into the vsphere Client with an account that has permissions to create new VMs. 3. Select the File > Deploy OVF Template menu, shown in the following figure: 16

17 Installation Guide 4. In the first page of the Deploy OVF Template wizard, select the extracted Connection Broker OVA-file. 5. Click Next >. 6. Review the OVF Template Details page and click Next >. 7. Follow through the remainder of the Deploy OVF Template wizard to define the location and configuration for the virtual appliance. Installing into Citrix XenServer 6.x Use XenCenter to install the Connection Broker into Citrix XenServer, as follows. 1. Download the Connection Broker for Citrix XenServer. 2. Extract the Connection Broker XVA-file onto the local desktop running XenCenter. 3. In XenCenter, select the File > Import menu, as shown in the following figure. 4. In the Filename edit field on the first page of the Import wizard, enter or browse to the full path to the Leostream Connection Broker XVA-file. 5. Click Next. 6. In the Select the location where the imported VM will be placed page of the Import XVA wizard: a. Select the home server for the Connection Broker VM. b. Click Next >. 17

18 Chapter 3: Installing the Connection Broker 7. In the Select target storage page of the Import XVA wizard: a. Select the storage for the Connection Broker VM. b. Click Next >. 8. In the Select network to connect VM page: a. Configure the virtual network for the Connection Broker VM. b. Click Next >. 9. In the Review the import settings page, click Finish. If DHCP is not able to obtain a network address for your Connection Broker, you must manually configure the Connection Broker IP address (see Manually Configuring the Connection Broker Address). Installing into Microsoft Hyper-V Server 2012 Use the Microsoft System Center Virtual Machine Manager (SCVMM) to install the Leostream Connection Broker into a Hyper-V virtualization layer. SCVMM stores VHD-files in the Virtual Machine Manager Library. The Leostream Connection Broker no longer installs on Hyper-V Server If you require support for Hyper-V 2008, please contact supportsite@leostream.com. If you plan to use the Connection Broker to manage VMs hosted on this Hyper-V hypervisor, you must also install the Leostream Agent on the Hyper-V server. See Using the Leostream Agent with Microsoft Hyper-V Server for more information. To install the Connection Broker: 1. Download the ZIP-file associated with the Connection Broker for Microsoft Hyper-V. 2. Extract the contents of the ZIP-file into the Virtual Machine Manager library share folder s VHDs directory. If you plan to deploy multiple Connection Brokers, archive a copy of the extracted files. By default, the VMM library share folder is located in the following directory: %LocalDisk\ProgramData\Virtual Machine Manager Library Files\VHDs 18

19 Installation Guide where %LocalDisk is typically C:. The library can also be found at: \servername\msscvmmlibrary\vhds 3. Open the Virtual Machine Manager. 4. In the left-hand pane of the SCVMM interface, click on Library. 5. In the Library, expand the Library Servers node. 6. In the Library Servers node, expand the server node where you unpacked the Connection Broker ZIP-file. 7. Inside the appropriate server node, right-click on the VHDs folder and select Refresh. The folder you unpacked in step 2 should appear in the right hand pane of Physical Library Objects. 8. In the VHDs folder, select the folder you unpacked in step 2. The Connection Broker vhdx file appears in the Physical Library Objects. 9. Right-click on the vhdx file and select Create Virtual Machine, as shown in the following figure. a. On the Specify Virtual Machine Identity page, enter a name into the Virtual Machine Name edit field. You must use a unique name for every Connection Broker appliance that you deploy. 19

20 Chapter 3: Installing the Connection Broker Select Generation 1 from the Generaion drop-down menu and click Next. b. On the Configure Hardware page, select Hyper-V for the Compatibility profile and click Next. c. On the Select Destination page, select Place the virtual machine on a host. Select the Destination host and click Next. d. On the Select Host page, select the Hyper-V server where the Connection Broker appliance will reside and click Next. e. On the Configure Settings page, enter the absolute path name where the Connection Broker appliance will be stored and click Next. f. On the Select Networks page, select the network that the Connection Broker appliance will use and click Next. g. On the Add Properties page, select CentOS Linux 5 (32 bit) from the Specify operating system you will install in the virtual machine drop-down menu and click Next. h. In the Confirm the settings page, check the Start the virtual machine after deploying it option and click Create. 10. After the Create virtual machine job finishes, in the left-hand pane, select VMs and Servers. The Connection Broker that you created should appear in the list of VMs in the right hand pane. If the Connection Broker does not appear in the list, go to the left-hand pane, right-click on the Hyper-V Server where the Connection Broker appliance was deployed, and select Refresh Virtual Machines. To view the Connection Broker console, right-click on the Connection Broker in the list of VMs and select Connect or View > Connect via Console. VMM may display warning when creating the Connection Broker VM. This warning can result when you create a new VM from a VHD-file with a non-windows operating system, and can be ignored. Installing into Red Hat Enterprise Virtualization 3.0 The Connection Broker runs as a virtual appliance on the Red Hat Enterprise Virtualization 3.0 hypervisor. Use the Import option in the Red Hat Enterprise Virtualization Manager to install the Connection Broker in your environment, as follows. 1. If you do not already have an export domain attached to your Red Hat Enterprise 20

21 Installation Guide Virtualization Manager, create an export domain and attach it to your data center before proceeding. 2. Uncompress the Leostream archive in the root of the export domain, which is located under a UID, one directory down from the mount point. 3. You must set the permissions of all files to vdsm:kvm using the following command: chown -R 36:36 4. In the Red Hat Enterprise Virtualization Manager, under the storage domain, go to the VM Import tab 5. Click on the LeostreamCB VM and click Import. 6. In the Complete the import page, ensure that the Start VM after import option is selected and click Finish. 7. After the virtual machine is running, connect to the Connection Broker console to view the Connection Broker IP address. Starting the Connection Broker Virtual Machine Once the Connection Broker disk image is associated with a virtual machine, check the configuration to ensure that there is a bridged network connection assigned to the Connection Broker virtual machine. To do this, use your virtualization management console to start the Connection Broker virtual machine, and view the Connection Broker console page. After the virtual machine starts, a welcome screen displays a list with at least one Connection Broker IP address, as shown in the following figure. Use this IP address to access the Connection Broker interface via a Web browser running on the same network as the Connection Broker virtual machine. If the physical server hosting the Connection Broker virtual machine is connected to an Ethernet segment with a DHCP server, a second IP address for the Bridged Ethernet port is reported. 21

22 Chapter 3: Installing the Connection Broker If the Connection Broker cannot obtain a DHCP supplied address, it defaults to If you cannot connect to this IP address, manually change the IP address within the Connection Broker console. Manually Configuring the Connection Broker Address If your virtualization layer s console cannot obtain an IP address from DHCP, you can manually configure your Connection Broker IP address, as follows. Entering the Connection Broker Address The look-and-feel of your console dialogs may not match those shown in this procedure, depending on your virtualization platform. 1. Go to the Connection Broker Console panel in your virtualization layer s management tool, shown in the following figure. 2. Enter Ctrl-C to go to the Leostream administrator login page, shown in the following figure. 3. Log into the Administrator console. The default username is leo and password is leo. The Leostream administrator menu, shown in the following figure, opens. 22

23 Installation Guide 4. Select Network and hit <Enter>. The following menu opens. 5. Select Edit a device params and hit <Enter>. The Select a Device menu, shown in the following figure, opens. 6. Select eth0 (eth0). 7. Press <Enter>. The Devernet Configuration menu, shown in the following figure opens. 23

24 Chapter 3: Installing the Connection Broker 8. Scroll down to the Use DHCP option and hit the spacebar to deselect this option. 9. Enter in the network information for your Connection Broker in the Static IP, Netmask, and Default gateway IP edit fields. 10. Select Ok to accept the changes and return to the Select a Device menu. 11. Select Save to return to the Select Action menu. 12. Select Save&Quit. 13. When prompted to restart the Connection Broker, select OK. This is only a reminder to restart your Connection Broker. You must manually restart your Connection Broker. Restarting the Connection Broker To restart the Connection Broker from the Leostream administrator menu: 1. Navigate back to the Main menu in the Leostream Administrator menu. 2. Select Power and hit <Enter>. 3. In the Power menu, select Restart and hit <Enter>. 4. In the confirmation menu, select Yes and hit <Enter>. Returning to the Connection Broker Welcome Screen After the Connection Broker has restarted, select Continue by hitting <Enter>. To return to the Connection Broker Welcome screen: 1. In the Power menu, select <== Back and hit <Enter>. 2. In the Main menu, select Exit and hit <Enter>. The Linux shell opens. 24

25 Installation Guide 3. At the Leostream prompt, type exit and hit <Enter>. Configuring Second Network Adapter for PCoIP If you plan to use the Connection Broker to manage a PCoIP-based system, configure a second network adapter on the virtual appliance. With a second network adapter, the Connection Broker can discover and manage the PCoIP end devices using the video network, while still managing everything else over the standard corporate network. Once you have changed the configuration file for the virtual appliance, and associated the second NIC on the virtual appliance with a physical NIC attached to the video network, you can turn on the Connection Broker virtual machine. In the Connection Broker Web interface, go to the > System > Network page, which displays the two networks to configure. Setup the first network to communicate with the corporate network, and the second network to the video network, as shown in the following figure. Using Firewall Ports To the network, the Connection Broker virtual appliance appears like any other physical appliance. Depending on your installation, different ports are available to the Connection Broker: The Connection Broker uses port 443. Port 80 is also open, by default. If you enable SSH access (using the Console access to the virtual appliance), port 22 is open. SSH access to the Connection Broker is off, by default. If you enable hardware-based PCoIP support, port 50,000 is open. The only network facing services that are accessible are Apache and SSH, assuming SSH is enabled. 25

26 Chapter 3: Installing the Connection Broker The following figure provides a schematic of Connection Broker ports and their usage. 26

27 Installation Guide Chapter 4: Installing the Leostream Agent Install the Leostream Agent on your remote desktops to optimize Connection Broker performance. To maximize your policy control, Leostream recommends that you install the Leostream Agent on every virtual and physical machine running a supported operating system. Installing on Microsoft Windows Operating Systems The Leostream Agent supports the following Windows operating systems: Windows Server 2008 and Windows Server 2008 R2 Windows 7, including SP1 Windows Server 2012 Windows 8 and 8.1 Do not install the Leostream Agent on desktops used as client devices. The Leostream Agent is required in the following cases. If you plan to use the Leostream Connection Broker USB management, extended monitor support, network printer plans, or registry plans. If you want to perform single sign-on to a remote desktop when connecting using either VNC or Teradici PC-over-IP protocols. If you plan to assign Terminal Services sessions. In this case, install the Leostream Agent in the Microsoft Windows Server operating system on each of the Terminal Services servers. If you plan to assign applications published in a Citrix XenApp farm and the Citrix server does not enable its XML-RPC service. By default, the Leostream Connection Broker uses the Citrix XML interface to communicate with XenApp, and you do not need a Leostream Agent. If you do not want to enable the XML service, or the Connection Broker is blocked from using it, install the Leostream Agent into your primary Citrix server in the farm. If you do install the Leostream Agent, see Configuring the Leostream Agent for Citrix XenApp Support for information on enabling the Leostream Agent to communicate with your Citrix XenApp farm. If you plan to manage VMs hosted in a Microsoft Hyper-V server (see Using the Leostream Agent with Microsoft Hyper-V Server). If you will use Windows Deployment Services to deploy operating systems to HP Moonshot System nodes. 27

28 Chapter 4: Installing the Leostream Agent If you plan to push assignments from Leostream into Citrix XenDesktop in order to provide HDX connections, install the Leostream Agent on the Windows server running the Citrix Desktop Studio (see Configuring the Leostream Agent for Citrix XenDesktop Support). You can download the Leostream Agent and manuals from: you uninstalled a previous version of the Leostream Agent, but did not restart the desktop when prompted by the uninstaller, you will not be able to successfully install a new Leostream Agent. If you are unsure if a desktop restart is required, perform the Leostream Agent installation. The installer will indicate if you need to restart the desktop. To install the Leostream Agent: 1. Run the LeostreamAgentSetupXXXX.exe executable file, where XXXX is the Leostream Agent version number. Appendix A lists options available when running the installation from the command line. The License Agreement page opens, as shown in the following figure. 2. On the License Agreement page: 1. Read the license agreement. 2. If you accept the license agreement terms, select the I accept the agreement option. 3. Click Next >. 3. On the next page, enter or browse for the directory to install the Leostream Agent into, as shown in the following figure. 28

29 Installation Guide 4. Click Next >. 5. On the page that appears, shown in the following figure, select any additional tasks to run during the installation. If you are installing the Leostream Agent on a Citrix Desktop Studio, select only the Install Microsoft VC++ runtime task. Do not select any other Leostream Agent installation tasks Install end-user experience extension: Select this option if you plan to use Leostream display plans, Leostream printer plans, Leostream registry plans, or disconnect or idletime functions in Leostream release plans. Extended display support allows end users to split their display across the different monitors. See the Leostream Multiple Display Support document for more information. o Enable multi-display support for Windows logon: Select this option to install the Leostream GINA. This option appears only when installing the Leostream Agent on a Windows operating system that uses the Windows GINA, such as Windows XP. The GINA handles dialog positioning for native Windows logon dialogs when the user s session is spanned across multiple displays. The GINA also is required when using the idle-time features in release plans. o Enable multi-display support for 32-bit applications: When installing on a 64-bit 29

30 Chapter 4: Installing the Leostream Agent operating system, select this task if the user runs legacy 32-bit applications. If this task is not selected, the Leostream Agent cannot successfully position windows associated with 32-bit applications. Enable USB over IP (may require reboot): Select this task if you want USB devices attached to the client desktop to appear within this remote desktop. Do not select this task if you have another USB over IP solution installed, for example, the HP RGS solution. If two USB solutions are installed side-by-side, you may not be able to predict which solution is managing the USB devices. Enable single sign-on for PCoIP VNC: Select this task to enable single sign-on for users connecting to their desktops using VNC or PC-over-IP display protocols. The Connection Broker provides native single sign-on for all other display protocols. Do not select this task if your users connect using any protocol other than VNC or PC-over-IP. You can use this task to provide single sign-on for SPICE connections, if you do not want to use the native SPICE single sign-on capabilities. On Windows 7 and Vista, the single sign-on task installs the Leostream Credential Provider. When the Leostream Agent service starts, the Leostream Agent disables the Ctrl-Alt-Del key combination. The Ctrl-Alt-Del function is restored when the Leostream Agent service stops. On older Windows operating systems, this task installs the Leostream GINA. Install Microsoft VC++ runtime: Select this task if you do not have the latest Microsoft Visual C++ run-time libraries installed on the desktop. Uncheck this option only if the desktop already has an installed Microsoft VC++ runtime environment. The Leostream Agent requires that MSVC runtime be installed in order to create an SSL certificate and key to use when communicating with the Connection Broker. If you uncheck this option, and do not have an MSVC runtime environment installed, the Leostream Agent produces SSL errors. To resolve this issue, reinstall the Leostream Agent with the Install Microsoft VC++ runtime option selected. 6. Click Next >. 7. Review the installation setup in the next page, shown in the following figure, then click Install. 30

31 Installation Guide If the desktop does not prompt for a restart, the installation is complete. If you installed the enduser experience or USB over IP tasks, you may be prompted to restart your machine. In this case, the installation is complete only after you restart the desktop. If you do not restart the desktop when prompted, you may encounter difficulties when subsequently upgrading the Leostream Agent. The installer automatically starts the Leostream Agent when the installation completes. To turn off the Leostream Agent, or configure it to point to a particular Connection Broker IP address, open the Leostream Agent Control Panel dialog. For a 32-bit system, you can find the Leostream Agent icon in the machine s Control Panel, as shown in the following figure: For a 64-bit system, the Leostream Agent icon is located in the x86 Control Panel. To modify the Leostream Agent options, you must be logged into the desktop with administrator privileges, or run the Leostream Agent with administrator privileges. On desktops running Windows 7 operating systems, to run the Leostream Agent configuration with the necessary privileges, right-click on the Leostream Agent and select Run as administrator, as shown in the following figure. 31

32 Chapter 4: Installing the Leostream Agent Starting and Stopping the Leostream Agent The Leostream Agent must be running in order for the Connection Broker to perform the assignment options associated with Connection Broker policies. To start or stop the Leostream Agent: 1. Double-click on the Leostream Agent icon in the Control Panel. The Leostream Agent dialog opens. 2. Go to the Status tab. a. If the agent is running, stop the agent by clicking the Stop button. b. If the agent is not running, as shown in the following figure, start the agent by clicking the Start button. Entering the Connection Broker IP Address By default, the Leostream Agent looks for a DNS SRV record associated with your Connection Broker. If you do not have a Connection Broker DNS SRV record, you can enter the Connection Broker address in the Leostream Agent Control Panel dialog. The Leostream Agent can communicate with multiple Connection Brokers. You do not need to specify a Connection Broker address in the Leostream Agent Control Panel dialog, unless you want to explicitly register the Leostream Agent with a particular Connection Broker. To enter a specify Connection Broker IP address: 1. Double-click on the Leostream Agent icon in the Control Panel. The Leostream Agent dialog opens. 2. Go to the Options tab. 3. Uncheck the Obtain Connection Broker address automatically option. The Address edit field enables, as shown in the following figure. 32

33 Installation Guide 4. Enter the Connection Broker address in the edit fields. 5. Click Apply to accept the address and leave the Leostream Agent dialog open, or OK to accept the address and close the dialog. You can click Test to check if the address you entered is valid. A dialog opens indicating if the Leostream Agent can contact the Connection Broker at the specified address. Using the Leostream Agent with Microsoft Hyper-V Server The Connection Broker manages Microsoft Hyper-V virtual machines using the Microsoft System Center Virtual Machine Manager (SCVMM). In order for the Connection Broker to communicate with SCVMM, you must install the Leostream Agent on the SCVMM server. After you install the Leostream Agent on the VMM server, configure the Leostream Agent, as follows. 1. Open the Leostream Agent Control Panel dialog. 2. Go to the Options tab. 3. Uncheck the Obtain Connection Broker address automatically option. 4. Erase any entry in the Address edit field. The Leostream Agent on the VMM server does not need to initiate calls to the Connection Broker. Leaving an entry in this field could unintentionally cause the VMM server to appear in your Connection Broker Uncategorized Desktops center. If you reboot the SCVMM server, the Leostream Agent may not automatically restart. You can manually restart the Leostream Agent using the Leostream Agent Control Panel Options dialog. Configuring the Leostream Agent for Citrix XenDesktop Support If you are installing the Leostream Agent on a Citrix Desktop Delivery Controller (DDC) or Desktop Studio, ensure that the Leostream Agent communicates on a port that is different from the port 33

34 Chapter 4: Installing the Leostream Agent already in use by the DDC. Leostream recommend configuring the Leostream Agent to use port 8730, as follows. 1. On the DDC or Desktop Studio server, open the Leostream Agent Control Panel dialog. 2. Go to the Options tab. 3. Change the Port to listen on to 8730, as shown in the following figure. Configuring the Leostream Agent for Citrix XenApp Support The Connection Broker does not require an installed Leostream Agent for Citrix XenApp centers. Instead, the Connection Broker communicates with the XenApp server over the Citrix XML RPC port. Using the XML RPC service provides a higher level of performance for XenApp servers that contain a large number of applications. If you do not enable the XML RPC service in XenApp, or the XML RPC port is blocked, you must install the Leostream Agent. By default, the Leostream Agent service runs under the machine s Local System account. If your XenApp server is not installed under the same account, your XenApp centers appear offline in your Connection Broker. To get your centers online, modify the Leostream Agent service to run under the same account as your XenApp server, as follows. 1. Open the Component Services administrative tool. 2. Click on the Services (Local) item and locate the Leostream Windows Agent service, as shown in the following figure. 34

35 Installation Guide 3. Right-click on the Leostream Windows Agent service, and select Properties. The following dialog opens. 4. Select the This account option. 5. Enter the account name and associated password. 6. Click OK. Installing on Linux Operating Systems The Leostream Agent for Linux operating systems allows you to manage users that connect to their remote Linux desktops using NoMachine NX, HP RGS, or Exceed ondemand. The Leostream Agent provides single sign-on to PCoIP environments. The Leostream Agent for Linux is a Java application, which requires a Java Run Time Environment (JRE) version 1.7 or higher. 35

36 Chapter 4: Installing the Leostream Agent You can download the Leostream Agent and manuals from: The Leostream Agent is packaged in an installer, which runs on the following operating systems. CentOS Debian Fedora Novell SUSE Linux Enterprise Red Hat Enterprise Linux Solaris Ubuntu You cannot use the graphical installer if the remote desktop does not have a graphical user interface or the X11 DISPLAY environment variable is not correctly set. In these cases, install the Leostream Agent at the console (see Installing at the Console). Also, if you are connected to the remote desktop using a display protocol such as NoMachine NX, you cannot run the graphical installer. Prerequisites for Installing USB over IP Support Leostream provides USB redirection for 32- and 64-bit Linux operating systems. On Linux operating systems, the Leostream Agent installer must build the required USB drivers. In order to build the drivers, Leostream Agent requires the following two header files: hcd.h hub.h The Leostream Agent provides these header files for kernel versions to More recent kernel versions include these files in the kernel source. USB redirection is not supported for kernel version higher than The Leostream Agent uses files in the kernel source directory to execute the make command that builds the drivers. These files are typically located in /usr/src/kernels. Some operating systems provide the necessary directories. If your operating system does not provide the appropriate kernel files, you must download and install them, using the appropriate distribute method for your operating system. For example, use the following commands for desktops running CentOS. yum install kernel-devel yum install gcc 36

37 Installation Guide You must install the kernel source that exactly matches your kernel version. To determine which kernel version your Linux desktop is running, execute the following command. uname r Prerequisites for Installing the Desktop Experience The Leostream Agent Desktop Experience task installs the Leostream Desktop component onto the remote workstation. Leostream Desktop runs in the user s space, providing information about the user s session to the Leostream Agent. The Desktop Experience is required if you want to use the idle-time actions in Connection Broker Release Plans, or provide single sign-on for PCoIP sessions. The Desktop Experience task requires the following two shared object files. libx11.so libxss.so Ensure that your desktop includes these two files in the same directory before beginning the Leostream Agent installation. Using the Graphical Installer To run the graphical installer: 1. Login to the desktop using the root account, or with an account that has permission to use the sudo command. If you plan to install the Leostream USB over IP feature, you must install the Leostream Agent using the root account. 2. From the directory that contains the installer, issue the following command: java -jar LeostreamAgentJava-x.x.x.x.jar Where x.x.x.x is the version number at the end of the installer file name. Run this command using sudo if you are not logged in with the root account. If the desktop has multiple JRE versions, enter the full path to the correct Java installation. The installer Welcome page, shown in the following figure, opens. 37

38 Chapter 4: Installing the Leostream Agent To run the installer with debugging trace turned on, include the following text in the command line: -DTRACE=true For example: java DTRACE=true -jar LeostreamAgentJava-x.x.x.x.jar 3. Click Next in the Welcome page. 4. The License Agreement page opens, as shown in the following figure. In this page: a. Read the license agreement. b. If you accept the license agreement terms, select the I accept the terms of the license agreement option. 38

39 Installation Guide c. Click Next. 5. In the Additional Tasks page, shown in the following figure, select the appropriate tasks to complete during installation. a. You must select the Leostream Agent task, which installs the core Leostream Agent components. b. To use Leostream to manage USB devices, select the Enable USB over IP task. c. To monitor and perform Release Plan actions based on user idle time, select the Desktop Experience task. d. To support single sign-on in a PCoIP environment, select the Enable SSO and the Desktop Experience tasks. 6. In the Installation Directory page, shown in the following figure, enter or browse for the location to install the Leostream Agent. If you are installing the Leostream Agent into a Sun Ray environment, ensure that the Leostream Agent installation directory is different from the installation directory used for Leostream Connect. 39

40 Chapter 4: Installing the Leostream Agent 7. Click Next. 8. If necessary, the installer warns you that it will create or over write the installation directory. Click OK to accept the warning to move on with the installation, or click Cancel to enter a different directory. 9. If you selected the Enable USB over IP task, specify the full path to the Linux kernel build directory, as shown in the following figure. The installer validates this directory by looking for the module.symvers file. If this file does not exist in the specified directory, you cannot continue with the installation. 10. Click Next. 11. In the Agent Configuration page: a. Specify the Connection Broker address to use for this Leostream Agent. If you have a DNS SRV record for your Connection Broker, leave the Connection Broker Address field empty and select the Enable auto-detection of broker using DNS option. To 40

41 Installation Guide enter a static Connection Broker address, clear the selection in the Enable autodetection of broker using DNS option and enter the address into the Connection Broker Address field. b. In the Leostream Agent Port edit field, specify the port used for incoming communications from the Connection Broker to the Leostream Agent. 12. Click Next. You can specify or change the Connection Broker address and port associated with this Leostream Agent at any time, by modifying the leostreamagent.conf file. See the Leostream Agent Administrator s Guide for information on using this file. 13. The Ready to Install page provides a summary of the settings you provided to the installer. Click Next to begin the installation. 14. The installer displays the progress in the Installing Leostream Agent page. If you are installed the USB-over-IP task, the installer appears to pause halfway through the installation. At this point, the installer is building the Linux kernel object for the USB drivers, which may take a couple minutes. When the installation completes, click Next. 15. In the Installation Finished window, click Generate an automatic installation script if you want to generate an XML-file that can be used to perform silent installations of the Leostream Agent on other desktops. 16. Click Done to exit the installer. When running the installer from a terminal, you may see the following message in standard out: /usr/src/linux-headers...-generic/ - isdir: true - mustexist: true - cancreate: false: This message can be ignored. 41

42 Chapter 4: Installing the Leostream Agent If you installed the USB drivers, check that the daemon is live by running the following command: cat /proc/modules grep lsusbd If the daemon is not live, the remote desktop cannot accept USB devices. Contact for a resolution. Silent Installations using XML-Files The Java version of the Leostream Agent supports silent installation using an XML-file. You must perform the installation once using the Graphical Installer, and click the Generate an automatic installation script option on the final panel in the installer to generate the required XML-file. Add the AGENT_PORT parameter to the XML-file to specify a non-standard port for the Leostream Agent. To perform silent installs, copy the XML-file and the original Leostream Agent installer to the new desktop. Use the following command to run the silent installation. Where: sudo java jar LeostreamAgentJava-x.x.x.0.jar auto-install-xml-path java is the full path to the java binary JRE x.x.x.0 is the version number at the end of the installer file name auto-install-xml-path is the full path to your XML-file Installing at the Console To install the Leostream Agent into an environment that does not have a graphical user interface, invoke the installer with the -console option, as follows. You cannot disable the USB feature when installing the Leostream Agent at the console. 1. Login to the desktop using the root account, or with an account that has permission to use the sudo command. 2. From the directory that contains the installer, issue the following command: java -jar LeostreamAgentJava-x.x.x.x.jar -console Where x.x.x.x is the version number at the end of the installer file name. Run this command using sudo if you are not logged in with the root account. If the desktop has multiple JRE versions, enter the full path to the correct Java installation. 42

43 Installation Guide The following instructions appear at the console. 3. Enter 1 to continue the installation. The Leostream End User License Agreement displays. 4. Read through the Leostream End User License Agreement. a. Press <Enter> to go to the next page of the EULA b. Press X to exit the installation 5. At the end of the EULA, enter 1 to accept the license agreement and continue the installation. 6. Enter the target path for the installation, typically /opt/leostreamagent. 7. Press 1 to accept the target installation directory. 8. The installer attempts to automatically discover the path to the Linux kernel build, which is required to compile the USB drivers. Currently, you cannot disable the USB redirection feature when running the installer from the console. 9. Enter 1 to continue the installation. 10. The installer next asks if you want to discover the Connection Broker address, as shown in the following figure. a. Enter 1 to instruct the Leostream Agent to look for a Connection Broker DNS SRV record, in order to discover the Connection Broker address. b. Enter 0 to manually configure the Connection Broker address. 11. Enter the Connection Broker address. If you entered 1 in step 10, enter the Connection Broker address to use in the event a DNS SRV record cannot be found. 12. Press 1 to accept the Connection Broker address and complete the installation Starting the Leostream Agent Service The Leostream Agent service automatically starts after installation. Should you need to restart the service, use the associated service command for the given operating system on which the Leostream Agent is installed. 43

44 Chapter 4: Installing the Leostream Agent For example, on CentOS, use the service command. service leostreamagentd start For a full list of arguments supported by leostreamagentd, run the service command with no input arguments, as follows. service leostreamagentd Leostream Agent Files In addition to the files in the installation directory, the installation adds the following files to the desktop. /etc/leostreamagent.release /var/run/leostreamagentd.pid /var/log/leostreamagent.log /etc/init.d/leostreamagentd /etc/init.d/lsusbd (when installing the USB component) 44

45 Chapter 5: Installing Leostream Connect Installing on Microsoft Windows Operating Systems Installation Guide You can install the Windows version of the Leostream Connect client on machines running any of the following Microsoft operating systems. Windows Server 2008 Windows Server 2008 R2 Windows 7, including SP1 Windows Server 2012 Windows Server 2012 R2 Windows 8 and 8.1 Leostream Connect also installs on legacy Windows XP operating systems. To install Leostream Connect, log into the client device with an account that has Administrator privileges for the desktop. Then, follow through the installation, as follows: 1. Run the LeostreamConnectSetupXXXX.exe executable file, where XXXX is the Leostream Connect version number. Appendix A lists options available when running the installation from the command line. The Encoding the Connection Broker IP Address section shows how to change the name of the executable to encode your Connection Broker IP address into the installation. 2. Select the language to use during installation from the drop-down menu on the Select Setup Language dialog that opens. 3. Click OK. 4. On the page that appears, shown in the following figure: Read the license agreement. If you accept the license agreement terms, select the I accept the agreement option. Click Next >. 45

46 Chapter 5: Installing Leostream Connect 5. Enter or browse for the directory to install Leostream Connect into, as shown in the following figure: 6. Click Next >. 7. On the page that appears, shown in the following figure, select any additional tasks to run. If you do not have administrator privileges on the desktop, you cannot select any additional tasks. 46

47 Installation Guide Enable USB over IP: Select this task if you want USB devices attached to this client desktop to appear within the connected remote desktop. You must also install the Leostream Agent on the remote desktop. Ensure that the USB over IP task is selected when installing the Leostream Agent. The installer installs either 32-bit or 64-bit drivers depending on the type of operating system that you are running. If you install the files for USB over IP support, you may have to reboot your Windows operating system. Do not install this option if you have another USB-over-IP solution installed, for example, the HP RGS solution. If two USB solutions are installed side-by-side, you may not be able to predict which solution is managing the USB devices. Enable Run as Shell mode: Select this option to install Leostream Connect in shell mode. In shell mode, Leostream Connect replaces the Winlogon shell command, which is normally the Windows Explorer (explore.exe). See Running Leostream Connect for Windows in Shell Mode in the Leostream Connect Administrator s Guide and End User s Manual for more information on using, configuring, and removing shell mode support. Enable client-side credential passthrough: Select this option to installs the Leostream GINA or Credential Provider on the client device. Client-side credential passthrough allows Leostream Connect to store the user s Windows login credentials, and automatically use those credentials when the user launches Leostream Connect. When client-side credential passthrough is used with shell mode, it supports the following scenario: when the user logs into the client device, Leostream Connect automatically launches, logs the user into the Connection Broker using the credentials provided at login and, if the user is assigned a single desktop, launches the remote viewer session. Do not install client-side credential passthrough on a client device running a Windows 7 or Windows Server 2008 operating system if that client device connects to Windows 7 or Window Server 2008 remote desktops. The Leostream credential provider is incompatible with the Windows credential provider in this configuration, with the result that RDP connections cannot be established. If the Windows 7 or Windows Server 2008 client device connects only to older versions of the Windows operating system, client-side credential passthrough is supported. Install Leostream Update service: Select this task to instruct Leostream Connect to contact the Connection Broker and automatically install any available Leostream Connect updates. Because the Leostream Update service runs in the system context, the user does not require administrator privileges on the client to upgrade Leostream Connect. Install Microsoft VC++ runtime: Select this task if you do not have the latest Microsoft Visual C++ run-time libraries installed on the desktop. 47

48 Chapter 5: Installing Leostream Connect 8. Click Next>. Uncheck this option only if the desktop already has an installed Microsoft VC++ runtime environment. 9. Review the installation setup in the Ready to Install page, and click Install. 10. When the installation completes, you may be given the option of restarting your computer, as shown in the following figure. Select an option to restart now or later. If you do not restart the desktop when prompted, you may encounter difficulties when subsequently upgrading Leostream Connect. 11. If Leostream Connect does not require you to restart your computer, the following dialog opens: 12. Click Finish, and the Leostream Connect icon appears on your desktop and in your Start menu. 48

49 Installation Guide Entering the Connection Broker IP Address Leostream Connect can automatically determine the Connection Broker address by querying the DNS SRV records. If you do not want do configure an SRV record, you can manually enter the Connection Broker IP address, as follows: 1. Launch Leostream Connect, for example, by double-clicking on the Leostream Connect icon. 2. Click Cancel on the Login User dialog. Alternatively, if you installed Leostream Connect in shell mode, press Ctrl-Shift-O to open the Options dialog, and skip to step Select Options from the Leostream Connect system tray menu. 4. In the Broker tab, uncheck the Obtain Connection Broker address automatically option. The Address edit field enables, as shown in the following figure. 5. Enter the Connection Broker address in the Address edit field. 6. Click Apply to accept the address, or OK to accept the address and close the dialog. You can click Test to check if the Connection Broker address you entered is valid. A dialog opens, indicating if the Leostream Connect client can contact the Connection Broker at the specified address. 49

50 Chapter 5: Installing Leostream Connect Installing on Linux and Apple Mac Operating Systems The Leostream Connect for Linux can be downloaded from the Leostream Resources > Downloads & Documentation Web page: Leostream Connect for Linux is a Java application, which requires the following additional software be installed on your client device. An X Window System, such as X11 R6 or X.Org A Java Run Time Environment (JRE) version 1.7 or higher Leostream Connect is packaged as an installer that runs on the following operating systems. Apple Mac CentOS Debian Fedora Novell SUSE Linux Enterprise Red Hat Enterprise Linux Solaris Ubuntu For information on installing Leostream Connect onto an HP gt7725 thin client, see the How do I install Leostream Connect on an HP gt7725 Thin Client? article on the Leostream Knowledge Center. You cannot perform a network install of the Java version of Leostream Connect. Prerequisites for Installing USB over IP Support Leostream provides USB redirection for 32- and 64-bit Linux operating systems. On Linux operating systems, the Leostream Connect installer must build the USB drivers. In order to build the drivers, Leostream Connect requires the following two header files: hcd.h hub.h Leostream Connect provides these header files for kernel versions through Higher kernel versions include these header files in the kernel source. USB redirection is not supported for kernel versions higher than

51 Installation Guide Leostream Connect uses files in the kernel source directory to execute the make command that builds the drivers. These files are typically located in /usr/src/kernels. Some operating systems provide the necessary directories. If your operating system does not provide the appropriate kernel files, you must download and install them, using the appropriate distribute method for your operating system. For example, use the following commands for desktops running CentOS. yum install kernel-devel yum install gcc You must install the kernel source that exactly machines your kernel version. To determine which kernel version your Linux desktop is running, execute the following command. uname r Installation Instructions If you plan to install the Leostream USB over IP feature, you must install Leostream Connect as root. To install Leostream Connect: 1. From the directory that contains the installer, issue the following command: java -jar LeostreamConnectJava-x.x.x.x.jar Where x.x.x.x is the version number at the end of the installer file name. If the desktop has multiple JRE versions, enter the full path to the correct Java installation. The installer Welcome page, shown in the following figure, opens. 51

52 Chapter 5: Installing Leostream Connect 2. To run the installer with debugging trace turned on, include the following text in the command line: -DTRACE=true For example: java DTRACE=true -jar LeostreamConnectJava-x.x.x.x.jar 3. Click Next. 4. The License Agreement page opens, as shown in the following figure. In this page: a. Read the license agreement. b. If you accept the license agreement terms, select the I accept the terms of the license agreement option. c. Click Next. 5. In the Additional Tasks page, shown in the following figure, select the appropriate tasks to complete during installation. By default, you must install the Leostream Connect for Java task. 52

53 Installation Guide a. If you are using Leostream to redirect USB devices from the client to the remote desktop, select the USB over IP integration option. This option is not available when installing into a Sun Ray environment. b. After selecting the appropriate tasks, click Next. 6. In the Installation Directory page, enter or browse for the location to install Leostream Connect. If you are installing Leostream Connect into a Sun Ray environment and previously installed the Leostream Agent, ensure that Leostream Connect installs into a different directory than Leostream Agent. 7. Click Next. 8. If necessary, the installer warns you that it will create or over write the installation directory. Click OK to accept the warning and move on with the installation, or Cancel to enter a different directory. 53

54 Chapter 5: Installing Leostream Connect 9. In the Configuration page, specify the Connection Broker address to use with Leostream Connect. If you have a DNS SRV record for your Connection Broker, leave the Connection Broker Address field empty and select the Enable auto-detection of broker using DNS option. To enter a static Connection Broker address, clear the selection in the Enable autodetection of broker using DNS option and enter the address into the Connection Broker Address field. You can specify or change the Connection Broker address associated with Leostream Connect at any time, by modifying the lc.conf file. See the Leostream Connect Administrator s Guide and End User s Manual for information on using this file. 10. Click Next. 11. If you selected the USB over IP integration task, specify the full path to the Linux kernel build directory, as shown in the following figure. The installer validates this directory by looking for the module.symvers file. If this file does not exist in the specified directory, you cannot continue with the installation. 54

55 Installation Guide 12. Click Next. 13. The Ready to Install page, shown in the following figure, provides a summary of the settings you set in the installer. Click Next to begin the installation. 14. The installer displays the progress of the installation. If you are installing the USB over IP feature, the installer appears to pause halfway through the installation. At this point, the installer is building the drivers necessary for USB support, which may take a couple minutes. After the installation completes, click Next. 15. In the Installation Finished window, click Generate an automatic installation script if you want to generate an XML-file that can be used to perform silent installations of Leostream Connect on other clients. 16. Click Done to exit the installer. If you installed the USB drivers, check that the daemon is live by running the following command: cat /proc/modules grep lsusbd If the daemon is not live, the remote desktop cannot accept USB devices. Contact supportsite@leostream.com for resolution. Leostream Connect Files In addition to the files in the Leostream Connect installation folder, the installer adds the release information file leostreamconnect.release to the client device. The location of this file depends on whether the installer was run as root, or not. If installing as root, the file is located in /etc/leostreamconnect.release If not installing as root, the file is located in the.leostream directory, found in the home directory of the user who ran the installer. 55

56 Chapter 5: Installing Leostream Connect Leostream Connect creates a.leostream directory in the user s home directory. This directory has the following purposes. When Leostream Connect runs, it creates a.lock file in the.leostream directory to prevent simultaneously running multiple instances of Leostream Connect. If no log file or directory was specified for Leostream Connect, or Leostream Connect cannot write logs to the specified file and/or directory, then Leostream Connect creates an lc.log file in the user's.leostream folder to keep track of errors/debugging information. If the user running Leostream Connect cannot write to the lc.conf file found in the installation directory, or cannot write to the lc.conf file in the directory specified when running Leostream Connect, then Leostream Connect creates an lc.conf file in the user's.leostream folder. Silent Installations using XML-Files The Java version of Leostream Connect supports silent installation using an XML-file. You must perform the installation once using the Graphical Installer, and click the Generate an automatic installation script option on the final panel in the installer to generate the required XML-file. To perform a silent installation, copy the generated XML-file and the original Leostream Connect installer to the new client device. Use the following command to run the silent installation. sudo java jar LeostreamConnectJava-x.x.x.0.jar auto-install-xml-path Where: java is the full path to the java binary JRE x.x.x.0 is the version number at the end of the installer file name auto-install-xml-path is the full path to your XML-file Installing Leostream Connect on HP Thin Clients Some HP thin clients include a native Leostream client. For thin clients that do not include a Leostream component, you can install the Leostream Connect software client. To access the Leostream Connection Broker from an HP client running Microsoft Windows XPe, install the windows version of the Leostream Connect client. To access the Leostream Connection Broker from an HP client running a version of a Linux operating system, install the Java version of the Leostream Connect client. When you install the Java version of Leostream Connect, the client creates a client ID, which it sends to the Connection Broker when a user logs in from the thin client. The Connection Broker 56

57 Installation Guide uses the client ID to uniquely identify different physical client devices. If you clone your thin clients from a standard image that includes a Leostream Connect installation, you may create multiple unique physical devices with the same client UUID. The replicated client identifiers cause the Connection Broker to incorrectly inventory your client devices. To avoid this problem, delete the.clientuuid file found inside the Leostream Connect installation directory on the image used to build your thin clients. 57

58 Chapter 7: Setting Connection Broker DNS Service Location (SRV) Chapter 7: Setting Connection Broker DNS Service Location (SRV) Service Location records enable the Leostream Agent and Leostream Connect to automatically discover the address of the Connection Broker by querying the DNS server for the following SRV record: _connection_broker._tcp.yourdomain.com. Where yourdomain.com is your domain. A correctly configured DNS server returns the IP address of one Connection Brokers. If you have multiple Connection Brokers, create multiple _connection_broker SRV records. The DNS server returns the weight and priority of each SRV record. Weight: Allocates connection requests between Connection Brokers in the same cluster. The default value of 100 indicates that the load is evenly spread between all Connection Brokers. Setting the weight higher indicates that a particular Connection Broker handles a greater percentage of requests. Priority: Sets the order in which Connection Brokers are queried. A priority of zero means a Connection Broker (or a cluster of brokers that all have the same priority) would be selected first. A priority of is the lowest possible priority. Use priority, in conjunction with dividing Connection Brokers up into geographic regions, to ensure that a user is normally connected to a cluster in their region, but, if this cluster is down, they are connected to the next closest region. To achieve this it is necessary to setup Sites within DNS. A site corresponds to a geographic region, in this case. Manually register a Connection Broker with a Microsoft DNS server, as follows: 1. Open the DNS console and click on the Forward Lookup Zone. 2. Right-click on your domain name in the list on the left-hand side of the window, and select Other New Records from the context menu, as shown in the following figure. 58

59 Installation Guide 3. In the Resource Record Type dialog that appears, click on Service Location, as shown in the following figure. 4. Click Create Record. The New Resource Record dialog opens. 5. In the New Resource Record dialog, enter the following settings: Service: _connection_broker Protocol: _tcp Priority: 100 (This is a temporary value) Weight: 100 (This is a temporary value) Port Number: 443 Host offering this service: connectionbroker.domainname.com Where connectionbroker.domainname.com is your Connection Broker address. 59

60 Chapter 7: Setting Connection Broker DNS Service Location (SRV) 6. Click OK to save the settings and return to the main DNS console window. 7. To configure additional Connection Broker SRV records, in the Resource Record Type dialog, click Create Record and repeat steps 5 and 6. Otherwise, in the Resource Record Type dialog, click Done. To view your Connection Broker Service Location records, expand the domain name node in the DNS console and select the _tcp node, as shown in the following figure. You can check for the DNS SRV records using the following two nslookup commands: set querytype=srv _connection_broker._tcp.domain.name Where domain.name is your domain name. If the record exists, nslookup returns the priority, weight, port, and SRV hostname. Otherwise, it returns a message indicating the record is not found. You can use DNS A records instead of DNS SRV records. However, the Leostream Agents and Leostream Connect clients will not automatically discover the Connection Broker address in a DNS A record. If using DNS A records, you must manually configure the Connection Broker address in every Leostream Agent and Leostream Connect client. In addition, to have the Connection Broker send the name in the A record instead of the Connection Broker IP address, you must enter the A record name into the Connection Broker VIP field (see Setting Network Configuration and Connection Broker VIP in the Connection Broker Administrator s Guide). If the Java version of the Leostream Agent is not detecting the DNS SRV record, ensure that the resolve.conf file on the desktop where the Leostream Agent is installed contains information for the correct domain. If the DNS SRV record exists in a different domain from that specified in the resolve.conf file, the Leostream Agent cannot discover the Connection Broker address. 60