Remote desktop configuration

Transcription

1 Remote desktop configuration User manual CoreStation and DXM Series Blades HB-CONF-0001 Revision 1.1 April 2019

2 Product Information CAUTION To prevent damage to the DXM Series Blades: install in accordance with these instructions; always turn off and unplug the host computer before handling the unit; always use appropriate anti-static handling procedures when handling the unit; only use attachments and accessories approved by Amulet Hotkey; do not expose the unit to moisture; do not place objects filled with liquids on or near the unit; clean the unit only with a dry cloth; refer all servicing to qualified personnel. LASER SAFETY The CoreStation and DXM Series Blades may be fitted with SFP network modules that contain Class 1 lasers. The SFP module emits invisible radiation which can cause harm if installed or serviced incorrectly. Follow the guidelines below: Warning: Class 1 laser product. Warning: Invisible laser radiation can be emitted from the aperture of the SFP port when no fibre is connected. To avoid exposure to laser radiation, do not stare into open apertures. Warning: Only trained and qualified personnel may install, replace, or service this equipment. Thank you Thank you from everyone at Amulet Hotkey for purchasing this product. Much time and energy has gone into making this the best and most reliable solution available. We are confident we have provided a state-of-the-art unit that will provide you with long and reliable service regardless of the application. To get the best from this product, follow this manual carefully. Shipment and product inspection Your product was carefully packed prior to despatch to guarantee safe transit. Make sure you thoroughly examine all packaging and contents for signs of physical damage before use. If any damage has occurred, notify the shipping company and your supplier immediately. Otherwise, claims for damage or replacement may not be granted. Retain the original packaging for use in the event that the equipment has to be stored, shipped or returned for service. If you choose to dispose of the packaging, please do so in an environmentally friendly fashion. Technical support If you have further questions, do not hesitate to contact Amulet Hotkey technical support for expert assistance: EMEA +44 (0) eurosupport@amulethotkey.com N America +1 (212) ussupport@amulethotkey.com South America latamsupport@amulethotkey.com Asia Pacific apsupport@amulethotkey.com Or look at the resources page on our website: Amulet Hotkey Ltd. All rights reserved. The information contained in this document represents the current view of Amulet Hotkey as of the date of publication. Because Amulet Hotkey must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Amulet Hotkey, and Amulet Hotkey cannot guarantee the accuracy of any information presented after the date of publication. Sections of this document are reproduced with the kind permission of Teradici Corp. This document is for informational purposes only. Amulet Hotkey make no warranties, express, implied or statutory, as to the information in this document. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without express written permission from Amulet Hotkey. Amulet Hotkey may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Amulet Hotkey, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Teradici, PC-over-IP, and PCoIP are registered trademarks of Teradici Corporation. VMware and View are registered trademarks of VMware Corp. Amulet Hotkey and solutions you can bank on are trademarks of Amulet Hotkey Ltd. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Page 2

3 Remote desktop configuration FCC Notice This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Title 47, Part 15 (47 CFR 15) of the Federal Communications Commission (FCC) Rules and Regulations establishes Radio Frequency (RF) emission limits for unlicensed emissions to provide an interference-free radio frequency spectrum. Many electronic devices, including computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules. These rules place computers and related peripheral devices into two classes, A and B, depending upon their intended installation. Class A devices are those that may reasonably be expected to be installed in a business or commercial environment. Class B devices are those that may reasonably be expected to be installed in a residential environment (personal computers, for example). The FCC requires devices in both classes to bear a label indicating the interference potential of the device as well as additional operating instructions for the user. A label on the device shows which class (A or B) the equipment falls into. Class B devices have an FCC logo or FCC ID on the label. Class A devices do not have an FCC logo or FCC ID on the label. The DXM Series Blades has been tested and found to comply with the limits for a Class A digital device, as defined by Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at their own expense. EU Notice This product complies with EMC Directive 2014/30/EU and the Low Voltage Directive 2014/35/EU. Conformity is shown by compliance with the applicable requirements of the following documents: EN (CISPR 32) (Class A) - Emissions EN (IEC ,3,4,5,6,8,11) - Immunity EN (IEC ) - Power Line Harmonics EN (IEC ) - Power Line Flicker EN (IEC 60950) - Product Safety! Caution: This equipment is compliant with Class A of CISPR 32. In a residential environment this equipment may cause radio interference.! Caution: The CE/EMC compliance is tested with video, USB and audio cables that are no longer than 3 m long. Page 3

4 Product Information Contents 1. Introduction What is PCoIP? About PCoIP hosts DXM Series Blades models Solutions with 14G PowerEdge Blades Solutions with 13G PowerEdge Blades Solutions with 12G PowerEdge Blades Typical configuration Overview Initial preparations Identify the correct Fabric Obtain the MAC address Obtain the latest firmware Change the host card default IP address Set up the blade for one host card Set up an FC640 blade for one host card Assignment of blades to PCIe slots STEP 1: Power up the blade STEP 2: Log in to the CMC STEP 3: Check blade health STEP 4: Set BIOS settings through the idrac STEP 5: Obtain the IP address for the host card STEP 6: Log in to the host card STEP 6: Check the firmware of the host card STEP 7: Set up the zero client STEP 8: Download drivers How to set up a FC640 blade for VDI STEP 1: Power up the blade STEP 3: Log in to the CMC STEP 4: Check blade health STEP 5: Obtain the IP address for the host card STEP 6: Log in to the host card STEP 7: Check the firmware of the host card STEP 8: Set up the zero client STEP 9: Download drivers Page 4

5 Remote desktop configuration 6. Set up the blade for two host cards STEP 1: Power up the blade STEP 3: Log in to the CMC STEP 4: Check blade health STEP 5: Obtain both host card IP addresses STEP 6: Log in to the primary host card STEP 7: Check the firmware of the host card STEP 8: Configure the secondaray host card STEP 9: Disable audio on the second host card STEP 10: Set up the zero clients STEP 11: Connect zero clients to the blade Select PCoIP session type Connect zero clients to the blade STEP 12: Download and install drivers Set up a PCoIP session Power up the zero client Set the PCoIP session type Auto Detect Connect directly to a specified host Connect to a choice of hosts using SLP Discovery PCoIP Connection Manager PCoIP Connection Manager + Auto-Logon Connect using VMware View Connect with View Connection Server and Auto-Logon Connect using a connection broker Set an automatic connection Disconnect from a host PC or virtual desktop Choose a connection broker if required Role of the connection broker Specify the connection broker Using the connection broker Page 5

6 Contents 8. Additional information Update the Teradici firmware Set up a zero client for an automatic connection Record host card details before installation Use DHCP to simplify installation Additional administrative tasks Disconnect from a host PC or virtual desktop Further information Available supported configurations M1000e Chassis solutions FX2s Chassis solutions...36 Page 6

7 Remote desktop configuration List of figures Figure 1:.1. Host card in correct slot for Fabric B. 2. Host card in correct slot for Fabric C...13 Figure 2:.Fabric connections map...13 Figure 3:.Power button on the front of a PowerEdge blade...15 Figure 4:.LCD module on the M1000e chassis...15 Figure 5:.CMC login screen Figure 6:.Blade Properties window...16 Figure 7:.DXM-PCoIP-Series-DXM-13-X installed...16 Figure 8:.Example DHCP command window...16 Figure 9:.Alert window Figure 10:.Add Exception window...17 Figure 11:.Confirm Security Exception window...17 Figure 12:.FX2s mapping between modules and blades...19 Figure 13:.Power button on the front of a PowerEdge blade...19 Figure 14:.CMC login screen Figure 15:.Blade Properties window...20 Figure 16:.Check health of PCIe slots...20 Figure 17:.System BIOS settings...20 Figure 19:.Alert window...20 Figure 20:.Add Exception window...20 Figure 18:.Example DHCP command window...21 Figure 21:.Confirm Security Exception window...21 Figure 22:.Power button on the front of a PowerEdge blade...25 Figure 23:.LCD module on the M1000e chassis...25 Figure 24:.CMC login screen Page 7

8 Contents Figure 25:.Blade Properties window...26 Figure 26:.Two DXM-PCoIP-Series-DXM-13-X installed...26 Figure 27:.Example DHCP command window...26 Figure 28:.Alert window...27 Figure 29:.Add Exception window...27 Figure 30:.Confirm Security Exception window...27 Figure 31:.Connect the keyboard and mouse and optional headset...28 Figure 32:.Connect up to eight monitors...28 Figure 33:.PCoIP connection with daisy chain...29 Figure 34:.PCoIP connection with daisy chain...29 Figure 35:.Connect the Power Supply Units (PSUs)...29 Figure 36:.Zero client On Screen Display...30 Figure 37:.Connection Type drop down list...30 Figure 38:.Direct to Host connection screen...30 Figure 39:.Session selection drop down list...31 Figure 40:.Direct to Host connection type...31 Figure 41:.The zero client OSD discovers and lists the first 10 available PCoIP hosts discovered...32 Figure 42:.View Connection Server selection...32 Figure 43:.Connection Management Interface selection...32 Figure 44:.OSD Automatic connection screen...33 Figure 45:.Disconnect option on the OSD...33 Figure 46:.Firmware Upload window...35 Figure 47:.Successful upload window...35 Figure 48:.OSD Automatic connection screen...35 Figure 49:.Disconnect option on the OSD...36 Page 8

9 Remote desktop configuration List of tables Table 1:.Common configurations for DXM Series Blades...11 Table 2:.List of monitor configurations...28 Table 3:.M1000e chassis solutions and MXM cards...36 Table 4:.FX2s chassis solutions and host cards Page 9

10 Contents Page 10

11 Introduction 1 1. Introduction This manual is for the Amulet Hotkey CoreStation and DXM Series Blades. These Amulet Hotkey solutions are based on the Dell PowerEdge Blade range. 1.1 What is PCoIP? The PCoIP (PC-over-IP) protocol compresses, encrypts and encodes the entire computing experience on a host PC. In a PCoIP system, a PCoIP host transmits the computing experience from a host PC (pixels only) across a standard IP network to a remote zero client. Actual data never leaves the host PC and all pixel transfers are encrypted with advanced security algorithms. PCoIP supports high resolution, full frame rate 3D graphics and HD media, multiple large displays, full USB peripheral connectivity, and high definition audio, all connected over the corporate LAN or WAN. PCoIP technology allows all desktops in your enterprise to be centrally located and managed in a data centre, while providing remote users with full desktop performance. This may be in a geographically remote location if necessary. 1.2 About PCoIP hosts A PCoIP host is something that converts a remote blade workstation (or PC) into a pixel broadcast centre. The host s Tera-series processor uses advanced algorithms to encode a user s full desktop environment, allowing the host to deliver high-end images to a zero client in any location. In a PCoIP system, the PCoIP host is installed inside or near to the remote blade or PC. The host takes digital video, audio and USB data generated by the PC and compresses and encrypts this data. It then transmits this data in real time over an IP network to the user s PCoIP zero client. 1.3 DXM Series Blades models The DXM Series Blades are Dell PowerEdge Blades housed in a chassis that has its own power supply and cooling system. Typically up to 16 blades can be installed in the M1000e chassis. The CoreStation WFC640 uses the new Dell FX2s chassis. The following solutions are available: Solutions with 14G PowerEdge Blades CoreStation WM640 (M640 PowerEdge Blade) CoreStation WFC640 (FC640 PowerEdge Blade) Solutions with 13G PowerEdge Blades DXM Solutions with 12G PowerEdge Blades DXM420 DXM520 DXM Typical configuration The CoreStation and DXM Series Blades typically accomodate: MXM Host cards Video DIsplay 1 x Single Slot or 1 x Double SlotS 2 x Single Slot Table 1: x x x x x x x x 1600 Common configurations for DXM Series Blades This manual will show you how to complete a basic manual configuration for one or two host cards in a single blade. Page 11

12 Introduction Page 12

13 2 Preparation 2. Overview There are many different blade solutions available, but the principle for setting up a remote desktop for each solution is essentially the same: 1 a). Install one or two Amulet Hotkey MXM host cards with onboard GPUs in a blade solution. See the relevant Quick Start Guides for this. b). Take a note of the MAC addresses on the cards. c). Install the blade in an appropriate Dell chassis (M1000e or FX2s). d). Make an ethernet connection to the card(s). 2 e). Set up the zero client(s). f). Connect to the blade from the zero client(s). Note: This manual also refers to the MXM host card as host card. 2.1 Figure 1: 1. Host card in correct slot for Fabric B. 2. Host card in correct slot for Fabric C Initial preparations Before you start the configuration, do the following. Identify the correct Fabric Obtain the MAC address Obtain the latest firmware Identify the correct Fabric 1. If configuring a single MXM host card, make sure that the card is installed in the correct MXM in the blade for the fabric that it will use in the M1000e chassis. See Figure 1 and Figure 2. Note: For two single slot cards used with an interconnection board, it is important to note which MXM is used by the primary host card. Note: For a dual slot card, it is important to note which MXM that the card is installed in, as the card covers both MXMs when installed. Figure 2: Fabric connections map Page 13

14 Preparation Obtain the MAC address This is usually recorded during the installion process. For a DHCP network, when the blade is powered on, the host cards will attempt to obtain an IP address. An administrator can easily view the DHCP server to see the IP addresses assigned, MAC addresses and other network information. Note: This step is relevant for those who may not have installed the cards themselves or are managing a lot of units. Important! If you do not have the MAC address, you may need to open up the blade to read the label on the host card Obtain the latest firmware 1. Check what the latest firmware is for the zero clients and blade host firmware and download from the Amulet Hotkey Resources website. See 3.6 and Check what the latest drivers are for the blade and for the GPU(s) on the host card(s) and download from the Amulet Hotkey Resources website. See 3.8 and Change the host card default IP address! Caution: Change the default IP address as soon as possible - unless the host card will be on a completely isolated network (for example with a pass-through one-to-one system) If your network uses DHCP, the host card obtains its IP address from the DHCP server. If no DHCP server is available, the host card times out after three minutes and adopts its default IP address of All host cards will revert to the same default IP address, this can cause conflicts as the network grows. Use the Administrative Web Interface (AWI) to assign a different static IP address from the default. 1. From the Configuration menu select the Network option. 2. Make sure the Enable DHCP option is unchecked. 3. Enter the new fall-back default IP address into the IP Address fields. 4. Make sure the Enable DHCP option is checked. Page 14

15 Set up the blade for one host card 3 3. Set up the blade for one host card. This section describes how to set up your DXM Series Blades with a single host card and up to four heads of video. 3.1 STEP 1: Power up the blade 1. If not already in the chassis, make sure the blade is installed in the correct slot 2. Press the green power button. The power button flashes. 2. The screen displays: idrac Config Auto configure slot (X)? DHCP enabled....where (X) is the number of the slot you have installed the blade). 3. Press the middle button on the panel to accept. 3.2 STEP 3: Log in to the CMC 1. Open a web browser and enter the IP address of the M1000e chassis to access the CMC login screen. The CMC login screen appears. Power button Figure 3: Power button on the front of a PowerEdge blade STEP 2: Identidfy the M1000e idrac front panel display 1. Locate the front panel display on the M1000e chassis (it may be folded out of sight). See Figure 4. Figure 5: CMC login screen 2. Select a value for the timeout from the drop down window. 3. Select the domain as This Chassis. 4. Login with the username and password. Figure 4: LCD module on the M1000e chassis Page 15

16 Set up the blade for one host card 3.3 STEP 4: Check blade health 1. Locate the Server overview list in the left hand window. Click on the blade slot that the blade is installed in. The blade Properties window appears. 3.4 STEP 5: Obtain the IP address for the host card 1. Discover the IP address created for the host card. You can either: a). Check with your IT or network admin to find out what IP address has been assigned to the host card. b). Access the DHCP server to look up the IP address associated with the MAC address (noted in Initial preparations) for the host card. See Figure 8. Figure 6: Blade Properties window 2. Make sure there is a green tick next to Health. See Figure 6. Important! If there is an issue, the writing of the slot details for the blade in the left hand panel will be coloured in red. 3. Make sure, that under I/O Fabric Interfaces, the host card is listed as installed. See.Figure 7. Figure 7: DXM-PCoIP-Series-DXM-13-X installed Figure 8: Example DHCP command window Page 16

17 Remote desktop configuration 3.5 STEP 6: Log in to the host card 1. Type the IP address obtained in STEP 5 into a web browser. An alert window appears. Figure 9: Alert window 2. Click on Advanced. The Add Exception window appears. 3.6 STEP 7: Check the firmware of the host card 1. Check the firmware version in the AWI window is the correct and up to date firmware for that product. 2. If the firmware is not correct then you must update the firmware. See 8.1 Update the Teradici firmware on page STEP 8: Set up the zero client 1. Follow setup instructions from a Quick Start Guide to install a Zero Client. 2. Select Direct to Host connection method. 3. Select the IP address in STEP 5: from the drop down list. One head of video showing the windows desktop appears. 3.8 STEP 9: Download drivers 1. Download the latest blade drivers such as Chipset, RAID Controller, NIC, USB Drivers and the latest GPU driver for the MXM from the Amulet Hotkey Resources website. Note: The 640 series blade requires USB 3.0 drivers, see our website for the latest blade drivers. 2. Install any required blade drivers and restart the blade. 3. Install the graphics driver. After installation, up to four heads of video are showing. 4. Installation is complete. Figure 10: Add Exception window 3. Click on Add Exception. The Confirm Security Exception window appears. Figure 11: Confirm Security Exception window 4. Click on the Confirm Security Exception button. Page 17

18 Set up the blade for one host card Page 18

19 Set up FX2s for 1 to Set up an FC640 blade for one host card. This section describes how to set up your Corestation WFC640 with a single host card and up to four heads of video. Important! The CoreStation WFC640 must have a customized Amulet Hotkey idrac installed. 4.1 Assignment of blades to PCIe slots Rather than the traditional integrated mezzanine card in the PowerEdge blades, the host card and GPU are now installed in the quad bay module PCIe slots in the rear of the chassis by way of an expansion module. Use the PCIe mapping option to assign the PCIe slot to the blade. By default each of the four blades will have two PCIe slots assigned. There is not normally a need to change this mapping. 4.2 STEP 1: Power up the blade 1. If not already in the chassis, make sure the blade is installed in the correct slot. 2. Press the green power button. The power button flashes. Power button Figure 13: Power button on the front of a PowerEdge blade 4.3 STEP 2: Log in to the CMC 3. Open a web browser and enter the IP address of the FX2s chassis to access the CMC login screen. The CMC login screen appears. Figure 12: FX2s mapping between modules and blades Each FC640 blade in the chassis requires a DXH4 PCIe host card with a dedicated GPU PCIe card connected to two PCIe slots. There is no requirement to connect the cards together using the mini-dp cables in the front of the card this as this is managed over the PCIe bus in the quad bay module. Figure 14: CMC login screen 4. Select a value for the timeout from the drop down window. 5. Select the domain as This Chassis. Page 19

20 Set up FX2s for 1 to 1 6. Login with the username and password. 4.4 STEP 3: Check blade health 1. Locate the Server overview list in the left hand window. Click on the blade slot that the blade is installed in. The blade Properties window appears. 4.6 STEP 5: Obtain the IP address for the host card 1. Discover the IP address created for the host card. You can either: a). Check with your IT or network admin to find out what IP address has been assigned to the host card. b). Access the DHCP server to look up the IP address associated with the MAC address (noted in Initial preparations) for the host card. See Figure STEP 6: Log in to the host card 1. Type the IP address obtained in STEP 5 into a web browser. An alert window appears. Figure 15: Blade Properties window 2. Make sure there is a green tick next to Health. See Figure 15. Important! If there is an issue, the writing of the slot details for the blade in the left hand panel will be coloured in red. 3. Check that the two PCIe slots assigned to that blade also show good health. See Figure 16. Figure 19: Alert window 2. Click on Advanced. The Add Exception window appears. Figure 16: Check health of PCIe slots 4.5 STEP 4: Set BIOS settings through the idrac 1. Set the Dell Wyse P25/P45 BIOS Access parameter to ENABLE in the BIOS to allow the remote PCoIP to enter and modify the BIOS settings. See Figure 17. Figure 20: Add Exception window Figure 17: System BIOS settings Page 20

21 Remote desktop configuration 3. Click on Add Exception. The Confirm Security Exception window appears. Figure 21: Confirm Security Exception window 4. Click on the Confirm Security Exception button. 4.8 STEP 6: Check the firmware of the host card 1. Check the firmware version in the AWI window is the correct and up to date firmware for that product. 2. If the firmware is not correct then you must update the firmware. See 8.1 Update the Teradici firmware on page STEP 7: Set up the zero client 1. Follow setup instructions from a Quick Start Guide to install a Zero Client. 2. Select Direct to Host connection method. 3. Select the IP address in STEP 5: from the drop down list. One head of video showing the windows desktop appears STEP 8: Download drivers 1. Download the latest blade drivers such as Chipset, RAID Controller, NIC, USB Drivers and the latest GPU driver for the MXM from the Amulet Hotkey Resources website. Note: The 640 series blade requires USB 3.0 drivers, see our website for the latest blade drivers. 2. Install any required blade drivers and restart the blade. 3. Install the graphics driver. After installation, up to four heads of video are showing. 4. Installation is complete. Figure 18: Example DHCP command window Page 21

22 Set up FX2s for 1 to 1 Page 22

23 Set up FX2s for VDI 5 5. How to set up a FC640 blade for VDI To set up a FC640 or WM640 blade for VDI, refer to KBA Set up VDI for the DXG-M6, DXG-P6 and DXF-G cards on our resources website. Page 23

24 Set up FX2s for VDI Page 24

25 Set up the blade for two host cards 6 6. Set up the blade for two host cards. This section describes how to set up your blade with two MXM host cards for up to eight heads of video. 6.1 STEP 1: Power up the blade 1. If not already in the chassis, make sure the blade is installed in the correct slot 2. Press the green power button. The power button flashes. 2. The screen displays: idrac Config Auto configure slot (X)? DHCP enabled....where (X) is the number of the slot you have installed the blade). 3. Press the middle button on the panel to accept. 6.2 STEP 3: Log in to the CMC 1. Open a web browser and enter the IP address of the M1000e chassis to access the CMC login screen. The CMC login screen appears. Power button Figure 22: Power button on the front of a PowerEdge blade STEP 2: Identidfy the M1000e idrac front panel display 1. Locate the front panel display on the M1000e chassis (it may be folded out of sight). See Figure 23. Figure 24: CMC login screen 2. Select a value for the timeout from the drop down window. 3. Select the domain as This Chassis. 4. Login with the username and password. Figure 23: LCD module on the M1000e chassis Page 25

26 Set up the blade for two host cards 6.3 STEP 4: Check blade health 1. Locate the Server overview list in the left hand window. Click on the blade slot that the blade is installed in. The blade Properties window appears. 6.4 STEP 5: Obtain both host card IP addresses 1. Discover the IP addresses created for both host cards. You can either: a). Check with your IT or network admin to find out what IP address has been assigned to each host card. b). Access the DHCP server to look up the IP addresses associated with the MAC addresses (noted in Initial preparations) for the host cards. See Figure 27. See 8.7 Use DHCP to simplify installation for what to do when no DHCP is available. Figure 25: Blade Properties window 2. Make sure there is a green tick next to Health. See Figure 25. Important! If there is an issue, the writing of the slot details for the blade in the left hand panel will be coloured in red. 3. Make sure, that under I/O Fabric Interfaces, both host cards are listed as installed. See Figure 26. Figure 26: Two DXM-PCoIP-Series-DXM-13-X installed Figure 27: Example DHCP command window Page 26

27 Remote desktop configuration 6.5 STEP 6: Log in to the primary host card 1. Type the IP address of one host card obtained in STEP 5 into a web browser. This will be the primary host card. An alert window appears. 6.6 STEP 7: Check the firmware of the host card 1. Check the firmware version in the AWI window is the correct and up to date firmware for that product. 2. If the firmware is not correct then you must update the firmware. See 8.1 Update the Teradici firmware on page STEP 8: Configure the secondaray host card 1. Do STEP 6 thru STEP 8 to configure the secondary host card. Figure 28: Alert window 2. Click on Advanced. The Add Exception window appears. 6.8 STEP 9: Disable audio on the second host card 1. Select Configuration > Audio from the AWI menu of the secondary host card. 2. Uncheck the audio option and select OK. 3. Restart the blade. Figure 29: Add Exception window 3. Click on Add Exception. The Confirm Security Exception window appears. Figure 30: Confirm Security Exception window 4. Click on the Confirm Security Exception button. Page 27

28 Set up the blade for two host cards 6.9 STEP 10: Set up the zero clients 1. Connect the keyboard, mouse and headset (optional) to one DXZ4, this is your primary zero client that will connect to the primary host card in the blade. Figure 31: Connect the keyboard and mouse and optional headset 2. Connect a combination of monitors to each zero client as shown in Table 2. Secondary Primary HDMI cables 2560 x 1600 resolution monitors 1920 x 1200 resolution monitors Figure 32: Connect up to eight monitors Connect to the Primary zero client... Connect to the Secondary zero client... Either: Up to 4 of 1920 x 1200 Either: Up to 4 of 1920 x 1200 Or: Up to 2 of 1920 x 1200 Or: Up to 2 of 1920 x 1200 and x 1600 and x 1600 Or: Up to x 1600 Or: Up to x 1600 Table 2: Page 28 List of monitor configurations

29 Remote desktop configuration 3. Connect the network cables. There are two options: Connection option 1: Daisy chain. Use this method if you want to use fewer network ports on the network. AUX MAIN Secondary a). (DXZ4-M only). Fit SFP modules to the AUX and MAIN network sockets on the primary DXZ4-M and to the MAIN network socket on the secondary DXZ4-M. b). Connect a suitable network cable between the AUX network socket on the primary DXZ4 to the MAIN network socket on the secondary DXZ4 with a suitable cable. Primary c). Connect a suitable network cable between the MAIN network socket on the primary DXZ4 and your PCoIP network. PCoIP Network Figure 33: PCoIP connection with daisy chain Connection option 2: Direct connection Use this method if you want a network connection to each DXZ4. AUX MAIN Secondary a). (DXZ4-M only). Fit SFP modules to the MAIN network sockets on the primary and secondary DXZ4-M zero clients. b). Connect a suitable network cable between the MAIN network socket on each zero client to your PCoIP network. Primary PCoIP Network Figure 34: PCoIP connection with daisy chain 4. Connect the power supplies. Important! The power connector has a locking sleeve that needs to be pulled back to release the connector from the socket. a). Connect the supplied PSU to the primary zero client. b). Connect the supplied PSU to the secondary zero client. c). Turn on both PSUs. Secondary Primary Power Supply Unit To power outlets Power Supply Unit Figure 35: Connect the Power Supply Units (PSUs) Page 29

30 Set up the blade for two host cards 6.10 STEP 11: Connect zero clients to the blade 1. Switch on the power button on the primary zero client. The OSD screen appears Connect zero clients to the blade For full details of all different connection methods, see 7. Set up a PCoIP session. Important! The one connection method described below is not practical for very large PCoIP deployments. 1. On the primary zero client, select the Direct to Host connection method from the drop-down list. The Direct to Host connection screen appears. Figure 36: Zero client On Screen Display After you install the zero clients, you must establish a PCoIP session between the zero clients and a remote PCoIP host or virtual desktop. When you press the power switch on the zero client for the first time, it displays the On Screen Display (OSD) connection screen. If more monitors are connected, the menu displays on Video port 1. The connection screen will also display if the Menu button is pressed while the unit is on Select PCoIP session type To set the type of PCoIP session the zero client will use to connect the host, use the OSD and change the configuration settings. 2. Select Options > Configuration and select the Session tab. 3. Click Unlock and enter the password. (Default is ahkdante). Figure 38: Direct to Host connection screen 2. Enter the IP address (or DNS name) for the primary host card (obtained in STEP 5) into the field provided. One head of video showing the windows desktop appears. Note: You must also configure a Direct from Client session connection type on the host. 3. (Optional) You can set the Enable Auto-Reconnect in the advanced settings to make the zero client reconnect with the last connected host when a session is disconnected. 4. Repeat sections and for the secondary zero client STEP 12: Download and install drivers 1. Download the latest blade drivers such as Chipset, RAID Controller, NIC, USB Drivers and the latest GPU driver for the MXM from the Amulet Hotkey Resources website. Note: The 640 series blade requires USB 3.0 drivers, see our website for the latest blade drivers. 2. Install any required blade drivers and restart the blade. 3. Install the graphics driver. After installation, up to eight heads of video are showing. 4. Installation is complete. Figure 37: Connection Type drop down list Page 30

31 Zero client connection methods 7 7. Set up a PCoIP session This section describes how to connect a DXZ4 or DXZC series zero client to a remote PCoIP host or virtual desktop. 7.1 Power up the zero client After you install the zero client, you must then establish a PCoIP session between the zero client and a remote PCoIP host or virtual desktop. When you press the power switch on the zero client for the first time, it displays the On Screen Display (OSD) connection screen. If more monitors are connected, the menu displays on Video port 1. The connection screen will also display if the Menu button is pressed while the unit is on. 7.2 Set the PCoIP session type To change the type of PCoIP session that the zero client uses to connect to the host, select the configuration in the OSD. 1. Select Options > Configuration and the Session tab. 2. Click Unlock and enter the password. (Default is ahkdante) The following connection methods are available: Auto Detect Connect directly to a specified host Connect to a choice of hosts using SLP Discovery PCoIP Connection Manager PCoIP Connection Manager + Auto-Logon Connect using VMware View Connect using a connection broker Note: For full details about each connection method, refer to the Session Connection Types section in the Teradici PCoIP Zero Client and Host Administrator Guide Auto Detect With this setting, the zero client connects to the address of any specified server. This session type is used where the client must choose between virtual and physical hosts Connect directly to a specified host Important! This is not practical for large PCoIP deployments. 1. Select the Direct to Host session connection type from the drop down list. Figure 39: Session selection drop down list Figure 40: Direct to Host connection type 2. Enter the IP address (or DNS name) for the PCoIP host. Note: You must also configure a Direct from Client session connection type on the host. 3. (Optional) You can also set the Enable Auto-Reconnect in the advanced settings to remember the last connected PCoIP host. Page 31

32 Zero client connection methods Connect to a choice of hosts using SLP Discovery If the zero clients and PCoIP hosts reside on the same subnet, you can use the Direct to Host + SLP session connection type to discover available PCoIP hosts on the subnet. You must know the IP address (or MAC address) of the PCoIP host that you want to connect to. Important! Use this connection method mainly for testing and evaluation purposes. 1. Select the Direct to Host + SLP Host Discovery session connection type from the drop down list Connect using VMware View You can configure zero clients to use PCoIP to connect to a virtual desktop in a VMware View environment. If you want users to log on manually: 1. Set the session connection type to View Connection Server. Figure 41: The zero client OSD discovers and lists the first 10 available PCoIP hosts discovered 2. Select the host you want and click OK. If the zero client successfully connects to the host, the front panel PCoIP status LED illuminates green to indicate an active session. 3. (Optional) You can also set the Enable Auto-Reconnect in the advanced settings to remember the last connected PCoIP host. Note: You must also configure a Direct from Client session connection type on the host PCoIP Connection Manager With a PCoIP Connection Manager you can centrally administer a large number of PCoIP devices. 1. Select the PCoIP Connection Manager session connection type from the drop down list. 2. Enter the server URI of the PCoIP Connection Manager. Figure 42: View Connection Server selection 2. Enter the IP address (or DNS name) of the VMware View Connection Server Connect with View Connection Server and Auto-Logon 1. Set the session connection type to View Connection Server + Auto-Logon. 2. Enter the IP address (or DNS name) of the VMware View Connection Server. 3. Enter the user s logon credentials. Other virtual desktop connection types are also supported, such as kiosk implementations. For details, see the Teradici PCoIP Zero Client and Host Administrator Guide Connect using a connection broker A connection broker is a resource management application. The broker dynamically assigns zero clients to host PCs from the identity of the user connecting from the zero client. 1. Set the session connection type on both the zero client and PCoIP host to Connection Management Interface PCoIP Connection Manager + Auto-Logon This connection type allows you to include the user name, password and domain of the user so that the connection and logon of the zero client is automatic. 1. Select the PCoIP Connection Manager + Auto-Logon session connection type from the drop down list. 2. Enter the server URI of the PCoIP Connection Manager. 3. Enter the user s Username, Password and Domain. Figure 43: Connection Management Interface selection Page 32

33 Remote desktop configuration 2. Enter the IP address (or DNS name) for the third party connection broker. 3. Click OK. See section Figure 26 for more information about third party connection brokers. 7.3 Set an automatic connection You can set up zero clients to automatically connect to a remote PCoIP host or virtual desktop when the end-user logs on. With this setup, there is minimal impact on the end-user. Once set up, at the end of the day the user: 1. Logs out of Windows. 2. Powers off their monitors. 3. Presses the power switch on the zero client to put it in standby. In the morning, the user: 1. Presses the power switch on the zero client to bring it out of standby. 2. Turns on their monitors. There is a pause while the zero client acquires the host IP address. The PCoIP On Screen Display (OSD) briefly shows a connection progress screen on the monitor attached to video output 1. See Figure 44. Figure 44: OSD Automatic connection screen 3. After a few seconds, the user logs on via the Windows login screen. 7.4 Disconnect from a host PC or virtual desktop 1. Press the front panel Menu button. 2. Choose Disconnect from the Zero Client Control Panel that appears on screen. See Figure 45. Figure 45: Disconnect option on the OSD 7.5 Choose a connection broker if required All Amulet Hotkey zero clients can be configured to use a third party connection broker (also known as a connection management server). For example, the following connection broker products include PCoIP support: VMware View Connection Server; Leostream Connection Broker Role of the connection broker Connection brokers simplify the administration effort for managing large complex PCoIP systems. A connection broker interacts with systems such as Active Directory to dynamically assign PCoIP hosts to zero clients based on the identity of the user establishing a connection from the zero client. Connection brokers are also used to allocate a pool of hosts to a group of zero clients Specify the connection broker You can use any of the available management tools (see section 8.7) to specify the connection broker: you must provide the IP address or DNS name of the connection broker; you must also specify the Connection Management Interface connection type for the PCoIP session Using the connection broker Instructions for using a connection broker to connect your zero clients to hosts are available in the Teradici PCoIP Zero Client and Host Administrator Guide (available to download from techsupport.teradici.com). Note: For further information about using connection brokers, contact Amulet Hotkey Technical Support. See also the Knowledge Base Article Can I use a connection broker with PCoIP technology? ( ) on the Teradici website. Page 33

34 Zero client connection methods Page 34

35 Additional information 8 8. Additional information This section provides extra information you may find useful. 8.1 Update the Teradici firmware! Caution: Check with technical support before you upgrade the firmware in your system. 1. Login with the AWI. See 6.5 STEP 6: Log in to the primary host card on page 27 for how to do this. 2. Select Firmware from the Upload menu. The Firmware Upload window appears. Figure 46: Firmware Upload window 3. Click Browse and navigate to the host firmware file. Note: This must be a *.all file. Example: tera2_4-9-0.all 4. Click Upload and select OK at the prompt. After the firmware has downloaded successfully, a prompt appears. 5. Click Reset. Another prompt appears. 6. Click OK to continue. 8.2 Set up a zero client for an automatic connection You can set up zero clients to automatically connect to a remote PCoIP host or virtual desktop when the end-user logs on. With this setup, there is minimal impact on the end-user. Once set up, at the end of the day the user: 1. Logs out of Windows. 2. Powers off their monitors. 3. Presses the power switch on the zero client to put it in standby. In the morning, the user: 1. Presses the power switch on the zero client to bring it out of standby. 2. Turns on their monitors. There is a pause while the zero client acquires the host IP address. The PCoIP On Screen Display (OSD) briefly shows a connection progress screen on the monitor attached to video output 1. See Figure 48. Figure 47: Successful upload window Figure 48: OSD Automatic connection screen Page 35

36 Additional information 3. After a few seconds, the user logs on via the Windows login screen. See for how to do this. 8.3 Disconnect from a host PC or virtual desktop 1. Press the front panel Menu button. 2. Choose Disconnect from the Zero Client Control Panel that appears on screen. See Figure 49. Figure 49: Disconnect option on the OSD 8.4 Further information For further information about zero client security, see the Teradici PCoIP Zero Client and Host Admin Guide, particularly the PCoIP Zero Client Security Overview and Security settings Checklist sections. This manual is available on the Doc Center page of the Teradici Support site at techsupport.teradici.com. 8.5 Available supported configurations Table 3 and Table 4 give an indication of what host cards are available with what blade solutions M1000e Chassis solutions 8.6 Record host card details before installation Before installing blades in a chassis, make a list of which host cards belong to which blades. Do this either: by recording host card and blade details manually, or; obtain this information from Technical Support. Having this information simplifies installation, making it easier to cross check blades with host cards, especially in Octal blades. 8.7 Use DHCP to simplify installation Is the PCoIP network using statically assigned IP addresses or DHCP? a). For a static network, host cards fall back to their X address. There a couple of ways to reassign a relevant IP to the cards for production use, such as using a private DHCP server connected to the chassis switching, or individually changing the IP address, card by card, using pass-through; b). For a DHCP network, once the blades have been powered on, the host cards will attempt to obtain an IP address. This method is much easier and enables an administrator who can view the DHCP server to view the IP addresses assigned, MAC addresses and other network information. 8.8 Additional administrative tasks Once the IP addresses have been assigned to the host cards the next steps could be: a). If there is a PCoIP Management Console present, run discovery and ensure all the cards are present; b). If there is a Connection Broker present, make sure the cards are listed in the Broker. Note: Octal blade host cards require pairing in the Broker to function together. Model WM640 DXM630 DXM620, DXM520, DXM420 Available MXMs or host cards DXM-P5000, DXM-M3000SE, DXM-S7100X, DXM-M2200, DXM-M1200, DXM-S4000X DXM-5000SE, DXM-M3000SE, DXM-M2000M, DXM-K2200M, DXM-S4000X DXM2-4 (E6760), DXM4-4 (S4000X) Table 3: M1000e chassis solutions and MXM cards FX2s Chassis solutions Model WFC640 Host cards DXF-G-P5000, DXF-G-S7100X, DXF-G-M3000SE, DXF-G-M2200, DXF-G-S4000X Table 4: FX2s chassis solutions and host cards Page 36

37 Remote desktop configuration Page 37

38