Accops HyWorks v2.5 Quick Start Guide Last Update: 4/18/2016 2016 Propalms Technologies Pvt. Ltd. All rights reserved. The information contained in this document represents the current view of Propalms Technologies Pvt. Ltd. on the issues discussed as of the date of publication. Because Propalms must respond to changing market conditions, it should not be interpreted a commitment on the part of Propalms and Propalms cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. Propalms makes no warranties, express or implied, in this document. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) or for any purpose, without the express written permission of Propalms Technologies Pvt. Ltd.
TABLE OF CONTENTS Introduction... 2 About HyWorks... 2 Terminologies... 2 HyWorks Components... 3 Accops HyWorks Deployment Options... 4 Shared hosted desktops... 4 Dedicated desktops... 5 HyWorks Deployment in LAN Environment... 6 HyWorks Deployment in WAN Environment:... 6 Four Step Process of Deploying EDC Suite... 7 Install HyWorks controller Service and Management Console... 7 Configure HyWorks Controller... 8 License Configuration... 8 Desktop Provider ConfiGuration... 9 Authentication Server Configuration... 10 Configuring DVM Pools and Assignments... 10 Devices Configurations and User Logon... 11 Login from Device using appropriate user credentials... 13 Assumptions... 13 References... 14
INTRODUCTION ABOUT HYWORKS Accops HyWorks Suite is solution for deploying a secure, cost effective, less power consuming, less space consuming virtualized infrastructure for organizations. Fact that it can be deployed with VMware (vcenter Server or ESXi), Microsoft Hyper-V or SCVMM and Microsoft RDS makes it suitable for all the organization either organization willing to deploy the fresh virtualized infrastructure or organizations which are already having virtualized infrastructure in place. The HyWorks Suite can be used to serve dedicated desktops from virtualization platforms VMware, Citrix and Microsoft Hyper-V and also can be used to server shared hosted desktops and applications from Microsoft Terminal Servers. TERMINOLOGIES Following terms are used frequently in the remaining section of the document. Accops HyWorks Controller Service Accops HyWorks Controller Service runs as a windows service on supported windows platforms and is the primary controller layer for Accops HyDesk devices. The core operations of Accops HyWorks Controller Service are: Registering and managing devices Configuration and management of DVMs (Desktop Virtual Machines) Managing Sessions Maintaining logs for all device and controller interactions. The web interface used for facilitating all above tasks is Accops HyWorks Controller Management Console. Accops HyWorks Controller Management Console Accops HyWorks Controller Management Console is a web interface accessible on browsers and provides the interface for administrators to manage the devices, sessions, creation and management of desktop providers, connection profiles and other settings. Accops HyDesk, HyWorks Client Managed thinclients running integrated HyWorks Client software is termed as HyDesk. Following HyDesk models are supported: o Hy2000 o Hy3000 o Hy3200 o Hy4000 You will need one of these devices to connect to your virtual desktop infrastructure. HyWorks Client: Client application which can be installed on Windows or Linux platforms to work as an end point for HyWorks solution Desktop ProvIder Desktop Provider refers to resource which is going to provide the desktops to end users. The supported desktop providers can be of two categories:
DVM Providers: Hypervisors which can be configured to provider virtual machines from it. Supported hypervisors are: o VMware ESXi or vcenter Server (ESXi 5.1/5.5/6.0 vcenter 5.5/ 6.0) o Microsoft Hyper-V or SCVMM 2012 R2 o Microsoft RDS Server External Desktop Brokers: Refers to desktop providers which have their own management console for configuring user/ application/ desktop management. Supported external desktop providers are: o Propalms TSE (Version 7 with Web Service) o Pano Controller (version 6.0.1) Note: 1. Please note appropriate licenses must be available on ESXi or vcenter servers to enable the provisioning support. Standard or Evaluation licenses do not support APIs used by HyWorks Suite DVM Desktop Virtual Machine termed as DVM in the remaining section of the document. Virtual machine exported from DVM provider such as VMware or Microsoft Hyper-V is referred as DVM: Desktop Virtual Machine. DVMs can be managed from HyWorks Controller Management Console DVM tab HyWorks Tools and Accops HyWorks Desktop Agent HyWorks Desktop agent is an integral part of HyWorks Suite solution which comes packaged with HyWorksTools setup. HyWorks Desktop agent enables and configures the remote desktop services and power policies on the DVMs. HyWorksTools consists of Built-In USB redirection desktop component along with HyWorks Desktop Agent, which is recommended for dedicated desktop environment. HYWORKS COMPONENTS The following table lists the core components of HyWorks Suite, its necessity in deployment, download location of the same, where can it be installed etc. Component Is Necessary Installation Platforms Must to have Windows 2008 R2 or Windows HyWorks Controller Service (Installed with HyWorks 2012 R2 Controller) HyWorks Controller Management Console HyWorks License Service HyWorks Upgrade Service Must to have (Installed with HyWorks Controller) Must to have (Installed with HyWorks Controller) Good to have for automatic upgrade of HyWorksTools (Installed with HyWorks Controller) Windows 2008 R2 or Windows 2012 R2 Windows 2008 R2 or Windows 2012 R2 Windows 2008 R2 or Windows 2012 R2 HyDesk Clients Must to have HyDesks End Point
Dedicated VDI Shared Hosted VDI Accops HyWorks Tools Pano Direct Service In-Built Connection Broker (DVM Provider) Third Party - Pano Controller TSE Microsoft RDS VMware ESXi or vcenter Server Microsoft Hyper-V or SCVMM HyWorks DVM Agent USB Redirection Software Yes, if Pano Controller is configured as Desktop Provider Either of these must be configured for providing dedicated desktops to end users Recommended - In-built connection broker Either of the two must be configured for shared hosted VDI Recommended TSE Yes, for In-build Connection Broker Optional (Required for USB device sharing) Yes, On All Virtual Machines to be served from Pano Controller Thinclients with integrated HyWorks Client HyWorks Client Client software installed on supported Windows/ Linux platforms Please refer respective documents from VMware, Microsoft or Pano Controller deployments Pano Controller Readymade Appliance to be imported into Hypervisors TSE To be installed on Windows 2008 R2/ Windows 2012 R2 VM On all virtual machines, for configuring remote access and policy managements On all virtual machines for redirecting USB redirection On All Virtual Machines to be served from Pano Controller ACCOPS HYWORKS DEPLOYMENT OPTIONS Accops HyWorks Suite can be deployed to serve following two types of desktops to end users Shared Hosted Desktops Dedicated Desktops SHARED HOSTED DESKTOPS To deploy Accops HyWorks Suite with shared hosted desktops, will require TSE or Microsoft RDS to be installed and configured. TSE: For the deployment and configuration of TSE, please read section Installation and configuration of Propalms TSE Microsoft RDS: Microsoft RDS configuration is also supported in skyspace with the limitation that all user and policy management need to be done separately.
User Sessi ons HyWorks Client for PCs, Smart Phones TSE RDS (Micro soft) HTTP 80 TCP Applicati on Servers HyDesk Hy2000/3000/3 200/4000 HTTPS and RDP traffic HyWorks Controller Directory Servers LAN/WAN/Internet Note: The red text indicates the specific path to be used in WAN environment and green text specifies the LAN environment. G3 DEDICATED DESKTOPS To deploy Accops HyWorks with dedicated desktops, will require VMware/ Hyper-V or Pano Controller to be installed and configured. VMware and Microsoft Hyper-V: Please refer VMware and Microsoft websites to download and install the virtualization software in enterprise environments.
The above mentioned deployments can be achieved in the LAN or WAN environment with little modifications in the HyDesk and HyWorks Controller settings. HYWORKS DEPLOYMENT IN LAN ENVIRONMENT Deployment of HyWorks in LAN environment will require following infrastructure: 1. HyWorks Controller installed and available in the LAN and no firewall or third party software blocking HyWorks Controller 2. HyDesk or HyWorks Clients are installed up and running in the same network and able to connect HyWorks Controller using either of the following settings o Detect HyWorks Controller Automatically o Connect to a local HyWorks Controller 3. Desktop Providers (e.g. VMware vcenter Server or Microsoft SCVMM Server) and authentication servers e.g. Microsoft Active Directory are available in the same network, HyWorks Controller has direct access to providers 4. DVMs running on Desktop Providers are directly reachable to HyDesk/ HyWorks Client devices Refer deployment images from Accops HyWorks Deployment section (Green Path Indicates the LAN Implementation) It shows that the device should be able to talk to the Accops HyWorks Controller on port 38866 and to virtual machine on TCP port 3389 Note: The LAN environment is highly encouraged for better performance in remote sessions. HYWORKS DEPLOYMENT IN WAN ENVIRONMENT: In usage situations like access over Internet, the user may have direct access to Accops HyWorks Controller using public IP but the virtual machines may not be available over a public IP address. To allow users to be able to access their virtual machine over Internet or such physically or virtually nonaccessible network segments, a new proxy feature is developed in devices and Accops HyWorks Controller. The feature enables the device to connect to the VM through Accops HyWorks Controller. As per the feature, the device uses Accops HyWorks Controller as a proxy to access the virtual desktop. Refer deployment images from Accops HyWorks Deployment section (Red Path Indicates the WAN Implementation) Highlights of the WAN configuration will be: 1. Devices are able to directly access Accops HyWorks Controller but do not connect to desktop provider or desktops directly 2. Devices are using EDC HyWorks Controller settings as Connect to a remote HyWorks Controller over WAN/Internet 3. Following ports must be opened in the firewall 38866 (Used by devices to connect to Controller) and 38861 (Used for RDP Session) Note: In WAN environment, user may find some performance degradation in comparison to LAN configuration.
FOUR STEP PROCESS OF DEPLOYING EDC SUITE The following steps are required to start serving the desktop on devices using configured desktop provider. 1. Accops HyWorks Controller Service and Management Console installation 2. Setup configurations in HyWorks Controller License, Authentication Server and Desktop Providers 3. Configuring Desktop Pools and Assignments 4. Device configurations and User Logon Step-1: Install Accops HyWorks Controller Step-2: Configure HyWorks Controller Step-3: Configuring DVM Pools and Assignments Step-4: Device Configurations and User Logon INSTALL HYWORKS CONTROLLER SERVICE AND MANAGEMENT CONSOLE Installation of HyWorks Controller Service and Management Console is simple and easy, which requires the following few steps o o o User will be needed to download the HyWorks Controller installer setup from Propalms Downloads. Copy the setup on the server to be configured as HyWorks Controller During installation, user will be needed to provide following important information, which must be remembered: Database Selection: Type of database to be configured, currently supported databases are: Embedded Microsoft SQL Server HyWorks Controller Service Logon Credentials: Account information with which HyWorks Controller Service will run on the system Port Configurations: Accops HyWorks Controller Port: The port on which HyWorks Controller will be running (Default is 38866). The same port is used for configuring
o o o Management Console controller service path and as well as for registering the devices with the server HyWorks Controller Management Console Port: The port will be used to run the Management console. Management console is the Web interface for Device management, Session management, HyWorks Controller configurations, desktop provider configurations, connection policies management etc. Default port number is 443 To access Management console, navigate to URL https:// <IP / Host name >: <Port Number> Administrator User Credentials User can opt to configure a new user (Username and password to be provided during installation) User can also configure an AD group (whose members will be having access to HyWorks Controller) Run the setup, follow the installation wizard and HyWorks Controller installation is done After successful installation, on last screen, user is displayed the URL for accessing the Management console. Execute HyWorks Controller Utility (v2.5.4.1) provided with HyWorks Controller to configure HyWorks Controller with latest client updates. For detailed steps and help on installation of HyWorks Controller, please refer the Accops HyWorks Controller Installation Guide available on Propalms Support Documentation. If you are facing any issue while installing HyWorks Controller, please contact Propalms support team. CONFIGURE HYWORKS CONTROLLER After the successful installation Accops HyWorks Controller Service and Management Console; User will be needed to configure License, authentication server and Desktop Providers in HyWorks Controller setup. This section describes the process to configure each of the mentioned components in the HyWorks Controller Setup. LICENSE CONFIGURATION 1. Contact Propalms Support to get appropriate license for the deployment. 2. Once ready with the following details: a. Username b. Password c. License Key 3. Access HyWorks Controller Management Console using URL in following format: https://<ip or Host name of HyWorks Controller>:<Management Console Port Number> e.g. https://192.168.1.198:443 4. Login with appropriate credentials (Configured during installation) 5. Go to Setup tab -> Expand License Management Section 6. Make sure the HyWorks Controller is connected to internet and able to connect to keyhive.propalmsnetwork.com 7. Provide appropriate license details i.e. Username, Password and Serial Key details 8. Click on Activate License online button and wait for process to be completed 9. Appropriate status message will be provided on successful configuration and license server section will start to display the license information.
10. License Server status will get changed to Configured and the Dashboard will start displaying appropriate license status DESKTOP PROVIDER CONFIGURATION HyWorks Suite 2.5 supports following two categories of desktop providers: 1. DVM Providers: Virtual Machine providers which can directly provide the desktops to the users and for which authentication and desktop assignments are done by HyWorks Controller are kept in the category of DVM Providers. Following three types of DVM providers are supported in Accops HyWorks Suite 2.5: 1. VMware vcenter Servers or ESXi 2. Microsoft Hyper-V/ SCVMM 3. Microsoft RDS 2. External Desktop Brokers Desktop providers, with their own Management console to manage users and desktops, come under the category of External Desktop Brokers. Following two types of External Desktop Brokers are supported in Accops HyWorks Suit 2.5: 1. TSE for shared hosted desktops 2. Pano Controller for dedicated desktops Follow below steps to configure required desktop provider in HyWorks Controller: 1. Access HyWorks Controller Management Console using URL in following format: https://<ip or Host name of HyWorks Controller>:<Management Console Port Number> e.g. https://192.168.1.198:443 2. Login with appropriate credentials (Configured during installation) 3. Go to Setup tab -> Expand Desktop Provider Section 4. Click on Add + button to open Create New Desktop Provider window 5. In Create New Desktop Provider Window, select Desktop Provider Category e.g. DVM Provider or External Desktop Broker a. For DVM Provider category i. Select Type as VMware/ vcenter, Microsoft Hyper-V/ SCVMM, Microsoft RDS ii. Provide logical Name for desktop provider e.g. vcenter-server-35 iii. Provide appropriate Host address (Should be reachable from HyWorks Controller) iv. Provide appropriate credentials (Username and Password) Required for VMware/vCenter Desktop Provider only b. For External Desktop Broker category i. Select Type as TSE or Pano Controller ii. Provide logical Name for desktop provider e.g. TSE-35 iii. Provide appropriate Host address (Should be reachable from HyWorks Controller) iv. Provide Domain (Enabled for TSE only but optional, if not provided users will be needed to provide credentials with domain information while logging-in) 6. Once all the information is entered, click on Test Connection button 7. Once connection is successful click on Add button to add the desktop provider 8. HyWorks Controller will sync with the desktop provider and will provide appropriate information in that section Note: 1. The HyWorks Hyper-V Connector windows service should be installed and running in order to configure Hyper-V or SCVMM as desktop provider.
2. Only TSE v7 with Web Services is supported 3. Microsoft RDS: Support for Microsoft RDS is limited to User/ Device Assignment from HyWorks, user authorization has to be configured from RDS server 4. Domain information provided for TSE (External Desktop provider) cannot be verified by HyWorks Controller during configuration therefore it is expected to provide correct details in Domain section AUTHENTICATION SERVER CONFIGURATION Supported Authentication Servers: Following types of authentication servers can be configured with HyWorks Suite 2.5 Microsoft Active Directory Novell edirectory Workgroup To configure authentication server, follow the below steps: 1. Access HyWorks Controller Management Console using URL in following format: https://<ip or Host name of HyWorks Controller>:<Management Console Port Number> e.g. https://192.168.1.198:443 2. Login with appropriate credentials (Configured during installation) 3. Go to Setup tab -> Expand Authentication Server Section 4. Click on Add + button to open Create New Authentication Server window 5. In Authentication Server widow a. Select Appropriate Server Type e.g. Microsoft Active Directory, Novell Directory or Workgroup b. Provide appropriate Server address e.g. 192.168.1.1 or Accops.com c. Provide Base DN information (Mandatory for Novell Directory, optional for Microsoft AD and not required for Workgroup) d. Provide administrator credentials with rights to read and write access to user account managements 6. Click on Test Connection button 7. Once the successful connection message appears, click on Add button 8. Authentication Server is configured now Note: For External Desktop Brokers (TSE or Pano Controller), Authentication server configuration is not needed as the user authentication and authorization management is done by them CONFIGURING DVM POOLS AND ASSIGNMENTS Once Step# 2: HyWorks Controller Setup is done; setup will be ready to be used. The Devices will be able to register with HyWorks Controller and will be displayed in HyWorks Controller Management Console Devices section. Follow the below steps to get the desktops from desktop providers and assign them to desired users, groups or devices (HyDesks) 1. Access HyWorks Controller Management Console using URL in following format: https://<ip or Host name of HyWorks Controller>:<Management Console Port Number> e.g. https://192.168.1.198:443 2. Login with appropriate credentials (Configured during installation)
3. Go to DVM Pools tab and click on Add button to add new DVM Pool 4. Create a new DVM pool by providing a. Short logical name and description for the DVM Pool b. DVM Pool Type as Device Based (For assigning desktops to HyWorks Devices) or User Based (For assigning DVMs to Users from configured Authentication Server) c. DVM Provider (Configured as Desktop Provider, External Desktop Providers are not supported for pooling and assignments) d. DVM Provisioning as None (if existing VMs from DVM providers to be used) and select Dynamic (if new VMs to be provisioned on the DVM Provider) (Not enabled if selected DVM provider is Microsoft RDS). Selecting DVM Provisioning as Dynamic will enable the Deployment and Customization section. i. Deployment screen will require the source VM, DVM Name Prefix, Clone Type (Full/ Linked), Maximum Capacity, DVM Creation Schedule and Advanced Settings ii. Customization is not mandatory but can be used to modify Owner, Organization, Computer Name, Local User and Password, Moving VM to domain or Workgroup, Specifying Locale and Product key (All the changes will be done post cloning) e. Assignment Type as Permanent (Assignments will be saved and the same DVM will be provided to the client on next logon) or select Temporary (if you wish to create nonpersistent assignments which will get removed after the connection is disconnected i. Assignment Type will not be enabled if selected DVM provider is Microsoft RDS f. Select Appropriate Devices/ Users as per the pool type and assign them to VMs (If None provisioning type Pool is created) 5. Configuration of DVM pool is done and setup is ready to be used (E.g. Pool1 is created using existing VM DVM1 and assigned to Device Dev1) Note: All the DVMs (except RDS type DVM Provider) should have HyWorks Tools installed in order to configure remote desktop services and power policies. In case of Dynamic provisioning the source DVM must have the latest HyWorks Tools installed so that all new cloned DVMs will also have the HyWorksTools pre-installed. DEVICES CONFIGURATIONS AND USER LOGON To start using DVMs from configured desktop providers. The devices must be configured appropriately using following steps: 1. Connect devices appropriately, the HyDesk Client will get launched automatically 2. Confirm if network icon is green (indicating it is connected to network)
3. Click on Settings button 4. Go to Controller settings 5. Choose appropriate option as per your deployment a. Choose option -1 Detect HyWorks Controller automatically In LAN environment with Controller broadcasting is enabled b. Choose option-2, Connect to a local HyWorks Controller In LAN environment and you want to specify HyWorks Controller manually c. Choose option-3, Connect to a remote HyWorks Controller over WAN/ Internet In WAN environment
6. Provide appropriate HyWorks Controller IP and Port number (Configured during installation) 7. Click on button Apply and Test Connection and wait for settings to take effect 8. Once HyWorks Controller is configured correctly, user will be prompted with successful dialog stating HyWorks Controller settings applied successfully. Please continue to login LOGIN FROM DEVICE USING APPROPRIATE USER CREDENTIALS 1. Connect device appropriately, the HyDesk Client will get launched automatically 2. Confirm if network icon and Server icons are green (indicating it is connected to network and HyWorks Controller) 3. Provide appropriate username and password in the following format: a. Username, Domain name\username or Username@domain name b. Password User password 4. Click on Login button 5. User will be provided the assigned desktop and other applications will be hidden ASSUMPTIONS Following assumptions are made while creating this document: 1. Desktop Providers which can be VMware ESXi, VMware vcenter Server, Microsoft Hyper-V or SCVMM, Microsoft RDS, Pano Controller or TSE are already installed and ready. 2. HyWorksTools (HyWorks DVM agent) is already installed on the target DVMs or the remote desktop settings are pre-configured on the target DVMs (In order to get a successful uninterrupted remote session) 3. Devices are able to connect to HyWorks Controller and target DVM 4. Refer document Readying VM for Deployment in skyspace for detailed instructions on readying the virtual machines for deployment in HyWorks Suite
REFERENCES HyWorks Documents: Readying VMs for Deployment in HyWorks HyWorks Documents: Accops HyWorks Admin Guide