Remote Application Server Version 14. Last updated:

Size: px
Start display at page:

Download "Remote Application Server Version 14. Last updated:"

Transcription

1 Remote Application Server Version 14 Last updated:

2 Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of 2X SOFTWARE Ltd. 2X RDP Client is a copyright of 2X SOFTWARE Ltd X SOFTWARE Ltd. All rights reserved. Version 14 Last updated February, 25, 2015

3 Manual Index Section 1 Introduction to 2X Remote Application Server 1. 2X Remote Application Server Description. Section 2 Installing 2X Remote Application Server 2. Planning and Implementing RAS 3. System Requirements 4. Installing and Configuring 2X Remote Application Server Section 3 Getting Started with 2X Remote Application Server 5. Configuring 2X Remote Application Server 6. The Farm and Components 7. 2X Secure Client Gateways 8. Configuring Multiple Gateways and Forwarding Gateways 9. IPV6 Configurations and Settings 10. Terminal Server Configuration and Settings 11. VDI Hosts and Configuration 12. Virtualization 13. Virtual Desktop Infrastructure 14. Remote PC Agents Section 4 Configuring 2X Backup Servers 15. Configuring and Adding Backup Servers 16. Modifying Backup Servers 17. Promoting a Backup Server to a Master Server Section 5 2X High Availability Load Balancer HALB 18. HALB High Availability Load Balancer 19. HALB Appliance Installation and Configuration 20. Adding an HALB Appliance from 2X RAS Section 6 Farm Settings 21. Auditing 22. Global Logging 23. URL Redirection Section 7 Terminal Server Load Balancing 24. Configuring Load Balancing and Tunneling Policies 25. Methods 26. Advance Settings Section 8 Publishing and Filtering 27. Application Publishing 28. Folders and Application Grouping 29. Desktop Publishing 30. Predefined Application Publishing 31. Document Publishing Section 9 2X Universal Printing

4 32. 2X Universal Printing 33. HTML5 Gateway and Chrome App Printing 34. Font Management Section 10 2X Universal Scanning 35. Universal Scanning Options 36. Configuring a Scanning Rename Pattern 37. Adding Scanning Applications Section 11 Connection and Authentication Settings 38. Authentication 39. Second Level Authentication 40. Configuring Deepnet, Safenet and Radius 41. Attributes 42. Allowed Devices Section 12 2X Client Connection Policies 43. Configuring Client Policies 44. Browser Mode, Criteria Connection Properties & Options Section 13 Client Manager 45. Devices 46. Windows Device Groups 47. Managing Windows Device Groups 48. Shadow a Windows Device 49. Desktop Replacement 50. Options 51. Scheduler Section 14 Administration 52. Multiple Sites 53. Adding a New Site to the Farm 54. Accessing Site Configuration 55. Configuring Administrators 56. Mailbox Setup 57. Sending Invitations and Settings to Users 58. Notifications 59. 2X Reporting 60. Backup, Software Updates & Settings Audit Section 15 Information 61. Local Information 62. Site Information 63. Support Section 16 Reporting 64. Software Requirements 65. Install & Setup MS SQL 66. 2X RAS Reporting Setup 67. 2X RAS Management Console Configuration 68. Viewing Reports 69. Available Reports Section 17 Licensing 70. Licensing & Activation

5 Section 18 3 rd Party SSL Certificates 71. Using Apache Certificates 72. Converting IIS Certificates Section 19 2X RAS Portal 73. 2X RAS Portal Prerequisites 74. Network Planning 75. Configuring IIS & Installing and Configuring 2X RAS Portal 76. Configuring 2X RAS Portal 77. Using the 2X RAS Portal Section 20 2X HTML5 Gateway 78. HTML5 Browser Settings 79. Adding a Standard RDP Connection 80. Adding a 2X Remote Application Server Connection Section 21 2X Clients 81. 2X Clients 82. Installing and Configuring 2X Windows Client and RDP Connections 83. Installing 2X Linux Client Section 22 References

6 Terminology Category A category consists of a number of settings related to a specific task or operation. In the 2X Remote Application Server Console the following categories are available: Farm Load Balancing Publishing Universal Printing Universal Scanning Connection Client Manager Policies Administration Information Reporting Licensing Farm A farm consists of a 2X Remote Application Server installation on a site or multiple sites. Licensing Server Site The site where the main configuration database is stored and manages all other sites in the 2X Farm. Other servers in a site can be upgraded to Licensing Server if the main licensing server is not available. Note: Upgrades of the 2X Remote Application Server MUST be applied to the licensing server site first. Publishing The act of making items installed on a Remote Desktop Server, VDI Host or Remote PC available to the users via the 2X Remote Application Server. Publishing Agent The Publishing Agent provides load balancing of published applications and desktops. RDS Remote Desktop Services is a server role in Windows Server that provides technologies to enable users to connect to virtual desktops and session based desktops. RDS replaced Terminal Services beginning in Windows 2008 R2. Site A site consists of a publishing agent, a SecureClient GW or multiple gateways and the agents installed on the Terminal Servers, VDIs and PCs.

7 2X Remote Application Server Description 2X Remote Application Server enables people to work from anywhere with virtually any device. It s a powerful tool that allows businesses to leverage their existing applications on multiple devices with clients for PC, MAC, Linux, ios, Android, HTML 5, and Chrome. Some of the key benefits of 2X Remote Application Server are: Centralized resources that can be more effectively managed from both a cost and security perspective. o o The cost of software updates can be reduced with volume licensed copies that can be shared instead of a full individual copy for every user. Users terminal server access can be strictly controlled with security groups and group policies i.e. software cannot be installed or downloaded on terminal servers. SSL connections and second level authentication can used to create a secure environment. Applications can be delivered to users on multiple OS platforms for both desktop and mobile devices. o o o The 2X client is available for Windows XP, 7, 8, OS X, Linux, desktop operating systems. The 2X client is available iphone, ipad, and phones, Android tablets and phones. The 2X HTML 5 Client provides access from any device with an HTML 5 browser. HALB Appliance (High Availability Load Balancer) o o The 2X HALB is a software solution that sits between the user clients and two (or more) back end 2X RAS gateways. Any number of HALB services can be running concurrently, and, at any one time, one is set as the master and the others set as slaves. Not only does the 2X HALB distribute the requests to the two back end servers, it also checks the health of the back end servers. If one of them is down, all requests will automatically be redirected to the remaining back end server. In addition to that, the load balancer nodes monitor each other using keepalived, and if the master fails, a slave becomes the master, which means the users will not notice any disruption of the service. 2X Desktop Replacement o o o 2X Desktop Replacement allows you to extend the lifespan of your hardware and delay migration to the latest OSs to a time that suits you best. The 2X solution allows you to be very flexible: you can lock machine configuration on the user side, placing your corporate data in an extremely secure position, or you might decide to allow users to run some local and remote applications. 2X Client Desktop Replacement is able to reduce the operability of the local machine by disabling the most common local configuration options, while guaranteeing the same level of service and security afforded by thin clients directly from your existing PCs. 2X RAS Reporting Service o o 2X Remote Application Server has a built in reporting engine which the administrator can use to understand how the system is functioning. The information provided can help in adjusting the system to perform better and to be used in a more efficient way. You can detect bottlenecks that can lead to future problems thus avoiding them. You can also analyze how your users are using the system and extract important statistics. The system provides 13 reports which are grouped into 5 categories. You can view the available reports in a flat view by clicking the flat view button in the reports header as shown below. Business Continuity and Disaster Recovery o o Application downtime is reduced with redundant systems and quick client build times. The 2X Remote Application Server has backup capabilities built in.

8 Planning and Implementing RAS There are 3 major mechanisms required to deliver published items. 1. Servers connect users to applications, desktops, folders or documents. There can be a single or multiple servers configured to deliver published items using the following agents using the RDS. Gateway * Publishing Agent* Terminal Servers Agent (Used to publish applications using RDS) VDI Host Agent (Used to publish virtual desktops) *Required 2. Clients may be a PC s, tablet or phone which the 2X Client is installed on and can connect to the published items. A list of available clients is as follows: Windows XP, 7, 8, 8.1 in 32bit and 64bit Mac OS X Linux ipad iphone Android HTML 5 Windows Mobile 8 3. Network Which consists of a LAN or WAN connections. LAN connections are on port 80 by default WAN connections can be made on port 80 but SSL is recommended. Any port available from outside the network that is forwarded to the gateway The basic functionality of an environment consisting of clients and server over a network is shown the picture below. Clients request Applications, RDS Desktops, VDI Desktops, Folders, Documents or Remote PC access and the 2X Remote Application Server delivers them to the client utilizing RDS. Basic Functionality

9 System Requirements Depending on the capacity requirements the gateway, publishing agent and terminal server can be installed on the same hardware or separated across multiple servers on either physical or virtual servers. When planning the capacity that the servers will need delivering items there are multiple factors to consider but the first steps are to determine: 1. The number of users 2. The number of items that are to be delivered (i.e. how many items will be published to users?) 3. What types of applications and the load they will place on servers Two methods that may be used help determine capacities are Piloting or Simulation. 1. Piloting is a common approach by which a server is deployed to production for a test group of users. Users give feedback as to the experience using the published items and administrators can make adjustments if needed accordingly. Monitoring the hardware utilization of CPU, RAM and Network Adapters can help determine capacity is also helpful. This method works well in smaller environments but does not provided the accuracy needed in larger environments to determining resource utilization for specific events. Since users are randomly accessing resources this can lead to an unforeseen issue with utilization due to non specific use during testing. 2. Simulation evaluates capacity based on systems testing that monitor s hardware utilization under specific conditions during client testing of published items. This method is more precise for determining capacity and effective for larger environments that need to purchase and provision multiple servers. Capacity Planning Reference: us/download/details.aspx?id=17190 Minimum Hardware Requirements Physical Machines Dual Core Processor with a minimum of 4GB of physical memory Virtual Machines 2 Virtual Processors with a minimum of 4GB of virtual hardware memory Windows Server Role Requirements Application Publishing Required Roles The following Microsoft Windows Server roles and features are required for published Applications, Folders, Documents and RDS Desktops. Terminal Server (Windows Server 2003 and 2008) Remote Desktop Services (Windows 2008 R2 and 2012 Editions) NOTE : Installing 2X Remote Application Server on a Domain Controller is not supported. Terminal Services and Remote Desktop Services is not supported on a domain controller by Microsoft. 2X Remote Application Server should not be installed on a server running DHCP services. Licensing A valid copy of Windows Server is needed to install 2X Remote Application Server, Gateways and RDS on. RDS/TS CAL s are needed for application and document publishing. A CAL is used when an application or document is opened as opposed to a 2X Connection which applies to 2X Licensing. Configuration Setting 1. Enable Remote Desktop Connections 2. Disable Windows Firewall or open the appropriate ports 3. Disable Antivirus (Rules can be set on each 2X Software executable) 4. Disable UAC on both Servers and Client computers Clients Whether existing clients or new clients will be used there are many considerations that need to be taken into account before implementation. While 2X has clients for most devices please check to ensure a client exists for the device.

10 2X RDP Client is approved for the following operating systems: Windows XP SP3 Windows Vista Windows 2003 SP1 Windows 7 Windows Windows CE Windows Embedded Mac 10.5.x and above ios (iphone and ipad running IOS 7.0 and Higher) Android 1.5 and above Ubuntu 8.04, 8.10, 9.04, 9.10 OpenSuse 11.1 Fedora Core 9, 11 CentOs 5.2 VectorLinux 6.0 Chrome OS Ensure that the correct version is used with the OS that s installed on the device. There are 32 and 64 bit version of the 2X client for PC s and different versions for OS X. Link For ios clients the 2X client must be downloaded from the App Store. The 2X Android clients can be downloaded from the Google Play. Network To ensure optimum performance please use industry best practices for network design that utilizes network segmentation reducing the maximum number of devices to fewer than 300 on any one VLAN. If other systems utilize the same network such as VOIP no more than 150 devices per VLAN should be implemented. 2X Remote Application Server are configured to connect clients on port 80 by default due to port 80 being configured to accept all http requests. If port 80 is already in use the client connection can operate on any available port. For higher levels of security SSL can be used over port 443 by default with self signed or 3 rd certificates. User experience can be optimized based network speeds in the client settings as well as proxy configuration.

11 Installing and Configuring 2X Remote Application Server Before installing 2X Remote Application Server on please consult the Microsoft Remote Desktop Services Overview for proper configuration of RDS/Terminal Services. (For all versions) us/library/hh aspx For servers with 2X Remote Application Server installed without RDS installed use the following reference: Refer to the 2X Remote Application Server manual for specific procedures on installing. Choose Custom to select specific agents for installation or to remove specific agents for installation. Custom Installation continued...

12

13 Configuring 2X Remote Application Server Configuring a 2X Remote Application Server Administrator Account The first time you launch the 2X Remote Application Server Console you have to specify a username and password in FQDN format example administrator@domain.local, as seen in the below screenshot. The user specified will be automatically configured as the 2X Remote Application Server administrator. Use any user from the active directory or the local machine to login where the 2X Remote Application Server is installed. NOTE: An example of a custom installation would be for configuring a server as a Gateway. To remove an agent from installation list select Entire feature will be unavailable from the drop down. After a default installation of 2X Remote Application Server the following services will be running on the server. 2X Publishing Agent provides load balanced applications and desktop publishing. 2X Redundancy Service provides redundancy to 2X Remote Application Server 2X SecureClientGateway tunnels all traffic needed by 2X applications on a single port and provides secure connections. 2X TerminalServer Agent provides terminal server information to 2X Publishing Agent Troubleshooting Tip: Check the service state when an agent status is Not Verified

14 The Farm and Components There are several components that make publishing items possible which include: Application Server The Farm Publishing Agent Secure Client Gateway Agent Terminal Server Agent VDI Host Agent Guest Agent PC Agent Remote Application Server The 2X Remote Application Server is the collective components, systems and graphical interface of a Farm set up. The Farm Design view shows all systems managed by the Publishing Agent. The categories in the left pane of the console provide access the individual systems of 2X Remote Application Server. Selecting an icon provides access to properties, options, configuration settings, enable and disable depending on the system. The Farm The Farm contains sites or a site that is configured to deliver published items, manage thin clients and access the properties of those components. From the Farm portion of the console administrators can: Change the name of the Farm Add a Site Change the Properties of a Site Delete a Site Check the Agent Switch Sites Change Licensing Server Site

15 Publishing Agent The Publishing Agent (PA) controls all the communications between components and systems. There can be only one PA active in a Farm. The PA controls the decision algorithm for Load Balancing, Authentication, 2nd Level Authentication, Filtering and other processes. Other PA s are configured as a backup and will take over when the Master PA fails. Secure Client Gateway The gateway provides clients a connection point to the 2X Remote Application Server and as an entry point for the connection broker for Wyse terminals. The connections can come from multiple sources such as a Windows, Linux, Macintosh, RAS Portal or Smart phone client. When a connection request is received by the Secure Client Gateway, it will communicate to all Publishing Agents to see if the requesting user has permission to access the requested resources. The gateway also delivers and installs 2X Desktop replacement and Windows PC Client Management. It can also tunnel HTTP traffic to an intranet. This is processed in the following order: 1. Gateway receives a connection request 2. Gateway forwards the request to the Publishing Agent 3. Publishing Agent performs Load Balancing checks and Active Directory security lookup to obtain security permissions. 4. If user is requesting a published resource and has been granted access, the publishing agent returns the response to the gateway service and which terminal server the end user can access. 5. Depending from the connection mode the client either disconnects from the gateway and connects directly to the RDS Server (Direct Mode) or asks the gateway to open a tunnel to the Terminal Server (Gateway Mode). Terminal Server Agent The Terminal Server Agent is installed on RDS servers to provide a connection to the Farm and allows the PA to publish applications and manage them. From the Properties tab Agent Settings, RDP Printer format and Scheduler can be configured for the Terminal Server Agent. VDI Host Agent The VDI Host Agent is installed on the hypervisor host or appliance (i.e. vcenter) to connect the host to the Farm. From the Properties tab the Host can be removed from the Farm. Agent Settings, RDP Printer format and Scheduler are located in the properties of the VDI Host Agent. Guest Agent The guest agent allows the PA to publish and manage guest virtual machines (VM s). In the advanced settings you can manage/control the Guests, change settings, or update agents. PC Agent The PC agent is used to connect physical (vs. virtual) PC s to the Farm and give user s access to those PC s. From the Properties tab the Remote PC can be removed from the Farm. The Agent Settings and RDP printer format are also found in the Remote PC Properties. Configuring RAS

16 After installing 2X Remote Application Server depending on the environment there are specific components that need to be configured. For Publishing a Gateway and Publishing Agent are required as well as a Terminal Service Agent, VDI Host Agent or Remote PC Agent depending on what is being published. The most common use of 2X Remote Application Server is to publish applications from a RDS server to a client. That scenario requires a Gateway, PA and TS to deliver applications to clients. The following sections will review configuring each of these agents needed to publish.

17 2X Secure Client Gateways The first gateway will be installed in a Farm using the default installation. If a custom install was used and the gateway agent was not installed on the same server as the Publishing Agent it can be pushed to the server using the Install button located in the Gateways section of the Farm. Make sure the 2X Secure Client Gateway has access to port otherwise it will not be able to retrieve the published applications list and load balance the application requests. To configure the gateway choose Gateway from the Farm and then select properties. Select Properties from the Task drop down dialog box to configure Network, SSL/TLS, HTML 5, and Wyse, Advanced or Security settings. A gateway can be disabled from the properties tab and a description can be added. IP Address tab contains IP Versions that are supported with the 2X Gateway. Version 14 of 2X RAS introduces IPv6 to the system. The product will still need IPv4 in order to work as IPv6 is introduced at the Secure Proxy Gateway and Connectivity Level. This means that IPv6 is for end user usage In order for tunneling policies to work properly, you must make sure that the IP Bindings to your physical gateway is set to all available addresses.

18 Network tab contains the port settings that 2X Clients connect to the Gateway on. The default port for the Secure Client Gateway is port 80. The RDP Port setting is used for Load Balanced RDP connections. This can be changed to another available port number but it must be changed in the 2X Client settings as well. Changing this port will cause users to append the port number to their connection string in RDC if this port number is changed. SSL/TLS tab is used to configure settings for secure client connections and to enable the HTML 5 Gateway. The default port for SSL connections is 443 but can be changed to another available port and will need to be changed in the 2X Client as well. Navigate to the SSL/TLS tab in the gateway properties. Tick the option Enable SSL on Port and configure a port number (default is 443). (Optional) Select the SSL version accepted by the 2X Secure Client Gateway from the Accepted SSL Versions dropdown listed below (Default is TLS v1 TLS v1.2): TLS v1.2 Only (Strong) TLS v1.1 TLS v1.2 TLS v1 TLS v1.2 SSL v3 TLS v1.2 SSL v2 TLS v1.2 (Weak) (Optional) Tick the option Allow only strong ciphers to only allow the usage of certificates using strong encryption algorithms. SSL / TLS continued

19 A self signed or a 3 rd party certificate must be installed to use SSL. Select Generate new certificate to create a self signed certificate. After the encryption Key size and information fields are completed select Save and the certificate will be enabled. To use a certificate from a trusted authority to enable SSL on a 2X Secure Client Gateway, navigate to the SSL/TLS tab in the gateway properties. Click on Generate certificate request, fill in all the required details and click Save.

20 Configuring SSL Certificate Details Once ready a window will pop up with the certificate request, as show in the below screenshot. Click Copy to copy the request which you should send to the certificate authority. Generated Certificate Request Once you receive the SSL certificate from the certificate authority click on Import public key, browse for the certificate file containing the public key and click Open. Click OK to save the settings. Enabling HTML 5 Support HTML 5 gateway allows connections to published items from HTML 5 browsers. SSL must be enabled to utilize the HTML 5 gateway. 2X Remote Application Server will listen for HTML 5 gateway connections on Port To connect to the HTML 5 gateway use the following URL:

21 There are 3 modes the HTML 5 gateway can operate in which are: Allow Connection to this Gateway Only Select this option so users can only access a connection to this gateway from the HTML 5 interface. Tick the option Create Default Connection so the connection to the gateway is already available in the HTML 5 interface. Allow Modification of 2X Connections Select this option to allow users to create new connections to other gateways or modify existing ones from the HTML 5 interface. Allow Modification of 2X and RDP Connections Select this option to allow users to create new connections to other gateways or modify existing ones, and also allow them to create new RDP connections from the HTML 5 interface. Wyse Wyse tab allows Wyse ThinOS support from 2X Remote Application Server by checking the Enable Wyse ThinOS Support box. The 2X Secure Client Gateway will then act as a Wyse broker. Advanced Advanced tab contains the settings for the HTTP Server port that is used with the 2X Gateway. The Publishing Agent host name and port number are also located in the Advanced properties. Port is used to connect the Publishing

22 Agent and Gateway. A 2X Secure Client Gateway can also be set to forward to another 2X Secure Client Gateway by selecting Forward requests to next 2X Secure Client Gateway in chain which is typically used when placing a Gateway in a DMZ. Security Security tab contains settings to exclude specific 2XClients from connecting to the gateway. There is also option to Allow only specific 2X Clients to connect to the gateway. To use this feature the 2X Client must be installed on the device. Select Add for either Allow all except or Allow only to choose which clients to add to the list.

23 Tunneling Policies Tunneling Policies are better known as a Load Balancing Rule. With tunneling policies you are able to create an interface that allows you to load balance specific servers or server groups to another dedicated IP address. By default 2X Remote Application Server will load balance all servers that are joined to the server farm. First the Gateway IP is selected then the servers or server group is selected which will create a new Tunneling Policy once the Ok button is clicked. NOTE: In order for tunneling policies to work properly, you must make sure that the IP Bindings to your physical gateway is set to all available addresses. This setting is located under the Gateway Properties Screen under the IP Address tab.

24 Configuring Multiple Gateways and Forwarding Gateways Multiple Gateways If more than concurrent users connect to a 2X Secure Client Gateway in gateway mode latency may be experienced due to excessive connections. A network load balancer, HALB and second gateway can be used to improve performance. Multiple 2X Gateways ensure client connections are maintained at optimal performance and also provide redundancy to help ensure system uptime in the event of a failure. In the image below both 2X Gateways are configured to forward requests to the same 2X Publishing Agent. Forwarding Gateways 2X Secure Client Gateway can forward requests to the next 2X Secure Client Gateway in the chain (Cascading Firewall) by selecting this option in the Advanced Tab of the Gateway properties. In the image bellow with this option enabled the 2X Secure Client Gateway (GATEWAY 1) will forward connection requests (on port: 80 by default) to the next 2X Secure Client Gateway (GATEWAY 2) configured in the Forwarding 2X Secure Client Gateway(s) list. Forwarding gateways are useful in separating WAN connections from LAN connections and make it possible to disconnect WAN segments in the event of issue without having to disrupt LAN connections.

25

26 IPV6 Configurations and Settings Introduction 2X RAS version 14 introduces IPv6 at the Secure Proxy Gateway and Connectivity Level, this means that IPv6 is for end user usage and requires IPv4 to work. IPv4 and IPv6 use the following Ports (by default) 2X Secure Client GW Port (TCP 80) SSL (TCP 443) Direct RDP Connection (TCP 3389) RDP UDP Data Tunneling (UDP 80) Only if 2X Secure Client GW is opened RDP UDP Data Tunneling (UDP 443) Only if SSL is opened Client Manager Port (UDP 20009) The following port is used only for IPv4: Broadcast Service (UDP 20000) Setting up IPv6 for the 2X Secure Proxy Gateway 1. Open the Proxy gateway settings from Gateways> Properties> IP Address 2. Select Version 6 from Use IP Version dropdown list One must note that the binding rules for IPv4 and IPv6 are different, so one can be listening on all IPs available for version 4 and one particular IP for version 6. Once the settings have been applied and state check cycle completed, you can verify that the actual IPs and ports are listening from the Site information page. Client Settings The 2X RAS Clients do not need any specific settings to use IPv6. The client will resolve both IPv4 and IPv6 and connect to any of the available IP addresses. The following Clients support IPv6: 1. 2X RAS client for Windows (Starting from ) 2. 2X RAS client for ios (Starting from ) 3. 2X RAS client for MAC (Starting from ) 4. 2X RAS Portal (Starting from ) 5. 2X RAS client for Android (Starting from ) 6. 2X Chrome client (Starting from ) 7. 2X RAS client for Windows Phone (Starting from ) 8. 2X RAS client for Linux (Starting from ) The 2X HTML5 Gateway does not support IPv6. Features within 2X RAS which are affected by IPv6 Forward requests to Publishing Agents (PA) and Http Server To set up the forwarding requests to PA and Http Server: 1. Open Farm > Gateways >Advanced > Forward Request to 2X Publishing Agent and Http Server

27 2. Select the HTTP Server IP address from the Server list by selecting IPv6 servers. Please note that the HTTP server needs to support the same IP version as that of the Browser doing the request (i.e. the first G/W in the chain). Forward requests to another Gateway To set up the forwarding requests to PA and Http Server: 1. Open Farm > Gateways >Advanced > Gateway Forwarding to another Gateway Mode 2. Set the Gateway to work in Forwarding mode by forwarding the data to another Gateway which is listening on IPv6. 3. Please note that GW can forward data to another GW which has a different version of IP. No effect should be observed apart from the HTTP protocols. This is obviously not advisable. Gateway Security To set up the Gateway Security: 1. Open Farm Gateways Security 2. Set MAC Filtering to work with connections which are IPv6 by adding the MAC Address list.

28 Filtering Publishing Items To set up filtering for publish items: 1. Open Publishing Items Filtering 2. Setup filtering rules for publishing which support IPv6 entries. An entry can contain one IP or a range of IPs to match. Setting up an IP Exclusion List: To set up and IP Exclusion List: 1. Open Connection Second Level Authentication 2. Enable 2nd Level authentication is enable and set an IP Exclusion List. IP Exclusion List can have both IPv4 and IPv6 entries.

29 Client Manager Devices List Users can view the list of devices connecting by using an IPv6 as follows: 1. Open Client Manager Devices 2. The search feature accepts IPv4 and IPv6 ranges. If no range is specified (i.e. no ), the search will do a partial text match (e.g. if I type 36 any IPv4 or IPv6 have 36 such as 201::36:1 or will be displayed) Sending Invitations to IPv6 connections Users can send invitations and set the IP or host with which the client connects: 1. Open Administration Send Invitations 2. Define the public IP or host with which the client will connect. This supports IPv6 format (e.g. [fe80::ddcf:14eb:4549:a56d%13]:80/443) Site Information Users can view site information from: 1. Open Information Site Information 2. The site information will have all IPv6 in use listed. These can be any of the following: Available IPs on a Gateway Ports running on IPv6 RDP Sessions using IPv6

30 Terminal Server Configuration and Settings A Terminal Server Agent must be installed for publishing applications or remote desktops from a RDS server. The agent may be removed from the Farm from the Properties tab which is useful during maintenance. The 2X Terminal Server Agent Port (default TCP 20003) is used to communicate with the 2X Terminal Server Agents which should be installed on the terminal servers. The 2X Terminal Server Agent provides information to the 2X Remote Application Server over this port. Troubleshooting Tip: The netstat a command can be used to test if the Publishing Agent has established connections to ports (Gateway) and (RDS). Properties tab allows for several settings to be configured. Max Sessions can be changed to limit the number of sessions to an RDS server. This might be used to ensure the server is not over utilized. The Description field can be used add additional information about the TS such as what applications are installed on it. Agent Settings tab allows the port for RDP services to be changed. This change is made when a Terminal server is also used with 2X Load Balancer because the 2X Gateway utilizes this port as well. The registry will also need to be changed to match the change to the Terminal server port number. Only the Terminal server with Load Balancer installed will need the RDP port changed. This change is only made when using the 2X Load Balancer as a standalone product it does not need to change with 2X Remote Application Server Load Balancing

31 The Publishing Session Timeout field is used to set the amount of time that each session will stay connected in the background after the user has closed all published applications. This is done to avoid unnecessary reconnections with the server. Checking the Allow Client URL/Mail Redirection box allows http and mailto links to be opened using local applications instead of using terminal server resources. To prevent a URL from being redirected to the client, click on settings under the site icon. Then click on the URL Redirection and add URL s you don t want redirected. Selecting the Allow 2XRemoteExec to send command to the client would allow the server session to send commands to the client. This is done by using the command line application called 2XRemoteExecpackaged with the 2X Remote Application Server. Logging allows the server to log actions that occur on the server and also identifies any issues related to the server. Click on Request Log to download a copy of the log file. You can clear the server s log file by clicking Clear Log File. RDP Printer tab settings are used to change the name format of RDP printers in Windows server before 2008 and MS Easy print. Scheduler is used to provide administrators with a tool for creating maintenance windows. Select Add to enter time, date, duration and repeat information.

32 On disable is used to change the session state of the client connections. This is useful when changes have been made to the RDS servers and sessions need to be updated.

33 VDI Hosts and Configuration A VDI Host (host machine) is defined as the computer on which a hypervisor is running one or more virtual machines. Each virtual machine is called a guest machine. The hypervisor presents the guest operating systems with a virtual operating platform and manages the execution of the guest operating systems. Multiple instances of a variety of operating systems may share the virtualized hardware resources. 2X Remote Application Server supports HyperV, Citrix XEN, VMware VCenter, VMware ESXi. By adding the VDI Host to the 2X Application Server you can manage the virtual machines on the VDI Host, create guest clones and publish virtual desktops and applications from virtual guests. Host Agent is installed on the hypervisor host to publish VDI desktops from 2X Remote Application Server. From the VDI Host section of the Farm select Add and choose the Hypervisor type being used to host clients. Enter the hostname or IP of the VDI Host and select Next. From the Properties tab choose the VDI version type and enter the credentials to allow access to the host. Agent Settings tab allows the direct address to be changed. A description can be added and the number of connections can be changed. The Publishing Session Timeout field is used to set the amount of time that each session will stay connected in the background after the user has closed all published applications. This is done to avoid unnecessary reconnections with the server. The maximum number of connections is 1000.

34 Checking the Allow Client URL/Mail Redirection box allows http and mailto links to be opened using local applications instead of using terminal server resources. RDP Printer settings are used to change the name format of RDP printers in Windows server before 2008 and MS Easy print. Scheduler is used to provide administrators with a tool for creating maintenance windows. Select Add to enter time, date, duration and repeat information.

35 Virtualization Define Virtualization Virtualization is the process of multiple systems sharing resources to achieve increased utilization of the resources and therefore and increased return on investment. The increased utilization also resolves other issues such space, power and climate control of data centers. In hardware virtualization the host machine is the actual machine on which the virtualization takes place, and the guest machine is the virtual machine. A host machine is defined as the computer on which a hypervisor is running one or more virtual machines. Each virtual machine is called a guest machine. The hypervisor presents the guest operating systems with a virtual operating platform and manages the execution of the guest operating systems. Multiple instances of a variety of operating systems may share the virtualized hardware resources. Virtualization Layers Starting with a bare metal server a hypervisor is installed and then virtual machines are created and managed with the hypervisor. Then 2X Remote Application Server can be installed on the virtual machines using Windows Server 2003, 2008, 2008 R2 or 2012 and 2012 R2. Applications and desktops can then be published and delivered to devices. Desktop OS s can also be installed on the hypervisor to publish VDI desktops. Hypervisors Determining the hypervisor plays a key role in the configuration of the system to publish applications or desktops as it determines what features and functionality the system will have. There are 3 predominate hypervisors on the market today are: VMware ESXi up to 5.5 Hyper V 2008 R2 Hyper V 2012 Hyper V 2012 R2 Citrix Xen Server up to 6.2 When choosing a hypervisor, consider the following: Number of VM s the can be installed on a single instance of hypervisor Functionality (How easy is it to manage VM s) Tools ( Clustering, Failover, Backups) These hypervisor are built on different OS platforms and differ greatly in functionality. 2X Remote Application Server can function with these platforms as well as others that can be found at: Application Server/approved vdi/

36 Planning and Implementing Hosts The planning and implementing a virtual environment has many important considerations and best practices to resolve. These considerations are: Virtual Storage Virtual Networking Memory Allocation CPU Management Virtual Storage Virtual storage differs from physical machines in that most likely a separate storage device will be used for VM drives and not local storage on the actual server. It is critical to the success of a virtual environment to choose the right storage device because of disk I/O, array configuration and provisioning. If these three characteristics of storage devices are not properly chosen VM performance will suffer. Concerning disk I/O consider the following characteristics of storage arrays: NAS Low Disk I/O iscsi Moderate Disk I/O Fiber Channel High Disk I/O In addition to disk I/O another consideration to virtual storage is array configuration. There are three predominate types of storage devices which are: NAS, iscsi and Fiber Channel. Each has different characteristics for the provisioning of disk arrays. For optimum performance ensure that the device can create separate RAID arrays and therefore separate LUN s not logical LUN s. Logical LUN s are stripped across all the drives in and array because the drive is a single large array. The LUN s are created with the management software and doesn t physically isolate storage to specific drives as RAID does. If multiple VM s with high disk I/O are on the same array there may be significant performance issues. Provisioning of VM drives can be static or dynamic and depending and the naming convention is unique to the hypervisor. For example VMware calls static provisioning Thick and dynamic Thin. Static provisioning is the same as with creating a physical machine drive in that when the administrator provisions the drive for a VM that space is set aside for that VM only. Dynamic on the other hand allows the administrator to set the maximum drive size but only the necessary drive space that is needed at the time of crating the VM is used on the disk and as it grows. This allows for oversubscribing the hard drive space. This makes dynamic drive provisioning a poor choice in a production environment. The biggest issue with dynamic provisioning is that the VM s OS will not know if it has run out of space for writing to the disk. This can cause a crash that can t be recovered. A backup can be used to restore the VM but this can be avoided using static provisioning. Virtual Networking Virtual networking follows some of the same practices as physical machines but implemented in a virtual environment. To ensure strong VM performance separate the storage network from the other networks with a separate NIC that is configured on a separate VLAN and virtual switch. Additional NIC s may also be needed if there are VM s that have high bandwidth utilization i.e. and SQL servers. Another consideration is segmenting the network environment. The industry standard for network segmentation is no more than 300 devices on a single VLAN. This is due to broadcast domains and the amount of chatter that is generated by devices. If the network has mixed protocols such as VOIP as well as IP the number of devices should be reduce to or they should be isolated to different VLAN if possible. Memory Allocation To ensure suitable VM performance memory must be allocated and managed properly. Some key considerations are: Do not over subscribe memory in production environments Monitor memory utilization on VM after creation Maintain OS versions and patches as similar as possible Use monitoring tools to create alerts for memory issues Over subscribing memory is possible in a virtual environment it is not recommended as it will invoke the use swap files. Most of the time memory allocation is an educated guess on the administrator s part and should be monitored after VM is created to determine if the appropriate amount was allocated. Adjustments should be made if the memory is underutilized or over utilized. Hypervisors can optimize memory by examining memory files and allowing multiple VM s to utilize the same memory page if they are the same. Maintaining servers with same builds and patch versions assist in allowing memory page sharing. Motoring tools should be setup to alert administrators when memory issues arise to avoid swap file use and prevent degradation in VM performance.

37 CPU Management CPU management is another vital part of virtualization and should be considered in planning and implementing a virtual environment. Each of the three hypervisors mention has their own unique considerations to manage CPU s. An example is CPU % Ready in VMware. CPU % Ready increase when processors have to wait for instructions sets to be processed. This is a result of VM s consisting of different processor configurations some being single core, some dual and others quad core. The quad core VM s must wait until 4 processors are available to execute code. If the CPU % Ready is high VM performance will suffer. Check the best practices for CPU management pertaining to the hypervisor that is chosen. Configuring Virtual Machines Once the planning and implementation of the virtual host has been configured the next step is to configure VM s for deployment. With regard to 2X Publishing Agents, Secure Client Gateways and RDS servers here are the recommended best practices for VM configuration: Install the Hypervisor tools Sysprep Templates Turn off UAC Configure Firewall Settings with Appropriate Ports Open or Off Configure Anti Virus Exclusions for 2X Remote Application Server and Related Services Hypervisor tools are used to manage VM s from the hypervisor console and are also needed by 2X for VDI. Syspreping templates is import to ensure the SID is unique to the VM being created. Turning of UAC insures various services can function properly like activating 2X Remote Application Server. Configuring firewall appropriately will ensure proper communications between 2X services. Anti virus programs may interfere with the functionality of 2X Remote Application Server and its services. It may be necessary to add 2X Remote Application Server and its services to an exclusion list in the anti virus software.

38 Virtual Desktop Infrastructure Installing the VDI Guest Agent To publish VDI desktops a 2X Host Agent must be installed on the hypervisor host server. Each hypervisor has a specific manual for utilizing VDI which can be found at: Installing the 2X Guest Agent will allow the Publishing Agent the ability to publish VDI guests. First select VDI Hosts from the Farm. Next, select Virtual Desktop Host tab and click Virtual Guest Setting in the lower left corner of the window. From Virtual Guest List select a guest and click Check Agent from the Task menu. If the Guest Agent hasn t been installed select Install. Once the install is complete click Done

39 Publishing VDI Desktops Now the Guest can be published by selecting Desktop form the top menu. Select Virtual Desktop and click Next. Next name the Guest to be published and a description may be added to explain its purpose.

40 From the Connect to menu select what type of Guest to publish next. Any Guest and Guest will give the option to choose what pool to get a Guest from. Then choose the Pool to publish the Guest from and select Ok. Note that all Guest are in the Default Pool but other Pools can be created for organizational purposes. If Specific Guest is chosen then a list will Guest will be presented to choose from.

41 Select the type of filtering to be used and click Finish. Configuring Pools Pools offer administrators more flexibility when managing an extensive number of Guests, especially when they are implemented in large company infrastructures. 2X Remote Application Server console provides the framework and tools needed to create a complete Pool Management foundation. To add a Pool to your farm click the green + symbol and then enter the Pool name. To delete a Pool, click on the Pool in the Name list and then click on the red symbol.

42 Adding Pool Members to a Pool Select the Pool that you want to add Members to and then click on the Add button from the Task menu. Choose from the following types of Guests: All Guests in Farm: All guests that are located in the farm. All Guests in Host: All guests that are located on a particular host. Guest: A single guest located in the farm. Native Pool: Group of guests that have been previously configured from the hypervisor management tool. Please note that the hypervisor may use different terminology instead of pools (e.g. resource pools) 2X Template: Guests that are automatically created from a 2X Template. Wildcard Function The Wildcard field is used to match specific guests from any available guests within a pool. Select the guests from the list and add to your Pool. Use the asterisk (*) symbol to match any characters. For example, XP* will find only guests whose name starts with XP and *XP* will find guests with XP in their name. Delete a Pool Member Select the Pool member you want removed and click on Delete. The selected Guest is then deleted from that Pool. Pool Guests The Pool Guests button allows you to view and manage Guests in a particular Pool. Select a Pool and the Guests that are included in that Pool appear in the Virtual Guests List. Click on the Refresh button to view new additions to the Pool list. Click on a Guest in a Pool and then click on Clear Settings

43 Virtual Guests List Choose a Guest from the Virtual Guests List and click on Check Agent to verify that the Guest Agent is installed. Select a Guest within a Pool and click on Properties. Guest Advanced Settings The Guest Advanced Settings dialog box appears and you can further configure each Guest in the Pool. Enable Do not use this guest checkbox so the system ignores the particular Virtual Guest. The Computer Name field allows you to set the network name (domain name / IP address) of the computer that the system will use to connect to the Virtual Guest. The Port field contains the port number that the system will use to connect to the Virtual Guest. Use the Connection Timeout field to set a time limit on attempts a 2X Remote Application Server can connect to the particular Virtual Guest. Protocol is the method used for 2X Remote Application Server to communicate with the Virtual Guest. You can set what actions the guest will take if a user disconnects from a session by choosing an option from the If session disconnects drop down list. You can choose the amount of time that needs to pass before the selected action is taken. A session can be terminated after the user disconnects from the session. You can choose the amount of time that needs to pass before the disconnected session is terminated. The user can reconnect to a previous session if that session is still available. Configuring 2X Templates With the aid of 2X Templates you can better utilize host resources. 2X Templates allows you to automatically create and deploy Guest VMs when needed. To create a 2X Template, click on the 2X Templates tab and then click Add. Creating a 2X Template The Virtual Guests List dialog box appears. Select a Guest that will be designated as a 2X Template, then click on OK.

44 Once you have selected which guest you will be converting to a 2X Template the Guest Agent Information dialog box appears containing all the information that is associated with that particular Guest. If the agent is not verified or installed, you can install it by clicking the Install button. The Guest Agent makes it possible to create new clones, use universal printing and scanning. Once the status is complete click Done.

45 After the Guest Agent has been installed a new dialog box appears showing the updated Guest Agent information. Click Make Template to create a 2X Template. Given that clones are created from the templates, it is possible to view information about the clones created from the templates by clicking Info

46 Maintenance Mode If there is the need to update the template OS, you need to put the template into Maintenance Mode. In the mode the OS can be booted and modified. Once the desired changes have been applied you can put the template off Maintenance Mode. This is required when you need to: install Operating System service packs, install new software, or uninstall current packages. During maintenance mode clones cannot be created from the guest and the entry from the 2X Templates in Farm becomes greyed out. NOTE: When maintenance mode is applied on a template this will only affect newly created VMs. Any VMs already created, are not affected. Also only use maintenance mode to convert templates to VM s. 2X Template Properties Select a 2X Template from the list and then click on Properties. The 2X Template Properties dialog box opens. 2X Template: Enter a descriptive name for the 2X Template or re name existing templates. Maximum Guests: The maximum number of guests that can be created.

47 Pre created Guests: Enter the number of guests that will be pre created so that users will find a desktop ready without having to wait for the cloning process to finish. Guest Name: Enter the Guest Name. Please note that each guest name is appended with the guest ID. If you don t want to allocate space on the server for Guests that are not in use enable the Check the Delete unused guests checkbox and set the time limit if you would like the guests that are not being utilized deleted. Advanced The Folder field is the location where the newly created guests (created from the 2X Template by Remote Application Server) will be created. This folder feature is available for Hyper V, Parallels Server4, Citrix Xen and VCenter. If the hypervisor you are using supports Native Pools, then the newly created Guests will be part of the specified Native Pool location. VMWare ESX, VMWare VCenter and VMWare Server support Native Pools. SysPrep The SysPrep tab contains settings you need to be able to join your Guest to either a workgroup or a domain. Computer Name: Enter the computer name that will be using the 2X Template guest. Owner Name: Enter the user or owner name of the user that will be using the 2X Template guest. Organization: Enter your organization s name Administrative password: Enter the administrator password. Join workgroup: Select this option if the guest will be part of a workgroup. Enter the workgroup name in the field provided. Join domain: Select this option if the guest will be part of the domain. Enter the appropriate information such as the domain name and the administrative credentials.

48 License Keys The License Keys tab allows you to add the licensing information of the Guest s operating system. Click on Add and the Add License Key dialog box appears. Enter the License key information and the maximum number of guests that will be using the license. Persistent Guests

49 When a published application from a guest is set as persistent, the first time a user launches the application, the publishing agent will create a persistent guest rule. Below is the list of rules that the publishing agent preserves. The publishing agent will always connect the user to the same guest when the persistent rule is used. The Persistent Guests can be viewed and managed on this tab. The information that is provided includes the Guest name, Host IP address, the last time this guest was used, when the persistent guest rule was created and the state of the persistent rule. Click on the headings and you can choose to show or hide any of the column headings. Click on the Refresh button to view new additions to the Persistent Guests list. To delete a persistent guest entry, select and click on Delete. To delete all the existing persistent guests in the list click on Delete All. Choose to automatically remove persistence if the guest is not used for the specified amount of time. Choose from 24 hours, 1 day, 1 week or 30 days.

50 Remote PC Agents The Remote PC Agent is installed on remote PC s (physical machines) as a service. Properties tab of the Remote PC Agent allows the Remote PC to be enabled or disabled in the Farm. A description can be added to provide additional information about the Remote PC. Agent Setting contains the port number that the system will use to connect to the Remote PC. You can configure the direct address by checking the Change Direct Address box and entering a new direct address. This address is used in Direct Connection mode only. This can be an internal or external IP address; depending where the clients will be. If external, the IP address must be assigned at your firewall to your servers. 2X Remote Application Server can wake a PC by sending a packet over the network. This will continue until the receipt of the packet is acknowledged or until the connection is timed out. In the Connection Timeout field, choose a connection time out. The Publishing Session Timeout field allows you to designate a time before the publishing session times out conserving system resources. Checking the Allow Client URL/Mail Redirection box allows http and mailto links to be opened using local applications instead of using terminal server resources.

51 RDP Printer settings are used to change the name format of RDP printers in Windows server before 2008 and MS Easy print. Remote PCs The 2X Remote Application Server install package has a Remote PC Agent which can be deployed in a variety of different scenarios to meet different end user requirements. The 2X Remote Client can be installed on any supported version of Microsoft Windows and from these workstation applications and desktops can be published. The Remote PC Agent works in a similar way to the 2X Terminal Server Agent but it s designed for a standalone PC installation. It uses the RDP protocol to publish desktops and applications from that PC much in the same way desktops and applications can be published using the terminal server agent.

52 The Remote PC Agent is made available for a variety of different scenarios which may require the publishing of a resource from a standalone network computer rather than a terminal server or a VDI host. The reasons for such scenarios may include: Insufficient licensing for a terminal server environment some applications require a special license when installed on terminal servers making it impossible to publish a particular application from a terminal server. Can t Install on Server Some applications may have a strict installation requirement for legacy versions of Windows or may not be installable alongside certain Windows Server services. Legacy OS Support Some application may not work on newer versions of Windows and may only be compatible on older versions of windows. Microsoft Windows ships with the ability to remotely connect to the machine using RDP with an administrator account. However, this is a 1 user license only using the administrator account Prerequisites The Remote PC client generally supports all versions of Windows for Windows XP, 7 and 8. The RDP service should be enabled and ready to accept incoming RDP connections. Installing the Remote PC Agent The Remote PC Client is pushed installed from the 2X Remote Application Server console. In order to commit a push install from the 2X Remote Application Server console please proceed to do the following: Open the 2X Remote Application Server console and navigate to Farm > Remote PCs. Click Add The below window will pop up, enter the hostname or IP Address of the Remote PC and click Next. The Get MAC button can be used to verify the hostname and acquire the MAC Address

53 After clicking Next the 2X Remote Application Server will the presence of a Remote PC agent already installed on this computer. If not found, the below screen will display offering you to install it. Click Install to begin the installation. When the installation is complete, click Done to add the Remote PC agent to the catalog. At this point the Remote PC agent can be used to publish applications and desktops. Uninstalling a Remote PC Agent The Remote PC agent can be uninstalled from the 2X Remote Application Server console. Open the 2X Remote Application Server console and navigate to Farm > Remote PCs. Click Check Agent and then click Uninstall. When the agent is uninstalled. Finalize the uninstallation after completion to remote the Remote PC agent from the catalog. Configuring Remote PC s The Remote PC agent has more or less the same publishing functionalities and features as other 2X resource agents, for example 2X Universal Printing can be used and drive redirection is supported. The settings for the Remote PC agents are editable from the 2X Remote Application Server console and any changes will be pushed out to a Remote PC Agent automatically after applying. Click Properties to review the settings which can be changed for a Remote PC agent.

54 Properties Enable Remote PC Is set to On Make sure that Enable Remote PC box is checked so the new Remote PC is enabled in your Farm. In the Remote PC field then you can enter or edit the name of the remote pc. MAC Address Enter the MAC Address of the PC you would like to add. Use the Get MAC button, if you are adding your local machine to easily get the MAC Address. The MAC Address is a unique identifier relating to the workstation s network card or communication hardware used to identify specific machines on a network. Protocol The Protocol field identifies the protocol used by the Remote PC. Only RDP can be used on Remote PC, however other 2X Resource Agents may allow for ICA remote protocols for example. Description An area where a summary for this entry can be entered. Agent Settings This tab contains network and communication related settings that are pushed to the Remote PC Client. Port The Port field contains the port number that the system will use to connect to the Remote PC. Change Direct Address You can configure the direct address by checking the Change Direct Address box and entering a new direct address. This address is used in Direct Connection mode only. This can be an internal or external IP address; depending where the clients will be. If external, the IP address must be assigned at your firewall to your servers. Connection Timeout Timeout when a remote connection which is not responding will be ended by the Remote PC agent. RDP Printer The RDP Printer tab gives you the option of selecting the format of redirected printers. The format may vary depending of which version and language of the server you are using. Set your RDP Printer Name Format by choosing from the following three options: Printername (from Computername) in Session no. Session no. (computername from) Printername Printername (redirected Session no)

55 Configuring and Adding Backup Servers To ensure users do not experience an interruption in service due to a failure with the primary Publishing Agent a Backup Server can be configured. The figure below shows a Backup Server in the environment with a Master PA and TS s. Adding 2X Backup Servers Open the 2X Remote Application Server console and navigate to the Backup Servers node in the navigation tree. Configuring Backup Servers for a Site Click Add from the Tasks drop down to launch the Backup Server wizard. Specify the IP address of the server that will be the new backup server. In the second step of the wizard you are prompted to install the 2X Backup Server service on the target server unless already installed. Click Install to install the backup service. Note: If the server is currently used for some other role the option to take over will be available instead of install.

56 If you want to take over the server to use it as a backup server, click the Take Over button. In the Installing 2X Redundancy Service dialog highlight the server name on which the 2X Agent is to be installed. (Optional) Tick the option Override system credentials to specify and use different credentials to connect to the server and install the 2X Agent as seen in the below screenshot. Installing the 2X redundancy Service Click Install to install the agent and click Done once it has been successfully installed. Click OK to add the server to the farm. NOTE: The Install button changes according to the status of the selected server. It will change to Update if an older version of the 2X Backup Server is found, while it will change to Take Over if the selected server is already configured with a 2X Publishing Agent configured as the master server.

57 Modifying Backup Servers To change the properties of each backup server, select the particular server and click Properties. You can enable or disable the selected backup server and you can also install update or uninstall the backup server from the properties dialog box. To delete a particular backup server, select the required server from the Backup Servers list and click Delete. Each backup server in the list is given a priority. By default the local 2X Publishing Agent is given the Master priority and this cannot be changed. You can change the priority of the backup server. To assign a higher priority in the backup list select the required backup server from the list and click Move up. To assign a lower priority in the backup list select the required backup server from the list and click Move Down. The Backup Server with priority configured as Backup Server 1 will be the first backup server to take over in case the Master Server is not available. Additional backup servers will take over in case Backup Server 1 is also not available according to their priority.

58 Promoting a Backup Server to a Master Server When the primary server cannot be recovered due to various reasons such as hardware failure or OS startup failure a 2X Backup Server can be easily promoted to a Master server. First launch the 2X Console located on the backup server. Then click Promote to Master located at the bottom of the Backup Server tab. After the server has been promoted a full 2X Remote Application Server console will be available.

59 HALB High Availability Load Balancer Before you can configure HALB from the 2X RAS console, you first have to import an appliance with either of the following Hypervisor platforms; Virtual Box or VMware. An appliance is a pre configured virtual machine (including the operating system and other relevant settings). For Virtual Box or VMware this appliance should be imported with either the OVA or zipped VMDK appliance file obtained from the 2X Website. If deployed via the OVA file, the VM is applied with machine specifications already configured. Alternatively deployment via the VMDK file deploys the VM without pre configured specifications. The minimum specifications for this VM are outlined below: 1 CPU 256 mb RAM 1 Network Card For Microsoft Hyper V this appliance should be imported with the VDH file obtained from the 2X Website. Once confirmed, proceed with the 2 stage setup process; HALB appliance installation and configuration and adding an HALB appliance from 2X RAS.

60 HALB Appliance Installation and Configuration The HALB appliance should be imported on a Hypervisor running on a machine within the same local network as 2X RAS. Import the HALB appliance on a supported Hypervisor according to the procedure below. Download the required HALB package i.e. either the OVA, VMDK or VDH file from the 2X Website. You will need to unzip the VMDK file, if required. Then simply import either the VMDK, OVA or VDH file from the virtualization platform s management console. Then power up (boot) the new appliance. Adjust the network settings if necessary and click Apply to continue. The Configuration Console is displayed and the HALB appliance is ready to be added to a 2X RAS farm.

61 Adding an HALB Appliance from 2X RAS Subsequent to the 2X HALB appliance installation, the appliance has to be configured from a 2X Remote Application Server (RAS) farm. Configure the 2X HALB appliance according to the procedure below: 1. Log in to the 2X RAS Console. 2. Go to Farm > HALB. 3. Enable HALB check box. 4. Enter the Virtual IP (shared IP) in the first field. This is the IP that the clients will connect to. This will also be the floating IP used by the HALB appliances. 5. Enter the appropriate network mask. 6. For load balancing normal gateway connections, enable the LB Gateway Payload check box and click Configure. 7. From the HALB Configuration window, select the gateways that 2X RAS will load balance using the HALB appliances and click OK. 8. Next, for load balancing SSL connections, enable LB SSL Payload check box and click Configure.

62 9. The mode selected Mode dropdown specifies where the SSL decryption process is performed. By default, the SSL connections are tunneled directly to the gateways (referred to as pass through) where the SSL decryption process is performed. 10. To set the SSL decryption process to be performed on the HALB appliance, select SSL Offloading Mode and click Configure. This mode requires an SSL certificate installed on configured HALB appliances. 11. From the window illustrated above, upload an SSL certificate to the HALB appliance for SSL offloading. This can be either a self signed certificate or a certificate obtained from a registered Certificate Authority. (Optional) Tick the option Allow only strong ciphers to only allow the usage of certificates using strong encryption algorithms. Select the Accepted SSL Version from the options available in the drop down. Click on Generate new certificate and enter the required details. Alternatively, set up a certificate from a trusted authority according to the instructions below. Click on Generate certificate request

63 Fill in the details and click Save to bring up the certificate request window. Click Copy to copy the request. This certificate request should be sent to a certificate authority. Once you receive the SSL certificate from the certificate authority click on the Import public key, browse for the certificate file containing the public key and click Open. Click OK to save the settings.

64 12. Upon completion, proceed to add all the HALB appliances that will be managed by this farm. Click the green plus icon shown above to bring up the Add HALB Devices window. 2X RAS is capable of detecting 2X HALB appliances over the network and display them, as a list. Selecting detected HALB appliances from this list is the preferred method for adding new appliances. If for some reason, the appliance cannot be detected, you can also add the appliance manually by specifying the appliance IP in the IP Address field. Click OK to apply the config. 13. After the OK button is pressed, the appliance is initialized and added to the list.

65 14. Finally, click Apply for configuration to be applied to all added HALB appliances.

66 Farm Settings Auditing The Setting in the Farm allows the Auditing, Global Logging and URL Redirection to be configured. Auditing can be enabled to capture Date & Time, Action, Application ID, Application, Server Name, Session ID and PID information.

67 Global Logging Global Logging can be enabled to track various data communications between servers. It creates a Zip file to a location set by the administrator.

68 URL Redirection URL Redirection creates an exception to URL Redirection and will open the URL using the Terminal Server browser.

69 Configuring Load Balancing and Tunneling Policies The 2X Load Balancer is designed to balance RDS connections made from 2X Clients or RDC to 2X Remote Application Server with more than one RDS server in the Farm. Load Balancing is automatic once the second RDS server is added to the Farm. That is contingent on the items being published being on more than one RDS server. The key components of the Load Balancer are: Method Session Connections Advanced Settings Tunneling Policies To view Load Balancing choose the Load Balance icon from the systems menu. In the center console the properties of the Load Balancer can be seen.

70 Methods The default load balancing method is Resourced Based and is configured to monitor User Sessions, Memory and CPU usage. Round Robin is also available as a load balancing method and can be changed using the drop down menu for Method. The Round Robin method sends users in sequential order to the next RDS server with regard to status of the resources of that server. If there are 2 RDS servers user 1 is sent to server 1, user 2 is sent to server 2 and user 3 will be sent to server 1. Round Robin is best used in scenarios where the resources are the same across all servers and the connections are the same from every client. Troubleshooting Tip: the Round Robin method may be used if all new connections are getting disconnected or not connecting to and RDS server at all. A server with an issue will have the least amount of utilization and therefore all new connection will be sent to it. Session Connections Reconnecting to disconnected sessions is configured by default to ensure users reconnect to a session that was disconnected and the applications or other items that were in use reopened in the same state. Reconnect sessions using client s IP address only is used to reconnect RDP sessions due the configuration of RDP packets. It isn t needed with 2X Client connections. Limit users to one session per desktop are useful to ensure multiple sessions are not opened by one user witch would cause more than 1 RDS CAL to be used by that user.

71 Advanced Settings The Advanced Load Balancer Settings can be used to test connections from the Publishing Agent to the RDS server and prevent connections being sent to it if it isn t responding. These times may be adjusted for latency on the network. A process can be excluded so it isn t counted against the total of CPU % being utilized.

72 Publishing and Filtering Applications Publishing Publishing from 2X Remote Application Server is one of its fundamental uses. 2X Remote Application Server can publish the following: Applications Folders Desktops Predefined Applications Documents To publish applications select the Publishing icon from the systems menu. This will show what applications have already been published. If the application has yet to be published select the Application icon from the console top menu. Then select where you would like to publish the application from. Applications can be published from RDS servers, Virtual Guest and Remote PC s. Next choose the type of application to be published.

73 When Single Application is chosen first the Server (s) must be selected to publish the application. If All Servers in Farm is chosen then the application must be installed on all the servers in the Farm. A Server Group or Individual servers can be selected. Once a server or servers has been selected choose the Target folder and.exe of the application to be published by selecting Next the application can be filtered to determine which users can access the application. There are several methods for filtering which are: User Client IP Address MAC User filtering allows filtering users by either Workgroup or LDAP (Active Directory).

74 Client filtering allows for filtering by computer hostname. IP Address filtering allows for filtering by a computer IP Address.

75 MAC filtering allows for filtering by a computer MAC Address. Click Finish after the filtering selection is completed.

76 Published applications will appear in Published Resources and in the 2X Client after clicking the Apply button. The configuration for published applications can be changed by selecting the Published Resource. Then select the tab that corresponds with the change that needs to be made.

77

78 Folders and Application Grouping A folder can be created to place documents or applications in to organize them. First select the Folder icon from the console top menu. Then enter a folder name and description (optional). The icon for the folder can be changed from the default which is shown in the in the picture. Next a filter can be applied to control access to the folder. Published Folders will appear in Published resources and in the 2X Client after clicking the Apply button.

79

80 Desktop Publishing 2X Remote Application Server can publish full Terminal Server, Virtual and Remote PC desktop. To publish a desktop select the Desktop icon from the console top menu. Then select the type of desktop to be published. The Terminal Server, Virtual or Remote PC Desktop must be selected from the server, guest or PC they will be published from. RDS Desktop Virtual Desktop Remote PC Filtering is the final step to publishing a desktop.

81 Published desktops will appear in Published Resources and in the 2X Client after clicking the Apply button.

82 Predefined Application Publishing Predefined applications can be published by selecting the Predefined Application icon from the console top menu. Then select the application or applications to be published and click ok. Published items will appear in Published resources and in the 2X Client after clicking the Apply button.

83 Document Publishing To publish a document the Document icon from the console top menu. Then select where the document is to be published from. Select the document type. Then depending on where the document is to be published from a Terminal Server, Virtual Desktop or Remote PC needs to be selected and location of chosen using the next to Target. RDS Desktop Virtual Desktop Remote PC

84 The document can be filtered as with other published items. Published documents will appear in Published resources and in the 2X Client after clicking the Apply button.

85 Managing Published Items Published items can be managed from the options menu of the console when Publishing has been selected from the systems menu. Applications can be Added, Deleted, and Moved Up, Moved Down, Disabled, Sorted or a searched for using the Find option. These options are self explanatory but it s worth noting that the Sort will place published items in alphabetical order. Troubleshooting Tip: Placing the published items in a specific order may be beneficial to admins so that can refer to the icons without looking directly at the 2X Client.

86 2X Universal Printing When using 2X Remote Application Server the printing process is greatly simplified by the 2X Universal Printer which is automatically installed when you install the agents for Terminal Server, VDI Guest and Remote PC. 2X Universal Printing will solve most printer driver problems. If the client is using a printer where the server does not have a suitable printer driver the normal printing redirection will not work. You do not need to install a specific printer driver on the server when you are using 2X Universal Printing. The 2X Universal Printer drivers are available in 32 and 64 bit format. 2X Universal Printer Support was added to HTML5Gateway and the Chrome app in Version 14. Starting from 2X Remote Application Server version 10.1 you can redirect multiple printers at the same time as opposed to the previous versions where only one printer (2X Universal Printer) was available on each terminal server. The administrator can choose the format of each printer name by editing the Printer rename Pattern text box. You can also choose to continue to work in legacy mode by choosing <2X Universal Printer> as the printer rename pattern, in this case only the first printer redirected by the client is utilized. You can use any of the following variables in the Printer Rename Pattern text box: %PRINTERNAME% %USERNAME% %SESSIONID% Client side printer name User name connected to the server Session ID of the active session <2X Universal Printer> Legacy mode (only one printer for all users) Choosing <DEFAULT>, the default printer pattern is used. The default pattern is %PRINTERNAME% for %USERNAME% by 2X. Redirected printers are only accessible by administrators and the user who redirected the printer. Choosing <2X Universal Printer> only one printer will be shown on the server and is available for all users.

87 HTML5 Gateway and Chrome App Printing With the introduction of Version 14 2X Remote Application server we have added support for 2X Universal Printing. When printing via the HTML5Gateway and the Chrome App the user will see the 2X Universal Printer option. Chose this print option and click print. Once the users prints the 2X Universal Printers for HTML5Gateway and Chrome App will open the local printers installed on the device. To enable or disable the functionality of 2X Universal Printing from each Terminal Server, VDI Guest or Remote PC in the farm, select the Terminal Server(s), VDI Guest(s) or Remote PC s and click Enable from the Task drop down menu. Click on Select All to facilitate 2X Universal Printing on every type. To Disable Universal Printing, select the Terminal Server, VDI Host or Remote PC and then click Disable from the Task drop down menu.

88 Fonts Management To control the embedding of fonts within a print job use the EMF Properties tab and check/uncheck Embed Fonts. By default a number of fonts will already be excluded since these are normally available on standard Windows platforms. If the client selects Enhanced Meta File data format for Universal Printing the fonts are embedded with the print job. To add a new font click on the Add button from the Task menu and select the font to be added. To delete a font select the font from the excluded list and click the Delete button from the Task menu.

89 2X Universal Scanning Scanner redirection enables users who are connected to a remote desktop or accessing a published application to make a scan using the scanner that is connected to the client machine. 2X Universal scanning uses TWAIN, as well as WIA redirection to let any application using either technology hardware connected to the client device for scanning. With 2X Universal Scanning there is no need to install any scanner driver on the server. Only one scanner is shown on the server regardless of the number of users and sessions currently in use on the terminal server. Note: The server feature Desktop Experience is required in order in enable both WIA and TWAIN scanning on Terminal Servers. With 2X Universal Scanning there is no need to install any scanner drivers on the server. Only one scanner is shown on the server regardless of the number of users and sessions currently in use on the terminal server. The 2X Universal Scanning drivers come in 32 and 64 bit format.

90 Universal Scanning Options By default the 2X Universal Scanning driver is automatically installed with the Terminal Server, VDI Guest and Remote PC agents. Therefore upon adding a server to the farm the 2X Universal Scanning is installed. Note: The 2X Universal Scanning driver is available in 32 and 64 bit format. Currently only 32 bit applications are supported. NOTE: Embedded fonts are deleted after print job.

91 Configuring a Scanning Rename Pattern By default 2X Remote Application Server renames the scanners using the following pattern: %SCANNERNAME% for %USERNAME% by 2X. Therefore if a user Samuel that has SCANNER1 installed locally connects to a remote desktop or published application, his scanner is renamed to SCANNER1 for Samuel by 2X. To change the pattern used to rename scanners specify a new pattern in the Scanner rename pattern input field found in the 2X Remote Application Server Console > Universal Scanning node. The variables available for renaming scanners are: %SCANNERNAME%: client side scanner name %USERNAME%: username of the user connected to the server %SESSIONID%: session ID of the action session You can also configure a different scanner renaming pattern specifically for each server from the server properties. Note: Redirected scanners are only accessible by administrator and the user who redirected the scanner. Enabling and Disabling 2X Universal Scanning Support To enable or disable WIA or Twain 2X Universal Scanning support from a particular server follow the below procedure: Open the 2X Remote Application Server console and open the Universal Scanning category in the navigation bar. Click the WIA tab or the TWAIN tab. Highlight the name of the server you would like to modify and click Enable to enable 2X Universal Scanning support or Disable to disable it from the Tasks drop down menu.

92 Adding Scanning Applications TWAIN applications that will use the Universal Scanning feature have to be added from the TWAIN tab by selecting the TWAIN Applications button so they can use the Twain driver, hence making it easier for the administrator to set them up. Follow the below procedure to add an application to the list of Scanning applications: Open the 2X Remote Application Server console and open the Universal Scanning category. Click the TWAIN tab. Click on the Twain Applications button and click Add. Browse to the application executable and click Open. Configuring Scanning Applications Note: Some applications might use different or multiple executables. Make sure that all used executables are added to the list of scanning applications. Deleting a Scanning Application To delete a scanning application from the list highlight the application name and click Delete from the Tasks drop down menu. Note: By deleting an application from the list of scanning applications the installation of the application will not be affected.

93 Connection and Authentication Settings Authentication The Connection Manager section of the 2X Remote Application Server allows administrators to require all users authenticate connections against a 2X Remote Application Server. All trusted domains or workgroups will be allowed to make connections to the 2X Remote Application Server by default. An individual domain or workgroup can be selected from a list by selecting which will allow only that domain or workgroup to connect to the 2X Remote Application Server. If the domain is specified the Use client domain if specified can be unchecked and it will automatically populate that field in the 2X Client. To clear all cached session IDs click on the Clear cached session IDs. NOTE: To authenticate a workstation not joined to a domain a local account can be used. In order to avoid user filtering problems it is suggested to use the NetBIOS name instead the FQDN in the domain field.

94 In order to specify authentication with a workstation you must enter [workgroup_name] / [machine_name]. Therefore if you would like to authenticate against a machine named SERVER1 that is a member of the workgroup named WORKGROUP, you would have to enter: WORKGROUP/SERVER1 in the domain field.

95 Second Level Authentication Second Level Authentication is used to provide higher level of security. 2 nd Level Authentication provides networks with an extra layer of security. Users will authenticate through two successive stages to access their network. While the first authentication will use the native authentication AD/LDAP the second level authentication is supported by one of the following: Deepnet Authentication Server Safenet Server Radius Server 2 nd Level Authentication works differently than 1 st Level Authentication as a standard username and password are not provided. Although you may have a static username consisting of numerals the password is not consistent as it is provided on a when needed basis as a One Time Password (OTP). Here is a list of our supported tokens: SafeID FlashID MobileID QuickID GridID SecureID (RSA) DigiPass (Vasco)

96 Configuring Deepnet, Safenet or Radius To add 2 nd Level Authentication to your 2X Remote Application Server you can use Deepnet, Safenet or Radius Authentication vendors. Open 2X Console and click on the Connection button on the left hand pane then browse the Second Level Authentication tab. Check the Enable second level authentication checkbox, and then choose the second level provider. Deepnet Settings Connection Enter the server name and port that was used to set up the Authentication Server. Click on Check Connection to test that the Authentication Server can be reached. Choose to connect to your Deepnet server over SSL by checking the Enable SSL checkbox. Application Select the application profile that will use Deepnet to authenticate users in the Application field. The Default Domain fields will enable you to choose the default domain used for authentication and when users are added. Any Deepnet user accounts imported or verified will be done so using this default domain The Use LDAP checkbox should be checked if you are importing Deepnet user accounts and groups that contain other sub groups. The Import Deepnet user accounts button will automatically add the specified users/groups into the Deepnet application. The Verify Deepnet user account names button checks that all the users in the Deepnet application are in the following format: \\domain\username. Users added in the format of username@domain will be automatically changed to the appropriate format and users without a domain will have the default domain assigned to them. The Deepnet Applications dialog allows an application to be chosen that is used by 2X Remote Application Server for authentication.

97 Select how you want your users to be authenticated. Mandatory for all users means that every user using the system must login using two factor authentication. Create token for Domain Authenticated Users will allow 2X Remote Application Server to automatically create software tokens for Domain Authenticated Users. Choose a token type from the drop down list. Note that this option only works with software tokens. Use only for users with a Deepnet account will allow users that do not have a Deepnet account to use the system without having to login using two factor authentication. From the Allow Channels section specifies what channels are available to the user to activate the token or when requesting a Quick ID OTP. For example, if you select as the Allow Channel activation code can be sent only via as shown below.

98 Safenet Settings Connection Enter your OTP Service URL and then click on the Check connection button to verify URL connection. Authentication Select an authentication mode: Mandatory for all users: All users use the same log on authentication. Create token for Domain Authenticated users: A new token is created for each authentication domain user Use only for users with a SafeNet account: Only users that have access to a SafeNet account will be allowed access. TMS Web API URL URL of the safenet server. This is required to be able to create tokens for Domain authenticated users User Repository: Where the authentication files reside on the server.

99 Radius Settings In the Server text box enter the hostname or IP of the Radius Server. In the Port text box enter the port number for the Radius Server. You can insert the default port (1812) number by clicking Default button. In the Timeout text box specify the packet timeout in seconds. In the Retries text box, specify the number of retries when attempting to establish a connection. The global timeout is timeout * retries. Click the Check connection button so that you validate the above connection settings inserted. In the Secret Key text box insert the secret key which must match the secret key specified on the Radius server. Specify the Password Encoding with either PAP (Password Authentication Protocol) or CHAP (Challenge Handshake Authentication Protocol), according to the setting specified on the Radius Server. Click Ok after configuring the connection settings.

100 Attributes Radius Attribute Value Pairs might be needed in order to authenticate with your Radius server. To configure an Attribute Value please select the Attribute tab. Click Add to add an Attribute to the list. Select the vendor for the attribute from the Vendor dropdown list. Select the vendor attribute from the Attribute dropdown list. Enter the value for the selected attribute. The value can be a numeric value, a string, an IP or a time value. Adding Vendor Attributes In order to manually add a Vendor Attribute you need to modify the file RadiusAttr.def. Please find the file in the installation folder of Application Server. The default location of the Application Server is: C:\Program Files (x86)\2x\remote Application Server The following describes how to add a new vendor called Vendor Example with 4 attributes values. Open the RadiusAttr.def file with notepad.

101 Increment the count in the Vendor section. In this case the count was incremented from 18 to 19. Add the vendor ID and vendor name as highlighted above. Please note that the id and name tag start with the previous count value. Create a section under the vendor Attributes using the id as the name of the section, in this case 777. Add the count of attributes provided and enter the description for each attribute. Please note that the attribute type must be one of the following: Type Value String 0 Numeric 1 IP 2 Time 3 Verify that the attributes added load properly in the configuration window. Once the Second Level Authentication settings have been configured exclusions can be set:

102 User / Group exclude list allows you to add users or groups within your active directory that will be excluded from using Deepnet Authentication. Client IP exclude list allows you to add IP addresses or a range of IP addresses that will be excluded from using Deepnet Authentication. Client MAC exclude list allows you to add MAC addresses that will be excluded from using Deepnet Authentication. Connection to the following Gateway IP s allows the Gateway to be set so users connected to the Gateway will be excluded from using Deepnet Authentication.

103 Allowed Devices The Allowed Devices tab allows you to configure which type and version of the clients available are allowed to list the published items. The Allow published items listing from All Clients button will allow published items from all clients. The Allow published items listing only from selection gives the administrator the ability to allow published items only from the specified 2X Client running the build set or higher. For example, if the user from 2X Windows Client gets application listing from a 2X Client with a build lower than the one specified in the text box above, the following error is seen:

104 Configuring Client Policies Client Policies are accessible through the Polices Icon. Client Policies provide a way to restrict configuration of Connection Properties and Options of 2X Clients on Windows Desktop OS (including Windows CE and XP Embedded). Users or Groups can be added to a policy which pushes different 2X Client settings and options to the users depending on the policy settings. A device Licenses are not needed to use these options.

105 Browser Mode, Criteria Connection Properties & Options Browser Mode There are 3 Browse Modes for searching Users & Groups depending on the whether a Workgroup or Active Directory structure is used. WinNT This mode is faster than LDAP mode, but doesn t allow processing of nested groups. LDAP This mode allows nested groups but is slower than the other modes. Secure Identifier Secure Identifier mode is the most efficient mode and supports nested groups. Criteria You can configure a policy where only if matched the policy will be applied to the users. This allows you to create different policies to the same user which will be applied depending from where he is connecting and what device he is using. To apply client policy criteria depending on gateway IPs select one of the following options: Client is connected to any gateway Select this option so that the 2X Client Policy is applied to the client when connecting to any gateway. Client is connected to one of the following gateways Select this option so that the 2X Client Policy is applied to the client only when the connection comes from any of the gateways specified in the Gateway IPs. Client is not connected to one of the following gateways Select this option so that the 2X Policy Criteria will be applied only if the client connection does not come from any one of the gateways specified in the Gateway IPs list. To apply client policy criteria depending on MAC Address select one of the following options: Any client MAC Address Select this option so that the 2X Client Policy is applied to the client when connecting from a machine using any MAC Address. Client MAC Address is one of the following Select this option so that the 2X Client Policy is applied to the client only when it connects from a machine using any of the MAC Address configured. Client MAC Address is not one of the following Select this option so that the 2X Policy Criteria will be applied to the client only if it connects from a machine using any MAC Addresses other than the those configured. Connection Properties Select which categories from the Connection Properties you want to enforce in the 2X Client Policy from the Category Management section. Please note that these categories will not be available for editing on the client.

106 Options Please refer to the 2XClient For Windows manual for more information about the options available on the 2X Client. The Advanced Settings contains settings for various features including redirecting paper size.

107 Client Manager With Client Manager you can manage windows clients, shadow clients and replace the desktop shell with 2X Desktop shell replacement. Client manager supports the following windows operating systems. Windows XP, Windows 7, Windows 8, Windows 8.1. These editions must be able to accept an inbound RDP connection. NOTE: Version 14 and higher no longer supports the 2XOS.

108 Devices From the Client Manager category in the 2X Remote Application Server Console you can view all clients connected to the system. You can manage, shadow and deploy the 2X Desktop Shell replacement to windows desktops only. Once the windows device is in management mode you will be able Power On, Power Off, Reboot, Log Off and shadow the desktop. Example of a managed 2X Windows Client.

109 Windows Device Groups With Windows Device Groups you now have the ability to group windows devices into manageable groups. This will give the administrator the ability to create managed groups to control all devices within the group under one setting.

110 Managing Windows Device Groups Convert Windows devices running Windows XP up to Windows 8.1 to Thin Clients using the 2X RDP Client for Windows. Install and Configure Download the 2X RDP Client for Windows from: Double click to run the 2xclient.msi or 2xclientx64.msi and proceed through the installation Wizard (install the 64 bit version on 64 bit Windows). Upon completion, run the 2X RDP Client and configure a new 2X RAS connection according to the steps below: 1. Click File 2. Click Add New Connection 3. Select 2X Remote Application Server and click ok. 4. Next, configure the connection properties below: Primary Connection Specify the 2X Remote Application Server FQDN or IP User Credentials Enter Username, password and domain 5. Click OK to create the new connection Windows Device Enrolment Windows devices can be set to automatically be managed by your farm or require that the admin approves them first.

111 Approve a device to be managed by 2X Remote Application Server from the 2X RAS Console according to the next steps: 1. Go to Client Manager > Devices 2. Click a device 3. Click Tasks 4. Click Manage Device The device state will change to Pair pending until the device reconnects. Once the 2X RDP Client reconnects, the enrolment process is completed and the device is managed by 2X RAS. Alternatively, set 2X Remote Application Server to automatically manage Windows devices according to the next steps:

112 1. Go to Client Manager 2. Click Options 3. Enable Automatically Manage Windows Devices Once managed, applications published by 2X RAS are available on the 2X RDP Client as per the above screenshot. The administrator can now check the state of the device and perform power control actions such as Power On, Power Off, Reboot and Logoff. NOTE: Devices running older versions of the client cannot be managed and are marked as Not Supported.

113 Shadow a Windows Device Shadow a Windows device to gain access to the full desktop and control applications running locally on the system as well as any remote applications published from 2X Remote Application Server. Shadow a Windows device according to the below steps: 1. Go to Client Manager > Devices 2. Select a device 3. Click Shadow NOTE : The Windows user will be prompted to allow the administrator to take control and can choose to deny access. This prompt can be deactivated by the administrator. In addition, shadowing requires a direct connection between the machine from where the console is running has device itself.

114 Desktop Replacement The Replace desktop option limits users from changing system settings or installing new applications. Replace the Windows Desktop with the 2X RDP Client, to convert the Windows operating system into a thin client like OS without replacing the operating system. In this case, the user can only deploy applications from the 2X Client. To enable the Replace Desktop feature: 1. Right click the Windows device 2. Click Properties 3. Click OS Settings 4. Enable Replace Desktop 5. Click OK Note: This feature requires an administrative password set to switch between user and admin mode on the Windows device. Switching to Admin Mode In User Mode, the user is restricted to use only the applications provided by the administrator. To change system settings, switch the device to administration mode. Change to Admin Mode by right clicking on the system tray icon, selecting Switch to admin mode and providing the password configured.

115 The above table outlines features available in Admin Mode and User Mode. Configuring Local Applications when using the 2X RDP Client Desktop replacement With the Replace Desktop option enabled, the administrator s target should be to deploy remote applications or remote desktops and use the native OS simply to deploy the software needed to connect remotely. However, in some instances local applications may be needed. The administrator still has the ability to configure local applications to be shown within the 2X RDP Client Desktop Replacement, however it is necessary to switch to admin mode prior. Publish a local application according to the next steps: 1. Shadow the user s session or use the user device station directly. 2. Switch the 2X RDP Client Desktop Replacement to admin mode. 3. Click File > Add New Application 4. Fill in the Application information

116 5. Applications added will be visible in the Application Launcher. 6. Switch back to user mode once all the applications needed are configured. For a full list of Desktop Replacement features available per OS, go here: desktop replacement/

117 Options Device Status and Color Coding Devices that connect to the 2X Remote Application Server can have any of the following Status : Off: Device is switched off Booting: Device is booting Installing: Device is installing Connected: Device is connected Logged On: Devices is logged on to the system Restarting: Device is restarted Standalone: Device has previously connected to the 2X Remote Application Server but is not managed or isn t a manageable device, therefore it cannot be managed Needs Approval: Device needs approval to connect to the 2X Remote Application Server Deny: Device has been denied access to the 2X Remote Application Server Not Support: Device is not supported by the 2X Remote Application Server Error: Device is experiencing errors

118 Scheduler The scheduler gives the administrator the ability to manage devices schedules. The administrator can pre program actions to switch on, switch off or reboot devices at a specific time of the day.

119 Administration Multiple Sites A 2X Remote Application Server RAS farm can have multiple sites. Each site consists of a publishing agent, a SecureClient GW or multiple gateways, and the agents installed on the Terminal Servers, VDIs and PCs. At least one server has to be dedicated for a site where the master publishing agent and gateway will be installed. Additional site requirements. Must be on the same LAN or have a VPN connection to the remote secondary site. Must be on the same domain or have a two trust between domains. The first default site added to the 2X Remote Application Server RAS farm is the Licensing Server, where the main 2X Remote Application Server configuration database is stored. Every other additional site on the farm will have a synched copy of the configuration database and once changes are applied to a particular site, the Licensing Server database is updated. Sites can be managed from the Farm node in the navigation tree available in the Farm category. Configuring Sites in 2X Remote Application Server RAS. NOTE: The Farm node is only available to administrators which have full permissions on the farm.

120 Adding a New Site to the Farm To add a site to the 2X Remote Application Server farm follow the below procedure: Click the Farm node in the navigation tree and click the Green Plus button to launch the Add Site wizard. Alternatively you can also select the Add option from the Tasks drop down menu. In the first step of the wizard, specify a site name in the Site input filled and specify the server IP or FQDN where the master publishing agent and gateway will be installed in the Server input field. First Step of the Add a New Site Wizard In the second step of the wizard the 2X Remote Application Server checks if the 2X Publishing Agent is installed on the site server. If not, click Install to proceed with the remote installation. Second Step of the Add a New Site Wizard Check for Publishing Agent In the Installing 2X Publishing Agent dialog, highlight the server name on which the 2X Publishing Agent is to be installed as seen in the below screenshot. (Optional) Tick the option Override system credentials to specify and use different credentials to connect to the server and install the 2X Agent.

121 Installing 2X Publishing Agent Dialog Box Click Install to install the publishing agent and gateway, and click Done once it has been successfully installed. In the last step of the Add Site wizard, click OK.

122 Accessing Site Configuration Once a new site is created you can access its configuration by running the 2X Remote Application Server Console on the site server or by switching to its configuration from the 2X Remote Application Server Console as explained in the following section Switching Between Sites Configurations. NOTE: When running the 2X Remote Application Server Console you will always be connected to the licensing server database, even if running it from a site server. Once changes are applied, configuration changes are replicated from the licensing server to the site servers. Switching Between Site Configurations From the 2X Remote Application Server Console you can only view the configuration of one site at a time. If you login as a farm administrator, the configuration of the Licensing Server site will be loaded. If you login with an administrator that has access to a specific site, the configuration of that site will be loaded. To switch between the configuration of different sites from the 2X Remote Application Server Console follow the below procedure: Open the Farm category and click on the Farm node from the navigation tree to access the list of sites in the farm. Highlight the site you would like to configure and from the Tasks drop down menu select Switch to this Site. Alternatively you can use the top bar and select the site you want to switch to from the Site drop down menu. Managing Sites Sites can be managed from the Farm node in the navigation tree available in the Farm category. From this section you can change the farm name and also add or delete sites. Replicating Site Settings to all Sites Any setting which is site dependent can be replicated to all other sites. Refer to the below table for more specific information about which settings can be replicated to other sites. Category Section Options Farm VDI Hosts, Persistent Guests Auto removal timeout Farm Settings, Auditing All Settings Farm Settings, Global Logging Logging Settings Farm URL Redirection All Settings Load Balancing Load Balancing All Settings Publishing Advanced, Shortcuts All Settings Publishing Advanced, Extensions All Settings Publishing Advanced, Licensing All Settings Publishing Advanced, Display All Settings Publishing Filtering, User All Settings Publishing Filtering, Client All Settings Publishing Filtering, IP Address All Settings Publishing Filtering, MAC All Settings

123 Universal Printing Universal Printing Printer Renaming Universal Printing Font Management All Settings Universal Scanning Scanning Applications All Settings Connection Authentication All Settings Connection Second Level Authentication All Settings Connection Allowed Devices All Settings Reporting Reporting Engine Reporting Engine Type Reporting Engine specific settings All Settings To replicate a specific setting to all other sites, tick the option Replicate settings highlighted in the below screenshot. Enabling Replication of Configuration Changes to all other Sites Overriding Site Replicated Settings If an administrator has permissions to enable or disable the replication settings makes a change to a specific setting, such setting is replicated to all other sites. If an administrator has access to a particular site only, upon modifying site settings which have been replicated, the replicated settings are overridden and the option Replicate Settings is automatically switched off, therefore such settings will no longer be replicated to other sites. Setting a Site as a Licensing Server If the licensing server fails, or if you would like to set a different site as a Licensing Server, click on the site s name from the Farm node in the navigation tree, and from the Tasks drop down menu select Set Site as Licensing Server

124 Configuring Administrators The administration section allows administrators to grant permissions to user accounts, setup accounts, notifications, import/export backups, update software and audit settings. Administration After installing 2X Remote Application Server an administrator account with full permissions is created for the user that performed the installation. Additional administrator accounts can be added with varying permissions. By selecting either + or Add from the Task Menu will present an Active Directory dialog box to add additional administrators. The administrative permissions can be set at this time by selecting Change Permissions. Full Permissions and All Sites are the default setting.

125 Site permissions can be set by removing Full Permissions. Each category of Site Permissions has a detailed description of the permissions it effects and can be set for all or specific sites.

126 Mail box Setup After configuring monitoring the SMTP server connection details should be configured to send s once a monitoring counter is triggered. Below is a list of settings to configure notifications from the Mailbox Setup tab: Sender Address SMTP Server IP or FQDN Disable or enable TLS / SSL encrypted communication SMTP Server Credentials in case the SMTP server requires authentication

127 Sending Invitations and Settings to Users 2X Remote Application Server supports multiple platforms, ranging from desktop PC s and MAC s to mobile devices and ChromeApps. The Invitation feature is designed to reduce the complexities involved in the installation and client rollout process. This feature allows the administrator to send client installation and auto configuration instructions to end users from the central management console. Before proceeding, first confirm you have correctly configured the Mail box. Send Invitation settings in the Administration Category Once confirmed navigate to Administration > Send Invitations and configure the options below: 1. First select your recipients from the Recipient section: you can browse your Active Directory and simply select a user or a group. 2. From the Options section configure the options below: 3. Target Device choose the platform that the recipients are running. The current platforms available are: Windows XP 8.1 desktops Linux desktops MAC desktops Android ios Chrome App HTML5 enabled browsers Public Gateway IP choose the gateway (GW) domain name or IP. Please note that this can be the public IP, in order to reach the system from a remote user. Gateway Mode Choose the gateway connection mode. Note that SSL modes require the GW to have SSL configured.

128 Default Invitation template 4. The section displays the message that will be sent to the addresses added from the Recipients section. Choose to edit the text within this or leave it as default. The variables available to be added to the are: %RECIPIENT% Recipient username %SENDER% Administrator account which the is sent from %INSTRUCTIONS% Includes the automatic configuration process %MANUALINSTRUCTIONS% Includes the manual configuration process 5. Upon completion, Click Send Invitation to send out the to the recipients added; Preview to view how the will be displayed to the users; Default to revert the back to the original text.

129 Notifications To be notified when some counters exceed a certain amount, you will need to enable the notification options. In the Notification tab you ll be notified if some server parameters exceed what you define as appropriate. You can choose any of the counters monitored by the 2X Terminal Server Agent and set the appropriate number accordingly. For example, if you want to be notified when a terminal server is handling more than 45 sessions simultaneously or if the terminal server has more than 10 disconnected sessions simply check the appropriate checkbox and set the right amount.

130 2X Reporting Before you can generate reports from the 2X RAS console, MS SQL and the 2X Reporting Service must be installed and configured. Please See Section 16 for reporting configuration. Once 2X RAS Reporting is configured you can test your reporting server s settings as well as maintain data retention. Data Retention Settings

131 Backup, Software Updates & Settings Audit Backup A backup of the Application Server configuration can be made by using Export under the Backup tab. To restore a new installation or repair an Application Server the configuration can be Imported. The files exported after Version 11 have a DAT2 extension. Prior to Version 11 the extension on the file was DAT. A DAT file can t be imported into a system running Version 11 and higher. The configurations file should be exported once the server is completed configured. It is recommended that this file be exported and stored somewhere else besides the host server. Prior to any major changes it s recommended to make a backup and export the file out too. Software Update The 2X Remote Application Server Console will automatically check for updates if you have the Check for updates when launching 2X Remote Application Server box enabled. You may also click the Check Now button to check for the latest updates. In the Modules Information field you can find information about the modules used by 2X Remote Application Server. This field will give you an overview of what files are installed and their current version. This is the information that will be requested from technical support should you need to contact them.

132 Settings Audit From the Settings Audit tab in the Administration category you can see all the 2X Remote Application Server configuration changes done by all 2X Remote Application Server administrators, as seen in the below screenshot.

133 Local Information The Information section provides administrators with information to help them see client connections, send notifications, log and audit, check for updates and get support. Select Information from the navigation bar. You can monitor the status of each service, while also monitoring sessions connected to the Virtual Desktop Host, Terminal Servers that are enabled in the farm. The status is refreshed every minute. Click on the Refresh button to manually refresh the content.

134 Site Information The Site Information tab displays various information about the 2X environment such as: Servers Gateways Sessions Applications Server information shows the type, Agent status, CPU utilization, Memory utilization, Active Sessions and Disconnected Sessions. Gateway information shows the OS type, 2X Version, Gateway Mode, Allow only strong ciphers, Gateway port number, SSL/TLS status and port number, Broadcast service, active RDP sessions and Security Mode. Sessions information shows the active session User ID, IP, Protocol, State and Type. Application information shows what applications Users have opened and the session number.

135 Support For further technical support queries or further information about 2X products view contact details on this tab. Click on the Send Support Request button to contact 2X Support directly from the 2X Remote Application Server console. Fill in the required details; add an attachment if needed and click Send. You should configure your mail settings in order to contact 2X Support from the 2X Remote Application Server console. You can save your support request information as a Zip file, this way you don t have to send the straight away; you can send the Zip file later on from any other machine.

136 2X Reporting Software Requirements With the introduction of Version 14 2X introduced a built in reporting tool. 2X Reporting is a service that use Microsoft SQL Server to supply 14 reports to administrators. NOTE: 2012 SQL Express edition has a 10 Gigabit data base limitation. Before you can generate reports from the 2X RAS console, MS SQL and the 2X Reporting Service must be installed and configured. Before doing so, first check whether your machine complies with the prerequisites outlined below. Once confirmed, proceed with the 3 stage process; MS SQL installation and configuration, 2X Reporting Services installation and 2X RAS configuration. Supported Operating Systems A machine running Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 or Windows Server 2012 R2 with.net 4.5 installed. Database Engine Microsoft SQL Server 2012, SQL Server 2008 R2 Service Pack 1, SP2 and SP3. NOTE: On farm environments with multiple terminal servers, gateways, or vdi servers it is recommended that MS SQL is installed on a dedicated machine. Active Directory User Requirements To View reports, a user must be created in the Active Directory with the following credentials: Username: RASREPORTINGVIEW

137 Install & Setup MS SQL Reporting requires a database instance installed either on the same machine running 2X Remote Application Server or recommended on a different machine running within the 2X RAS local network. Setting up Reporting 1. Run the SQL Server setup file > Installation. Select New SQL Server stand alone installation or add features to an existing installation to launch the setup. The Setup Support Rules page will attempt to identify any issues during the SQL Server Setup Support Files installation. Upon completion, click Next to continue.

138 Enter product license key, click next and accept the license terms to continue to the Setup Role dialog. Next, select SQL Server Feature Installation and click next.

139 Next, enable the features listed below that are required for 2X RAS reporting and click next to continue: Database Engine Services Reporting Services Native Management Tools 2X RAS Reporting Services requires that the SQL server has been configured using a specific named instance. From the Instance Configuration page, select the option Named instance, input the information below and click next to continue: Named Instance: RASREPORTING Instance ID: RASREPORTING Without the named instance above, 2X Reporting setup will not complete.

140 Subsequently, the Disk Space Requirements and Server Configuration dialogs are shown. Confirm the information and click the next button to proceed. At the Database Engine Configuration window select Windows authentication mode and add the users below as SQL Server administrators: Systems Administrator AD Administrator System User

141 The next step introduces the Reporting Service Configuration that is used to by 2X RAS to generate reports. Select the Install and configure option click next to continue. From the Ready to install section, ensure that; Features to be installed include: Reporting Services Management Studio Tools Database Engine Instance Name MUST BE: RASREPORTING Once confirmed, click Install to proceed with the installation. Upon completion, proceed to the Verification process and port setup procedures.

142 Next, proceed to Verify that reporting services have been set up correctly. Open the Reporting Services Configuration Manager. Input the server name from the Report Server Instance dropdown, select RASREPORTING and click Connect. Verify that the Report Service Status = Started. Verify the Web Service URL is set to: ReportServer_RASREPORTING Next change the SQL Reporting Services default port to 8085 to avoid conflicts between 2X RAS gateways and SSRS (port 80). For further information, the step by step procedure is outlined in the following link ssrs default port/

143 2X RAS Reporting Setup At this stage you will proceed to install 2X RAS Reporting Services. Log in to the machine running MS SQL with an account that has administrative privileges (AD) and proceed to install 2X RAS reports. Download the latest version of the 2X RAS Reporting Service setup from the 2X Website. Double click 2XRASReporting.msi setup file to run the installation Wizard. Click Next when prompted. Review and approve the end user license agreement and click Next. Specify the folder location where 2X RAS will be installed, click Next and then Install to commit the config and initiate the installation.

144 You have successfully installed 2X RAS Reporting. Click Finish to complete the installation.

145 2X RAS Management Console Configuration Reports are generated from the 2X Remote Application Server Console. To generate reports 2X RAS must be configured to communicate with the reporting service. Configure reporting from the 2X Remote Application Server Console > Administration > Reporting. Click the Reporting Engine dropdown and select 2X Reporting. Server Specify the IP address of the machine hosting your SQL database that the Reporting service is installed on. If the database is located on the same machine you have installed 2X RAS on, you can also use localhost. Port Specify the port used to communicate with the 2X Reporting service. Prompt user for Login Details If selected, will prompt the user for AD credentials when generating reports. Use following credentials If selected, specify AD username and password to be used each time a report is generated. Subsequently click Test Connection to test the configuration and Apply to commit the configuration. NOTE: The default user for viewing reports is RASREPORTINGVIEW created during the installation process. Alternate users need to be configured in SSRS with browser permissions.

146 Viewing Reports After the configuration is complete and credentials are verified via the test button, switch to the 2X Reporting category to generate and view the reports. Note that the first time you view reports you may be requested to add RAS server domain/ IP address> as a trusted website. This will appear depending on the 2X RAS machine s Internet Explorer Enhanced Security Configuration settings.

147 Available Reports 2X RAS Reporting has 14 available reports to choose from. These reports can be exported and printed out. The reports are exported in the following formats. XML, CSV, PDF, MHTML, Excel, TIFF file and word. Users Reports Users Activity User Sessions Activity Devices Used by Users Client Operating Systems Used by Users Groups Reports Groups Activity Groups Sessions Activity Devices Used by Group Client Operating System Used by Group Devices Reports Devices Used Client Operating System Used 2X RDP Version Used Servers Reports Sessions Activity on Server Server Health by Server Application Reports Applications Usage

148 Licensing The licensing section will allow you to view licensing details and enter a license key. 2X Remote Application Server trial version has a 50 user 30 day trial period. After 30 days you will need to activate the product with a valid key or use the free key that allows for 3 connections. License Activation Fill in the required details in the License Activation dialog box and click the Activate button to activate your license key. When the license key is activated a dialog which states that the license key activated successfully will appear.

149 3rd Party SSL Certificates 3 rd Party Certificates used with 2X Secure Client Gateway can be installed with two different methods depending on the type of certificate purchased. Using Apache Certificates Converting IIS Certificates Using Apache Certificates 1. Go to the 2x console > Farm > Gateway > Properties> SSL/TLS tab 2. Choose your SSL settings choices SSL v3, etc. 3. Choose CSR 4. Fill in the data 5. Copy and paste the CSR into notepad and save the file for your records. 6. Paste the CSR into the Vendors Website page or it to the vendor. 7. Request a return Certificate in the following format: Apache, all in one single file (which has the private, public and intermediate CA all in one file), with the pem extension. 8. When you receive this file, place it in a secure folder for back up retrieval. 9. Click the Import Public Key button, and browse to this folder or a secondary location where you have a copy of the single all in one cert and insert this pem file into the Certificate key field. 10. Clicks apply and test. Note: The private key should already be populated from your initial CRS request. Converting IIS Certificates If the same Cert is used for IIS and the 2X RAS Portal then the IIS conversion method should be used. With an IIS cert install it in IIS, export a copy of the cert in pfx format then convert it to PEM file and place the single key generated in the Private Key and Public Key Field. One important note, the trusted.pem file on the 2X client side, must have the intermediate Certificate in its contents to be able to verify the cert from the third party vendor. If the Intermediate Certificate for the vendor is not in the trusted.pem file you will have to paste it in manually or create a trusted.pem template file with the proper Intermediate Certificates in its contents and then replace the old trusted.pem file with this newly updated one. This file resides in program files\2x or program files(x86)\2x on the client side. In order to use this certificate onto the 2X Client Gateway, we should convert the PFX file to the unencrypted PEM format. Use the open source utility OpenSSL to perform the conversion from PFX to PEM. You can download a Win32 distribution off: OpenSSL here: To convert a PFX file to a PEM file, follow these steps on a Windows machine: 1. Download and install the Win32 OpenSSL package from: 2. Create a folder c:\certs and copy the file cert.pfx into the c:\certs folder 3. Open a command prompt and change into the GnuWin32\bin directory: 4. cd %ProgramFiles%\GnuWin32\bin 5. Type the following command to convert the PFX file to an unencrypted PEM file: 6. Openssl pkcs in c:\certs\cert.pfx out c:\certs\cert.pem nodes 7. When prompted for the import password, enter the password you used when exporting the certificate to a PFX file. You should receive a message that says MAC verified OK. Enable SSL with cert.pem On the 2X Client Gateway page enable secure sockets layer (SSL) and click to browse for the pem file. Click Apply to apply the new settings. Your browser may not support display of this image. 2X Clients do not trust the Issuer Certificate Authority (Optional) This step is needed as the 2X Clients do not trust the Issuer Certificate Authority as they are not aware of it. Therefore we would need to extract the certificate out of the Certificate Authority and assign it to the 2X Remote Application Server Clients. 1. Using the certificate snap in find the certificate of the issuer* from the certificates console. *Issuer certificate is the certificate of the Certificate Authority that issued the certificate. 2. Right click on the issuer certificate, All tasks > Export 3. Choose No do not export the private key; as we only need the certificate 4. Then as a format we should choose Base 64 encoded X.509 (.CER) 5. Specify the file name that you want to export and save the certificate as 6. Click finish

150 7. Open the exported certificate with an editor such as notepad or WordPad and copy the contents to the clipboard. 2X Client Side 1. On the clients side under C:\Program Files\2X\Remote Application Server Client\ there should be a file called trusted.pem. This file contains the certificates of the common trusted authorities. 2. Paste the content of the exported certificate (attached to the list of the other certificates) This will add the certificate of the issuer with the list of trusted authorities on the client side and one would be able to connect over SSL with a certificate issued from an organization Certificate Authority.

151 2X RAS Portal The RAS Portal provides a mechanism to install the 2X Client to the user s computer with some of the configuration predefined using only a username and password. The RAS Portal can be setup to automatically install 2X Clients direct to the end user s computer, thus reducing the need for contact with system administrators. The 2X RAS Portal provides a web interface for users to access published resources from a 2X Remote Application Server. These published resources can be accessed from the LAN or WAN using an installed 2X Client on the end user s computer. The RAS Portal will check the computer for the 2X Client and if it isn t installed the RAS Portal will automatically install the 2X Client onto a workstation. 2X RAS Portal Pre Requisites When planning the 2X RAS Portal the following requirements should be taken into account: Server The 2X RAS Portal can be installed on the same machine as the 2X Remote Application Server or a different one. The following mandatory requirements must be in place for the server the 2X RAS Portal is installed: Windows Server 2003, 2008, 2008 R2, 2012, 2012 R2 Microsoft.NET Framework II/III IIS6, IIS7 or IIS8 NOTE: The 2X RAS Portal is designed to interface with a 2X Remote Application Server farm and is not designed for standalone use. Client Client Operating Systems and Browsers Supported IE v6/7/8 IE v9/10 Firefox 20 Opera 12 Chrome 26 Safari 3/4

152 Windows 2000, XP, Vista X N/A X X X X Windows 7/8 X X X X X N/A Mac N/A N/A X N/A N/A X Linux N/A N/A X X N/A N/A Automatic Client Detection and Installation Windows 2000, XP, Vista Windows 7/8 IE v6/7/8 IE v9/10 Firefox 20 Opera 12 Chrome 26 Safari 3/4 Active X or Java Enabled Active X or Java Enabled N/A Active X or Java Enabled Java Enabled Java Enabled Java Enabled Java Enabled Java Enabled Java Enabled Java Enabled Mac N/A N/A Java Enabled N/A N/A Java Enabled Linux N/A N/A N/A N/A N/A N/A N/A Before installing the 2X RAS Portal the prerequisites listed should be met. The 2X RAS Portal is designed to interface with an already existing 2X Remote Application Server farm but it does not need to be installed on the same server. It is important to note that IIS web should be installed on the same Windows Server that the 2X RAS Portal is installed. With the IIS web service installed and working the 2X RAS Portal can be installed and will be functional out of the box without further IIS configurations. Additional features such as SSL, changes to ports and/or specific permissions may require IIS configuration changes.

153 Network Planning The 2X RAS Portal can be installed on the same machine as 2X Remote Application Server or a separate server although the following considerations are required for the setup to work from a networking perspective. The installed 2X RAS Portal service must be able to directly access the 2X Secure Client Gateway and the Publishing Agent. The 2X Cloud end user clients must be able to access both the installed 2X RAS Portal page, and also be able to access the 2X Secure Client Gateway. The below diagram describes how the 2X RAS Portal issues a command to a locally installed 2X Cloud Agent to communicate with the 2X Remote Application Server Farm. IIS Roles Windows 2008 and later To install the IIS Role go to the Server Manager, and then add a new role. Select the IIS Role with default installation options. The following Web Server role services also need to be installed: ASP.NET plus dependencies To install IIS Web Server role services, open the server manager and highlight Web Server (IIS) under the Roles node.

154 Still within the server manager and with Web Server highlighted, click Add Role Services in the Role Services section.

155 In the add role services dialogue locate the required Role Services, and check them. Click Install to apply, and confirm any additional dependency roles if required. NOTE: Please note that IIS7 caches dynamic content as well as static content. To disable the caching for.aspx,.asmx and.ashx pages for the 2X RAS Portal directories with an asp.net page that depends on the session state. Please perform the following on the 2X Web Server, 2XWebPortal and 2XWebService. These are shown in the following screenshot.

156 Configuring IIS & Installing and Configuring 2X RAS Portal From the IIS console select the 2X Web Server and configure the following steps. If the port number for RAS Portal needs to be changed highlight 2X Web Server then select bindings to change the port. Installing and Configuring the 2X RAS Portal The 2X RAS Portal comes in 32bit and 64bit versions. There is no difference in the actual installation procedure of the 2X RAS Portal for the different versions. Use the following procedures for installing the RAS Portal: Download the latest version of the 2X RAS Portal installer from the 2X Website The installation documentation can be found at: The 2X RAS Portal is 81 by default. The port chosen must not conflict with any other products like the 2X HTML5 Gateway for example. Client When the 2X RAS Portal is installed users can access it directly by using the URL in a browser window, or by using the link if the 2X Remote Application Server is setup with HTTP Redirection in the Gateway properties.

157 On initial connection to the 2X RAS Portal webpage a check will be performed to verify the 2X Client is installed locally. A pop up will be shown within the web browser window similar to the below if the 2X Client needs installing on the local client machine. The client machine will prompt the user to download the client. The version of the 2X Client can be set manually on the RAS Portal. This will allow the Administrator to manually push the version of the 2X Client to users on Windows Desktop or Linux Desktop ONLY. The administrator can also have it download the latest 2X Client for Windows and Linux from 2X Directly. This setting can be found on the Administration Site of the 2X RAS Portal.

158 Note: The Windows Full Client install requires Admin Rights. The administrator can choose to upload the version a version on this screen for Windows and Linux Clients only. Note: The Basic Client Install has no admin right requirement. Note: 2X is contractually obligated to redirect all Apple and Android based devices to the respectful stores.

159 Configuring 2X RAS Portal No initial configurations are required in the 2X Remote Application Server console when interfacing with a 2X RAS Portal. The only change that may be desirable is apply a HTTP redirector onto the 2X Remote Application Server farm Gateway to forward any HTTP requests from it to the 2X RAS Portal. This can be set by opening the 2X Remote Application Server console interface, go to Farm > Gateways and gateway properties. In the Advanced tab apply the IP Address and port of the 2X RAS Portal which any forward requests to the 2X Secure Client Gateway. The 2X RAS Portal installs with an administration user interface. In order to setup the 2X RAS Portal so that end users can access published resource from a 2X Farm the farm should be added in the 2X Cloud Administration interface. The 2X Cloud Administration interface offers access to the following: Configuration of 2X Remote Application Server farms which end users can connect. System and Security Settings Customized 2X Cloud interface appearance Software Updates Farm Settings During initial installation a default farm connection is created which is set to connect to the local computer s hostname on TCP port 80. If a 2X Remote Application Server is installed on the same computer as the 2X RAS Portal, this initial default connection would immediately allow end user access to the farm via the 2X Cloud User Portal. If the initial 2X Cloud farm connection settings are not sufficient, these can be added in the Farm Settings. Enter the name of your 2X connection as it would be shown on the 2X RAS Portal web page and click Add Farm Click the newly created farm link and a new screen will show allowing entering the following 2X Secure Client Gateway details allowing you to edit the farm properties: Primary Hostname/IP Enter the hostname or IP Address that the 2X Remote Application Server secure gateway 2X Cloud service will use to connect. Secondary Hostname/IP If available, enter a backup hostname or IP Address of the 2X Remote Application Server secure gateway. Connection type Enter the connection type for the 2X RAS Portal service. This would be Direct Mode, meaning the 2X Cloud service needs direct network access to the 2X Remote Application Server gateways. SSL can optionally be specified. When multiple farms are added, all will be made available for login on the 2X Cloud User Login page.

160 Advanced Settings The Farm Settings advanced settings relate to configurations which are applied to the 2X Cloud Client (not the 2X RAS Portal Service itself). By default the 2X Client will use the same gateway credentials the 2X RAS Portal service is configured to use as in the previous Farm details settings. The following alternate settings specifically for the 2X RAS Portal Client can be applied: Override 2X Secure Client Gateway IP/Host Primary Hostname / IP Configure alternate gateway that the 2X Cloud Clients should use. Override 2X Secure Client Gateway IP/Host Secondary Hostname / IP Configure backup gateway that the 2X Cloud Clients should use. Override Gateway Port By default for non SSL connections to a 2X Remote Application Server Gateway this is port 80, if a different port is required it can be specified here. Override SSL Gateway Port By default for SSL encrypted connections to a 2X Remote Application Server Gateway this is port 443, if a different port is required it can be specified here. General Settings The 2X RAS Portal General Settings area allows general settings to be applied to the 2X RAS Portal service installation. This menu allows access to the following sub menu items: Logging The 2X RAS Portal can log all the changes made by the administrator or a user. The log can be cleared by clicking on Clear Log. 2X RAS Portal will compress the log file to a repository on a weekly basis. Click on Download repository to download the stored logs. System Settings This menu has access to Logon Settings, Security Settings and Client Installation Settings. The following settings can be applied from this area: Session Timeout (minutes) If a session is no longer responding or inactive, this setting can be applied to free the connection. This would guarantee no end users can indefinitely leave connections open taking up licenses. Show Public / Private Logon Options Desc Pending Enforce Security (HTTPS / SSL) Enforces 2X RAS Portal service communication and encryption at all times. Enforce Advanced Client Security 2X Cloud Clients acquire their settings at all times from the 2X Cloud service and do not store locally for higher security. Show Change Password option Allow 2X Cloud password changes Installation Mode Three install options exist when end users connect to the 2X RAS Portal. No Client Detection which would not offer a mechanism to automatically deploy the 2X Cloud Client, Install Client which prompts the user to install a client, and Install Client Silently which will silently deploy the 2X Cloud Client on the end users machine without need of interaction. The auto install only works with Windows Desktop OS versions. Installation Type There are three installation types for the 2X Cloud Client, Full Installation, Basic Installation and Basic Installation with Cleanup. A Full Installation option deploys the 2X Cloud Client which installs on the end user s computer. This full 2X Client installation is accessible from the start menu and can be used to add further connections. The basic client installation types offer a more cut down 2X Client which offers less end user functionality, ensuring that the 2X Cloud Client install is just for 2X Cloud Service usage only. Client Detection Failure Options Configurable behavior of what the end user experiences should the initial check for the installation of the 2X Cloud Client fails. Customized Appearance The 2X RAS Portal User login screen can be setup in such a way that the end user is presented with a custom form, which may include the active directory domain automatically filled in, a company logo and familiar name. Multiple 2X RAS Portal user login forms can be configured, and if multiple forms are configured they would be specifically accessed using a URL which is also confirmed within this menu section when a customized appearance template is created. The following options are made available to edit within a customized appearance template: Company ID This is a re confirmation of the initial name specified for the template. This is not changeable and is hence greyed out. Display Company Name: Specified company name for the template as specified in the user login page. Banner A custom banner can be used to display a company logo. Banners can be uploaded using the Browser button and should conform to standard web browser compatibility such as.gif format. Message A custom welcome display for the 2X Cloud user login page. URL A confirmation of what the access URL is for this specific 2X Cloud login template.

161 Default Domain If authentication for the 2X Remote Application Server farm requires the active directory domain to be specified in the login, the domain can be automatically prefixed here. Replication Settings 2X RAS Portal can be installed on more than one machine (e.g. High Availability with Multiple Gateways and 2X Web Access Portals or High Availability with a dual firewall DMZ), and it can be useful to keep the settings of each web portal exactly the same. Use the Replication Settings feature to avoid setting the same configuration for each web portal. Click here for examples of scenarios. Enter the server name and click on Add Server. Enter HostName/IP and Port (default 81) then click on Apply Settings. By default the Override Advanced Farm Settings? box is checked allowing you to replicate the advanced settings for each farm. Software Update To check for updates for the 2X RAS Portal automatically, select Check for updates when launching 2X RAS Portal Console. To manually check for updates click Check Now. About The version and build information for the 2X RAS Portal installation can be found by selecting About.

162 Using the 2X RAS Portal To access an installed 2X RAS Portal, the URL should be used as specified from the 2X RAS Portal Administrator page, in the template area. This URL would look like Login Screen During initial connection to the 2X RAS Portal web page the end user will get the following login screen: On the 2X RAS user login page are links to the 2X Console administrator and also links to non English language login form templates if required. A Farm drop down box will activate if multiple farm connections are configured in the 2X Administrative Console allowing the end user to choose the 2X Remote Application Server farm. Accessing Published Resources Once successfully logged in to the 2X RAS Portal, the end user can access 2X published resources made available from the 2X Remote Application Server. When the end user double clicks on a resource to access it, the 2X RAS Portal will issue a command to the locally installed 2X RAS Client to connect to the 2X Remote Application Server Gateway and access the published resource. Additional Options When an end user client is logged to the 2X RAS Portal as well as access published resources the end user has the following options: Change Password The end user can change the password used for login to the 2X RAS Portal. Logout The end user can log out, and access other farms if required. Connection Mode The end user can change the gateway connection mode if required. If the end user does not have direct access to the server from which the published resources are used, Regular Gateway should be used. Languages The end user can select from a range of different languages which the 2X RAS Portal can be implemented in.

163

164 HTML 5 Browser Settings Once the HTML 5 Gateway has been enabled and configured in the Gateway properties users can connect to the published items through an HTML 5 enabled browser. With the introduction of 2X RAS Version 14, 2X Universal Printing, Mail and URL redirection was added to the HTML5 Gateway. Note: SSL/TLS must be enabled to use the HTML 5 Gateway. A Default Connection is configured in the Gateway and can be modified in the Gateway properties under the HTML tab. Local drive redirection isn t supported on the 2X HTML5 Gateway. To connect to an HTML 5 Gateway use the following URL example: Choose your language Data Storage Connections and passwords are stored in plain text and are easily accessed by anyone using the same browser. When using a public computer it is recommended that your data is cleared upon closing the browser. This setting can be set within the Secure Client Gateway, under the HTML5 Gateway. Once the credentials are entered users have access to the published items.

165

166 Adding a Standard RDP Connection If users have been permitted through policy they can Add a Standard RDP Connection to a server or PC within the LAN where the 2X RAS Server is located. Simply right click on Standard RDP to add the connection. Users can also delete connections, refresh, change experience settings and color depth.

167

168 Adding a 2X Remote Application Server Connection If users have been permitted through policy they can Add a 2X Remote Application Server Connection to another 2X Remote Application Server. Simply right click on 2X RAS and add the 2X Remote Application Server Connection. Version 14 and higher has the 2X Universal Printer redirection as well as URL and Mail redirection.

169 2X Clients 2X Software has the following clients available. 2X Windows Client 2X Windows CE 2X Mac Client 2X ipad/iphone Client 2X Android Client 2X Chrome Client 2X Windows Phone 2X Linux Client The Windows and Linux clients can be downloaded from the following site. client/downloadlinks/ The Mac client, ipad/iphone client must be download from the Apple store. The Android and Chrome client can be downloaded from the Google Play store.

170 Installing and Configuring 2X Windows Client and RDP Connections There are multiple clients that can be used to connect to 2X Remote Application Server which can be downloaded at: client/downloadlinks/ Please ensure that the correct version is downloaded for the corresponding operating system. There are different versions for Windows and OS X depending on the Bit or version of the OS. Documentation for each client can be downloaded at: During the installation process for Windows clients a Single Sign On option can be select to utilize domain credentials used for PC logon as well as 2X. It can be change to the opposite state in the Options General settings in the client. To add a new 2X Connection or Remote Desktop Connection select File from the 2X Client menu. For a 2X Client Connection add the hostname or IP in the Primary Connection field.

171 Browsing to select the Primary Connection is also possible by selecting The Client Connection Mode s give administrators the choice to make connections with or without using SSL. They also provide for making direct connections to RDS servers after the initial connection is made through the gateway. In the Connection Mode field there are four types available: Gateway Mode : Clients are connected with the 2X Secure Client Gateway and the session connection is tunneled through the first available connection. This mode is ideal for servers which are only reachable via the gateway and do not require a high level of security. Gateway SSL Mode : Connection is made as in the regular gateway mode, but the connection is encrypted. Direct Mode: Clients first connect to the 2X Secure Client Gateway for the best available Server and then connect directly with that particular Server. This is best used when the client and the server are on the same network. Direct SSL Mode : This connection is created as in the Direct Mode option, but the connection to the 2X Secure Client Gateway is encrypted.

172 The Port number can be changed in the 2X Client but must also be changed in the Properties of the Gateway Agent under the Network or SSL tab depending on the Mode being used. Port 3389 is the default port for RDC connections. A Secondary Connection can be added as failover in the event the primary Gateway can be reached. As with the Primary Connection the hostname, IP must be entered or selected and the Mode must be chosen. An Alias name can be entered to help make identifying connections easier.

173 The Logon section of the 2X Client is used to enter and store user account information. Auto Logon can be selected to establish a connection to the Publishing agent when the user logs on to their computer. Save Password can be selected to retain the user s password between sessions. Single Sign On (SSO) can be selected to use the current domain credentials used to log on to the computer. This is used for domains that require users to change their password regularly and keeps the 2 X Client passwords current. Note that the credentials are greyed out. To configure the other features of the 2X Client a copy of the manual for the respective client can be downloaded at:

174 The 2X Client for Linux allows the same functionality provided by other 2X Clients, mainly connectivity to a 2X Farm or via RDP to a desktop. The 2X Client for Linux has been approved for the following 32bit Linux Distributions: Ubuntu OpenSuse Fedora Core Fedora 15 CentOS The 2X Client for Linux can be directly downloaded from the Ubuntu Directory, or else directly through the 2X Downloads page available from: client/downloadlinks/ Different packages for the 2X Client for Linux have been made available in different formats, mainly: 1..deb 2..rpm 3..tar.bz2 4. SSO bundled in the.deb package

175 Installing 2X Linux Client These different packages can be installed by executing the relevant installation procedures to the distros terminal. Installation Procedures (DEB Version) 1. Switch to the root user. 2. To install type: dpkg i 2XClient.deb 3. 2X Client for Linux binaries are now installed under: /opt/2x/client/bin 4. Run the following command to launch 2X Client: /opt/2x/client/bin/2xclient 5. You can also run the following commands to obtain a list of all usage parameters for 2X Client session: cd /opt/2x/client/bin./appserverclient? Installation Procedures (RPM Version) 1. Switch to the root user. 2. To install type: rpm ivh 2XClient.i386.rpm 3. 2X Client for Linux binaries are now installed under: /opt/2x/client/bin 4. Run the following command to launch 2X Client: /opt/2x/client/bin/2xclient 5. You can also run the following commands to obtain a list of all usage parameters for 2X Client session: cd /opt/2x/client/bin./appserverclient? Installation Procedures (.TAR.BZ2 Version) 1. Switch to the root user. 2. Switch to the root folder: cd/ 3. To install type: tar jxvf 2XClient.tar.bz2 4. 2X Client for Linux binaries are now installed under: /opt/2x/client/bin 5. Run the following command to launch 2X Client: /opt/2x/client/bin/2xclient 6. You can also run the following commands to obtain a list of all usage parameters for 2X Client session: cd /opt/2x/client/bin./appserverclient? SSO (Single Sign On) Installation Procedures 1. Install pam_2xclient.so module to have Single Sign On for 2X Client. 2. The module always returns true and will use an authentication token that will be provided by a higher authentication module. NOTE: When a higher authentication module has been configured to SUFFICIENT, it will return on success immediately and pam_2xclient.so won t be called. Please change SUFFICIENT TO REQUIRED. 3. To install 2X Client PAM module, add two lines to your session manage service (eg. /etc/pam d/gdm): auth optional pam_2xclient.so password optional pam_2xclient.so Module arguments: Debug: Debug trace will be written to /tmp/pam_2xclient.log. If the file cannot be opened, then syslog will be used. You can use debug argument with all module types. EG. Session optional pam_2xclient.so debug <service_list> The module will create an SSO cookie only for well known session services. You can change the list of services to allow: EG. auth optional pam_2xclient.so gdm kde kdm kde4 4. <service_list> The module will create an SSO cookie only for well known session services. 5. You can change the list of services to allow: EG. auth optional pam_2xclient.so gdm kde kdm kde4

176 Configuring 2X Linux Client Once the 2X Client for Linux is installed it s a matter of configuring the client so that it can connect to the proper resources. Just like the Windows client the 2X Client for Linux can connect to a 2X Farm or to a Terminal Server via the RDP Protocol. When adding a 2X Connection through File > Add New 2X Connection, the following details would be required: 1. Hostname / IP Address of the 2X Client Secure Gateway we are connecting to 2. Connection Mode 3. Port 4. Username 5. Password 6. Domain Likewise, when adding a new RDP connection through File > New Remote Desktop Connection, the following details would be required: 1. Hostname / IP Address of the machine we want to connect to 2. Port 3. Username 4. Password 5. Domain Adding a 2X Connection

177 Adding an RDP Connection In a nutshell, the 2X Client for Linux allows the users to Access Remote desktop and files. The ability to run remote applications seamlessly over a secure channel is also possible. Apart from this standard baseline functionality that the 2X Client provides, the Linux client also comes with a command line interface that can be access through the following command: Usage: /opt/2x/client/bin/appserverclient s Server u User [options] Some examples of possible commands can be found below: appserverclient s<server IP> a<"application Name"> u<user Name> appserverclient s a"internet Explorer" u Administrator The 2X Client for Linux Manual contains a comprehensive list of possible command line options available here: documentation/2x client linux/

178 Configuring Linux Peripherals The 2X Client for Linux allows the usage of the following local resources when logged on the remote computer: 1. Disk Drives 2. Printers 3. Serial Ports 4. Smart Cards. All of these options can be configured from the Local Resources Tab under the Connection Properties Under the same configuration pane, we are also able to configure whether sound redirection from the remote computer should be redirected to the client machine. Another possible option made available is the ability to apply windows key combinations for desktops that would make the usage of shortcuts such as alt + tab available. Redirection of local printers is also possible by configuring the printer in options dialog of the 2X Client for Linux. The user is expected to input the printer name as well as the driver to the printer list under the Printing options tab under the 2X Client for Linux Options.

Remote Application Server Version 14. Last updated: 25-02-15

Remote Application Server Version 14. Last updated: 25-02-15 Remote Application Server Version 14 Last updated: 25-02-15 Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise

More information

Remote Application Server Version 14. Last updated: 06-02-15

Remote Application Server Version 14. Last updated: 06-02-15 Remote Application Server Version 14 Last updated: 06-02-15 Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise

More information

2XApplication Server XG v10.1

2XApplication Server XG v10.1 2XApplication Server XG v10.1 Introduction 1 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein are

More information

2XApplication Server XG v10.6

2XApplication Server XG v10.6 2XApplication Server XG v10.6 Introduction 1 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein are

More information

Quick Start Guide for VMware and Windows 7

Quick Start Guide for VMware and Windows 7 PROPALMS VDI Version 2.1 Quick Start Guide for VMware and Windows 7 Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the

More information

Parallels Remote Application Server

Parallels Remote Application Server Parallels Remote Application Server Administrator's Guide v15 Copyright 1999-2016 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH Vordergasse 59 8200 Schaffhausen

More information

Quick Start Guide for Parallels Virtuozzo

Quick Start Guide for Parallels Virtuozzo PROPALMS VDI Version 2.1 Quick Start Guide for Parallels Virtuozzo Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the current

More information

2X ApplicationServer & LoadBalancer & VirtualDesktopServer Manual

2X ApplicationServer & LoadBalancer & VirtualDesktopServer Manual 2X ApplicationServer & LoadBalancer & VirtualDesktopServer Manual 2X VirtualDesktopServer Contents 1 2X VirtualDesktopServer Contents 2 URL: www.2x.com E-mail: info@2x.com Information in this document

More information

2X ApplicationServer & LoadBalancer Manual

2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Contents 1 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies,

More information

2X ApplicationServer & LoadBalancer Manual

2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Contents 1 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies,

More information

Setting up VMware ESXi for 2X VirtualDesktopServer Manual

Setting up VMware ESXi for 2X VirtualDesktopServer Manual Setting up VMware ESXi for 2X VirtualDesktopServer Manual URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples

More information

Thinspace deskcloud. Quick Start Guide

Thinspace deskcloud. Quick Start Guide Thinspace deskcloud Quick Start Guide Version 1.2 Published: SEP-2014 Updated: 16-SEP-2014 2014 Thinspace Technology Ltd. All rights reserved. The information contained in this document represents the

More information

2X ApplicationServer & LoadBalancer Manual

2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Manual 2X ApplicationServer & LoadBalancer Contents 1 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies,

More information

Accops HyWorks v2.5. Quick Start Guide. Last Update: 4/18/2016

Accops HyWorks v2.5. Quick Start Guide. Last Update: 4/18/2016 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

More information

Virtual Appliance Setup Guide

Virtual Appliance Setup Guide The Barracuda SSL VPN Vx Virtual Appliance includes the same powerful technology and simple Web based user interface found on the Barracuda SSL VPN hardware appliance. It is designed for easy deployment

More information

VMware Identity Manager Connector Installation and Configuration

VMware Identity Manager Connector Installation and Configuration VMware Identity Manager Connector Installation and Configuration VMware Identity Manager This document supports the version of each product listed and supports all subsequent versions until the document

More information

Setting up Hyper-V for 2X VirtualDesktopServer Manual

Setting up Hyper-V for 2X VirtualDesktopServer Manual Setting up Hyper-V for 2X VirtualDesktopServer Manual URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples

More information

PHD Virtual Backup for Hyper-V

PHD Virtual Backup for Hyper-V PHD Virtual Backup for Hyper-V version 7.0 Installation & Getting Started Guide Document Release Date: December 18, 2013 www.phdvirtual.com PHDVB v7 for Hyper-V Legal Notices PHD Virtual Backup for Hyper-V

More information

Release Version 3 The 2X Software Server Based Computing Guide

Release Version 3 The 2X Software Server Based Computing Guide Release Version 3 The 2X Software Server Based Computing Guide Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless

More information

Installing and Configuring vcenter Multi-Hypervisor Manager

Installing and Configuring vcenter Multi-Hypervisor Manager Installing and Configuring vcenter Multi-Hypervisor Manager vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.1 This document supports the version of each product listed and supports all subsequent

More information

2X SecureRemoteDesktop. Version 1.1

2X SecureRemoteDesktop. Version 1.1 2X SecureRemoteDesktop Version 1.1 Website: www.2x.com Email: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious

More information

Enterprise Manager. Version 6.2. Administrator s Guide

Enterprise Manager. Version 6.2. Administrator s Guide Enterprise Manager Version 6.2 Administrator s Guide Enterprise Manager 6.2 Administrator s Guide Document Number 680-017-017 Revision Date Description A August 2012 Initial release to support version

More information

Parallels Remote Application Server

Parallels Remote Application Server Parallels Remote Application Server Solutions Guide v15 Copyright 1999-2016 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH Vordergasse 59 8200 Schaffhausen

More information

Veeam Backup Enterprise Manager. Version 7.0

Veeam Backup Enterprise Manager. Version 7.0 Veeam Backup Enterprise Manager Version 7.0 User Guide August, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may

More information

Interworks. Interworks Cloud Platform Installation Guide

Interworks. Interworks Cloud Platform Installation Guide Interworks Interworks Cloud Platform Installation Guide Published: March, 2014 This document contains information proprietary to Interworks and its receipt or possession does not convey any rights to reproduce,

More information

Virtual Appliance Setup Guide

Virtual Appliance Setup Guide The Virtual Appliance includes the same powerful technology and simple Web based user interface found on the Barracuda Web Application Firewall hardware appliance. It is designed for easy deployment on

More information

Connection Broker Managing User Connections to Workstations, Blades, VDI, and More. Quick Start with Microsoft Hyper-V

Connection Broker Managing User Connections to Workstations, Blades, VDI, and More. Quick Start with Microsoft Hyper-V Connection Broker Managing User Connections to Workstations, Blades, VDI, and More Quick Start with Microsoft Hyper-V Version 8.1 October 21, 2015 Contacting Leostream Leostream Corporation http://www.leostream.com

More information

Storage Sync for Hyper-V. Installation Guide for Microsoft Hyper-V

Storage Sync for Hyper-V. Installation Guide for Microsoft Hyper-V Installation Guide for Microsoft Hyper-V Egnyte Inc. 1890 N. Shoreline Blvd. Mountain View, CA 94043, USA Phone: 877-7EGNYTE (877-734-6983) www.egnyte.com 2013 by Egnyte Inc. All rights reserved. Revised

More information

Proof of Concept Guide

Proof of Concept Guide Proof of Concept Guide Version 4.0 Published: OCT-2013 Updated: 2005-2013 Propalms Ltd. All rights reserved. The information contained in this document represents the current view of Propalms Ltd. on the

More information

Setting up Citrix XenServer for 2X VirtualDesktopServer Manual

Setting up Citrix XenServer for 2X VirtualDesktopServer Manual Setting up Citrix XenServer for 2X VirtualDesktopServer Manual URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples

More information

Release Version 4.1 The 2X Software Server Based Computing Guide

Release Version 4.1 The 2X Software Server Based Computing Guide Release Version 4.1 The 2X Software Server Based Computing Guide Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless

More information

WhatsUp Gold v16.3 Installation and Configuration Guide

WhatsUp Gold v16.3 Installation and Configuration Guide WhatsUp Gold v16.3 Installation and Configuration Guide Contents Installing and Configuring WhatsUp Gold using WhatsUp Setup Installation Overview... 1 Overview... 1 Security considerations... 2 Standard

More information

2X Cloud Portal v10.5

2X Cloud Portal v10.5 2X Cloud Portal v10.5 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise

More information

LifeCyclePlus Version 1

LifeCyclePlus Version 1 LifeCyclePlus Version 1 Last updated: 2014-04-25 Information in this document is subject to change without notice. Companies, names and data used in examples herein are fictitious unless otherwise noted.

More information

Propalms TSE Deployment Guide

Propalms TSE Deployment Guide Propalms TSE Deployment Guide Version 7.0 Propalms Ltd. Published October 2013 Overview This guide provides instructions for deploying Propalms TSE in a production environment running Windows Server 2003,

More information

Core Protection for Virtual Machines 1

Core Protection for Virtual Machines 1 Core Protection for Virtual Machines 1 Comprehensive Threat Protection for Virtual Environments. Installation Guide e Endpoint Security Trend Micro Incorporated reserves the right to make changes to this

More information

Interact Intranet Version 7. Technical Requirements. August 2014. 2014 Interact

Interact Intranet Version 7. Technical Requirements. August 2014. 2014 Interact Interact Intranet Version 7 Technical Requirements August 2014 2014 Interact Definitions... 3 Licenses... 3 On-Premise... 3 Cloud... 3 Pulic Cloud... 3 Private Cloud... 3 Perpetual... 3 Self-Hosted...

More information

System Administration Training Guide. S100 Installation and Site Management

System Administration Training Guide. S100 Installation and Site Management System Administration Training Guide S100 Installation and Site Management Table of contents System Requirements for Acumatica ERP 4.2... 5 Learning Objects:... 5 Web Browser... 5 Server Software... 5

More information

ArCycle vmbackup. for VMware/Hyper-V. User Guide

ArCycle vmbackup. for VMware/Hyper-V. User Guide ArCycle vmbackup for VMware/Hyper-V User Guide 2 Copyright Copyright ArCycle Software, Ltd., 2011-2014. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system,

More information

Virtual Appliance Setup Guide

Virtual Appliance Setup Guide Virtual Appliance Setup Guide 2015 Bomgar Corporation. All rights reserved worldwide. BOMGAR and the BOMGAR logo are trademarks of Bomgar Corporation; other trademarks shown are the property of their respective

More information

Installing and Configuring vcenter Support Assistant

Installing and Configuring vcenter Support Assistant Installing and Configuring vcenter Support Assistant vcenter Support Assistant 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.0.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

Mobile Device Management Version 8. Last updated: 17-10-14

Mobile Device Management Version 8. Last updated: 17-10-14 Mobile Device Management Version 8 Last updated: 17-10-14 Copyright 2013, 2X Ltd. http://www.2x.com E mail: info@2x.com Information in this document is subject to change without notice. Companies names

More information

Setting up Hyper-V for 2X VirtualDesktopServer Manual

Setting up Hyper-V for 2X VirtualDesktopServer Manual Setting up Hyper-V for 2X VirtualDesktopServer Manual URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein

More information

Product Manual. MDM On Premise Installation Version 8.1. Last Updated: 06/07/15

Product Manual. MDM On Premise Installation Version 8.1. Last Updated: 06/07/15 Product Manual MDM On Premise Installation Version 8.1 Last Updated: 06/07/15 Parallels IP Holdings GmbH Vordergasse 59 8200 Schaffhausen Switzerland Tel: + 41 52 632 0411 Fax: + 41 52 672 2010 www.parallels.com

More information

DameWare Server. Administrator Guide

DameWare Server. Administrator Guide DameWare Server Administrator Guide About DameWare Contact Information Team Contact Information Sales 1.866.270.1449 General Support Technical Support Customer Service User Forums http://www.dameware.com/customers.aspx

More information

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11.

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11. Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures Goliath Performance Monitor Installation Guide v11.6 (v11.6) Document Date: August 2015 www.goliathtechnologies.com

More information

RingStor User Manual. Version 2.1 Last Update on September 17th, 2015. RingStor, Inc. 197 Route 18 South, Ste 3000 East Brunswick, NJ 08816.

RingStor User Manual. Version 2.1 Last Update on September 17th, 2015. RingStor, Inc. 197 Route 18 South, Ste 3000 East Brunswick, NJ 08816. RingStor User Manual Version 2.1 Last Update on September 17th, 2015 RingStor, Inc. 197 Route 18 South, Ste 3000 East Brunswick, NJ 08816 Page 1 Table of Contents 1 Overview... 5 1.1 RingStor Data Protection...

More information

StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with Hyper-V Cluster

StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with Hyper-V Cluster #1 HyperConverged Appliance for SMB and ROBO StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with MARCH 2015 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

NSi Mobile Installation Guide. Version 6.2

NSi Mobile Installation Guide. Version 6.2 NSi Mobile Installation Guide Version 6.2 Revision History Version Date 1.0 October 2, 2012 2.0 September 18, 2013 2 CONTENTS TABLE OF CONTENTS PREFACE... 5 Purpose of this Document... 5 Version Compatibility...

More information

Windows Server 2012 2,500-user pooled VDI deployment guide

Windows Server 2012 2,500-user pooled VDI deployment guide Windows Server 2012 2,500-user pooled VDI deployment guide Microsoft Corporation Published: August 2013 Abstract Microsoft Virtual Desktop Infrastructure (VDI) is a centralized desktop delivery solution

More information

Desktop Surveillance Help

Desktop Surveillance Help Desktop Surveillance Help Table of Contents About... 9 What s New... 10 System Requirements... 11 Updating from Desktop Surveillance 2.6 to Desktop Surveillance 3.2... 13 Program Structure... 14 Getting

More information

F-Secure Internet Gatekeeper Virtual Appliance

F-Secure Internet Gatekeeper Virtual Appliance F-Secure Internet Gatekeeper Virtual Appliance F-Secure Internet Gatekeeper Virtual Appliance TOC 2 Contents Chapter 1: Welcome to F-Secure Internet Gatekeeper Virtual Appliance.3 Chapter 2: Deployment...4

More information

VMware/Hyper-V Backup Plug-in User Guide

VMware/Hyper-V Backup Plug-in User Guide VMware/Hyper-V Backup Plug-in User Guide COPYRIGHT No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying,

More information

Rally Installation Guide

Rally Installation Guide Rally Installation Guide Rally On-Premises release 2015.1 rallysupport@rallydev.com www.rallydev.com Version 2015.1 Table of Contents Overview... 3 Server requirements... 3 Browser requirements... 3 Access

More information

Enterprise Solution for Remote Desktop Services... 2. System Administration... 3. Server Management... 4. Server Management (Continued)...

Enterprise Solution for Remote Desktop Services... 2. System Administration... 3. Server Management... 4. Server Management (Continued)... CONTENTS Enterprise Solution for Remote Desktop Services... 2 System Administration... 3 Server Management... 4 Server Management (Continued)... 5 Application Management... 6 Application Management (Continued)...

More information

Citrix Access on SonicWALL SSL VPN

Citrix Access on SonicWALL SSL VPN Citrix Access on SonicWALL SSL VPN Document Scope This document describes how to configure and use Citrix bookmarks to access Citrix through SonicWALL SSL VPN 5.0. It also includes information about configuring

More information

DOCSVAULT Document Management System for everyone

DOCSVAULT Document Management System for everyone Installation Guide DOCSVAULT Document Management System for everyone 9 v Desktop and Web Client v On Premises Solution v Intelligent Data Capture v Email Automation v Workflow & Record Retention Installing

More information

Enterprise Manager. Version 6.2. Installation Guide

Enterprise Manager. Version 6.2. Installation Guide Enterprise Manager Version 6.2 Installation Guide Enterprise Manager 6.2 Installation Guide Document Number 680-028-014 Revision Date Description A August 2012 Initial release to support version 6.2.1

More information

F-Secure Messaging Security Gateway. Deployment Guide

F-Secure Messaging Security Gateway. Deployment Guide F-Secure Messaging Security Gateway Deployment Guide TOC F-Secure Messaging Security Gateway Contents Chapter 1: Deploying F-Secure Messaging Security Gateway...3 1.1 The typical product deployment model...4

More information

Dell SonicWALL SRA 7.5 Citrix Access

Dell SonicWALL SRA 7.5 Citrix Access Dell SonicWALL SRA 7.5 Citrix Access Document Scope This document describes how to configure and use Citrix bookmarks to access Citrix through Dell SonicWALL SRA 7.5. It also includes information about

More information

CTERA Agent for Linux

CTERA Agent for Linux User Guide CTERA Agent for Linux September 2013 Version 4.0 Copyright 2009-2013 CTERA Networks Ltd. All rights reserved. No part of this document may be reproduced in any form or by any means without written

More information

The SSL device also supports the 64-bit Internet Explorer with new ActiveX loaders for Assessment, Abolishment, and the Access Client.

The SSL device also supports the 64-bit Internet Explorer with new ActiveX loaders for Assessment, Abolishment, and the Access Client. WatchGuard SSL v3.2 Release Notes Supported Devices SSL 100 and 560 WatchGuard SSL OS Build 355419 Revision Date January 28, 2013 Introduction WatchGuard is pleased to announce the release of WatchGuard

More information

Avalanche Site Edition

Avalanche Site Edition Avalanche Site Edition Version 4.8 avse ug 48 20090325 Revised 03/20/2009 ii Copyright 2008 by Wavelink Corporation All rights reserved. Wavelink Corporation 6985 South Union Park Avenue, Suite 335 Midvale,

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

Quick Start Guide For Ipswitch Failover v9.0

Quick Start Guide For Ipswitch Failover v9.0 For Ipswitch Failover v9.0 Copyright 1991-2015 All rights reserved. This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with

More information

Kaspersky Lab Mobile Device Management Deployment Guide

Kaspersky Lab Mobile Device Management Deployment Guide Kaspersky Lab Mobile Device Management Deployment Guide Introduction With the release of Kaspersky Security Center 10.0 a new functionality has been implemented which allows centralized management of mobile

More information

Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010

Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010 Setting Up a Unisphere Management Station for the VNX Series P/N 300-011-796 Revision A01 January 5, 2010 This document describes the different types of Unisphere management stations and tells how to install

More information

Setting up VMware Server v1 for 2X VirtualDesktopServer Manual

Setting up VMware Server v1 for 2X VirtualDesktopServer Manual Setting up VMware Server v1 for 2X VirtualDesktopServer Manual URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples

More information

Installation Guide for Pulse on Windows Server 2008R2

Installation Guide for Pulse on Windows Server 2008R2 MadCap Software Installation Guide for Pulse on Windows Server 2008R2 Pulse Copyright 2014 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software

More information

Getting Started with ESXi Embedded

Getting Started with ESXi Embedded ESXi 4.1 Embedded vcenter Server 4.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent

More information

Ensure that the server where you install the Primary Server software meets the following requirements: Item Requirements Additional Details

Ensure that the server where you install the Primary Server software meets the following requirements: Item Requirements Additional Details ZENworks 11 SP3 System December 2014 The following sections provide the Novell ZENworks 11 SP3 requirements for hardware and software: Section 1, Primary Server, on page 1 Section 2, Managed Device, on

More information

PROPALMS VDI. Version 2.1. Administrators Guide. Rev. 2.1.5

PROPALMS VDI. Version 2.1. Administrators Guide. Rev. 2.1.5 PROPALMS VDI Version 2.1 Administrators Guide Rev. 2.1.5 Published: JUNE 2012 1999-2012 Propalms Ltd. All rights reserved. The information contained in this document represents the current view of Propalms

More information

Cyberoam Virtual Security Appliance - Installation Guide for VMware ESX/ESXi. Version 10

Cyberoam Virtual Security Appliance - Installation Guide for VMware ESX/ESXi. Version 10 Cyberoam Virtual Security Appliance - Installation Guide for VMware ESX/ESXi Version 10 Document Version 10.6.2-16/04/2015 Contents Preface... 4 Base Configuration... 4 Installation Procedure... 4 Cyberoam

More information

Why Migrate from Citrix to Parallels?

Why Migrate from Citrix to Parallels? Why Migrate from Citrix to Parallels? On 3 March 2015, Citrix reviewed the lifecycle of XenApp and Presentation Server, confirming that the end of extended support for Windows Server 2003 will be on 24

More information

Virtual Web Appliance Setup Guide

Virtual Web Appliance Setup Guide Virtual Web Appliance Setup Guide 2 Sophos Installing a Virtual Appliance Installing a Virtual Appliance This guide describes the procedures for installing a Virtual Web Appliance. If you are installing

More information

Sophos Mobile Control Installation guide. Product version: 3

Sophos Mobile Control Installation guide. Product version: 3 Sophos Mobile Control Installation guide Product version: 3 Document date: January 2013 Contents 1 Introduction...3 2 The Sophos Mobile Control server...4 3 Set up Sophos Mobile Control...16 4 External

More information

Networking Best Practices Guide. Version 6.5

Networking Best Practices Guide. Version 6.5 Networking Best Practices Guide Version 6.5 Summer 2010 Copyright: 2010, CCH, a Wolters Kluwer business. All rights reserved. Material in this publication may not be reproduced or transmitted in any form

More information

BlackBerry Enterprise Service 10. Version: 10.2. Configuration Guide

BlackBerry Enterprise Service 10. Version: 10.2. Configuration Guide BlackBerry Enterprise Service 10 Version: 10.2 Configuration Guide Published: 2015-02-27 SWD-20150227164548686 Contents 1 Introduction...7 About this guide...8 What is BlackBerry Enterprise Service 10?...9

More information

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11.

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11. Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures Goliath Performance Monitor Installation Guide v11.6 (v11.6) Document Date: June 2016 www.goliathtechnologies.com

More information

Parallels Remote Application Server

Parallels Remote Application Server Parallels Remote Application Server Parallels Client for Chrome User's Guide v15 Copyright 1999-2016 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH Vordergasse

More information

Table of Contents. FleetSoft Installation Guide

Table of Contents. FleetSoft Installation Guide FleetSoft Installation Guide Table of Contents FleetSoft Installation Guide... 1 Minimum System Requirements... 2 Installation Notes... 3 Frequently Asked Questions... 4 Deployment Overview... 6 Automating

More information

Installation Guide for Pulse on Windows Server 2012

Installation Guide for Pulse on Windows Server 2012 MadCap Software Installation Guide for Pulse on Windows Server 2012 Pulse Copyright 2014 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software

More information

2X HTML5 Gateway v10.6

2X HTML5 Gateway v10.6 2X HTML5 Gateway v10.6 URL: www.2x.com E-mail: info@2x.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise

More information

IT-ADVENTURES PLAYGROUND (ISERINK) Remote Setup Guide IOWA STATE UNIVERSITY INFORMATION ASSURANCE CENTER

IT-ADVENTURES PLAYGROUND (ISERINK) Remote Setup Guide IOWA STATE UNIVERSITY INFORMATION ASSURANCE CENTER IT-ADVENTURES PLAYGROUND (ISERINK) Remote Setup Guide IOWA STATE UNIVERSITY INFORMATION ASSURANCE CENTER Spring 2014 Gaining access to your systems Since ISERink runs on a simulated internet provided by

More information

Synchronizer Installation

Synchronizer Installation Synchronizer Installation Synchronizer Installation Synchronizer Installation This document provides instructions for installing Synchronizer. Synchronizer performs all the administrative tasks for XenClient

More information

WW HMI SCADA-08 Remote Desktop Services Best Practices

WW HMI SCADA-08 Remote Desktop Services Best Practices Slide 1 WW HMI SCADA-08 Remote Desktop Services Best Practices Steven L. Weygandt Portfolio Product Manager - Device Integration /Wonderware social.invensys.com @InvensysOpsMgmt / #SoftwareRevolution /InvensysVideos

More information

VMware vsphere-6.0 Administration Training

VMware vsphere-6.0 Administration Training VMware vsphere-6.0 Administration Training Course Course Duration : 20 Days Class Duration : 3 hours per day (Including LAB Practical) Classroom Fee = 20,000 INR Online / Fast-Track Fee = 25,000 INR Fast

More information

GRAVITYZONE HERE. Deployment Guide VLE Environment

GRAVITYZONE HERE. Deployment Guide VLE Environment GRAVITYZONE HERE Deployment Guide VLE Environment LEGAL NOTICE All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including

More information

vcenter Operations Manager for Horizon Supplement

vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon 1.6 This document supports the version of each product listed and supports all subsequent versions until the document

More information

Unitrends Virtual Backup Installation Guide Version 8.0

Unitrends Virtual Backup Installation Guide Version 8.0 Unitrends Virtual Backup Installation Guide Version 8.0 Release June 2014 7 Technology Circle, Suite 100 Columbia, SC 29203 Phone: 803.454.0300 Contents Chapter 1 Getting Started... 1 Version 8 Architecture...

More information

Veeam Cloud Connect. Version 8.0. Administrator Guide

Veeam Cloud Connect. Version 8.0. Administrator Guide Veeam Cloud Connect Version 8.0 Administrator Guide April, 2015 2015 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may be

More information

AVG 8.5 Anti-Virus Network Edition

AVG 8.5 Anti-Virus Network Edition AVG 8.5 Anti-Virus Network Edition User Manual Document revision 85.2 (23. 4. 2009) Copyright AVG Technologies CZ, s.r.o. All rights reserved. All other trademarks are the property of their respective

More information

XenClient Enterprise Synchronizer Installation Guide

XenClient Enterprise Synchronizer Installation Guide XenClient Enterprise Synchronizer Installation Guide Version 5.1.0 March 26, 2014 Table of Contents About this Guide...3 Hardware, Software and Browser Requirements...3 BIOS Settings...4 Adding Hyper-V

More information

Sophos for Microsoft SharePoint startup guide

Sophos for Microsoft SharePoint startup guide Sophos for Microsoft SharePoint startup guide Product version: 2.0 Document date: March 2011 Contents 1 About this guide...3 2 About Sophos for Microsoft SharePoint...3 3 System requirements...3 4 Planning

More information

VEEAM ONE 8 RELEASE NOTES

VEEAM ONE 8 RELEASE NOTES VEEAM ONE 8 RELEASE NOTES This Release Notes document provides last-minute information about Veeam ONE 8 Update 2, including system requirements, installation instructions as well as relevant information

More information

Installing and Using the vnios Trial

Installing and Using the vnios Trial Installing and Using the vnios Trial The vnios Trial is a software package designed for efficient evaluation of the Infoblox vnios appliance platform. Providing the complete suite of DNS, DHCP and IPAM

More information

VMware vcenter Log Insight Getting Started Guide

VMware vcenter Log Insight Getting Started Guide VMware vcenter Log Insight Getting Started Guide vcenter Log Insight 1.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by

More information

User Guide for VMware Adapter for SAP LVM VERSION 1.2

User Guide for VMware Adapter for SAP LVM VERSION 1.2 User Guide for VMware Adapter for SAP LVM VERSION 1.2 Table of Contents Introduction to VMware Adapter for SAP LVM... 3 Product Description... 3 Executive Summary... 3 Target Audience... 3 Prerequisites...

More information