Home

Connection Broker

Contents

1. Click OK to save all changes to the device properties You must individually configure each prestaged device Creating a Windows Deployment Server Center After you configure your Windows Deployment Services to use it with Leostream and deploy Windows images to your Moonshot nodes create a Windows Deployment Services center in your Connection Broker rood Es Leostream defines centers as the external systems that the Connection Broker communicates with to inventory desktops and other resources such as OS images applications printers and Teradici PC over IP host devices To create a Windows Deployment Services center 1 Go to the gt Resources gt Centers page in your Connection Broker 23 Using Leostream to Manage HP Moonshot Systems Click the Add Center link In the Add Center form select Windows Deployment Services from the Type drop down menu In the Name edit field enter a user friendly display name for this center In the Hostname or IP address of the Windows deployment services server edit field enter the WDS server address To limit the number of concurrent deployment commands sent to the WDS server enter that limit into the Maximum concurrent deployments edit field Enter zero or leave the field blank to allow an unlimited number of simultaneous deployments For information on configuring your WDS server to support a large number of concurrent connections consult the Windows Server documen
2. Using Leostream to Manage HP Moonshot Systems To scale a Leostream environment create a cluster of Leostream Connection Brokers connected to a single Microsoft SQL Server or PostgreSQL database The database holds all the Connection Broker configuration information as well as the Leostream Job Queue The brokers in the cluster work off the common job queue to handle user logins center scans and any other scheduled Connection Broker job Creating a cluster addresses three scalability goals Availability Using clusters enhances availability by allowing any Connection Broker instance in the cluster to handle the necessary system functions without operator intervention If one Connection Broker in the cluster fails user logins are processed by the other Connection Brokers resulting in no break in the end user experience Connection Broker instances that are not handling logins automatically process other system tasks Disaster Recovery Using clusters also allows you to mitigate system or site failures Run each Connection Broker in the cluster on a different virtualization host to ensure resiliency to a host failure Place Connection Brokers or entire clusters in different datacenters or regions to support disaster recovery scenarios Capacity The number of logins per second that can be handled depends on the overall structure of your Connection Brokers database and authentication server Typically each Connection Broker can handle 5
3. suspended desktops option in the When User is Assigned to Desktop section for example 36 Using Leostream to Manage HP Moonshot Systems Q Desktop Assignments from Pool Moonshot When User Logs into Connection Broker Number of desktops to offer 1 v Pool Moonshot v Backup pool Select v Offer desktops from this pool To all users of this policy M Select desktops to offer based on User follow me mode v Display desktop to user as Desktop name M Allow users to reset offered desktops No v Offer running desktops Yes only if Leostream Agent is running v Offer stopped and suspended desktops Yes only if Leostream Agent is installed v Offer desktops with pending reboot job Yes M Desktop selection preference Favor desktops previously assigned to this user v When User is Assigned to Desktop Revert the desktop to its most recent snapshot Confirm desktop s current power state Y Power on stopped or suspended desktops 7 Inthe Plans section select the Protocol Power Control and Release plan to associate with the desktop pulled form this pool for example Plans Protocol RGS v edit Power control Shutdown on Logout v edit Release Persistent v edit 8 Click Save For information on advanced features in the policy form see Configuring User Experience by Policy in the Connection Broker Administrator s Guide Adding Authentication Servers The Connection Broker authenticates users and in part
4. 10 minutes Y Y Offer desktops from this center Assign rogue users to desktops from this center requires Agent Set newly discovered desktops to Unavailable Continuously apply any Auto Tags Enter a name for the center in the Name edit field Enter the appropriate information in the Hostname or IP address of Chassis Management Module edit field In the Username and Password edit fields enter the credentials for a user with administrator privileges to the Chassis Manager The Inventory refresh interval instructs the Connection Broker on how often to refresh the desktops imported from this center The refresh interval is the length of time between when one refresh action is completes and the next refresh action begins Using Leostream to Manage HP Moonshot Systems For Moonshot the refresh interval is responsible for checking the power state and 8 Leave the remaining settings at their default values and click Save For a description of the additional center options see HP Moonshot System Centers in the Connection Broker Administrator s Guide After you save the center the Connection Broker contacts the Chassis Manager and retrieves information about the cartridges and nodes installed in the chassis and displays the nodes on the gt Resources gt Desktops page If the nodes do not have an installed operating system or a running Leostream Agent the Connection Broker retrieves only the nodes MAC addresses from the cha
5. 3 Enter a unique name for the plan in the Plan name edit field 4 Inthe When User Logs Out of Desktop section select Shutdown from the second drop down menu 5 Click Save Shutting down the node after use is optional Configure your Power Control Plan based on your particular needs Release Plans Release plans define how long a desktop remains assigned to a user and when it is released to its pool as well as if a user should be forcefully logged out of their desktop Available release plans are shown on the gt Plans gt Release page New Connection Broker installations contain one default release plan called Default The default release plan assigns a desktop to a particular user when the user first requests a connection to that desktop and leaves the desktop assigned to that user until they log out After the user logs out the default Release plan releases the desktop back to its pool 0900 Fin Leostream as long as a desktop is assigned to a particular user the Connection Broker offers that desktop only to that user If a desktop is for shared use you must release the desktop back to its pool The Connection Broker removes any user assignment when the desktop is released to its pool 34 Using Leostream to Manage HP Moonshot Systems To model persistent desktops allow the Connection Broker to policy assign a new user to an unassigned node but configure the Release Plan to maintain the assignment permanently Y
6. 39 25 AM Modified Friday August 8 2014 1 47 22 PM HAL type acpiapic Allow image to install in unattended mode Unattend File Images Windows 7 SP1 Moor Select File Prestaged Devices a You do not need to configure prestaged devices if you selected Respond to all client computers known and unknown for the PXE Response Policy see PXE Response Policy 21 Using Leostream to Manage HP Moonshot Systems The Prestaged Devices folder contains a list of known client devices that the WDS server will respond to when they perform a PXE boot Prestaging clients allows you to restrict the WDS server to respond only to a set of client devices for example just your Moonshot nodes If you configure your WDS server to respond only to known client computers you must configure the PXE Prompt Policy and Boot images on the Device Properties dialog After you add your prestaged devices right click on each device and select the Properties option In the Device Properties dialog that opens click on the Boot tab and configure the following two settings e Set the PXE Prompt Policy to either Always continue the PXE boot or Continue the PXE boot unless the user presses the ESC key This setting ensures that you do not have to interact with the nodes console in order to perform the PXE boot 1 Set the Boot Image to the default boot image specified for the Windows Deployment Services see B
7. Leostream to Manage HP Moonshot Systems Define pool using Centers v Center Selection Define a pool of desktops by selecting the desired centers Available centers Selected centers AD Helion Moonshot Uncategorized Desktops vSphere vSphere5 WDS 2012 Add highlighted items Remove highlighted items Add all items in list Remove all items in list Distribute new desktop assignments Evenly across all hosts v 7 Select one or more HP Moonshot System centers from the Available centers list 8 Move the center to the Selected centers list by clicking the Add highlighted items arrow 9 Use the Distribute new desktop assignments drop down menu to indicate the method used for distributing desktop assignments across the centers either e Evenly across all hosts This option evenly distributes desktop offers across all centers in the pool when possible To maximize the benefit of using this option ensure that the users policies set the Desktop selection preference option for this pool to any available desktops e To center with most available desktops This option randomly selects an available desktop from the center that contains the most desktops available for assignment e To center with least number of assignments This option randomly selects a desktop from the available desktops in the center with the least number of assigned desktops 10 Click Save The gt Resources gt Pools page displays a hierarchy
8. Lock desktop No v Perform actions when the user s session is idle frr No You can monitor CPU levels to delay the logout nti any processes the user is running complete Logout No Indicate if the desktop should be released back When Desktop is First Assigned to its pool independent of disconnect logout Release to pool No v or lock events If the user remains logged into Release if user does not login No the desktop after it is released the Connection Broker considers the user as rogue When Desktop is Released _ Log user out of the desktop lt To avoid rogue users forcefully log out the Delete virtual bin Fom dk user when the desktop is released to its pool Desktop must be in VMware or Leostream Cloud and also be marked as deletable Select this option if the Connection Broker should BOT OTC DOE SD DO MORE IR OMSK PICS delete the VM as soon as the desktop is released Notes The Edit Desktop page for the desktop must indicate that the desktop is deletable 3 Enter a unique name for the plan in the Plan name edit field 4 Inthe When User Logs Out from Desktop section select No from the Release to pool drop down menu 35 Using Leostream to Manage HP Moonshot Systems 5 Click Save The When Desktop is Idle section can be used with persistent desktops to add security by locking disconnecting or logging out the user s RGS session when the user is idle Creating Policies After you
9. for Active Using Leostream to Manage HP Moonshot Systems Directory this is sAMAccountName 9 Click Save For information on additional fields in the Add Authentication Server form see Chapter 13 Authentication Users in the Connection Broker Administrator s Guide Assigning Policies to Users When a user logs in to the Connection Broker the Connection Broker searches the authentication servers defined on the gt Users gt Authentication Servers page in order of the Position property until it locates the user After locating the user the Connection Broker steps through the assignment rules defined for that authentication server on the gt Users gt Assignments page to determine the user s role and policy The gt Users gt Assignments page automatically contains one row for every authentication server you defined on the gt Users gt Authentication Servers page Click the Edit link next to an authentication server to view the assignment rules associated with that server By default the Query for group information option is checked when you create your authentication server and the Edit Assignment form appears as in the following figure Domain name leostream Assigning User Role and Policy In this section you can set up rules to assign Users to Roles and Policies based on their group membership Optionally use the Order column to re order the rows Order Group Client Location User Role User Policy 1 any gr
10. logins per second To increase this throughput add additional Connection Brokers on different hosts and spread the traffic between the Connection Brokers using a load balancer The throughput scales linearly when using up to ten Connection Brokers For information on creating a Leostream cluster see Chapter 18 Scaling Deployments in the Connection Broker Administrator s Guide 47
11. management Traditional VDI environment however are often performance challenged especially when compared to traditional desktop paradigms Common VDI deployments may host over 100 virtual desktops on a dual socket server where joint sharing of resources like compute memory storage and networking causes bottlenecks and poor user experience Addressing these deficiencies by adding additional resources significantly increases the cost of VDI environments A key aspect of the end user experience is video quality In VDI achieving exceptional video quality can be a challenge because GPU functionality is typically provided by software rendering on the system CPU instead of specialized hardware Direct mapped GPU technology in the virtual environment or virtualizing dedicated GPU hardware among many users exists today but user density is very low and the cost is higher Enter HDI The HP Moonshot System HDI solution leverages the HP ProLiant m700 Server Cartridge and latest SoC System on a Chip from AMD with built in GPU APU This solution enables delivery of a natural desktop video experience all in a low power envelope with high density Solution Overview The Leostream HDI solution is designed to work with HP Moonshot System to help administrators manage and connect users to persistent desktops on HP ProLiant m700 Server cartridges The solution consists of the following high level configuration steps Install Register Moonshot Configu
12. of all available pools For a complete description of pools see the Creating Desktop and Application Pools chapter in the Connection Broker Administrator s Guide Defining Protocol Power Control and Release Plans After you separate your desktops into pools define the behaviors you want to assign to the desktops in those pools To perform this step ask yourself the following questions e What display protocols do want the user to be able to use to connect to their desktops e How do I want to manage the power state of each desktop for example should it be turned off when the user logs out e How long do I want my users to be able to claim a particular desktop For example if the user logs 31 Using Leostream to Manage HP Moonshot Systems out should they remain assigned to that desktop or should another user be able to log into that desktop The Leostream Connection Broker defines a plan as a set of behaviors that can be applied to any number of pools This step describes three types of pool based plans 1 Protocol 2 Power Control and 3 Release Power control and release plans control three particular points in the user s experience e When the user disconnects from their desktop e When the user logs out of their desktop e When the desktop is released to its pool e When the user s session has been idle for a specified length of time A The remote desktop must have an installed and running Leostream
13. resources from multiple pools See Configuring Desktop Policy Options in the Connection Broker Administrator s Guide for a complete description Using Client Locations to Define End User Experience When a user logs into the Connection Broker from a client device the Connection Broker registers that client device on the gt Clients gt Clients page The Connection Broker also assigns that client to one or more locations A client location is similar to a desktop pool Location represents a group of clients with similar attributes You can use locations to assign printer mappings to the user s desktop change the user s protocol plan or even change the user s policy Locations are listed on the gt Clients gt Locations page You define locations using a series of rules based on client attributes For example the following figure shows a location that contains all client devices running a Linux operating system 43 Using Leostream to Manage HP Moonshot Systems Name Linux Subset of location All M ee eae eS ea whereas as sens eee eee sag fan syrah Ste No eee dere Client attribute Conditional Value Operating system Y is equal to v Linux any v v v v v Add rows The Clients must match any of the attribute rules OR The Clients must match all of the attribute rules AND Plans Printer Select y Protocol rdesktop v Notes The Plans section in the form allows you to assign a Printer p
14. you plan to respond to all client devices or only to prestaged devices you must specify a default image for the Moonshot architecture as shown in the Default boot image section of the following figure Multicast Advanced TEIP General PXE Response ADDS Client DHCP PXE Boot Policy After a network boot is initiated define when a PXE boot will continue Known clients Require the user to press the F12 key to continue the PXE boot Always continue the PXE boot Continue the PXE boot unless the user presses the ESC key O Never continue the PXE boot Unknown clients Require the user to press the F12 key to continue the PXE boot O Always continue the PXE boot Continue the PXE boot unless the user presses the ESC key O Never continue the PXE boot Default boot image optional x86 architecture ia64 architecture x64 architecture Boot x64 Images boot m700 wim am architecture x86 UEFI architecture x64 UEFI architecture 0000 E When you create a Windows Deployment Services center in your Connection Broker Leostream modifies the default image to include necessary Leostream components Leostream modifies only the default image for each architecture If you need to use different images for different nodes contact supportsite leostream com for instructions on how to modify multiple images 18 Usi
15. 1 Available Running WIN QBGBGFCA30I 10 27 101 11 FC 15 B84 22 F6 68 WIN QBGBGFCA30I Windows 7 5 6 29 0 C10N2 Available Running WIN EEQHMQV100C 10 27 101 21 FC 15 B4 22 F6 6A WIN EEQHMQV100C Windows 7 5 6 29 0 C10N3 Available Running WIN CEQJRAO3272 10 27 101 18 FC 15 B4 22 F6 6C WIN CEQJRAO3272 Windows 7 56290 C10N4 Available Deploying FC 15 B4 22 F6 6E Viewing Chassis and Node Status The Status link circled in the following figure for the HP Moonshot System center you created on the gt Resources gt Centers page uses the Chassis Manager CLI to return basic status information for the Moonshot Chassis You can use this information to track the internal temperature of the chassis as well as the status of fans etc LEOSTREAM Status Clients Plans Tags Pools Desktops Applications Printers Add Center Actions Name Type All All Edit Refresh Log Moonshot HP ConvergedSystem 100 The output displayed by clicking the Status link is a combination of the information provided by the following three chassis manager commands e show chassis info e show chassis status e show chassis temperature The Status link on the gt Resources gt Desktops page circled in the following figure provides information about any active connections to the desktop if the Leostream Agent installed on the node is responding as well as status information returned by the chassis manager LEOSTREAM Status I Client
16. Agent to allow the Connection Broker to distinguish between user logout and disconnect and to perform actions based on idle time Not all display protocols allow the Connection Broker to perform actions at these times Protocol Plans Protocol plans determine which display protocol the Connection Broker uses when connecting to a desktop from a particular pool For a complete description of protocol plans see Building Pool Based Plans in the Connection Broker Administrator s Guide The Connection Broker provides one default protocol plan which is shown on the gt Plans gt Protocol page shown in the following figure LEOSTREAM Status Resources Clients Users System Search Power Control Release Display Printer Registry Create Protocol Plan Actions Name Leostream API Protocols Web Al v Default RDP RGS VNC Radmin NoMachine NX rdesktop Ericom Blaze ActiveX RDP RDP VNC mn owser Protocols Edit When connecting users to Moonshot nodes with an installed RGS Sender create a new Protocol Plan that defines how the RGS connection is established as follows 1 Goto the gt Plans gt Protocols page 2 Click the Create Protocol Plan at the top of the page The Create Protocol Plan form opens 3 Inthe Plan name edit field enter the name to use when referring to this protocol plan 4 Inthe Leostream Connect and Thin Clients Writing to Leostream API section a Select Do not use from
17. C address etc You can click the Status link next to the HP Moonshot System center to display the general information about the chassis as well as temperatures power supply status and more see Viewing Chassis and Node Status Deploying Operating Systems You can deploy an operating system on to one or more nodes using the Deploy bulk action available for desktops For example 1 Go to the gt Resources gt Desktops page in your Connection Broker 2 Inthe Bulk Action column select the checkbox associated with each desktop To select all the listed desktops click the check box at the top of the Bulk action column 26 Using Leostream to Manage HP Moonshot Systems tot Aig the check boxes are not visible click the customize link at the bottom of the gt Resources gt Desktops page and add the Bulk actions column to the Selected items list 3 Select the Deploy action from the drop down menu at the top of the column of checkboxes as shown in the following figure LEOSTREAM su cent Centers Tags Pools Applications Print Import Desktop Import Range of Desktops Filter this list Pool Nodes v Clear all filters M Actions Name User Name Deploy Y All All bj Control Edit View Log Status C1N1 Control Edit View Log Status C1N2 Control Edit View Log Status C1N3 Control Edit View Log Status C1N4 7 Control Edit View Log S
18. DS server as described in the following sections General Windows Deployment Services Properties Leostream requires you to specify default images and PXE boot responses in the WDS server The following sections describe how to configure the WDS server properties to satisfy the Leostream requirements To access your WDS server s Properties dialog 1 Expand the Servers node in the Windows Deployment Services tree 2 Right click on the WDS server and select Properties as shown in the following figure File Action View Help es r Q Bm E1 Windows Deployment Services Windows Deploy ment Services a JG Servers b mp wds 2012 leastes p D Active Directory ti Windows Deploy ment Servi Remove Server Windows Deployment Services enable All Tasks network Sire This Microsoft Management Console 1 Help Windows Deployment Services You ce multicast transmissions and configuri 3 Inthe Properties dialog go to the tab indicated in the following sections 16 Using Leostream to Manage HP Moonshot Systems PXE Response Policy Leostream supports deploying Windows images to all known clients and to pre staged clients To specify which clients the WDS server manages open the Properties dialog for your WDS server and click on the the PXE Response tab Select one of the following two options shown in the following figure e Respond only to known client computers In this case you must configure
19. LEOSTREAM Connection Broker HP Moonshot Systems for Hosted Desktops Getting Started with Leostream Abstract This document provides information on the deployment and configuration of HDI using the HP ProLiant Moonshot m700 and m710 server cartridges using the Leostream Connection Broker The intended audience for this guide includes system and network administrators AllianceOne Partner Version 8 1 November 2 2015 Moonshot Program Using Leostream to Manage HP Moonshot Systems Contacting Leostream Leostream Corporation 465 Waverley Oaks Rd Suite 200 Waltham MA 02452 USA http www leostream com Telephone 1 781 890 2019 Fax 1 781 688 9338 To request product information or inquire about our future direction email sales leostream com Copyright Copyright 2002 2015 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 Leos
20. Name edit field 4 Select one of the following options from the User has access to Administrator Web interface drop down menu a Yes Administrator Web interface only if the user is not assigned desktops via a policy or does not need to access their desktops from a web browser b Yes Both Web Client and Administrator interface if the user needs to access their assigned desktops using a web browser as well as the Connection Broker Administrator Web interface 5 Use the remainder of the form to specify the Connection Broker Administrator Web interface permissions For example the role configured by the following figure gives the user view only access to the gt Resources gt Centers page but full access to the Edit Desktop pages and power on options on the Control pages accessed from the gt Resources gt Desktops page 45 Using Leostream to Manage HP Moonshot Systems Yes Administrator Web interface only v 6 Click Save For a complete description on setting up roles see Chapter 9 Configuring User Roles and Permissions in the Connection Broker Administrator s Guide Scaling Up Leostream Environments The Leostream Connection Broker is designed to handle large scale deployments simply and effectively Because Leostream is not in the data path of the user s desktop connection Leostream measures scale by the number of users logging in at any point in time not at the number of users actively logged in 46
21. Prestaged Devices to indicate which client computers Leostream manages see Prestaged Devices e Respond to all client computers known and unknown In this case Leostream manages the Windows deployment for all client computers PXE booting on this network see PXE Boot Policy for example Advanced Network TFTP apps Boot Client DHCP PXE Response Policy Define which client computers this server will respond to Known clients are clients that appear in the list of prestaged devices D Do not respond to any client computers O Respond only to known client computers Respond to all client computers known and unknown Require administrator approval for unknown computers When you select this option you must approve the computers using the Pending Devices node in the snap in Approved computers will be added to the list of prestaged clients PXE Response Delay Adjust how quickly this server responds to clients Delay in seconds 0 Regardless of which option you select ensure that you configure the PXE boot to proceed without requiring user intervention described in later sections 17 Using Leostream to Manage HP Moonshot Systems Default Boot Images Leostream supports deploying images to Moonshot cartridges based on the default images To set the default images go to the Boot tab of the Windows Deployment Services Properties dialog Regardless of if
22. assign policies based on the user s memberOf attribute 4 Select the group from the Group drop down menu If you are using locations select a location from the Client Location drop down menu see Using Client Locations to Define End User Experience Assign end user and administrator permissions by selecting an item from the User Role drop down menu see Role Based Administration Assign a policy by selecting an item from the User Policy drop down menu The Connection Broker steps through the rules in order and assigns the role and policy from the first rule that the user matches Edit the value in the Order column to reprioritize the assignment rules Logging into the Connection Broker The Leostream Test Login functionality allows you to simulate a user login to ensure that your policies plans and assignment rules are configured correctly To test a user login 1 Gotothe gt Users gt Users page Click the Test Login link The Test Login form opens In the User Name edit field enter the name of the user you want to simulate logging in Choose the user s domain from the Domain drop down meu Select lt Any gt to instruct the Connection Broker to search all domains Click Run Test The Connection Broker searches through the authentication servers and assignment rules to determine which policy and desktops to offer to the user The logic and results are displayed below the Test Login form 40 Using Leostream t
23. assigns desktop The Release Plan indicates if the Connection Broker releases the desktop back to its pool and unassigns the desktop Otherwise the Connection Broker retains the desktop assignment Connect Broker applies power plan Lastly the Connection Broker takes any power control actions set in the user s power plan Documentation Leostream Installation Guide How to install the Connection Broker Leostream Connect and Leostream Agent Operating System Deployment on HP ProLiant Moonshot Server Cartridges How to configure Microsoft Windows Deployment Services for use with HP Moonshot Systems RGS User s Manual Detailed instructions on installing and using HP RGS Choosing and Using Display Protocols Information on managing RGS connections using Leostream Using Leostream to Manage HP Moonshot Systems Leostream Connection Broker Installation and General Configuration The Leostream Connection Broker is available as a virtual appliance or an ISO that installs bare medal onto certain HP workstations The deployed Leostream Connection Broker is managed as an appliance Leostream delivers updates as a single update file that maintains the Connection Broker application and underlying operating system The Leostream Connection Broker 8 0 appliance consists of the following components e CentOS Linux 6 6 e Apache 2 2 26 Web Server e OpenSSL version 1 0 1 e VMware virtual hardware version 8 Installing the Connectio
24. ction Broker allows a desktop to be a member of multiple pools allowing you to change how you manage that desktop for different users When working with HP Moonshot Systems a pool may be a grouping off all nodes hosted in a particular chassis may include nodes in multiple chassis or conversely may be restricted to a subset of nodes from one chassis The key to pooling in Leostream is that you have the flexibility to structure your pools in the manner that best fits your users needs For example you can create a pool that contains all the nodes in one or more Moonshot chassis as follows 1 Go to the gt Resources gt Pools page 2 Click Create Pool as shown in the following figure The Create Pool form opens LEOSTREAM Status I Clients Plans Users System Centers Tags Desktops Applications Printers Greate Pool Click link to open the Create Pool form 3 Inthe Name edit field enter a name that uniquely describes this pool 4 Inthe Display Name edit field enter in an option name to display directly to the end user when offering them a desktop from this pool By default the user does not see the pool name 5 Select the parent pool from the Subset of pool drop down menu By default the pool draws desktops from the All Desktops pool 6 Select Centers from the Define pool using drop down menu The form updates to display the Center Selection fields shown for desktops in the following figure 30 Using
25. d for your deployment For example you may want to shutdown nodes when the user logs out You can build a power control plan that performs this action as follows 1 Goto the gt Plans gt Power Control page 2 Select Create Power Control Plan The Create Power Control Plan form shown in the following figure opens 33 Using Leostream to Manage HP Moonshot Systems Adil Enter a descriptive name You ll refer to this scriptive name You ll refe name when assigning the plan to a pool When User Disconnects from Desktop Wait 0 minutes then Do not change power state V Select the amount of time to wait before changing the desktop s power state A wait time of zero tells p the Connection Broker to immediately execute the Bn Do not change power state v selected power control action When User Logs Out of Desktop Wait O minutes v When Desktop is Released Bey minutes sl Do not change power state MN Choose to change the desktop s power state or Seo minutes aan n ee revert the desktop to a snapshot For the When Desktop is Idle Shutdown Connection Broker to take actions based on ps Shutd dP ff disconnect or idle time events you must install the Wait O minutes Y then edit aa a minutes oan Power off Leostream Agent on that desktops Notes Fine ak ed In addition not all display protocols support dette __ disconnect actions Revert to snapshot
26. define your pools and plans build policies The Leostream Connection Broker defines a policy as a set of rules that determine which desktops are offered to users how users connect to those desktops and how the Connection Broker manages the users sessions The Connection Broker provides one default policy assigns one desktop from the All Desktops pool You can modify the default policy or create a new policy to assign Moonshot nodes to users For example you can create a new policy as follows 1 Goto the gt Users gt Policies page 2 Click the Create Policy link The Create Policy page opens 3 Enter a name for the policy in the Policy name edit field For a discussion on the remaining general policy properties see the Connection Broker Administrator s Guide 4 Inthe Desktop Assignment from Pools section 5 Select the Moonshot pool from the Pool drop down menu By default the policy offers a single desktop from the pool as configured by the Number of desktops to offer drop down menu 6 The Power Control plan created for this example shuts down node when the user logs out Therefore configure the policy to offer stopped desktops by selecting Yes only if Leostream Agent is installed from the Offer stopped and suspended desktops drop down menu By default the Connection Broker powers on stopped desktops when the user requests a connection to that desktop This default behavior is controlled by the Power on stopped or
27. determines which policy to offer to a user based on the user s attributes in your authentication servers The Connection Broker can authenticate users in standard LDAP systems such as Active Directory OpenLDAP or Novell eDirectory as well as using NIS To add an Active Directory authentication server 1 Goto the gt Users gt Authentication Servers page 2 Click Add Authentication Server as shown in the following figure 37 Using Leostream to Manage HP Moonshot Systems 38 7 8 LEOSTREAM Users Roles Policies Assignments My Options Status Resources Clients Plans System Search Add Authentication Server In the Authentication Server name edit field enter a name for this record in the Connection Broker In the Domain Name edit field enter the domain name associated with these Active Directory servers If you configure the Authentication Server Features on the gt System gt Settings page to include a domain field on the login page use the Include domain in drop down menu to indicate if this domain should be shown in that field If you set the Domain field to be displayed as an edit field select Yes as default to populate the edit field with this domain In the Connection Settings section shown in the following figure point your Connection Broker to your Active Directory Server as follows Connection Settings Type Active Directory Specify address us
28. eam Agent then click Next DE Windows logon Enable USB over IP may require reboot Enable single sign on for PCoIP and VNC Install Microsoft C runtime lt Back Il Next gt Cancel Click Next gt to continue with the installation using only the selected task 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 as follows 1 Open the All Control Panel Items window and switch the View by drop down menu to Small icons 14 Using Leostream to Manage HP Moonshot Systems 2 Double click on the Leostream Agent icon in the Control Panel circled in the following figure The Leostream Agent dialog opens 5 OD A Control Panel v All Control Panel Items v Gi Search Control Panel Adjust your computer s settings View by Smallicons e Action Center Administrative Tools P AutoPlay y Backup and Restore Dy BitLocker Drive Encryption Eil Color Management Credential Manager ey Date and Time Default Programs av Desktop Gadgets g Device Manager R Devices and Printers Display E Ease of Access Center Folder Options A Fonts A Getting Started HomeGroup Indexing Options Internet Options Keyboard Location and Other Sensors P Mouse SE Network and Sharing C
29. enter EE Notification Area Icons E Performance Information and Tools 3 Gotothe Options tab 4 Uncheck the Obtain Connection Broker address automatically option The Address edit field enables as shown in the following figure Leostream Agent x Status Options About Leostream Agent Port to listen on 8080 al Leostream Connection Broker I Obtain Connection Broker address automatically Address 10 110 38 54 Test Enter a FQDN or IP address and port number IV Enable Logging Settings View Agent Log OK Cancel Apply 5 Enter the Connection Broker address in the edit fields 6 Click Apply to accept the address and leave the Leostream Agent dialog open or OK to accept the address and close the dialog 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 15 Using Leostream to Manage HP Moonshot Systems Setting Windows Deployment Server Options Before configuring WDS for use with Leostream create your custom Moonshot boot and install images and add them to the Windows Deployment Services management interface Information on configuring your Windows images for use with HP Moonshot Systems can be found in the Operating System Deployment on HP ProLiant Moonshot Server Cartridges Users Guide After your Moonshot boot and install images are listed in your WDS server configure your W
30. erties for example File Action View Help e alr X Ba E Windows Deployment Services Windows 7 SP1 Moonshot 4 Install Image s 4 F Servers Image Name J Architecture ds 2012 1 s 4 b gt f FR EE Windows 7 HOMEBASIC Moonshot x64 d nstall Images XES E Windows 7 HOMEPRE n 2 Windows 7 PROFESSI Windows 7 SP1 Moonshot rer Windows 7 ULTIMATE 4 Select Allow image to install in unattended mode 5 Specify the Unattend File for example br Windows Deployment Services a x File Action View Help es alm X e Bm General Version Filters User Permissions r Windows Deployment Services Windows 7 SP1 Moonshi 4 J Servers Image Name sy vn 7 PROFESSIONAL Moonshol 4 T wds 2012 leostream net re 7 HOMEBAS BEBE EESS NEL Moonshel 4 1 Install Images b amp Windows 7 Moonshot x86 g Windows 7 SP1 Moonshot b 2 Boot Images E Windows 7 HOMEPRE E Windows 7 PROFESSIG Image pe GE Windows 7 ULTIMATE State Online Install Image b 03 Pending Devices Architecture x64 pam Prestaged Devices Description Windows 7 PROFESSIONAL Moonshot p amp Multicast Transmissions b E Drivers Priority 500000 p a Active Directory Prestaged Devices Image group Windows 7 SP1 Moonshot Image format WIM File name install 3 wim Expanded size 11542 MB 12103138056 bytes Created Sunday November 21 2010 12
31. for physical machines No power control v Using Leostream to Manage HP Moonshot Systems The Power control for physical machines option does not apply to Moonshot nodes The Connection Broker uses the Chassis Manager CLI to power control individual nodes 3 Inthe Authentication Server Features section indicate if users have the option to specify their domain by checking the Add domain field to login page option Keep this option uncheck if you want to hide the Domain field from end users 4 Users that launch RGS connections to Moonshot nodes typically log in using the Leostream Connect software client Use the Leostream Connect Configuration section to set default Leostream Connect behaviors such as if the client should log the user out of Leostream after they close their RGS session 5 Click Save For a full description of the options on the gt System gt Settings page see Chapter 3 Configuring Connection Broker Settings in the Connection Broker Administrator s Guide Your Windows Deployment Services must be configured properly before you can use it with Leostream as described in the next session 13 Using Leostream to Manage HP Moonshot Systems Configuring Windows Deployment Services Creating an Initial Install Image Leostream deploys operating systems to the m700 Server cartridges using Windows Deployment Services Before adding a standard Windows 7 SP1 operating system image to your WDS server you ma
32. ge as shown in the following figure LEOSTREAM cue 18 I Clients Plans Users System lt Main Menu Tags Pools Desktops Applications Printers Add Cente vw Secondary Menu Link This document uses the following syntax to these menus and links e gt Resources indicates a main menu selection e gt Resources gt Centers indicates a secondary menu selection e Add Center indicates selecting a particular link or action on a page Formatting Conventions Format Indicates The name of a menu item button or link to be Bold clicked or a selection from a drop down menu Courier Example code commands directory file names or New text to be entered into an edit field Italics Part of a command to be replaced by information specific to your configuration Using Leostream to Manage HP Moonshot Systems What is HDI A Hosted Desktop Infrastructure HDI provides users with a Microsoft Windows or Linux desktop by using high density unshared desktop images running on enterprise hardware Each user s desktop image runs on dedicated unshared hardware and each end user remotely accesses their desktop image using a display protocol and client device Why HDI An HDI solution shares many of the benefits of a classic virtual desktop infrastructure VDI deployment while solving the problems commonly associated with VDI VDI and HDI both deliver data security power savings and centralized
33. igure illustrates the different steps involved in connecting users to desktops With the exception of authenticating users policy and plan logic determines how the Connection Broker handles each step Connection Connection User requests Broker Broker offers connection to authenticates desktop based on desired user user s policy desktops User signs into Connection Broker Connection Broker assigns desktop and connects user User ends Connection remote desktop Broker applies connection release plan Connection Broker applies power plans 1 User signs into the Connection Broker Users log into the Connection Broker using the Leostream Connect software client or an HP thin client when connecting to desktops using HP RGS Different clients support different types of authentication systems such as user name password smart cards or fingerprint readers Using Leostream to Manage HP Moonshot Systems Related Connection Broker authenticates user After the Connection Broker receives the user s credentials from the client device it searches for the user in the domains defined in the broker If the user previously logged in the Connection Broker begins by looking in the authentication server used for the previous login then searches the remaining authentication servers in the order defined by the authentication server s Position If this is the first time the user logged in the Connection Broker searches all authentication se
34. ing Hostnames or IP address Hostname or IP address Port qa 2k3 dcleo leostream_net 389 if using multiple addresses separate each entry with spaces j Algorithm for selecting from multiple addresses Random v The sequential algorithm uses the first working address in the list C Encrypt connection to the authentication server using SSL LDAPS a Select Active Directory from the Type drop down list b Enter the IP address or hostname of your Active Directory server in the Hostname or IP address edit field To associate multiple Active Directory servers with this authentication server record enter multiple authentication server addresses separated by blank spaces In the Search Settings section enter the username and password for an account that has read rights to the user records The Connection Broker does not write any information to your Active Directory server and does not need full administrator privileges to your AD server The User Login Search section define where and how the Connection Broker looks for a user in the Active Directory tree a Inthe Sub tree Starting point for user search field enter the fully qualified path in LDAP format to the top point on the authentication server tree you want the Connection Broker to search for users b Inthe Match Login name against this field edit field enter the attribute that the Connection Broker should match the user s entered login name against Typically
35. lan to the location as well as over ride the Protocol Plan assigned to that client via the user s policy You can also use the location on the gt Users gt Assignments pages to assign the user to a policy based on the client they use to log in see Assigning Policies to Users For more information on building locations and location based plans such as Printer plans see Chapter 12 Configuring User Experience by Client Location in the Connection Broker Administrator s Guide Role Based Administration The Connection Broker assigns a role to all users including the default Connection Broker Administrator Connection Broker roles determine what Connection Broker Administration functionality a user can view and use Using roles you can restrict or provide different levels of access to the Connection Broker configuration enabling role based administration The Connection Broker provides two roles a default Administrator role and a default User role The default Administrator role has permission to edit all Connection Broker settings in the Administrator Web interface while the default User role cannot access the Connection Broker Administrator Web interface To create a role with restricted access to the Administrator Web interface 1 Goto the gt Users gt Roles page 44 Using Leostream to Manage HP Moonshot Systems 2 Click on the Create Role link to open the Create Role dialog 3 Enter a name for the new role in the
36. mance and high quality service running varied individual workloads HP Remote Graphics Software HP Remote Graphics Software RGS provides flawless secure and instant access to desktops hosted in an HP Moonshot system from any location RGS provides 3D graphics support for the latest versions of Open GL and Direct X All applications run natively on the remote desktop taking full advantage of its graphics resources The remote desktop is transmitted over a standard network to a window on a local computer using advanced image compression technology specifically designed for digital imagery text and high frame rate video applications A local keyboard and mouse are supported as well as redirection of most USB devices to provide an interactive high performance workstation experience In addition with HP RGS 7 0 end users can access their desktop from a Windows 8 tablet by turning swipes into hot keys pinches into zooms and taps and presses into precise onscreen mouse clicks For more information on HP RGS visit www hp com go rgs Leostream Connection Broker The Leostream Connection Broker lies at the heart of any HDI deployment and is the key component for deploying operating systems to HP Moonshot nodes assigning desktops to users connecting users to their desktops and controlling the end user experience When used with an HP Moonshot System the Using Leostream to Manage HP Moonshot Systems Leostream Connection Broker deploy
37. n Broker Virtual Appliance If you are running your HDI in a datacenter that includes virtualization use the Leostream Connection Brokers virtual appliance The Connection Broker runs as a virtual appliance within the following virtualization platforms e VMware Workstation 9 and higher e VMware vSphere 5 x e Citrix XenServer 6 x e Microsoft Hyper V Server 2012 and Windows Server 2012 R2 Hyper V requires SCVMM e Red Hat Enterprise Virtualization 3 0 e OpenStack clouds The Connection Broker requires virtual resources equivalent to the following hardware e 1500 MHz or faster Intel Pentium IV processor or equivalent e 1vCPU e 2 0 Gbytes of RAM e 8 Gbytes of hard drive space e Bridged Ethernet adapter ideally with Internet connectivity Installation instructions for each virtualization platform can be found in the Leostream Installation Guide Installing the Connection Broker on HP Server Hardware The Leostream Connection Broker is available as an ISO created using standard backup and restore software This ISO is intended for installation on an HP ProLiant DL380p Gen8 Server Other hardware configurations may not be compatible 10 Using Leostream to Manage HP Moonshot Systems The Connection Broker ISO can be downloaded at the following location http www leostream com resources downloads private LeostreamConnectionBroker_ Restore DL380 iso Before proceeding with the installation please check the integrit
38. ng Leostream to Manage HP Moonshot Systems PXE Boot Policy If you configure the PXE Response tab in your WDS server to respond to all client computers use the PXE Boot Policy section in the Boot tab of the Windows Deployment Services Properties dialog to ensure that you are not required to confirm the PXE boot Select one of the following options e Always continue the PXE boot e Continue the PXE boot unless the user presses the ESC key For example Multicast Advanced General PXE Response ADDS PXE Boot Policy After a network boot is initiated define when a PXE boot will continue Known clients O Require the user to press the F12 key to continue the PXE boot O Aways continue the PXE boot Continue the PXE boot unless the user presses the ESC key O Never continue the PXE boot Unknown clients Require the user to press the F12 key to continue the PXE boot Always continue the PXE boot Continue the PXE boot unless the user presses the ESC key O Never continue the PXE boot Default boot image optional x86 architecture ia64 architecture x64 architecture Boot x64 lmages boot m700 wim am architecture x86 UEFI architecture x64 UEFI architecture AA 19 Using Leostream to Manage HP Moonshot Systems Client Properties In order to automate the operating system installation specify a clien
39. nnonrvnnnnnvensennnrnnensnnesrnneneen 7 HP Remote Graphics Software ssssiccscissacasetssnssseatiarassesdeexiatsoadanetasnoneansataneuscouniaes 7 Leostream Connection Broke liui cccccccccsecccesseccecesssccecessecceceessececeentececeenteceeeenteees 7 HOW LEOSTREAM MANAGES USERS eeccccceesecceceescceceenecceceenaececeenaececseaececesnaseeessnaseeensnaes 8 RELATED DOCUMENTATION sa Rae Re Re Re RG 9 LEOSTREAM CONNECTION BROKER INSTALLATION AND GENERAL CONFIGURATION10 INSTALLING THE CONNECTION BROKER VIRTUAL APPLIANCE ccccceescccecesseceeceeseceeeeenaes 10 INSTALLING THE CONNECTION BROKER ON HP SERVER HARDWARE 10 STARTING THE CONNECTION BROKER csseecccceseeccececeeccceceescececeencececeenaeeeceenaceeesenacerenenacs 11 ADDING THE LEOSTREAM LICENSE KEY cccccccsssecceceesecceceesccceceeacceceeaceecessaceeeesnaceeenenas 12 CONFIGURING GENERAL CONNECTION BROKER SETTINGS ceesccceceescceeceececeecesseceeeesnas 12 CONFIGURING WINDOWS DEPLOYMENT SERVICES vervasevvnnvanevnnnnnnuvnnnnanuvnnnnnnunvennununeer 14 CREATING AN INITIAL INSTALL IMAGE cceceecccceceeccececeecccceceescececeensececsenaceeceenaceeessnacereneaas 14 INSTALLING THE LEOSTREAM AGENT ccccccceeeecceceesecceceescceceesacceceesacceceesccecessuceeeeenneeeeees 14 SETTING WINDOWS DEPLOYMENT SERVER OPTIONS c eceseccceceecccceceecceeceeeccecssseceeeeeaas 16 General Windows Deployment Services Properties rrrrrr
40. o Manage HP Moonshot Systems Advanced Leostream Configurations Configuring RGS Connections The Connection Broker establishes an HP RGS connection by passing a list of RGS Receiver parameters configured in the Protocol Plan to the Leostream Connect client along with the necessary information about the user s desktop and credentials Leostream Connect then users the native RGS APIs to launch the RGS Receiver After establishing the connection from the RGS Receiver to RGS Sender Leostream Connect is not in the data path for the RGS connection All native RGS features can be used when logging in using Leostream Use the Configuration file in the Protocol plan to set the Rgreceiver parameters that define the default values for different RGS functionality The HP Velocity feature does not require additional configuration To configure advanced video compression include the following parameters in the HP RGS configuration file in your protocol plan e Rgreceiver ImageCodec IsH264Enable Set to 1 to enable advanced video compression e Rgreceiver ImageCodec IsCPUEncode Set to 1 to cause the RGS Sender to use CPU encoding for h 264 If this parameter is set to zero the RGS Sender uses the GPU for encoding if available The advanced video compression and HP Velocity functionality available in RGS 6 0 and higher require activation the first time the RGS Receiver connects to the RGS Sender When connecting natively from the RGS Receive
41. oot Settings For example General Boot Client Unattend Join Rights You can specify an optional referral server from which this computer should download its boot program and PXE prompt policy when it PXE boots PXE Prompt Policy After a network bootis initiated define when a PXE boot will continue Use PXE prompt policy from server O Require the user to press the F12 key to continue the PXE boot Always continue the PXE boot Continue the PXE boot unless the user presses the ESC key Never PXE boot Use the following boot program Boot Image You can specify a boot image to use when PXE booting this computer Click Select to select an image on the referral server specified above or select the local server if the referral server field is blank Boot Image Boot x64 Images boot m700 wim 22 Using Leostream to Manage HP Moonshot Systems Next on the Client Unattend tab of the Device Properties dialog select the unattend file for this prestaged device for example General Boot Client Unattend Join Rights wasee You can specify a dient unattend file to automate the Windows Deployment Services Setup dient Enter the path to the dient unattend file to use relative to the REMINST directory of the referral server specified above Unattend File WdsClientUnattend m700 ClientUnattend_Win7 xml Browse Create New
42. ou can create a persistent Release Plan as follows 1 Goto the gt Plans gt Release page 2 Select Create Release Plan The Create Release Plan form shown in the following figure opens create Release plan ION Enter a descriptive name Refer to this name Slee nane when assigning this plan to pools Performs actions when the user disconnects from their remote session Console sessions send lock events when the user disconnects so EA display protocols such as HDX do not invoke Forced logout No v this section of the Release Plan When User Disconnects from Desktop lt __ Release to pool No i URL to call To model a persistent desktop ensure that the desktop is not released on disconnect PE or log out events After a desktop is When User Logs Out of Desktop assigned to a user the Connection Broker Release to pool Immediately T offers that desktop only to that user URL to call If the Leostream Agent is not installed on the remote desktop the Connection Broker cannot When Connection is Closed lt E distinguish disconnect from log out events In h i i Execute actions for When User Logs Out of Desktop these casas the Connection Broker uses this section of the Release Plan if the user s This section of the plan executes when no Leostream Agent is installed or communicating on the remote desktop Leostream Connect client indicates the connection to the remote desktop closed When Desktop is Idle
43. oup v All M User v amp Default v 2 v All M User v amp Default M 3 v All v User v amp Default v 4 v All v User v amp Default v Add rows Default Role User v Users will be assigned to this role if they do not match an assignment rule Default Policy Default v Users will be sssigned to this policy if they don t match an assignment rule Y Query for Active Directory Group information You must save this form for this setting to take effect Yes Active authentication server The table contains a list of assignment rules that determine what Role and Policy the user is assigned based on who the user is their Group and what client they log in from the Client Location When using an Active Directory authentication server the group is defined as the memberOf attribute 39 Using Leostream to Manage HP Moonshot Systems If your Active Directory server defines a large number of groups the Edit Assignments form may take a long time to load If this is the case or if you need to assign roles and policies using a different authentication server attribute uncheck the Query for Active Directory Group information option at the bottom of the Edit Assignments form After you save the form the format of the Assigning User Role and Policy section changes For more information see Assigning Roles and Policies Based on any Attribute in Chapter 14 of the Connection Broker Administrator s Guide To
44. r to RGS Sender activation dialogs open indicating if the activation succeeded or failed Leostream Connect suppresses the activation dialogs however the activation continues to take place If you configured a proxy within RGS to perform the activation include the following three parameters in the RGS configuration file in your protocol plan e Rgreceiver Network ProxyEnabled Set to 1 to enable the proxy if required in the environment e Rgreceiver Network ProxyPort Specify the proxy port e Rgreceiver Network ProxyAddress Specify the proxy hostname or IP address RGS uses the system proxy settings but only when manual proxy configuration is enabled RGS does not support the use of use PAC WPAD or proxy authentication If there is no internet access and no proxy possible RGS fails to activate and disables the HP Velocity and Advanced Video Compression features If the activation fails you can use the following Rgreceiver parameters to configure the resultant behavior e Rgreceiver Activation AutomationMode Specifies the path to take if the activation fails 41 Using Leostream to Manage HP Moonshot Systems either o 0 Continue without activation in this mode the RGS Receiver silently disables features requiring activation HP Velocity and Advanced Video Compression for the current session and continues with the connection The next RGS connection triggers activation again o 1 Retry the activation in this mode
45. r virtual machines registered in a Microsoft Active Directory service e HP Moonshot Systems e Teradici PC over IP host devices e Printers registered in an Active Directory service e Citrix XenDesktop farms for establishing HDX connections For example the following figure shows a Connection Broker configured to manage HP workstations joined to an Active Directory domain desktops hosted in HP Helion Public Cloud Moonshot nodes and virtual machines hosted in vSphere 42 Using Leostream to Manage HP Moonshot Systems LEOSTREAM Status Clients Plans Users System Tags Pools Desktops Applications PColP Host Devices Printers Add Center Actions Name Type Datacenter Status All v All v All M Edit Refresh Log AD Active Directory Online Edit Refresh Log Helion Leostream Cloud Desktops Online Edit Refresh Log Status Moonshot HP ConvergedSystem 100 Online Edit Refresh Log PColP Devices PColP Devices Online Edit Refresh Test View Log vSphere VMware vSphere and vCenter Server Online For information on creating different types of Centers see Chapter 5 Understanding Connection Broker Centers in the Connection Broker Administrator s Guide To connect users to desktops in different centers using different display protocols create a Protocol Plan for each desired protocol Then build policies for the different types of resources or use a single policy to offer
46. re and Use WDS to deploy Configure Broker to Connection Chassis Manager with register WDS with OS to Moonshot offer Moonshot Broker Connection Broker Connection Broker nodes desktops to users The following sections describe the components included in the solution Using Leostream to Manage HP Moonshot Systems HP Moonshot System and HP Moonshot 1500 Chassis The HP Moonshot System is a leap forward in infrastructure design that addresses speed scale and specialization needs The HP Moonshot 1500 chassis provides several shared functions that are leveraged by HDI solutions The HP Moonshot System provides a variety of servers which HP designates as cartridges which are purpose built for different workloads For HDI workloads the HP Moonshot System utilizes the HP ProLiant m700 server cartridge For more information on HP Moonshot System visit www hp com go moonshot HP ProLiant m700 Server Cartridge The HP ProLiant m700 Server Cartridge features four AMD Opteron X2150 APUs for hosted desktop infrastructure workloads With integrated graphics acceleration this cartridge is the foundation of the HP Moonshot System delivering 44 lower TCO than traditional desktops while improving security and compliance for mobile workers Because each user has an independent CPU NIC RAM SSD storage and GPU the high density HP Moonshot System delivers a fully functional PC desktop experience to each user Users enjoy consistent reliable perfor
47. rrrnrrnrrnrrnrnnrrrennrn 16 mage Properties isi eeinetan a oeeaaeaii aen 20 Prestaged BEE 21 CREATING A WINDOWS DEPLOYMENT SERVER CENTER cccccceceecccceceescceeceensceecesseceeeeeaaes 23 MANAGING HP MOONSHOT SYSTEMS 00 ccccssssscccccsssceccssssccccsssceececescececceseeececsseeeeecees 25 CREATING AN HP MOONSHOT SYSTEM CENTER cccecescccceceecccceceesccceceecceecesseceeesssaceeeeeaaes 25 DEPLOYING OPERATING SYSTEMG ccccccsssscccceesecceceesecceceescceceescceceescceceeseceseesuceeeeennneeeeees 26 VIEWING CHASSIS AND NODE STATUS ceseecccceseecececeecccceceescececeenaececseaceecesnacecessnaserentaaes 28 BASIC CONNECTION BROKER CONFIGURATION cccccsssscecccsssccceccssseccccsssececcsseseeees 30 BUILDING POOLS Lunnan O AA 30 DEFINING PROTOCOL POWER CONTROL AND RELEASE PLANSG c cccssccssccssecssessseesees 31 Pr tocol Plans rane easier 32 Power Control Plans srrvvnnrnnnnvnnnonnvvnnnnnnnvnnvennnvnnvennrvnnsersvvnnssrsvvnnsersrvenssrsvvnesessvven 33 Release Plans rava 34 CREATING POLICIES se 36 ADDING AUTHENTICATION SERVERS ccccccceesecceceescceceessccecseacceceensececsenaceeeesnaceeeeenacereeenaes 37 Using Leostream to Manage HP Moonshot Systems ASSIGNING POLICIES TO USERS ccccceseecccceesecceceesecceceececceceeaccecessaccecseaceecsenacesessnaseeensaaes 39 LOGGING INTO THE CONNECTION BROKER cccccsssecceceececceceescceceesecceceescceceesuceeeeenteeeeeen
48. rvers in order of their position Connection Broker offers resources based on user s policy The Connection Broker assigns a Leostream policy to the user using the assignment table associated with the authentication server chosen in step 2 The policy determines the desktops and applications offered to the user USB passthrough permissions and the display protocol to use User requests connection to desired desktop The client lists all desktops offered to the user by their policy The user then requests a connection to their desired desktop Connection Broker assigns desktop After the user requests a connection the Connection Broker assigns that desktop to the user When a desktop is assigned to a particular user the Connection Broker never offers that desktop to another user After the assignment is made the Connection Broker passes configuration information used to establish the desktop connection to the client device The client device such as Leostream Connect then launches the native client for the display protocol In the case of an HP RGS connection Leostream Connect launches the RGS Receiver Neither the Connection Broker nor the Leostream Connect client proxy the RGS connection User ends remote desktop session When the user disconnects or logs out of their RGS session the Connection Broker applies any power control or release actions specified by the plans assigned to that desktop in the user s policy Connection Broker un
49. s Plans Users System Search Centers Tags Pools Applications Printers Import Desktop Import Range of Desktops Filter this list Select filter v Clear all filters M Actions Name User Name Availability Power Status Hostname M All v All v All v All v All D Control Edit View Log Status C10N1 Available Stopped WIN QBGBGFCA30I D Control Edit View Log Status C10N2 Available Stopped WIN EEOHMQV100C Control Edit View Log C10N3 Available Running WIN QTDPOOQM12P m Control Edit View Log Status C10N4 Available Running WIN OVNQB5006SP 28 Using Leostream to Manage HP Moonshot Systems dt You can use the Status link for a desktop to retrieve status information from the chassis manager even if an operating system is not yet installed on the node The output displayed by clicking the Status link for a desktop is a combination of the information provided by the following two chassis manager commands e show node status e show node detail 29 Using Leostream to Manage HP Moonshot Systems Basic Connection Broker Configuration Building Pools The Leostream Connection Broker defines a pool as a group of desktops or applications When offering desktops to a user Leostream relies on the desktop s pool membership to determine how to connect the user to the desktop and how to manage the user s session Unlike other brokering solutions the Leostream Conne
50. s 40 ADVANCED LEOSTREAM CONFIGURATIONS ccccssccccccssseccccssseccccessscccceseececcsseeeeees 41 CONFIGURING RGS CONNECTIONS cccccceseeccceeceeccececsecececeenacceceeaececesaceceesnaeeeessnseeeesaas 41 BUILDING A MIXED HDI AND VDI ENVIRONMENT eeevvrvvnrrnvrrvnrrnnrrvnsennrsvnssnnrsnnsenurrenssnursnnsennrn 42 USING CLIENT LOCATIONS TO DEFINE END USER EXPERIENCE essecceceeeecceceeeereeeeees 43 ROLE BASED ADMINISTRATION ccsccccceseccceceesecceceenscceceesacceceesuceeceescceceesceecesntceeseentneeeeeas 44 SCALING UP LEOSTREAM ENVIRONMENTS cccccecccceceecccceceescccecsescececseaceecesnaceeessnaseeeesaaes 46 Using Leostream to Manage HP Moonshot Systems Introduction Using This Documentation This guide is intended for system and network administrators who are configuring and administering the Leostream Connection Broker via the Administrator Web interface Information on installing and configuring additional HP Moonshot System hardware and software is detailed in the documentation referenced throughout this guide e The term you in this document represents the administrator installing and configuring the Connection Broker e The term user or end user represents an end user that logs into the Connection Broker to access their assigned desktop Navigational Conventions The Connection Broker Administrator Web interface contains two navigational menus in addition to a set of links on each pa
51. s operating system to the individual nodes using Microsoft Windows Deployment Services The Leostream Connection Broker consists of the following four components e Connection Broker The main virtual appliance that manages the Hosted Desktop Infrastructure HDI The Connection Broker is the central management layer for configuring your deployment including inventorying nodes in HP Moonshot Systems deploying operating systems assigning nodes to users and defining the end user experience e Leostream Agent The Leostream Agent provides the Connection Broker with insight into the connection status of remote users It is required when using Microsoft Windows Deployment Services in conjunction with Leostream e Leostream Connect A software client provided by Leostream that allows users to connect to their desktops from fat or thin clients Certain thin clients provide built in Leostream clients Leostream Connect is available as a Windows application and as a Java application that runs on Linux and Apple operating systems Users that connect to desktops using RGS must use Leostream Connect or a thin client that supports Leostream logins and RGS connections e Database In a proof of concept environment the Connection Broker stores all information in an internal database Production deployments that use Connection Broker clusters must use an external Microsoft SQL Server 2012 or 2014 database How Leostream Manages Users The following f
52. ssis manager for example LEOSTREAM Status Clients Plans Users System Search Centers Tags Pools Applications Printers Import Desktop Import Range of Desktops Filter this list Select filter v Clear all filters lt previous next gt Page M Actions Name User Name Availability Power Status Hostname IP Address MAC Address v All Y All Y Al vy All M All vy Al Y All v Control Edit View Log Status C21N3 Available Stopped FC 15 B4 22 95 94 Control Edit View Log Status C21N4 Available Stopped FC 15 B4 22 95 96 Control Edit View Log Status C22N1 Available Stopped FC 15 B4 22 37 88 Control Edit View Log Status C22N2 Available Stopped FC 15 B4 22 37 8A Control Edit View Log Status C22N3 Available Stopped FC 15 B4 22 37 8C Control Edit View Log Status C22N4 Available Stopped FC 15 B4 22 37 8E Control Edit View Log Status C23N1 Available Stopped FC 15 B4 22 17 98 Control Edit View Log Status C23N2 Available Stopped FC 15 B4 22 17 9A Control Edit View Log Status C23N3 Available Stopped FC 15 B84 22 17 9C Control Edit View Log Status C23N4 Available Stopped FC 15 B4 22 17 9E If the nodes have an installed operating system with a running Leostream Agent the Connection Broker contacts the Leostream Agent to obtain information about the desktop s hostname IP address operating system version alternate MA
53. t unattend file for the default boot images Go to the Client tab on the Windows Deployment Services Properties dialog and configure the following settings e Select the Enable unattended installation option e For the Moonshot architecture specify the client unattend file For example Muticast Advanced General PXE Response ADDS Boot Unattend file When enabled installation options on the client computer are defined using the settings in the Windows Deployment Services client unattend file that you specify here V Enable unattended installation x86 architecture ia64 architecture x64 architecture WedsClient Unattend m 700 Clie am architecture x86 UEFI architecture x64 UEFI architecture Joining a Domain _ Do not join the client to a domain after an installation Client Logging _ Enable client logging Logging Level Log error waming and informational messages Image Properties You must select an image unattend file in order to automate the Windows Operating System installation To set the image unattend file 1 Click on the Install Images folder in the Windows Deployment Services tree 2 Select the image group that contains the image you plan to deploy to the Moonshot cartridges 20 Using Leostream to Manage HP Moonshot Systems 3 Right click on the Image name in the list and select Prop
54. tation on optimizing performance and scalability for Windows Deployment Services Enter any arbitrary notes into the Notes edit field Click Save When you save the form the Connection Broker instructs the Leostream Agent installed on the WDS server to perform two tasks 1 2 The Leostream Agent returns a list of all available Windows images and unattend files to the Connection Broker The Leostream Agent prepares all default images for deployment During this step the Leostream Agent is injected into the default image allowing new desktops deployed from this image to register with the Connection Broker automatically Contact supportsite leostream com for information on how the Leostream Agent prepares the images for deployment by the Connection Broker 24 Using Leostream to Manage HP Moonshot Systems Managing HP Moonshot Systems Creating an HP Moonshot System Center The Connection Broker manages HP Moonshot Systems using the HP Chassis Manager RESTful API To create a center that communicates with the chassis manager 25 1 2 3 Go to the gt Resources gt Centers page Click on Add Center The Add Center form opens Select HP Moonshot System from the Type drop down menu The form updates as follows Type HP Moonshot System v If you change the type please wait for the form to repaint Name Hostname or IP address of Chassis Management Module Username Password Inventory refresh interval
55. tatus C2N1 v Control Edit View Log Status C2N2 v Control Edit View Log Status C2N3 4 Inthe Deploy desktop form that opens select the image to deploy from the Operating system drop down menu All nodes are deployed from the same image 1000 Ensure that you select an image that has been prepared to use on m700 Server cartridges 5 Click OK The Connection Broker switches the boot mode of each selected node to PXE and powers on or restarts the node If the number of selected nodes exceeds the maximum number of concurrent deployments specified in the WDS center the Connection Broker powers on the maximum number of allowed nodes and marks the remaining nodes as scheduled After the initial PXE boot succeeds and begins deploying the operating system to the node the Connection Broker automatically switches the boot mode for that node to HDD The deployment completes when the Leostream Agent injected into the image installs and registers with the Connection Broker providing the hostname and IP addresses of the newly deployed operating system The node s Power Status switches to running and the remaining node information is populated for example 27 Using Leostream to Manage HP Moonshot Systems Leostream Leostream Name Availability Power Status Hostname IP Address MAC Address Machine Name Operating System Agent Status Agent Version Al Y All v All t All v All Y All v All All M All Y Al bd C10N
56. the Leostream License Key The first time you sign in the Leostream license dialog shown in the following figure opens License key CI have read and accept the License Agreement If you have not obtained a Leostream license for your Connection Broker contact sales leostream com After you obtain a license cut and paste your Leostream license key into the License key edit field Ensure that there are no spaces in or after the sequence and that you include the lines containing the text BEGIN LICENSE and END LICENSE line Read the license agreement and if you accept it select the have read and accept the license agreement check box and click Save You now have access to the Connection Broker Administrator Web interface Configuring General Connection Broker Settings More advanced Connection Broker features are disabled by default When working with an HP Moonshot System in particular you must explicitly turn on the feature to use Windows Deployment Services as follows 1 Goto the gt System gt Settings page 2 Inthe Enable Features section select the Windows deployment services provisioning option as shown in the following figure Enable Features Hardware PColP support v USB passthrough control Connection Broker forwarding Virtual machine provisioning Registry plans Resource offers from XenApp Services Site Connection Broker metrics Power control
57. the Priority menu associated with RDP b Select 1 from the Priority menu associated with HP RGS 32 Using Leostream to Manage HP Moonshot Systems c Inthe Configuration file edit field specify values for any RGreceiver parameters that should be used to launch the connection for example Plan name RGS VY Leostream Connect and Thin Clients Writing to Leostream API RDP and RemoteFX Priority Do not use Y ThinAnywhere Priority Do not use Y VMware View Priority Do not use Y Citrix HDX Priority Do not use Y HP RGS Priority 1 v Send user login name as USER Configuration file Rgreceiver IsBordersEnabled 0 Rgreceiver IsBordersEnabled IsMutable 0 Rgreceiver IsMatchReceiverResolutionEnabled 1 Rgreceiver IsMatchReceiverResolutionEnabled IsMut able 0 Rgreceiver IsMatchReceiverPhysicalDisplaysEnabled 1 Rgreceiver IsMatchReceiverPhysicalDisplaysEnabled IsMutable 0 5 Click Save For more information on configuring RGS connections see Configuring RGS Connections Power Control Plans Power control plans define what power control action is taken on a desktop when the user disconnects or logs out of the desktop or when the desktop is released to its pool Available power control plans are shown on the gt Plans gt Power Control page New Connection Broker installations contain one default power control plan called Default You can edit the default or create as many additional power control plans as neede
58. the RGS Receiver retries activation before falling back The number of retries is controlled by the Rgreceiver Activation RetryAttempts parameter o 2 default Do not activate in this mode the RGS Receiver disables the features that require activation On the next connection if the user has not re enabled those features no activation attempt will occur Rgreceiver Activation RetryAttempts default 5 The number of reactivation attempts before disabling features that require activation For more information on using RGS with Leostream see the HP Remote Graphics Software chapter in the Leostream Choosing and Using Display Protocols guide For more information on HP RGS visit www hp com go rgs Building a Mixed HDI and VDI Environment Leostream Centers and Protocol Plans support a wide range of back end hosting systems and display protocols allowing you to develop a single environment to provide access to all hosted resources After you configure you Connection Broker to manage your HDI you can create additional Centers to inventory and manage other virtual machines and physical machines hosted in your datacenter The Connection Broker provides centers for e Virtual desktops from Red Hat Microsoft VMware Citrix and Xen virtualization hosts e Amazon Web Services and OpenStack clouds e Citrix XenApp applications and desktops e Microsoft Windows Remote Desktop Services Terminal Services servers e Physical o
59. tream HP HEWLETT PACKARD and the HP Logo are registered trademarks that belong to Hewlett Packard Development Company L P Linux is the registered trademark of Linus Torvalds in the U S and other countries 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 products are patent pending Using Leostream to Manage HP Moonshot Systems Table of Contents TABLE OF CONTENTS eeasevevnnenvvennnnnvvennnnnnvennnnnnvennnnnnvennnnnnvennnnnnvennnnnnvennnnnunennnnnnnennnnnnnennnununenene 3 INTRODUC TION bis ssssccccsssccccsnsesdecccensdcatesessaccnoedseessesssaccdeosdeatdeessaacnoosstaancesieannoosdeaiseessaaawoosseesssesseee 5 USING THIS DOCUMENTATION c ccsscccceceescceceeseccecessaccecseaccecessaececssaececesaeeeessnaeeeeesnaeeeeneaaes 5 Navigational Conventions saa ssasescisscctscsissaaneusutivscsrsaatpaessecbiesundentuaconanneeancusceineats 5 Formatting NN 5 WHAT IS HDI man ens 6 WHY HDI seanse 6 SOLUTION OVERVIEW urene Gears eneeier 6 HP Moonshot System and HP Moonshot 1500 ChassisS rrrnvrnrvrrnrrnrnrrrenennr 7 HP ProLiant M700 Server Cartridge ronrnonnrnvonrnennrnr
60. y of the downloaded ISO The MD5 hash for the ISO is a8bd81102a8e335975b34954aadb20e9 Starting the Connection Broker After you install and start your Connection Broker the Connection Broker IP address appears in the console for example Welcome to version To configure Leostream remotely please open a eb browser and point it to the following URL http 10 110 72 3 For support please go to http uuu leostream com support To login please type Ctrl C If the console cannot obtain an IP address from DHOP you can manually configure the network See Manually Configuring the Connection Broker Address section in the Leostream Installation Guide for more information For information on configuring the Connection Broker IP address from within the Connection Broker Administrator Web interface see Setting Network Configuration and Connection Broker VIP in the Connection Broker Administrator Guide Point your Web browser at the Connection Broker IP address The Connection Broker Sign In dialog shown in the following figure opens By default log in as e User name admin e Password leo sann welcome to the Leostream Connection Broker eee Sign in with user name admin password leo Password You will be able to change the password from the gt Users gt My Options page Signing in constitutes continued acceptance of the license agreement 11 Using Leostream to Manage HP Moonshot Systems Adding
61. y want to customize it by adding applications data etc Most importantly to provide RGS connections to your users you must install the RGS Sender as well as the AMD graphics drivers available through www hp com In order to deploy a Windows image onto a Moonshot cartridge the Windows image must be modified using a software bundle provided by HP The HP software bundle contains the minimum set of drivers necessary to deploy a functional Windows image on the cartridge as well as scripts and unattend files to use in Windows Deployment Services Using the scripts drivers and unattend files in the software bundle the deployed instance of Windows has SAC and RDP enabled For a full description on creating a custom Windows image and modifying the boot and install images using the HP software bundles see the Operating System Deployment on HP ProLiant Moonshot Server Cartridges Users Guide Installing the Leostream Agent In order to use your Windows Deployment Services with Leostream you must install the Leostream Agent on the Windows server hosting WDS See the Leostream Installation Guide for complete instructions When installing the Leostream Agent select only the task that installs the Microsoft VC runtime library as shown in the following figure 16 Setup Leostream Agent E Select Additional Tasks Which additional tasks should be performed Select the additional tasks you would like Setup to perform while installing Leostr

Download Pdf Manuals

Related Search

Related Contents

UltraSPARC User's Manual  Mode d`emploi du touret Modèle Sommaire Consignes de sécurité    GSC 2,8 Professional    HG "agent contre l`efflorescence de maçonnerie"  事故防止対策（埋設管・バルク貯槽等）  

Copyright © All rights reserved. Failed to retrieve file