NICE Perform®

Release 3.2 3.2, & 3.5 3.1,

Virtualization Configuration Guide
November 2010

385A0809-01 Rev. A3

Insight from Interactions

®
TM

Information in this document is subject to change without notice and does not represent a commitment on the part of NICE Systems Ltd. The systems described in this document are furnished under a license agreement or nondisclosure agreement. All information included in this document, such as text, graphics, photos, logos and images, is the exclusive property of NICE Systems Ltd. and protected by United States and international copyright laws. Permission is granted to view and photocopy (or print) materials from this document for personal, non-commercial use only. Any other copying, distribution, retransmission or modification of the information in this document, whether in electronic or hard copy form, without the express prior written permission of NICE Systems Ltd., is strictly prohibited. In the event of any permitted copying, redistribution or publication of copyrighted material, no changes in, or deletion of, author attribution, trademark legend or copyright notice shall be made. All contents of this document are: Copyright © 2010 NICE Systems Ltd. All rights reserved.
This product is covered by one or more of the following US patents:
5,185,780 5,446,603 6,192,346 6,542,602 6,856,343 6,970,829 7,240,328 7,436,887 7,581,001 7,683,929 7,738,459 5,216,744 5,457,782 6,246,752 6,615,193 6,865,604 7,010,106 7,305,082 7,474,633 7,587,454 7,705,880 7,751,590 5,274,738 5,911,134 6,249,570 6,694,374 6,871,229 7,010,109 7,333,445 7,532,744 7,599,475 7,714,878 7,761,544 5,289,368 5,937,029 6,252,946 6,728,345 6,880,004 7,058,589 7,346,186 7,545,803 7,631,046 7,716,048 7,770,221 5,325,292 6,044,355 6,252,947 6,775,372 6,937,706 7,085,728 7,383,199 7,546,173 7,660,297 7,720,706 7,788,095 5,339,203 6,115,746 6,311,194 6,785,369 6,959,079 7,152,018 7,386,105 7,573,421 7,664,794 7,725,318 7,801,288 5,396,371 6,122,665 6,330,025 6,785,370 6,965,886 7,203,655 7,392,160 7,577,246 7,665,114 7,728,870 RE41,292

360o View, ACTIMIZE, Actimize logo, Alpha, Customer Feedback, Dispatcher Assessment, Encorder, eNiceLink, Executive Connect, Executive Insight, FAST, FAST alpha Blue, FAST alpha Silver, FAST Video Security, Freedom, Freedom Connect, IEX, Interaction Capture Unit, Insight from Interactions, Investigator, Last Message Replay, Mirra, My Universe, NICE, NICE logo, NICE Analyzer, NiceCall, NiceCall Focus, NiceCLS, NICE Inform, NICE Learning, NiceLog, NICE Perform, NiceScreen, NICE SmartCenter, NICE Storage Center, NiceTrack, NiceUniverse, NiceUniverse Compact, NiceVision, NiceVision Alto, NiceVision Analytics, NiceVision ControlCenter, NiceVision Digital, NiceVision Harmony, NiceVision Mobile, NiceVision Net, NiceVision NVSAT, NiceVision Pro, Performix, Playback Organizer, Renaissance, Scenario Replay, ScreenSense, Tienna, TotalNet, TotalView, Universe, Wordnet are trademarks and registered trademarks of NICE Systems Ltd. All other registered and unregistered trademarks are the property of their respective owners. Applications to register certain of these marks have been filed in certain countries, including Australia, Brazil, the European Union, Israel, Japan, Mexico, Argentina and the United States. Some of such registrations have matured to registrations.

385A0809-01 Rev. A3

com The Americas Region: (North.americas@nice. South America) Tel: 1-800-NICE-611 Fax: +720-264-4012 email: support.com For more information about NICE. Central. Africa) Tel: +972-9-775-3800 Fax: +972-9-775-3000 email: support@nice. and follow the online instructions. International Headquarters-Israel Tel: +972-9-775-3100 Fax: +972-9-775-3070 email: info@nice.com APAC Region: (Asia/Pacific) Tel: +852-8338-9818 Fax: +852-2802-1800 email: support. visit www.com United Kingdom Tel: +44-8707-22-4000 Fax: +44-8707-22-4500 France Tel: +33-(0)1-41-38-5000 Fax: +33-(0)1-41-38-5001 North America Tel: 1-800-663-5601 Fax: +201-356-2197 email: na_sales@nice. comments.com Germany Tel: +49-(0)-69-97177-0 Fax: +49-(0)-69-97177-200 Hong-Kong Tel: +852-2598-3838 Fax: +852-2802-1800 All queries.org. Visit the NUG Website at www.For assistance contact your local supplier or nearest NICE Systems Customer Service Center: EMEA Region: (Europe.nice. Middle East.apac@nice.com .com Israel: Tel: 09-775-3333 Fax: 09-775-3000 email: support@nice.com NICE invites you to join the NICE User Group (NUG). and suggestions are welcome! Please email: nicebooks@nice.niceusergroup.

Microsoft Hyper-V platform.VMware High Availability New chapter . Enabling NTP on ESX Servers. Terms and Abbreviations.Revision History Virtualization Configuration Guide Revision A1 Modification Date September 2009 Description • • Guide name changed from VMware Configuration Guide to Virtualization Configuration Guide. Snapshot management section for VMware configuration. New section . Added procedure for configuring memory reservation for the 32-bit operating system for the virtual machine running SQL Server. Network adapter configuration for VMware configuration.Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications A2 August 2010 • • • • • • • A3 November 2010 • • . Guidelines to virtual machine time synchronization. Procedure on how to convert a physical machine to a virtual machine.

.Blank page for double-sided printing.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Configuring the VoIP Logger’s Sniffing NIC for Promiscuous Mode . . . . . . . .13 2 VMware Configuration 17 Overview . . . . . . . . . . . . . . . . . .46 Configuring Memory Reservation for the 32-bit Operating System . .12 Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A3) 7 . . . . . .54 Setting the Priority for the VoIP Logger’s Capture NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Enabling NTP on ESX Servers . . .62 Increasing the Rx Buffer for the VMXNET2 (Enhanced) Card for ESX V4. .33 Virtual Machine Network Interface Card (NIC) Configuration . . . . . . . . . . . . . . . . . . . . .37 Changing the VoIP Logger’s Capture NIC Type to E1000 . . . . . . . . . . . . . .48 Configuring the Disk used for the Database Server as Mapped Raw LUN . . . . . . 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Virtual Machine with the VoIP Logger Installation . . . . . . .59 Increasing the Rx Buffer for the VoIP Logger’s Capture NIC . . . . . . . . . . . . . .18 VMware vCenter Server Summary View . . . . . . . . . . . . . . . & 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Allocating Resources for the Virtual Machines . . . . . . . . . . .52 Configuring Memory Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Virtual Machine with the SQL Database Installation . . . . . . . . . . . . .2. . . . . . . . . . . . . . .30 Virtual Machine Snapshot Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents 1 Virtualization in the NICE Perform Environment 11 Overview . .52 Disabling the Balloon Driver . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 NICE Perform ® Release 3. . . . . . . . . . . . . . . . . . . . . . . . . .5: Virtualization Configuration Guide (Rev. . . . . . . . . . . . . . . . . . . . . . . . . .0 . . . . . . . . . . . .35 Changing the NIC Type to Enhanced VMXNET / VMXNET2 (Enhanced) . . . . . . . . . . .18 Logging in to the VMware vCenter . . . . . .46 Configuring Memory Reservation for the 64-bit Operating System . . . . . . . . . . . . . . . . .25 Virtual Machine Time Synchronization . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .93 Client Login .96 NICE Perform ® Release 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5: Virtualization Configuration Guide (Rev. . . . . . . . . .82 Virtual Machine Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Configuring High Availability Settings . . . . . . . . . . . . . . 3. . . . . . .70 Sample Cluster with High Availability Settings . . . . . . . . . . . . . . . . . . . . . . . .94 Citrix XenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Network Adapter Configuration . .90 Supported Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . .79 Virtual Machine Settings . . . . . . . . . . . . . . . . . . . . . .91 PCoIP Display Protocol . . . . . . . . . . . . . . . . . . .90 VMware View . . . . . . . . . . . . .92 Guidelines for NICE Client-Side Applications Running on a VDMware Virtual Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Implications of High Availability in the Nice Perform Environment . . . . . . . . . . . . . . . . . . .96 Overview of XenDesktop . . . . . . . . . . . . . . . .5 . . . . . . . . . . . . . . . . . .69 Configuration Guidelines to VMware High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 3 Microsoft Hyper-V Configuration 75 Overview . . . . . . .92 Configuring the PCoIP Display Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 VMware High Availability . . . . . . . . . . . . . . . . . . . . . . . . . & 3. . . . . . . . . . . . . . . . A3) 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Configuring Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Examples of Virtual Machine Settings . .77 Hyper-V Host Server Disk Management . .78 Virtual Machine File Location for a New Virtual Machine . .87 4 Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications 89 Overview .Contents Increasing the Rx Buffer for the E1000 Card for ESX V3. . . . . . . . . . . . . . . . . . .76 Virtual Network settings .91 Overview of View Manager . . . . . . . . . . .

. . . . . 3. . . . . . . . . . . . . . . . . . . . . . . . . .105 Converting the Physical Machine into a Virtual Machine . . . . . . . . . . . . . . . .119 NICE Perform ® Release 3.99 Logging in via Web . . . . . . . . . . . . . . . .101 Playback Issue . . . . . . . . . . . . . . . . . . . . . . . .0. . . . . . . . . . . . . . . . . .Contents Desktop Delivery Protocol . . . . . . . . . . . . . . . . . . . .101 A Converting a Physical Machine into a VMware Virtual Machine 103 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5: Virtualization Configuration Guide (Rev. . . . . . . . . . . . A3) 9 . . . . . .1 . . . . . . . . . . . . .99 Logging in via the Online Plug-In . . . . . . . . . . . . . . . . .2. . .109 Defining the New Virtual Machine’s IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 Client Login . .100 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . .104 Installing VMware Converter 4. . . . . . . . . . .98 Guidelines for NICE Client-Side Applications Running on a Citrix XenDesktop . . . . . . . . . . . . . & 3. . . . . . . . .

Blank page for double-sided printing. .

................... A3) 11 ...... 12 Terms and Abbreviations........................... NICE Perform ® Release 3........ & 3..........5: Virtualization Configuration Guide (Rev..1........ 3.1 Virtualization in the NICE Perform Environment IN THIS CHAPTER Overview ......2.. 13 This chapter provides a basic overview of NICE Perform in the virtualization environment.............................

Chapter 1: Virtualization in the NICE Perform Environment Overview Overview Virtualization is the facility that enables multiple operating systems to run simultaneously on one machine in a safe and efficient manner.0.1.5: Virtualization Configuration Guide (Rev. This document provides general guidelines on how to configure NICE Perform servers in a virtual infrastructure. increasing agility and further automating IT operations. reducing Total Cost of Ownership by up to 75%. 3. The following topics are described: • VMware Configuration on page 17 The following topics are described: • • • • • • • • • Logging in to the VMware vCenter on page 18 VMware vCenter Server Summary View on page 19 Allocating Resources for the Virtual Machines on page 25 Virtual Machine Time Synchronization on page 29 Virtual Machine Snapshot Management on page 33 Virtual Machine Network Interface Card (NIC) Configuration on page 35 Virtual Machine with the SQL Database Installation on page 46 Virtual Machine with the VoIP Logger Installation on page 52 Microsoft Hyper-V Configuration on page 75 The following topics are described: • • • • • • Network Adapter Configuration on page 76 Hyper-V Host Server Disk Management on page 78 Virtual Machine File Location for a New Virtual Machine on page 79 Virtual Machine Settings on page 81 Virtual Machine Time Synchronization on page 87 Converting a Physical Machine into a VMware Virtual Machine on page 103 The following topics are described: • • Installing VMware Converter 4. A3) 12 . & 3.2.1 on page 105 Converting the Physical Machine into a Virtual Machine on page 109 NICE Perform ® Release 3. Of the benefits of virtualization are the lowering of hardware expenditures.

multiple operating systems.Chapter 1: Virtualization in the NICE Perform Environment Terms and Abbreviations Terms and Abbreviations Term Balloon Driver Description Memory reclaimed from virtual machines by cooperation with the VMware Tools (vmmemctl driver) and guest operating systems. Two versions exist . Hypervisor LUN Memory Reservation NICE Perform ® Release 3. 3. This is the preferred method for reclaiming memory from virtual machines. swaps them to its own virtual disk. The system "inflates" the balloon driver to increase memory pressure within the virtual machine. Although a virtual memory function will simulate an almost unlimited amount of memory. Operating systems and applications generally reserve fixed amounts of memory at startup and allocate more when the processing requires it. If there is not enough free memory to load the core kernel of an application. The ESXi Server has no service console and is the thinnest version available. allows multiple operating systems to run concurrently on a host computer— a feature called hardware virtualization.each virtual machine uses a configured section of a LUN. including multiple instances of the same operating system.Storage LUNs (Logical Unit Numbers) are commonly shared between virtual machines . Reserving memory for specific purposes. It is so named because it is conceptually one level higher than a supervisor.1.2. A3) 13 . Also called virtual machine monitor (VMM). it cannot be launched.5: Virtualization Configuration Guide (Rev. When memory is tight. can share hardware resources. ESX Server VMware's enterprise server virtualization platform. The hypervisor presents the guest operating systems with a virtual platform and monitors the execution of the guest operating systems. and if necessary. the guest operating system decides which particular pages of memory to reclaim.ESX Server and ESXi Server. since it reclaims the memory that is considered least valuable by the guest operating system. In that way. there is always a certain amount of "real" memory that is needed. & 3. causing the guest operating system to invoke its own native memory management algorithms. This proprietary technique provides predictable performance that closely matches the behavior of a native system under similar memory constraints. Logical Unit Number . ESX Server has many optional features like VMotion and VMHA and some built-in features like the VMFS file system.

This mode of operation is sometimes given to a network snoop server that captures and saves all packets for analysis (for example. & 3. In an Ethernet local area network (LAN).5: Virtualization Configuration Guide (Rev. 3. promiscuous mode allows a network device to intercept and read each network packet that arrives in its entirety. If the virtual machine's network driver runs out of receive (Rx) buffers. The number of dropped packets can be reduced by increasing the virtual network driver’s Rx buffers. Used to reduce Logger packet loss and improve performance. Load Balancing: Balancing the network traffic load on a server • can enhance the functionality of the server and the network. Promiscuous mode is often used to monitor network activity. promiscuous mode is a mode of operation in which every data packet transmitted can be received and read by a network adapter. receive packets could be dropped at the virtual switch. Teaming has two purposes: • Fault Tolerance: By teaming more than one physical NIC to a logical NIC. high availability is maximized. Rx Buffer NICE Perform ® Release 3. that is.1. Promiscuous Mode In a network. Each standalone host and each DRS cluster has an (invisible) root resource pool that groups the resources of that host or cluster.Chapter 1: Virtualization in the NICE Perform Environment Terms and Abbreviations Term NIC Teaming Description NIC teaming is the process of grouping together several physical NICs into one single logical NIC. Resource Pools Use resource pools to hierarchically partition available CPU and memory resources.2. for monitoring network usage). The process of grouping NICs is called teaming. A3) 14 . a buffer overflow occurs. which can be used for network fault tolerance and transmit load balance. The root resource pool is not displayed because the resources of the host (or cluster) and the root resource pool are always the same. Load balancing within network interconnect controller (NIC) teams enables distributing traffic amongst the members of a NIC team so that traffic is routed among all available paths. the network connection does not cease and continues to operate on other NICs. Promiscuous mode must be supported by each network adapter as well as by the input/output driver in the host operating system. Even if one NIC fails.

& 3. If the overall workload decreases. If the workload on one or more virtual machines drastically changes. The utility can be configured for manual or automatic control. VMware DRS redistributes the virtual machines among the physical servers.Chapter 1: Virtualization in the NICE Perform Environment Terms and Abbreviations Term VMware vCenter/Virtual Center VMware DRS Description ESX Server is managed by the VMware Infrastructure Client. removed or reorganized.5: Virtualization Configuration Guide (Rev.2. Its centralized management platform is called Virtual Center or VMware vCenter. some of the physical servers can be temporarily powered-down and the workload consolidated. VMware DRS (Distributed Resource Scheduler) is a utility that balances computing workloads with available resources in a virtualized environment. Resource pools can be easily added. resource pools can be isolated between different business units. With VMware DRS. A3) 15 .1. NICE Perform ® Release 3. If desired. users define the rules for allocation of physical resources among virtual machines. 3. The utility is part of a virtualization suite called VMware Infrastructure 3.

.Blank page for double-sided printing.

. 33 Virtual Machine Network Interface Card (NIC) Configuration .......0.... The guidelines described here refer to both VMware Infrastructure 3...... 46 Virtual Machine with the VoIP Logger Installation .... 18 VMware vCenter Server Summary View............... & 3. For NICE Perform configuration requirements and specifications...........2 VMware Configuration IN THIS CHAPTER Overview ....5: Virtualization Configuration Guide (Rev..... see the Design Considerations and Certified Servers guides....................0 (ESX 3..................1) deployments.... 3............ 69 This chapter describes the recommended settings for NICE Perform installations on the VMware platform.....5) and VMware vSphere (ESX 4....... NICE Perform ® Release 3...................................... 4........... 18 Logging in to the VMware vCenter ....... 19 Allocating Resources for the Virtual Machines................ A3) 17 .............................. 52 VMware High Availability. 25 Virtual Machine Time Synchronization ................ 35 Virtual Machine with the SQL Database Installation ............. 29 Virtual Machine Snapshot Management ......1............2. NOTE The examples shown in this chapter only represent a typical VMware solution and may not been seen at your site.................

A3) 18 . and the VMware vCenter Server username and password with administrative rights. is designed to run multiple virtual machines that facilitate hosting multiple operating systems running NICE Perform components. Double-click VMware vCenter . NICE Perform ® Release 3. If you do not have administrative rights. you can alert an administrator. who will then make the change. 3. & 3. Click Login. Infrastructure specifications.Chapter 2: VMware Configuration Overview Overview The VMware platform.5: Virtualization Configuration Guide (Rev. based on the ESX server. Enter the IP address or hostname of your VMware vCenter Server. 3. The VMware vSphere Client Login window appears. the virtual machines’ resources (disk.1. CPU. Logging in to the VMware vCenter To log in to the VMware vCenter: 1. memory. you can still log in to the system with read-only rights and review configuration settings. If a setting needs to be changed. The VMware vCenter Server appears. network) can be allocated and configured either directly within the ESX server or via the VMware vCenter.2. Figure 2-1 VMware vSphere Client Login Window 2.

You can therefore create a hierarchy of shared resources. select Hosts and Clusters. To display the VMware vCenter Server summary: 1. The root resource pool is not displayed because the resources of the host (or cluster) and the root resource pool are always the same. Each standalone host and DRS cluster has an invisible root resource pool that groups the resources of that host or cluster.1. A resource pool can contain child resource pools. The resource pools at a higher level are called parent resource pools. The NICE Perform integration with VMware does not require special customization to the Resource Pools. Note: VMware DRS facilitates balancing resources across virtual machines. Then click the Summary tab. In the VMware vCenter Server. & 3. from the Inventory drop-down list. or both. 2. 3. Resource pools and virtual machines that are at the same level are called siblings.Chapter 2: VMware Configuration VMware vCenter Server Summary View VMware vCenter Server Summary View This section describes how to display a summary of your VMware vCenter Server configuration. virtual machines. NICE Perform ® Release 3. Each ESX server contains Virtual Machines that can be grouped under Resource Pools.5: Virtualization Configuration Guide (Rev. The cluster itself represents the root resource pool. The Data Centers and ESX Servers related to each Data Center are displayed. A3) 19 . TIP Resource pools are used to hierarchically partition available CPU and memory resources. Log in to the VMware vCenter Server as described in Logging in to the VMware vCenter on page 18.2.

2.5: Virtualization Configuration Guide (Rev.ESX Server Summary NICE Perform ® Release 3. & 3. Select the ESX server.Chapter 2: VMware Configuration VMware vCenter Server Summary View Figure 2-2 VMware vCenter Server Summary View .1.Hosts and Clusters 3. Figure 2-3 VMware vCenter . 3. The ESX server resources are displayed. A3) 20 .

its manufacturer. click CPU. facilitating scenarios in which there exists competition for CPU resources between virtual machines.Chapter 2: VMware Configuration VMware vCenter Server Summary View The Summary tab displays the following information: • General area .the defined storage locations are displayed.information about the machine that is hosting the ESX server . 6.CPU Resource Allocation The Reservation and Limit columns indicate CPU allocation per virtual machine.5: Virtualization Configuration Guide (Rev. 5.2. • 4. NICE Perform ® Release 3. Figure 2-4 VMware vCenter . Click the Resource Allocation tab. memory (RAM). click Memory. model. Datastore area .1. From the View options. The Shares column indicates the CPU resource priority. the number of virtual machines running on this ESX. the number of installed network interface cards (NICs). processor type. processors. 3. From the View options. & 3. A3) 21 .

Memory Resource Allocation The Reservation and Limit columns provide information about the memory allocated per virtual machine. 3. The Shares column indicates memory priority. & 3. NICE Perform ® Release 3.Chapter 2: VMware Configuration VMware vCenter Server Summary View Figure 2-5 VMware vCenter . 8. A3) 22 .2. Configure resources as described here: • Memory Reservation (MB) Define zero (0) for all virtual machines except the virtual machines running the SQL server and NICE VoIP Logger. Click the Configuration tab.5: Virtualization Configuration Guide (Rev.1. See: • • • Memory Limit (MB) Virtual Machine with the SQL Database Installation on page 46 Virtual Machine with the VoIP Logger Installation on page 52 Unlimited 7. facilitating scenarios in which there exists competition for memory resources between virtual machines. Keep all other defaults.

NICE Perform ® Release 3. In Figure 2-7.Configuration Tab One (1) NIC Many virtual machines Additional configuration information about the ESX server is displayed. 3. one NIC is connected to several virtual machines.5: Virtualization Configuration Guide (Rev. See Figure 2-7.Chapter 2: VMware Configuration VMware vCenter Server Summary View Figure 2-6 VMware vCenter . you can see which virtual machine is connected to the different NICs (Network Interface Cards). When teaming NICs are configured. this is also displayed. & 3. A3) 23 .2. For example.1. additional NICs (vmnic0\1\2) under Physical Adapters are displayed. If several NICs are configured as teaming NICs.

that enables you to connect a single virtual switch to multiple physical Ethernet adapters.Chapter 2: VMware Configuration VMware vCenter Server Summary View Figure 2-7 VMware vCenter . NIC teaming policies are set at the port group level.5: Virtualization Configuration Guide (Rev.Teaming NICs Teaming NICs Several virtual machines TIP NIC Teaming is a feature of VMware Infrastructure 3 and above. 3. A team can share traffic loads between physical and virtual networks and provide passive failover in case of an outage. A3) 24 .2.1. NICE Perform ® Release 3. & 3.Configuration Tab .

Hosts and Clusters 4.Chapter 2: VMware Configuration Allocating Resources for the Virtual Machines Allocating Resources for the Virtual Machines To allocate resources for the virtual machines: 1. from the Inventory drop-down list. Figure 2-8 VMware vCenter Summary View . In the VMware vCenter.1.2. Each ESX server contains Virtual Machines that can be grouped under Resource Pools. Click the Summary tab. The Virtual Machine Properties window appears.5: Virtualization Configuration Guide (Rev. Select a virtual machine and click Edit Settings. Log in to the VMware vCenter as described in Logging in to the VMware vCenter on page 18. 3. NICE Perform ® Release 3. select Hosts and Clusters. 3. A3) 25 . & 3. The Data Centers and ESX Servers related to each Data Center are displayed. 2.

5. NICE Perform ® Release 3. Click the Resources tab. Disk.5: Virtualization Configuration Guide (Rev. The disk used for the virtual machine is usually the disk used for the shared storage to which the ESX server is connected. partitioning can be done later from the operating system. Memory. Disk. Using the Disk Management tool. A3) 26 . The CPU. Several disks can be assigned to one virtual machine. & 3.Chapter 2: VMware Configuration Allocating Resources for the Virtual Machines Figure 2-9 Virtual Machine Properties The CPU. and Advanced CPU resource types are listed. The size of each disk is determined when assigned to a virtual machine. 3. Network Adapter resource types for the selected virtual machine are displayed.1.2. Memory. The following resource types are configurable: • • • Memory (MB) CPU Disk Amount of allocated memory Number of CPUs (vCPU) that are allocated as specified in the Certified Servers Guide.

& 3. Figure 2-11 Virtual Machine Properties . The Resource Allocation area displays the configurable parameters for the Memory resource.2.1.Memory Resources NICE Perform ® Release 3.Chapter 2: VMware Configuration Allocating Resources for the Virtual Machines Figure 2-10 Virtual Machine Properties . Select Memory.Resources 6. 3. A3) 27 .5: Virtualization Configuration Guide (Rev.

the virtual machine with the Memory Shares with the highest priority will be allocated the highest memory resource priority. A3) 28 . 3. Default = 0 Limits the memory that the virtual machine will be able to consume. When there exists resource competition between virtual machines. the virtual machine with the the Disk Shares with the highest priority will be allocated highest disk resource priority. When there exists resource competition between virtual machines. you can configure the Shares disk parameter.Chapter 2: VMware Configuration Allocating Resources for the Virtual Machines In the Resource Allocation area. & 3. In the Resources tab. you can configure the following memory parameters: • Shares Default = Normal Memory Shares determine memory priority. • • Reservation Default = 0 Amount of Memory that will always be available for the VM.1. (MB) Limit (MB) 7.5: Virtualization Configuration Guide (Rev. • Shares Default = Normal Disk Shares determine disk priority. select Disk. NICE Perform ® Release 3.Disk Resources In the Resource Allocation area. Figure 2-12 Virtual Machine Properties .2. The Resource Allocation area displays the configurable parameters for the Disk resource.

Figure 2-13 VMware Tools Properties Window VMware Tools NICE Perform ® Release 3. & 3.2.5: Virtualization Configuration Guide (Rev.1. see Enabling NTP on ESX Servers on page 30. The Windows Time Service must be disabled. This eliminates the need to configure NTP for each virtual machine. To time-synchronize your virtual machines to the host ESX server: • In each virtual machine.Chapter 2: VMware Configuration Virtual Machine Time Synchronization Virtual Machine Time Synchronization Virtual machine time synchronization must be set as follows: • • • All virtual machines must be time-synchronized to the host ESX server. open the VMware Tools Properties window and select Time synchronization between the virtual machine and the ESX Server. A3) 29 . 3. All host ESX servers must be time-synchronized to your organization NTP. For instructions on setting NTP on the ESX Server.

Chapter 2: VMware Configuration Virtual Machine Time Synchronization Enabling NTP on ESX Servers In addition to enabling NTP on the ESX Server. In the Software area. 2. Click Properties. & 3. Connect via VMware vSphere Client to ESX or vCenter Server. NICE Perform ® Release 3.2.Configuration Tab > Time Configuration 4.5: Virtualization Configuration Guide (Rev. Your server clock will shortly start syncing with the NTP server you selected. the NTP client on each ESX host must be set to a physical time source. A3) 30 . If none are available within the organization. select Time Configuration. You can check the current time by clicking the Refresh link in the VI Client. 3. round robin DNS records can be configured to gather time from the Internet via UDP port 123. Select the relevant ESX server and click the Configuration tab. 3. To enable NTP on ESX Servers: 1. Figure 2-14 VMware ESX .1. The ESX built-in firewall will automatically be modified to allow outgoing connections on port 123.

2. Figure 2-16 Time Configuration Properties Window 5. A3) 31 .Configuration Tab > Properties The Time Configuration Properties window appears.Chapter 2: VMware Configuration Virtual Machine Time Synchronization Figure 2-15 VMware ESX . The NTP Daemon Options window appears. In the NTP Configuration area.1. Click Options.5: Virtualization Configuration Guide (Rev. 6. select NTP Client Enabled. & 3. NICE Perform ® Release 3. 3.

Chapter 2: VMware Configuration Virtual Machine Time Synchronization Figure 2-17 NTP Daemon Options ‐ General 7. 3. 10.5: Virtualization Configuration Guide (Rev. click Add. 8. select Start and Stop with Host. Changes are applied and NTP service is started. Then select Restart NTP service to apply changes. Figure 2-18 NTP Daemon Options ‐ NTP Settings 9.2. & 3. To add a new NTP server (or multiple NTP servers). Click General.1. NICE Perform ® Release 3. In the Startup Policy area. Click OK. A3) 32 . Click NTP Settings.

2. The Snapshots window appears. A3) 33 .5: Virtualization Configuration Guide (Rev.Chapter 2: VMware Configuration Virtual Machine Snapshot Management Virtual Machine Snapshot Management For performance reasons. select your virtual machine.1. To confirm that no snapshots have been saved on your virtual machine: 1. this button appears disabled Snapshot Manager button Virtual machine selected 2. virtual machine snapshots are prohibited. & 3. NICE Perform ® Release 3. 3. In the VMware vCenter. Figure 2-19 VMware vCenter .Virtual Machine Selected If no snapshots are defined. Click Snapshot Manager.

1.No Snapshots Defined NICE Perform ® Release 3. 3.2.5: Virtualization Configuration Guide (Rev. & 3.Chapter 2: VMware Configuration Virtual Machine Snapshot Management Figure 2-20 Snapshots Window . A3) 34 .

Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration Virtual Machine Network Interface Card (NIC) Configuration All virtual machines running NICE components must be configured with the recommended NICs.5 • • • • • All NICE components except for the VoIP Logger's capture NIC: [Enhanced VMXNET] or [E1000] NICE VoIP Logger’s capture NIC: E1000 ESX Version 4. If a virtual machine’s current NIC type is Flexible. & 3. 2. -or- • VoIP Logger’s capture NIC only: Changing the VoIP Logger’s Capture NIC Type to E1000 on page 40. VoIP Logger’s capture NIC only: Setting the Priority for the VoIP Logger’s Capture NIC on page 57 NICE Perform ® Release 3. These will enable enhanced network capabilities. 3. A3) 35 .1.recommended -or- [E1000] -or- [VMXNET 3] NOTE Make sure to install VMware Tools on each virtual machine.0: VoIP Logger's capture NIC: VMXNET2 (Enhanced) All virtual machines running NICE components: • • • [VMXNET2 (Enhanced)] . Changing the NIC type: • Changing the NIC Type to Enhanced VMXNET / VMXNET2 (Enhanced) on page 37. you must remove this NIC and install one of the recommended NIC types instead.5: Virtualization Configuration Guide (Rev. Virtual machine running the VoIP Logger: a. Changing the network interface card (NIC) type involves the following steps: 1. Recommended NIC types for virtual machines running NICE components: • ESX Version 3.2.

Passive VoIP Recording only: Configuring the VoIP Logger’s Sniffing NIC for Promiscuous Mode on page 59. & 3. NICE Perform ® Release 3.2.1. Increasing the Rx Buffer for the VoIP Logger’s Capture NIC on page 62. 3.5: Virtualization Configuration Guide (Rev. b. A3) 36 .Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration a.

The Select Device Type window appears. Click Add.5: Virtualization Configuration Guide (Rev. 3. To change a virtual machine’s network adapter type: 1.Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration Changing the NIC Type to Enhanced VMXNET / VMXNET2 (Enhanced) You configure the network adapter for each virtual machine via the Edit Settings option.2.1. Select the network adapter that needs to be removed and click Remove. Figure 2-21 Virtual Machine Properties 3. 2. & 3. A3) 37 . Shut down the virtual machine. The Virtual Machine Properties window appears. NICE Perform ® Release 3. 4. Select the virtual machine and click Edit Settings.

Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration

Figure 2-22 Select Device Type

5. Select Ethernet Adapter and click Next.

The Network Type window appears.
Figure 2-23 Network Type Window

6. Select Enhanced vmxnet and click Next.

NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3)

38

Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration

Figure 2-24 Network Type - Enhanced VMXNET 2

7. From the Type menu, select one of the following:

• •

For ESX3.5, select Enhanced vmxnet. For ESX4.0, select VMXNET2 (Enhanced).

8. Click Next.

The Ready to Complete window appears.
Figure 2-25 Ready to Complete Hardware Wizard

NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3)

39

Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration

NOTE

If the IP of the network card was already configured you may need to reconfigure the IP after the virtual machine is started.
9. Confirm settings and click Finish. 10. If you changed the NIC type for the VoIP Logger’s capture NIC, you may need to reset its

priority. See Setting the Priority for the VoIP Logger’s Capture NIC on page 57.

Changing the VoIP Logger’s Capture NIC Type to E1000
If ESX Version 4.0 is installed at your site, you must use VMXNET2 (Enhanced) for your VoIP Logger’s capture NIC. If ESX Version 3.5 is installed at your site, you must use E1000 for your VoIP Logger’s capture NIC. This section describes how to change the NIC type to E1000. If you need to change the NIC type to VMXNET2 (Enhanced), see Changing the NIC Type to Enhanced VMXNET / VMXNET2 (Enhanced) on page 37.
To change a virtual machine’s network adapter type to E1000: 1. Shut down the virtual machine running the VoIP Logger. 2. Select the VoIP Logger’s virtual machine and click Edit Settings. 3. Click the Options tab and change the Guest Operating System to Microsoft Windows Server 2003, DataCenter Edition.

NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3)

40

5: Virtualization Configuration Guide (Rev. Reopen the Logger’s Virtual Machine Properties window. 5. 6. 3. Click OK. NICE Perform ® Release 3. Click the Hardware tab.2.Options Tab 4. A3) 41 .Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration Figure 2-26 Virtual Machine Properties Window .1. & 3.

2. NICE Perform ® Release 3.5: Virtualization Configuration Guide (Rev. A3) 42 . Click Add. The Add Hardware Wizard starts.Hardware Tab 7.Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration Figure 2-27 Virtual Machine Properties Window .Select Device Type Window 8. 3. & 3.1. Figure 2-28 Add Hardware Wizard . Select Ethernet Adapter and click Next.

Network Type Window Example only select the NIC that will be used for capturing audio Configure the Network Type as described below: • • Adapter Type Network Connection Select E1000 From the Named network with specified label menu. 9. Click Next. & 3. select NIC that will be used for capturing audio (RTP). NICE Perform ® Release 3.2.5: Virtualization Configuration Guide (Rev.Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration The Network Type window appears.1. Figure 2-29 Add Hardware Wizard . 3. The Ready to Complete window appears. A3) 43 .

Click OK.5: Virtualization Configuration Guide (Rev. The network adapter appears in the Virtual Machine Properties window. A3) 44 .Ready to Complete Window 10.2.1.Network Adapter Configuration Network adapter designated for capturing audio (RTP) is now configured 11. Figure 2-31 Virtual Machine Properties Window . NICE Perform ® Release 3. Click Finish.Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration Figure 2-30 Add Hardware Wizard . & 3. 3.

Proceed to Setting the Priority for the VoIP Logger’s Capture NIC on page 57. Restart the virtual machine. 16.Guest Operating System 15.1. A3) 45 . 13. 3. 17. NICE Perform ® Release 3. Click OK.Chapter 2: VMware Configuration Virtual Machine Network Interface Card (NIC) Configuration 12. In the Guest Operating System area. Reopen the Logger’s Virtual Machine Properties window. 14. Reconfigure the NIC’s IP address. Standard Edition. 18.2. Your operating system recognizes this network adapter as if it were now newly connected. change the Version to Microsoft Windows Server 2003. & 3. Click the Options tab. Figure 2-32 Virtual Machine Properties Window .5: Virtualization Configuration Guide (Rev.

see the Certified Servers Guide. This will ensure that this virtual machine will have sufficient memory for performing all operations at all times. the Memory Reservation must equal the amount of memory allocated to the virtual machine. NOTE These procedures are relevant to the virtual machine running the Data Mart. & 3. select Hosts and Clusters.1. NICE Perform ® Release 3.2. Configuring Memory Reservation for the 32-bit Operating System on page 48. To configure Memory Reservation for the 64-bit operating system: 1. Configuring a virtual machine running the SQL database involves: • • • Configuring Memory Reservation for the 64-bit Operating System on page 46. Log in to the VMware vCenter as described in Logging in to the VMware vCenter on page 18. 3. For NICE requirements and specifications. The Virtual Machine Properties window appears. A3) 46 . In the VMware vCenter. 3. Select the virtual machine running SQL database and click Edit Settings.5: Virtualization Configuration Guide (Rev. from the Inventory drop-down list. Configuring the Disk used for the Database Server as Mapped Raw LUN on page 51. Configuring Memory Reservation for the 64-bit Operating System When your SQL database is installed on a virtual machine running on a 64-bit operating system.Chapter 2: VMware Configuration Virtual Machine with the SQL Database Installation Virtual Machine with the SQL Database Installation This section describes how to configure a virtual machine running the SQL database. 2.

1. 3. The CPU. Disk. Memory.Chapter 2: VMware Configuration Virtual Machine with the SQL Database Installation Figure 2-33 Virtual Machine Properties The CPU.5: Virtualization Configuration Guide (Rev.2. & 3. Figure 2-34 Virtual Machine Properties . A3) 47 . Network Adapter resource types for the selected virtual machine are displayed. 4.Resources NICE Perform ® Release 3. and Advanced CPU resource types are listed. Disk. Memory. Click the Resources tab.

This will ensure that this virtual machine will have sufficient memory for performing all operations at all times. configure parameters as described below: • • Shares Reservation (MB) Normal Set according to specifications in the Certified Servers Guide. 3. & 3. To configure Memory Reservation for the 32-bit operating system: 1. Click OK. NICE Perform ® Release 3. A3) 48 . Figure 2-35 Memory Reservation for the Virtual Machine Running SQL Example only In the Resource Allocation area. 3. from the Inventory drop-down list. 6.2.Chapter 2: VMware Configuration Virtual Machine with the SQL Database Installation 5.1. select Hosts and Clusters. In the VMware vCenter. Select the virtual machine running SQL database and click Edit Settings.5: Virtualization Configuration Guide (Rev. Log in to the VMware vCenter as described in Logging in to the VMware vCenter on page 18. The Virtual Machine Properties window appears. Configuring Memory Reservation for the 32-bit Operating System When your SQL database is installed on a virtual machine running on a 32-bit operating system. 2. you must configure the Memory Reservation to 4096 MB. Select Memory. The Resource Allocation area displays the configurable parameters for the Memory resource.

Memory. Figure 2-37 Virtual Machine Properties . 4. Memory. and Advanced CPU resource types are listed. Disk. & 3. The CPU. A3) 49 .2. 3. Click the Resources tab.5: Virtualization Configuration Guide (Rev.Chapter 2: VMware Configuration Virtual Machine with the SQL Database Installation Figure 2-36 Virtual Machine Properties The CPU. Network Adapter resource types for the selected virtual machine are displayed. Disk.Resources NICE Perform ® Release 3.1.

Click OK.1.5: Virtualization Configuration Guide (Rev. configure parameters as described below: • • Shares Reservation (MB) Normal 4096 MB 6. A3) 50 . The Resource Allocation area displays the configurable parameters for the Memory resource. Select Memory. NICE Perform ® Release 3. & 3. 3.2.Chapter 2: VMware Configuration Virtual Machine with the SQL Database Installation 5. Figure 2-38 Memory Reservation for the Virtual Machine Running SQL In the Resource Allocation area.

1. A3) 51 . The best practice for virtual machines running the SQL server is to map disk drives used for SQL data and logs to Raw LUNs.each virtual machine uses a configured section of a LUN. Figure 2-39 Virtual Machine Properties .Chapter 2: VMware Configuration Virtual Machine with the SQL Database Installation Configuring the Disk used for the Database Server as Mapped Raw LUN Storage LUNs (Logical Unit Numbers) are commonly shared between virtual machines . 3. In this way.5: Virtualization Configuration Guide (Rev. & 3. the LUN is dedicated to a specific virtual machine.2. You can verify whether a virtual machine is configured as Mapped Raw LUN in the Properties window of a selected virtual machine.Mapped Raw LUN NICE Perform ® Release 3.

from the Inventory drop-down list. & 3. Figure 2-40 Virtual Machine Properties NICE Perform ® Release 3. Disabling the Balloon Driver on page 54. A3) 52 . The Virtual Machine Properties window appears. 3. 3. Log in to the VMware vCenter as described in Logging in to the VMware vCenter on page 18.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Virtual Machine with the VoIP Logger Installation Configuring a virtual machine running the VoIP Logger installation involves: • • • • • Configuring Memory Reservation (below). select Hosts and Clusters.2.1. 2. Increasing the Rx Buffer for the VoIP Logger’s Capture NIC on page 62. To configure memory reservation for a virtual machine running the NICE VoIP Logger: 1. Passive VoIP Logger only: Configuring the VoIP Logger’s Sniffing NIC for Promiscuous Mode on page 59. Select the virtual machine running the VoIP Logger and click Edit Settings. In the VMware vCenter. Capture NIC only: Setting the Priority for the VoIP Logger’s Capture NIC on page 57. Configuring Memory Reservation The Memory Reservation for the virtual machine running the VoIP Logger must be configured with the same value that was allocated to the virtual machine.5: Virtualization Configuration Guide (Rev.

& 3. and Advanced CPU resource types are listed.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation The CPU.Resources 5. Figure 2-41 Virtual Machine Properties . Disk. Network Adapter resource types for the selected virtual machine are displayed. Memory.5: Virtualization Configuration Guide (Rev. Disk. Click the Resources tab. A3) 53 . 3. The CPU.1. Memory. Select Memory.2. The Resource Allocation area displays the configurable parameters for the Memory resource. NICE Perform ® Release 3. 4.

swaps them to its own virtual disk. NICE Perform ® Release 3. This is the preferred method for reclaiming memory from virtual machines. To enable the NICE VoIP Logger to run properly on the virtual machine. configure parameters as described below: • • • Shares Reservation (MB) Limit Normal At least 2048 MB Unlimited 6. the Balloon Driver reclaims memory from the virtual machines in cooperation with the VMware Tools (vmmemctl driver) and the guest operating systems. This section describes how to disable the Balloon Driver.1. A3) 54 .5: Virtualization Configuration Guide (Rev. When memory is tight. causing the guest operating system to invoke its own native memory management algorithms. the guest operating system decides which particular pages of memory to reclaim. This proprietary technique provides predictable performance that closely matches the behavior of a native system under similar memory constraints. Click OK. and if necessary. The system inflates the balloon driver to increase memory pressure within the virtual machine.2. the Balloon Driver must be disabled. & 3. Disabling the Balloon Driver In the VMware configuration. since it reclaims the memory that is considered least valuable by the guest operating system. 3.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-42 Memory Reservation for the Virtual Machine Running NICE VoIP Logger In the Resource Allocation area.

right-click the virtual machine and click Edit Settings. & 3.5: Virtualization Configuration Guide (Rev.1. 2. NICE Perform ® Release 3. Click the Options tab and select General. The Virtual Machine Properties window appears. 4.2.General Parameters 6. Log in to the ESX Server host as a user with administrative rights. On the Inventory panel. Shut down the virtual machine. 5. The Configuration Parameters window appears. Figure 2-43 Virtual Machine Properties Window . Using vSphere Client. connect directly to the ESX Server host on which the virtual machine resides. 3.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation To disable the Balloon Driver: 1. 3. Click Configuration Parameters. A3) 55 .

A3) 56 . NICE Perform ® Release 3. Click OK. 9. & 3. 3. type sched. 10. In the Value area.maxmemctl.2. Click Add Row. type 0.mem.5: Virtualization Configuration Guide (Rev.1. 8.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-44 Configuration Parameters Window Value area Type zero (0) Add Row 7. In the text field.

Figure 2-45 Network Connections Window . open the Network Connections window. select Advanced Settings. You set the NIC priority for the VoIP Logger’s capture NIC in the virtual machine’s operating system. From the Advanced menu. 2. 3. & 3.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Setting the Priority for the VoIP Logger’s Capture NIC The capture NIC must be set to second in priority. This section describes how to set NIC priority. To set the priority for the VoIP Logger’s capture NIC: 1.Advanced > Advanced Settings The Advanced Settings window appears. NICE Perform ® Release 3.2. From the virtual machine’s operating system. A3) 57 . you may need to reset the NIC’s priority.1. If you changed your virtual machine’s NIC type as described in Changing the NIC Type to Enhanced VMXNET / VMXNET2 (Enhanced) on page 37 or Changing the VoIP Logger’s Capture NIC Type to E1000 on page 40.5: Virtualization Configuration Guide (Rev.

NICE Perform ® Release 3.1. 5. A3) 58 . 3.2.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-46 Network Connections . In the Connections area.Advanced Settings The network adapter designated for capturing audio must appear second in the list 3. Click OK.5: Virtualization Configuration Guide (Rev. Restart the virtual machine. & 3. set the network adapter that is designated for capturing your audio (RTP) to appear second in the list. 4.

A3) 59 . Log in to the VMware vCenter as described in Logging in to the VMware vCenter on page 18. The Passive VoIP Logger uses a NIC (Network Interface Card) for sniffing audio on the network.5: Virtualization Configuration Guide (Rev. Select the ESX Server and click the Configuration tab. the NIC must be configured for Promiscuous mode. TIP What is Promiscuous mode? In a network. 3. & 3. the ESX server must be configured with this dedicated NIC. In the VMware environment. The installed NICs are listed. Select Networking. Promiscuous mode is often used to monitor network activity.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Configuring the VoIP Logger’s Sniffing NIC for Promiscuous Mode If you are running a Passive VoIP Logger on a virtual machine. 4. promiscuous mode is a mode of operation in which every data packet transmitted can be received and read by a network adapter. In an Ethernet local area network (LAN). promiscuous mode allows a network device to intercept and read each network packet that arrives in its entirety. To configure the sniffing NIC for promiscuous mode: 1. and to enable sniffing. Promiscuous mode must be supported by each network adapter as well as by the input/output driver in the host operating system. Click this virtual switch’s Properties button. for monitoring network usage). 2. Locate the virtual switch whose NIC will be used for sniffing.1.2. This VoIP Logger configuration requires at least one dedicated NIC for sniffing the audio. This mode of operation is sometimes given to a network snoop server that captures and saves all packets for analysis (for example. you must perform this procedure. 3. NICE Perform ® Release 3.

Configuration Tab The Properties window for the sniffing NIC appears.1. 3.5: Virtualization Configuration Guide (Rev. NICE Perform ® Release 3. & 3.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-47 VMware vCenter . A3) 60 .2.

Click Edit. 7. Click the Security tab and from the Promiscuous Mode drop-down list.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-48 NIC Properties Window 5. & 3. The ESX server’s dedicated NIC is now configured for Promiscuous mode. select Accept. The Edit Properties window appears. Click OK.1. NICE Perform ® Release 3.5: Virtualization Configuration Guide (Rev. Figure 2-49 Edit Properties Window 6.2. A3) 61 . 3.

5 on page 66 IMPORTANT Make sure that the network interface card designated for capturing audio is approved by NICE.5: Virtualization Configuration Guide (Rev. You can increase the Rx buffer for the VMXNET2 (Enhanced) card in one of the two following ways: • • Increasing the Rx Buffer in the .Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Increasing the Rx Buffer for the VoIP Logger’s Capture NIC This section describes: • • ESX V4.0 on page 62 ESX V3.0 The Rx buffer must be increased for every network interface card that is configured to capture voice via sniffing.2.0: Increasing the Rx Buffer for the VMXNET2 (Enhanced) Card for ESX V4. Increasing the network adapter’s Rx buffer improves the VoIP Logger’s performance and reduces packet loss. & 3. The dropped packets may be reduced by increasing the Rx buffers for the virtual network driver. 3.5: Increasing the Rx Buffer for the E1000 Card for ESX V3. the maximum Rx buffer supported by VMware for adapter type VMXNET2 (Enhanced) for ESX Version 4 is 512. While the default Rx buffer is 150. NICE Perform ® Release 3. that is. A3) 62 . See Virtual Machine Network Interface Card (NIC) Configuration on page 35.1. Increasing the Rx Buffer for the VMXNET2 (Enhanced) Card for ESX V4.vmx Configuration File -or- Increasing the Rx Buffer in the Virtual Machine’s Properties Window TIP From VMware KB1010071: Receive packets might be dropped at the virtual switch if the virtual machine's network driver runs out of receive (Rx) buffers. a buffer overflow.

However. before the buffer is changed.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Increasing the Rx Buffer in the .1.2. Shut down the virtual machine that is running the VoIP Logger. you must shut down the virtual machine. Open the . In the virtual machine’s Properties window. A3) 63 . Increasing the Rx Buffer in the Virtual Machine’s Properties Window To increase the Rx buffer in the virtual machine’s Properties window: 1. 3. NICE Perform ® Release 3.numRecvBuffers=512 TIP You can also change the buffer by using the Edit option.vmx configuration file and add the following line: Ethernet<x>. select the Options tab. Save and close the file.numRecvBuffers=<value> where <x> refers to your virtual NIC and <value> refers to the new value for the Rx buffer size.5: Virtualization Configuration Guide (Rev. 2.vmx Configuration File To increase the Rx buffer in the . 3. 2. & 3. Shut down the virtual machine that is running the VoIP Logger.vmx configuration file: 1. EXAMPLE: Ethernet1.

2. In the Value field. enter Ethernet1. Click Add Row. 4. NICE Perform ® Release 3.numRecvBuffers. See Figure 2-51.5: Virtualization Configuration Guide (Rev. enter 512. In the Parameter field. Verify the number of the Ethernet that is used for the sniffing.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-50 Virtual Machine Properties Window 3.1. 5. Select General. 6. A3) 64 . Then click Configuration Parameters. & 3. 3.

1.numRecvBuffers Value 7. A3) 65 . NICE Perform ® Release 3.5: Virtualization Configuration Guide (Rev. & 3. Click OK.ethernet1.2. 3.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-51 Configuration Parameters Window .

The Properties window appears. From the operating system.Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Increasing the Rx Buffer for the E1000 Card for ESX V3. Right-click the network adapter that was designated for capturing audio (RTP). 3. In the General tab. See Figure 2-53.5 You increase the Rx buffer for the E1000 card in the virtual machine’s operating system. Figure 2-54.2. 4. and select Properties. Figure 2-52 Network Connections . To increase the Rx buffer for the E1000 network interface card: 1. NICE Perform ® Release 3. Enter 512.Capture NIC Properties Window 3. Define values as described below: • • • Number of Receive Buffers Number of Coalesce Buffers Transmit Descriptors Enter 4096. Then click Advanced.5: Virtualization Configuration Guide (Rev. 2. & 3.1. Enter 512. open the Network Connections window. click Configure. A3) 66 . and Figure 2-55.

& 3.5: Virtualization Configuration Guide (Rev.Number of Coalesce Buffers Set Number of Coalesce Buffers to 512 NICE Perform ® Release 3.1.Number of Receive Buffers Set Number of Receive Buffers to 4096 Figure 2-54 Network Connection Properties . 3. A3) 67 .Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-53 Network Connection Properties .2.

Chapter 2: VMware Configuration Virtual Machine with the VoIP Logger Installation Figure 2-55 Network Connection Properties .2.Number of Transmit Descriptors Set Number of Transmit Descriptors to 512 5. A3) 68 . 3.5: Virtualization Configuration Guide (Rev. & 3. Restart the virtual machine.1. NICE Perform ® Release 3.

The VMware High Availability offers the following advantages over the traditional failover solution: • Reduced hardware cost and setup – When you use VMware High Availability. • • Implications of High Availability in the Nice Perform Environment When an ESX server fails and High Availability is configured: • • • Virtual Machines with NICE Perform components running on this host are shut down unexpectedly and the same virtual machines are restarted on other ESX servers. Downtime is determined by the time the virtual machines take to restart on the other ESX servers. NICE Perform downtime operates as follows: • • • NICE Perform System downtime changes according to the specific components that failed.Chapter 2: VMware Configuration VMware High Availability VMware High Availability VMware High Availability offers the following: • • • Provides automatic restart of virtual machines in case of physical host failures. have availability without increased computing needs. and monitored using vCenter Server VMware High Availability provides high availability for applications running on virtual machines. all applications that start automatically at restart. VMware High Availability can help recover from that failure. A3) 69 . NICE Perform ® Release 3.2. VMware Distributed Resource Scheduler (DRS) integration – If a host has failed and virtual machines have been restarted on other hosts. NICE Perform resumes functioning within a short period of time. managed. NICE Perform system recovery time is determined by the time the components take to resume functioning after restart. you must have sufficient resources to back up the number of hosts you need to guarantee. in the event of a failover. In the event of a failover. In the event of a physical server failure. Provides high availability while reducing the need for passive standby hardware and dedicated administration Is configured. & 3. Virtual machines are restarted. affected virtual machines are automatically restarted on other production servers with spare capacity.5: Virtualization Configuration Guide (Rev. In the event of a failover. This may take several minutes. Increased application availability – Because the virtual machine can recover from hardware failure. DRS can provide migration recommendations or migrate virtual machines for balanced resource allocation. the vCenter Server system automatically manages resource and configuration clusters. even if the application itself is not a clustered application. If one or both of the source and destination hosts of a migration fail. However.1. 3. This may vary between 2-30 minutes.

Chapter 2: VMware Configuration VMware High Availability

Configuration Guidelines to VMware High Availability
The VMware administrator is responsible for the High Availability configuration.

General recommendations for High Availability configurations are as follows:

• • • • •

ESX Servers are configured in a Cluster. The Cluster is configured with High Availability enabled. Virtual Machines with NICE Perform servers must reside on shared storage. All ESX servers in the Cluster must have access to the shared storage. ESX networking servers should be configured with the identical name and VLAN access to enable the virtual machines to access the same VLAN after having restarted on another ESX server.

Virtual Machine restart priority options are as follows:

Three (3) priority levels can be set for each Virtual Machine.

• • • • •

High Medium Low

The default priority setting is Use Cluster Settings – set to Medium. NICE Perform virtual machine recommendations:

• •

Database server – High Other servers – leave default settings

See Sample Cluster with High Availability Settings on page 71.

NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3)

70

Chapter 2: VMware Configuration VMware High Availability

Sample Cluster with High Availability Settings
This section describes the recommended settings for running NICE Perform in a VMware cluster configured for High Availability. Referring to Figure 2-56, a cluster called Consolidation has been defined. ESX servers and virtual machines have been configured on this cluster. DRS (Distributed Resource Scheduler) and HA (High Availability) have been enabled.
Figure 2-56 vCenter - High Availability Configuration

DRS & HA have been enabled

To access cluster features, select the cluster and click Edit Settings Virtual machines in the cluster ESX servers configured in the cluster

A cluster called Consolidation has been created

NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3)

71

Chapter 2: VMware Configuration VMware High Availability

Configuring High Availability Settings
To configure High Availability: 1. Select the cluster and click Edit Settings.

The Cluster Settings window appears. 2. Select the Cluster Features tab. In the Features area, select Turn On VMware HA and Turn On VMware DRS. See Figure 2-57.
Figure 2-57 Cluster Settings Window - Cluster Features Tab

3. Select the VMware HA tab. a. In the Host Monitoring Status area, select Enable Host Monitoring. b. In the Admission Control area, select Enable: Do not power on VMs that violate availability constraints. c. In the Admission Control Policy area, select Host failures cluster tolerates and

define a policy type. See Figure 2-58.

NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3)

72

2. 3. Set the VM Restart Priority for the virtual machine running the Database Server components to High.Medium. & 3. See Figure 2-59.1.VMware HA Tab 4. All other NICE Perform virtual machine components can remain with default setting .5: Virtualization Configuration Guide (Rev. A3) 73 .Chapter 2: VMware Configuration VMware High Availability Figure 2-58 Cluster Settings Window . Click the Virtual Machine Options tab. NICE Perform ® Release 3. 5.

A3) 74 .5: Virtualization Configuration Guide (Rev. 3. & 3.VMware HA Tab NICE Perform ® Release 3.1.Chapter 2: VMware Configuration VMware High Availability Figure 2-59 Cluster Settings Window .2.

..... 81 Virtual Machine Time Synchronization ..... 79 Virtual Machine Settings........................5: Virtualization Configuration Guide (Rev...... A3) 75 .....1............ & 3....................................................3 Microsoft Hyper-V Configuration Overview .......................................... 76 Configuring Hyper-V ............................... 77 Hyper-V Host Server Disk Management .........2........................ 76 Virtual Network settings. 87 This chapter describes how to configure the Microsoft Hyper-V Server 2008 R2 for NICE Perform............... 78 Virtual Machine File Location for a New Virtual Machine ................. NICE Perform ® Release 3............................. 3.

used for the connection between the host server and the LAN. A3) 76 .2. network) can be allocated and configured either by the Hyper-V Manager on the host server or via the management application called SCVMM (System Center Virtual Machine Manager 2008 R2) which is installed on Windows 2008 server in the same Domain as the Hyper-V server.Chapter 3: Microsoft Hyper-V Configuration Overview Overview The Microsoft Hyper-V Server 2008 R2 is designed to run multiple virtual machines that facilitate hosting multiple operating systems running NICE Perform components. memory.5: Virtualization Configuration Guide (Rev. For supported NICE Perform components. Figure 3-1 Network Interface Card Settings NICE Perform ® Release 3. One of the network cards is set for management. CPU. and specifications. 3. see the Design Considerations and Certified Servers guides. At least one NIC is designated to connect between virtual machines. This network connection is assigned the IP of the host server (Windows 2008 R2). Infrastructure specifications.1. & 3. Other NICs can be used as additional connections for the virtual machines or for a iSCSI connection to shared storage. Configuring Hyper-V This section describes the following topics: • • • • Network Adapter Configuration on page 76 Hyper-V Host Server Disk Management on page 78 Virtual Machine File Location for a New Virtual Machine on page 79 Virtual Machine Settings on page 81 Network Adapter Configuration Figure 3-1 describes the Network Interface Card (NIC) configurations and settings for the Microsoft Hyper-V Manager running on the Windows 2008 R2 with the Hyper-V installation. the virtual machines’ resources (disk. The configuration of this NIC is done by the Virtual Network Settings. configuration requirements.

Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Virtual Network settings The virtual network that is used by all virtual machines is connected to a physical NIC that is connected to the LAN.2. Figure 3-2 Virtual Network Settings NICE Perform ® Release 3. Several NICs may be configured in order to split the network load between the virtual machines.1. 3.5: Virtualization Configuration Guide (Rev. See Figure 3-2. & 3. Each of the NICs must be configured for a specific virtual machine. A3) 77 .

3. you can see all available disks – Local and Storage LUNs. Note that you only format the Storage disks that are for general use – contain the virtual machine’s HD files (. Figure 3-3 Disk Management NICE Perform ® Release 3.5: Virtualization Configuration Guide (Rev. should remain in Offline status so they will be available as dedicated disks for the SQL virtual machines. The LUNs that should be mapped as dedicated physical disks for the SQL servers Data and Log (total of 4 LUNs for DB and DM). & 3.2.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Hyper-V Host Server Disk Management In the Disk Management view.1.VHD). See Figure 3-3. A3) 78 .

The default location can be set in the Hyper-V Settings window.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Virtual Machine File Location for a New Virtual Machine When you create a new virtual machine or add a virtual disk. See Figure 3-4 and Figure 3-5. A3) 79 . the configuration files and the VHD (virtual hard disk file) must be configured to reside on the Shared Storage and not on the local disks of the host server. & 3. Figure 3-4 Location of the Virtual Hard Disk Files NICE Perform ® Release 3.5: Virtualization Configuration Guide (Rev. 3.1.2.

A3) 80 . & 3.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Figure 3-5 Default Location for Configuration Files NICE Perform ® Release 3. 3.1.2.5: Virtualization Configuration Guide (Rev.

All other disks will be defined as SCSI under SCSI controller. Memory allocation – RAM assigned to the virtual machine. see the NICE Perform Certified Servers Guide. 3.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Virtual Machine Settings The settings of each virtual machine contain the following parameters: • • • • • • Number of virtual CPU processors. This is selected when initially configuring a new virtual machine or when adding new virtual disk. • • • • See Examples of Virtual Machine Settings on page 82.1.2. After you complete setting up the operating system.5: Virtualization Configuration Guide (Rev. Network – the network adapter (one or more) assigned to the virtual machine. A3) 81 . For supported Nice Perform components and specifications of resources to assign to each virtual machine. Do not save virtual machine snapshots. NICE Perform ® Release 3. Virtual disks – the disk that contains the operating system must be defined as IDE under IDE Controller. see the virtual machine Settings > Management. Snapshots can compromise the performance of your virtual machine. To verify if they are already installed. NOTE • To optimize performance. it is recommended to install the Integration Services. the recommendation is to map two physical disks (path through) for SQL data and SQL log. More SCSI controllers can be added as well. One SCSI controller can be assigned to more then one hard drive. For SQL servers running on virtual machines. all virtual disks must be created with a fixed size. & 3. Make sure that Hyper-V Integration Services have been installed on each virtual machine.

& 3.5: Virtualization Configuration Guide (Rev.1.2.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Examples of Virtual Machine Settings Figure 3-6 Virtual Machine Processor – No Reservation or Limit NICE Perform ® Release 3. A3) 82 . 3.

3.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Figure 3-7 Virtual Machine Memory – RAM Figure 3-8 Virtual Machine . & 3.2.1.Network NICE Perform ® Release 3. A3) 83 .5: Virtualization Configuration Guide (Rev.

IDE for the Operating System Figure 3-9 Virtual Machine Hard drive – IDE for OS NICE Perform ® Release 3.5: Virtualization Configuration Guide (Rev. & 3.2.1. 3. A3) 84 .Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Virtual Machine Hard Drive Settings .

& 3.1. 3. the Hard Drive must be added under the SCSI Controller. A3) 85 .2. The location of this Hard Drive file (VHD) should be on the Shared Storage.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Virtual Machine Hard Drive Settings – SCSI for Partitions Without the Operating System For partitions other than C: (operating system).5: Virtualization Configuration Guide (Rev. Figure 3-10 Virtual Machine Hard Drive – SCSI for Partitions Without the Operating System NICE Perform ® Release 3.

Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Virtual Machine Database Server Settings The virtual machine used for database servers (DB or DM) with SQL – the Disks for SQL Data files and SQL Log files must be added as Physical Hard Drive. & 3.2. A3) 86 . The list of physical drives contains the LUNs that appear in the disk management in offline status. Two dedicated LUNs are needed per database server (one for Data and one for Log). 3. Figure 3-11 Virtual Machine Hard Drive for Database Server NICE Perform ® Release 3.1.5: Virtualization Configuration Guide (Rev.

1. select Time Synchronization.Chapter 3: Microsoft Hyper-V Configuration Configuring Hyper-V Virtual Machine Time Synchronization Virtual machine time synchronization must be set as follows: • • • All virtual machines must be time-synchronized to the host Hyper-V server.5: Virtualization Configuration Guide (Rev. This eliminates the need to configure NTP for each virtual machine. & 3.2. 3. To time-synchronize your virtual machines: • In each virtual machine. A3) 87 . in the Integration Services window. All host Hyper-V servers must be time-synchronized to your organization NTP.Time Synchronization NICE Perform ® Release 3. Figure 3-12 Virtual Machine Settings . The Windows Time Service must be disabled.

Blank page for double-sided printing. .

............................................. 91 PCoIP Display Protocol ........... 98 Client Login..................................... NICE Perform ® Release 3.................... 91 Overview of View Manager ........ 99 Troubleshooting......... 96 Desktop Delivery Protocol ................................. A3) 89 .... 94 Citrix XenDesktop......4 Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications IN THIS CHAPTER Overview .................1........................................ 101 This chapter describes guidelines to installing and accessing NICE applications in the VDI (Virtual Desktop Infrastructure) environment..... 96 Overview of XenDesktop .......................5: Virtualization Configuration Guide (Rev..................................................................2.. & 3.................................................................................. 3............. 90 VMware View ............................................ 90 Supported Solutions ............. 93 Client Login ... 98 Guidelines for NICE Client-Side Applications Running on a Citrix XenDesktop ............... 92 Guidelines for NICE Client-Side Applications Running on a VDMware Virtual Desktop ....................................................

A3) 90 . The client device may use an entirely different hardware architecture than that used by the projected desktop environment. The desktop virtualization model allows the use of virtual machines to let multiple network subscribers maintain individualized desktops on a single.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Overview Overview Desktop virtualization involves encapsulating and delivering either access to an entire information system environment or to the environment itself via a remote client device. 3. Users may be geographically scattered. The term was coined by VMware Inc. a wide area network. centrally located computer or server.5: Virtualization Configuration Guide (Rev. Supported Solutions Supported VDI solutions for NICE client-side applications: • VMWare: • • • • • VDM VMware View Citrix: Citrix Xen Desktop Citrix XenApplications (also known as Citrix Presentation Server) For a complete list of components supported by NICE Perform. see the Certified Servers Guide. business. The central machine may operate at a residence. sometimes referred to as server-based computing (SBC). or the public Internet. Virtual Desktop Infrastructure (VDI) is a method of hosting a desktop operating system within a virtual machine (VM) running on a centralized server. and may also be based upon an entirely different operating system. & 3. but all must be connected to the central machine by a local area network. NICE Perform ® Release 3. or data center. VDI is a variation on the client/server computing model.1.2.

Windows Vista or Windows 7 operating systems) running on the VMware ESX servers. allowing administrators to create desktops on virtual machines running on VMware ESX server.2. A3) 91 . Former versions of VMware View are called VDM (Virtual Desktop Manager). The desktops are managed and provisioned to the client by the VMware View Manager. back-end physical systems. Figure 4-1 Schematic Diagram of the View Manager Environment Thin Clients NICE Perform Servers Network View Connection Server LAN VMware vCenter Server Virtual Desktop ESX Host Virtual Desktop Virtual Desktop Virtual Desktop NICE Perform ® Release 3. or terminal servers. 7) to the client.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications VMware View VMware View VMware VDI called VMware View is a solution for delivering virtualized desktops (for example: desktop with Windows XP. View Manager utilizes your existing Active Directory infrastructure for user authentication and management. and then deploy these virtual desktops to end users. controlled by the VMware vCenter. & 3. Figure 4-1 provides a high-level view of the View Manager environment and its main components. Once a desktop has been created. The virtual desktops are virtual machines (with Windows XP. In addition.5: Virtualization Configuration Guide (Rev.1. Web-based or locally installed client software enables authorized end users to securely connect to centralized virtual desktops. Overview of View Manager View Manager integrates with VMware vCenter Server. 3. Vista.

0 (or higher) administrator per Desktop or Pool of Desktops. Microsoft RDP is also available as before. 3. Former versions of VMware VDI (VDM and View3. A3) 92 .2. PCoIP can compensate for an increase in latency or a reduction in bandwidth. To configure the PCoIP display protocol: • Open the VMware View Manager and set the Default display protocol to PCoIP. audio. improved. and enhanced protocol provided with VMware View 4. PCoIP is a new. Configuring the PCoIP Display Protocol It is recommended to set PCoIP as the default display protocol in the View Manager 4.1) used Microsoft RDP protocol for connecting the client to the desktop. and video content for a wide range of users on the LAN or across the WAN. PCoIP is supported as the display protocol for VMware View desktops with virtual machines and with physical machines that contain Teradici host cards.vmware. PCoIP provides an optimized PC experience for the delivery of images. PCoIP should be used for VMware View 4 (and higher). to ensure that end users can remain productive regardless of network conditions.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications VMware View PCoIP Display Protocol The Display Protocol is the method used for delivering the desktop remotely to the client.5: Virtualization Configuration Guide (Rev.pdf NICE Perform ® Release 3. see the VMware documentation guide http://www. Figure 4-2 VMware View Manager .Web Interface NOTE For information about View Manager administration.com/pdf/view40_admin_guide. & 3.1.

NICE Player Codec pack. 3. see the Certified Servers Guide. standalone Player. & 3. Desktop Analytics Agent) can be installed on the template before using it for deploying new virtual machines.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications VMware View Guidelines for NICE Client-Side Applications Running on a VMware Virtual Desktop • • For list of components supported by NICE Perform. A3) 93 .5: Virtualization Configuration Guide (Rev. ScreenAgent. Specific configurations • ScreenAgent installation • • • Installation mode: WorkStation mode Use the default capture component installation mode . Reporter Viewer.Hooking & Scraper methods For installation via template. select the Unique Agent User Name registration method NICE Perform ® Release 3. • • Component installation – NICE Perform components are installed on the virtual machine the same as they would be installed on physical desktops. ROD Desktop.2. Installation via template NICE client-side applications for the agent desktop (such as NICE Applications’ Set Security.1.

From the Start menu. To log in to a virtual desktop via the VMware View Client: 1. 3.1.5: Virtualization Configuration Guide (Rev. select Programs > VMware > VMware View Client. A3) 94 . Figure 4-3 VMware View Client Login Window 2.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications VMware View Client Login You log into the View Connection Server and connect to a virtual desktop in via the VMware View Client (requires installing VMware View Client software on the client machine). The VMware View Client login window appears. The Connection Server login window appears. NOTE Web Login is not supported for NICE client-side components.2. Enter the IP address or hostname of the View Connection Server at your site and click Connect. NICE Perform ® Release 3. & 3.

Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications VMware View Figure 4-4 VMware View Client Login Window 3. To select PCoIP.1. Figure 4-5 Selecting PCoIP in the Login Window 4. A3) 95 . & 3.2. 3. NICE Perform ® Release 3. TIP PCoIP can also be selected during client login to the virtual desktop. press on the VMware View Connection Server name’s arrow and select Display Protocol > PCoIP. Click Connect.5: Virtualization Configuration Guide (Rev. Available desktops on the VMware View Connection Server are displayed. Enter your username and password and click Login.

Windows Vista. 7) to the client. XenDesktop simplifies desktop management by using a single image to deliver personalized desktops to users and enables administrators to manage service levels with built-in desktop performance monitoring. to manage user personalization settings in virtualized or physical Windows environments. the agent enables direct ICA (Independent Citrix online plug-in . Overview of XenDesktop Citrix XenDesktop is a desktop virtualization system that centralizes and delivers Microsoft Windows XP. Desktop Delivery Controller .1. the Citrix online plug-in (formerly "Citrix Desktop Receiver") enables direct ICA connections from user devices to virtual desktops. This ensures that performance never degrades.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Citrix XenDesktop Citrix XenDesktop Citrix XenDesktop is Citrix VDI solution for delivering virtualized desktops (for example: desktop with Windows XP. It controls the state of the desktops. The open architecture of XenDesktop offers choice and flexibility of virtualization platform and endpoints. manages the assembly of users' virtual desktop environments. providing users with pristine.Installed on servers in the data center.5: Virtualization Configuration Guide (Rev. yet personalized. & 3. Figure 4-6 on page 97 provides a high-level view of the XenDesktop environment. Unlike other desktop virtualization alternatives. and brokers connections between users and their virtual desktops. desktops each time they log on. starting and stopping them based on demand and administrative configuration. A3) 96 . Citrix XenDesktop provides a complete virtual desktop delivery system by integrating several distributed components with advanced configuration tools that simplify the creation and real-time management of the virtual desktop infrastructure. Computing Architecture) connections between the virtual desktop and user devices. in some editions. the controller authenticates Virtual Desktop Agent . while the high speed delivery protocol provides unparalleled responsiveness over any network. users. 3. NOTE The descriptions in this section were taken from the Citrix documentation. Virtual desktops are dynamically assembled on demand. NICE Perform ® Release 3. XenDesktop delivers a high definition user experience over any connection including high latency wide area networks. Vista or 7 virtual desktops as a service to users anywhere. Desktop Delivery Controller also includes Profile management.2.Installed on user devices.Installed on virtual desktops.

Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Citrix XenDesktop Figure 4-6 Schematic Diagram of the XenDesktop Environment Thin Clients NICE Perform Servers Network DDC Desktop Delivery Controller LAN Xen Server Virtual Desktop Virtual Desktop Virtual Desktop Virtual Desktop NICE Perform ® Release 3.2. & 3. A3) 97 .1. 3.5: Virtualization Configuration Guide (Rev.

ScreenAgent. NICE Player Codec pack. standalone Player.2. Guidelines for NICE Client-Side Applications Running on a Citrix XenDesktop • • For list of supported components see the Certified Servers Guide. It enables the user with High Definition experience.1. Reporter Viewer.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Citrix XenDesktop Desktop Delivery Protocol Independent Computing Architecture (ICA) is Citrix proprietary protocol used to deliver the virtual machine desktop to the client.5: Virtualization Configuration Guide (Rev. 3. ROD Desktop.2 – UP 3.1 – UP 3. Specific configurations • NICE ScreenAgent installation • • • • • Installation mode: WorkStation mode Use default Capture component installation mode . • • Component installation – NICE Perform components are installed on the virtual machine the same as they would be installed on physical desktops. Installation via template NICE client-side applications for the agent desktop (such as NICE Applications’ Set Security. A3) 98 .19 or later NICE Perform Release R3. & 3.11 or later NICE Perform ® Release 3. Desktop Analytics Agent) can be installed on the template before using it for deploying new virtual machines.2.1.Hooking & Scraper methods) For installation on template select Unique Agent User Name registration method Limitations NICE ScreenAgent support • • NICE Perform Release 3.

Enter your username and password and click OK. select Programs > Citrix > Online plug-in.1. Figure 4-7 Citrix Online Plug-In 2. & 3. NICE Perform ® Release 3. The Citrix online plug-in login window appears. 3.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Citrix XenDesktop Client Login You can log in to the Desktop Delivery Controller and connect to a virtual desktop in two ways: • • Run the Online Plug-in that was installed on the client machine Web login Logging in via the Online Plug-In To log in to the Desktop Delivery Controller via the Online Plug-in: 1. From the Start menu.2.5: Virtualization Configuration Guide (Rev. A3) 99 .

Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Citrix XenDesktop Logging in via Web To log in to the Desktop Delivery Controller via Web login: 1.2. 3. & 3.5: Virtualization Configuration Guide (Rev. NICE Perform ® Release 3.1. Figure 4-8 Citrix XenDesktop Logon Window 2. In a Web browser. enter the following: http://<Desktop Delivery Controller IP address/hostname>/Citrix/DesktopWeb/auth/login. A3) 100 .aspx The Citrix XenDesktop Logon window appears. Enter your username and password and click OK.

Figure 4-9 Citrix Presentation Server Console . A3) 101 .1. Navigate to Farm > Policies. NICE Perform ® Release 3. in Citrix Xen Desktop Delivery Controller server.5: Virtualization Configuration Guide (Rev. Navigate to Client Devices > Resources > Audio > Turn off speakers and select Not Configured. do the following: 1. Select a policy and open its properties. & 3. 3.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Citrix XenDesktop Troubleshooting Playback Issue If the virtual desktop OS does not recognize the client’s local speakers audio device. 2.Select Properties 4.2. Open the Citrix Presentation Server console. 3.

2. 3. & 3.5: Virtualization Configuration Guide (Rev.Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications Citrix XenDesktop Figure 4-10 Citrix Presentation Server Console .1. A3) 102 .Turn off speakers NICE Perform ® Release 3.

NICE Perform ® Release 3.......... & 3... NOTE The process of converting a NICE physical machine into a NICE virtual machine is supported for a VMware vSphere version only............2..5: Virtualization Configuration Guide (Rev........... A3) 103 ............. 3..1 ..... 104 Installing VMware Converter 4...........1.................A Converting a Physical Machine into a VMware Virtual Machine Overview ........ Converting a NICE physical machine into a lower VMware version has not been certified.. 105 Converting the Physical Machine into a Virtual Machine 109 This appendix describes how to convert a physical machine into a VMware virtual machine.0......

1 2. You have administrative privileges to the ESX machine.0. & 3. The maximum disk size on the physical server is smaller than the maximum disk size that you will create on the ESX server. You have administrative privileges to the physical machine.1. NICE Perform ® Release 3. using VMware vCenter Converter Version 4. All NICE services running on the physical machine have been stopped. Before performing this procedure. see the Certified Servers Guide.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Overview Overview This appendix describes the process of converting a physical machine into a virtual machine running ESX Version 4. Converting a physical machine into a virtual machine involves the following steps: 1.0.5: Virtualization Configuration Guide (Rev.2.1. For server specifications. 3.0. A3) 104 . Installing VMware Converter 4. ensure that: • • • • • The network speed between all servers and the ESX is 100Mbp or higher. Converting the Physical Machine into a Virtual Machine 3. Defining the New Virtual Machine’s IP Address IMPORTANT The conversion is performed at the rate of 25GB per hour.

1 Installing VMware Converter 4.0.1 VMware Converter 4. 3. Click Next. The VMware vCenter License Agreement window appears.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Installing VMware Converter 4.1.0.1: 1. see http://www.1 must be installed on a dedicated machine. A3) 105 .com. Figure A-1 VMware vCenter Converter Welcome Window 2. Run VMware-converter-4. The VMware vCenter Converter Welcome Window appears.2.1-161434.0. For a list of supported operating systems.vmware.0.0. To install VMware Converter 4.5: Virtualization Configuration Guide (Rev.exe. NICE Perform ® Release 3. & 3.

click Change. A3) 106 .2.5: Virtualization Configuration Guide (Rev.1. The Change Current Destination Folder window appears. The Destination Folder window appears. To change the Destination Folder. Figure A-3 VMware vCenter Destination Folder Window 4. & 3. Select I accept the terms in the License Agreement and click Next.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Installing VMware Converter 4.0. 3.1 Figure A-2 VMware vCenter License Agreement Window 3. NICE Perform ® Release 3.

Figure A-5 VMware vCenter Setup Type Window 7. Click Next.1. Enter the new installation path and click OK.0. 6. The Ready to Install window appears. Select Local Installation and click Next.1 Figure A-4 VMware vCenter Change Current Destination Folder Window 5. A3) 107 . & 3. 3. The Setup Type window appears. NICE Perform ® Release 3. The new path appears in the Destination Folder window.5: Virtualization Configuration Guide (Rev.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Installing VMware Converter 4.2.

3. The VMware vCenter Converter is installed. 10. Click Finish.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Installing VMware Converter 4.2. 9. Click Install.1. NICE Perform ® Release 3. A3) 108 . & 3.0. Proceed to Converting the Physical Machine into a Virtual Machine on page 109.1 Figure A-6 VMware vCenter Ready to Install Window 8.5: Virtualization Configuration Guide (Rev.

& 3.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Converting the Physical Machine into a Virtual Machine To convert your physical machine into a virtual machine: 1. On the physical machine. Click Convert Machine.5: Virtualization Configuration Guide (Rev. A3) 109 . 3. shut down all NICE processes. 2.2. NICE Perform ® Release 3. Figure A-7 VMware vCenter Converter Standalone 3. The Specify Source tab appears.1. Open the VMware vCenter Converter Standalone.

& 3. 3.1. A3) 110 . NICE Perform ® Release 3.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Figure A-8 Specify Source Tab 4.5: Virtualization Configuration Guide (Rev. Enter the connection detail for the physical server and click Next. The Standalone Agent Deployment window appears.2.

3. NICE Perform ® Release 3.1. Select Automatically uninstall the files when import succeeds. A Deploying agent message appears.5: Virtualization Configuration Guide (Rev. Click Yes again. & 3. Then click Yes. A3) 111 .Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Figure A-9 Standalone Agent Deployment Window 5. The Specify Destination tab appears. 6.2.

& 3.5: Virtualization Configuration Guide (Rev. 3. Enter the ESX connection details and click Next.Specify Destination Tab (2) NICE Perform ® Release 3. Figure A-11 Specify Destination .Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Figure A-10 Specify Destination Tab (1) 7. The ESX connection details that you entered are displayed.1.2. A3) 112 .

3.2. Figure A-12 View/Edit Options Tab 9. The View/Edit Options tab appears. Click the Data to Copy Edit option. & 3. A3) 113 . Verify all details are correct and click Next. The Data to Copy View/Edit options appear. NICE Perform ® Release 3.1.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine 8.5: Virtualization Configuration Guide (Rev.

Select all devices and click Next. Figure A-14 Devices Tab NICE Perform ® Release 3. A3) 114 .2. & 3.5: Virtualization Configuration Guide (Rev. Information about the devices appears.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Figure A-13 Data to Copy View/Edit Options Tab 10. 3.1.

The Ready to Complete tab appears. NICE Perform ® Release 3. 3. A3) 115 . Figure A-15 Advanced Options 13.2.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine 11. & 3.1. Click Advanced options. Click Next. Select the following: • • • Install VMware tools on the imported virtual machine Remove system restore checkpoints on destination Reconfigure destination virtual machine 14. Configure the following: • • Number of virtual CPUs Ram Memory size 12.5: Virtualization Configuration Guide (Rev.

2. NICE Perform ® Release 3.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Figure A-16 Ready to Complete Tab 15. A3) 116 . 3.1. Verify installation details and click Finish. & 3.5: Virtualization Configuration Guide (Rev. Conversion status is displayed. The conversion process starts.

5: Virtualization Configuration Guide (Rev. 3.1. Wait until the conversion process completes.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Figure A-17 Conversion Status 16.2. NICE Perform ® Release 3. A3) 117 . & 3.

Appendex A: Converting a Physical Machine into a VMware Virtual Machine Converting the Physical Machine into a Virtual Machine Figure A-18 Conversion Completed All components have converted successfully. & 3.2. proceed to Defining the New Virtual Machine’s IP Address on page 119. Restart all NICE services. 3. 18.5: Virtualization Configuration Guide (Rev. A3) 118 .1. NICE Perform ® Release 3. To complete virtual machine definitions. 17.

3. Shut down the physical machine.Appendex A: Converting a Physical Machine into a VMware Virtual Machine Defining the New Virtual Machine’s IP Address Defining the New Virtual Machine’s IP Address To complete the new virtual machine’s definition. 2. you must define its IP address. From the Network Connections window. the new virtual machine will already be a member of the domain. Log onto the guest operating system.5: Virtualization Configuration Guide (Rev.2. open the Properties window for the virtual machine’s NIC and define its IP address. To define the new virtual machine’s IP address: 1.1. 3. & 3. A3) 119 . NICE Perform ® Release 3. NOTE Domain environment: If the physical machine was already defined as part of the domain.

Sign up to vote on this title
UsefulNot useful