Release 3.2
3.1, 3.2, & 3.5
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,216,744 5,274,738 5,289,368 5,325,292 5,339,203 5,396,371
5,446,603 5,457,782 5,911,134 5,937,029 6,044,355 6,115,746 6,122,665
6,192,346 6,246,752 6,249,570 6,252,946 6,252,947 6,311,194 6,330,025
6,542,602 6,615,193 6,694,374 6,728,345 6,775,372 6,785,369 6,785,370
6,856,343 6,865,604 6,871,229 6,880,004 6,937,706 6,959,079 6,965,886
6,970,829 7,010,106 7,010,109 7,058,589 7,085,728 7,152,018 7,203,655
7,240,328 7,305,082 7,333,445 7,346,186 7,383,199 7,386,105 7,392,160
7,436,887 7,474,633 7,532,744 7,545,803 7,546,173 7,573,421 7,577,246
7,581,001 7,587,454 7,599,475 7,631,046 7,660,297 7,664,794 7,665,114
7,683,929 7,705,880 7,714,878 7,716,048 7,720,706 7,725,318 7,728,870
7,738,459 7,751,590 7,761,544 7,770,221 7,788,095 7,801,288 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
For assistance contact your local supplier or nearest NICE Systems Customer Service Center:
EMEA Region: (Europe, Middle East, Africa)
Tel: +972-9-775-3800
Fax: +972-9-775-3000
email: support@nice.com
Israel:
Tel: 09-775-3333
Fax: 09-775-3000
email: support@nice.com
All queries, comments, and suggestions are welcome! Please email: nicebooks@nice.com
For more information about NICE, visit www.nice.com
Revision History
Virtualization Configuration Guide
2
VMware Configuration 17
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Logging in to the VMware vCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
VMware vCenter Server Summary View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Allocating Resources for the Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . .25
Virtual Machine Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Enabling NTP on ESX Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Virtual Machine Snapshot Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Virtual Machine Network Interface Card (NIC) Configuration . . . . . . . . . . . . . . .35
Changing the NIC Type to Enhanced VMXNET / VMXNET2 (Enhanced) . . . . .37
Changing the VoIP Logger’s Capture NIC Type to E1000 . . . . . . . . . . . . . . . . .40
Virtual Machine with the SQL Database Installation . . . . . . . . . . . . . . . . . . . . . .46
Configuring Memory Reservation for the 64-bit Operating System . . . . . . . . . .46
Configuring Memory Reservation for the 32-bit Operating System . . . . . . . . . .48
Configuring the Disk used for the Database Server as Mapped Raw LUN . . . . .51
Virtual Machine with the VoIP Logger Installation . . . . . . . . . . . . . . . . . . . . . . .52
Configuring Memory Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Disabling the Balloon Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Setting the Priority for the VoIP Logger’s Capture NIC . . . . . . . . . . . . . . . . . . .57
Configuring the VoIP Logger’s Sniffing NIC for Promiscuous Mode . . . . . . . . . .59
Increasing the Rx Buffer for the VoIP Logger’s Capture NIC . . . . . . . . . . . . . . .62
Increasing the Rx Buffer for the VMXNET2 (Enhanced) Card for ESX V4.0 .62
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 7
Contents
Increasing the Rx Buffer for the E1000 Card for ESX V3.5 . . . . . . . . . . . . .66
VMware High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Implications of High Availability in the Nice Perform Environment . . . . . . . . . .69
Configuration Guidelines to VMware High Availability . . . . . . . . . . . . . . . . . . . .70
Sample Cluster with High Availability Settings . . . . . . . . . . . . . . . . . . . . . . .71
Configuring High Availability Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
3
Microsoft Hyper-V Configuration 75
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Configuring Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Network Adapter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Virtual Network settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Hyper-V Host Server Disk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Virtual Machine File Location for a New Virtual Machine . . . . . . . . . . . . . . . . . .79
Virtual Machine Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Examples of Virtual Machine Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Virtual Machine Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
4
Virtual Desktop Infrastructure (VDI) for NICE Client-Side
Applications 89
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Supported Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
VMware View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Overview of View Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
PCoIP Display Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Configuring the PCoIP Display Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Guidelines for NICE Client-Side Applications Running on a VDMware Virtual
Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Client Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Citrix XenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Overview of XenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 8
Contents
A
Converting a Physical Machine into a VMware Virtual Machine 103
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Installing VMware Converter 4.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Converting the Physical Machine into a Virtual Machine . . . . . . . . . . . . . . . . .109
Defining the New Virtual Machine’s IP Address . . . . . . . . . . . . . . . . . . . . . . . .119
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 9
Blank page for double-sided printing.
1
Virtualization in the NICE Perform
Environment
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 11
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. Of the benefits of virtualization are the lowering of
hardware expenditures, reducing Total Cost of Ownership by up to 75%, increasing agility and
further automating IT operations. This document provides general guidelines on how to configure
NICE Perform servers in a virtual infrastructure.
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.0.1 on page 105
• Converting the Physical Machine into a Virtual Machine on page 109
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 12
Chapter 1: Virtualization in the NICE Perform Environment
Terms and Abbreviations
Term Description
Balloon Driver Memory reclaimed from virtual machines by cooperation with the
VMware Tools (vmmemctl driver) and guest operating systems.
This is the preferred method for reclaiming memory from virtual
machines, since it reclaims the memory that is considered least
valuable by the guest operating system. The system "inflates" the
balloon driver to increase memory pressure within the virtual machine,
causing the guest operating system to invoke its own native memory
management algorithms. When memory is tight, the guest operating
system decides which particular pages of memory to reclaim, and if
necessary, swaps them to its own virtual disk. This proprietary
technique provides predictable performance that closely matches the
behavior of a native system under similar memory constraints.
ESX Server VMware's enterprise server virtualization platform. Two versions exist
- ESX Server and ESXi Server. The ESXi Server has no service
console and is the thinnest version available. ESX Server has many
optional features like VMotion and VMHA and some built-in features
like the VMFS file system.
Hypervisor Also called virtual machine monitor (VMM), allows multiple
operating systems to run concurrently on a host computer— a feature
called hardware virtualization. It is so named because it is
conceptually one level higher than a supervisor. The hypervisor
presents the guest operating systems with a virtual platform and
monitors the execution of the guest operating systems. In that way,
multiple operating systems, including multiple instances of the same
operating system, can share hardware resources.
LUN Logical Unit Number - Storage LUNs (Logical Unit Numbers) are
commonly shared between virtual machines - each virtual machine
uses a configured section of a LUN.
Memory Reservation Reserving memory for specific purposes. 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, it cannot be
launched. Although a virtual memory function will simulate an almost
unlimited amount of memory, there is always a certain amount of
"real" memory that is needed.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 13
Chapter 1: Virtualization in the NICE Perform Environment
Terms and Abbreviations
Term Description
NIC Teaming NIC teaming is the process of grouping together several physical NICs
into one single logical NIC, which can be used for network fault
tolerance and transmit load balance. The process of grouping NICs is
called teaming. Teaming has two purposes:
• Fault Tolerance: By teaming more than one physical NIC to a
logical NIC, high availability is maximized. Even if one NIC fails,
the network connection does not cease and continues to operate on
other NICs.
• Load Balancing: Balancing the network traffic load on a server
can enhance the functionality of the server and the network. 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.
Promiscuous Mode In a network, promiscuous mode allows a network device to intercept
and read each network packet that arrives in its entirety. This mode of
operation is sometimes given to a network snoop server that captures
and saves all packets for analysis (for example, for monitoring
network usage).
In an Ethernet local area network (LAN), promiscuous mode is a mode
of operation in which every data packet transmitted can be received
and read by a network adapter. Promiscuous mode must be supported
by each network adapter as well as by the input/output driver in the
host operating system. Promiscuous mode is often used to monitor
network activity.
Resource Pools Use resource pools to hierarchically partition available CPU and
memory resources. Each standalone host and each DRS cluster has an
(invisible) root resource pool that groups the resources of that host or
cluster. The root resource pool is not displayed because the resources
of the host (or cluster) and the root resource pool are always the same.
Rx Buffer Used to reduce Logger packet loss and improve performance.
If the virtual machine's network driver runs out of receive (Rx)
buffers, that is, a buffer overflow occurs, receive packets could be
dropped at the virtual switch. The number of dropped packets can be
reduced by increasing the virtual network driver’s Rx buffers.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 14
Chapter 1: Virtualization in the NICE Perform Environment
Terms and Abbreviations
Term Description
VMware ESX Server is managed by the VMware Infrastructure Client. Its
vCenter/Virtual centralized management platform is called Virtual Center or VMware
Center vCenter.
VMware DRS VMware DRS (Distributed Resource Scheduler) is a utility that
balances computing workloads with available resources in a
virtualized environment. The utility is part of a virtualization suite
called VMware Infrastructure 3.
With VMware DRS, users define the rules for allocation of physical
resources among virtual machines. The utility can be configured for
manual or automatic control. Resource pools can be easily added,
removed or reorganized. If desired, resource pools can be isolated
between different business units. If the workload on one or more
virtual machines drastically changes, VMware DRS redistributes the
virtual machines among the physical servers. If the overall workload
decreases, some of the physical servers can be temporarily
powered-down and the workload consolidated.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 15
Blank page for double-sided printing.
2
VMware Configuration
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 17
Chapter 2: VMware Configuration
Overview
Overview
The VMware platform, based on the ESX server, is designed to run multiple virtual machines that
facilitate hosting multiple operating systems running NICE Perform components. Infrastructure
specifications, the virtual machines’ resources (disk, CPU, memory, network) can be allocated and
configured either directly within the ESX server or via the VMware vCenter.
2. Enter the IP address or hostname of your VMware vCenter Server, and the VMware vCenter
Server username and password with administrative rights.
If you do not have administrative rights, you can still log in to the system with read-only rights
and review configuration settings. If a setting needs to be changed, you can alert an
administrator, who will then make the change.
3. Click Login.
The VMware vCenter Server appears.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 18
Chapter 2: VMware Configuration
VMware vCenter Server Summary View
TIP
Resource pools are used to hierarchically partition available CPU and memory resources.
Each standalone host and DRS cluster has an invisible root resource pool that groups the
resources of that host or cluster. The root resource pool is not displayed because the
resources of the host (or cluster) and the root resource pool are always the same.
A resource pool can contain child resource pools, virtual machines, or both. You can
therefore create a hierarchy of shared resources. The resource pools at a higher level are
called parent resource pools. Resource pools and virtual machines that are at the same
level are called siblings. The cluster itself represents the root resource pool.
Note: VMware DRS facilitates balancing resources across virtual machines.
The NICE Perform integration with VMware does not require special customization to the
Resource Pools.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 19
Chapter 2: VMware Configuration
VMware vCenter Server Summary View
Figure 2-2 VMware vCenter Server Summary View - Hosts and Clusters
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 20
Chapter 2: VMware Configuration
VMware vCenter Server Summary View
The Reservation and Limit columns indicate CPU allocation per virtual machine. The Shares
column indicates the CPU resource priority, facilitating scenarios in which there exists
competition for CPU resources between virtual machines.
6. From the View options, click Memory.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 21
Chapter 2: VMware Configuration
VMware vCenter Server Summary View
The Reservation and Limit columns provide information about the memory allocated per
virtual machine. The Shares column indicates memory priority, facilitating scenarios in which
there exists competition for memory resources between virtual machines.
Configure resources as described here:
• Memory Define zero (0) for all virtual machines except the virtual
Reservation (MB) machines running the SQL server and NICE VoIP Logger.
See:
• Virtual Machine with the SQL Database Installation
on page 46
• Virtual Machine with the VoIP Logger Installation
on page 52
• Memory Limit (MB) Unlimited
7. Keep all other defaults.
8. Click the Configuration tab.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 22
Chapter 2: VMware Configuration
VMware vCenter Server Summary View
Many virtual
machines
Additional configuration information about the ESX server is displayed. For example, you can
see which virtual machine is connected to the different NICs (Network Interface Cards).
If several NICs are configured as teaming NICs, this is also displayed. In Figure 2-7, one NIC
is connected to several virtual machines.
When teaming NICs are configured, additional NICs (vmnic0\1\2) under Physical Adapters
are displayed. See Figure 2-7.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 23
Chapter 2: VMware Configuration
VMware vCenter Server Summary View
Teaming NICs
Several virtual
machines
TIP
NIC Teaming is a feature of VMware Infrastructure 3 and above, that enables you to
connect a single virtual switch to multiple physical Ethernet adapters. A team can share
traffic loads between physical and virtual networks and provide passive failover in case of
an outage. NIC teaming policies are set at the port group level.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 24
Chapter 2: VMware Configuration
Allocating Resources for the Virtual Machines
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 25
Chapter 2: VMware Configuration
Allocating Resources for the Virtual Machines
The CPU, Memory, Disk, Network Adapter resource types for the selected virtual machine are
displayed. The following resource types are configurable:
• Memory (MB) Amount of allocated memory
• CPU Number of CPUs (vCPU) that are allocated as specified in the
Certified Servers Guide.
• Disk The disk used for the virtual machine is usually the disk used for the
shared storage to which the ESX server is connected. Several disks
can be assigned to one virtual machine.
The size of each disk is determined when assigned to a virtual
machine. Using the Disk Management tool, partitioning can be done
later from the operating system.
5. Click the Resources tab.
The CPU, Memory, Disk, and Advanced CPU resource types are listed.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 26
Chapter 2: VMware Configuration
Allocating Resources for the Virtual Machines
6. Select Memory.
The Resource Allocation area displays the configurable parameters for the Memory resource.
Figure 2-11 Virtual Machine Properties - Memory Resources
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 27
Chapter 2: VMware Configuration
Allocating Resources for the Virtual Machines
In the Resource Allocation area, you can configure the following memory parameters:
• Shares Default = Normal
Memory Shares determine memory priority. When there exists
resource competition between virtual machines, the virtual machine
with the Memory Shares with the highest priority will be allocated the
highest memory resource priority.
• Reservation Default = 0
(MB)
Amount of Memory that will always be available for the VM.
• Limit (MB) Default = 0
Limits the memory that the virtual machine will be able to consume.
7. In the Resources tab, select Disk.
The Resource Allocation area displays the configurable parameters for the Disk resource.
Figure 2-12 Virtual Machine Properties - Disk Resources
In the Resource Allocation area, you can configure the Shares disk parameter.
• Shares Default = Normal
Disk Shares determine disk priority. 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.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 28
Chapter 2: VMware Configuration
Virtual Machine Time Synchronization
• In each virtual machine, open the VMware Tools Properties window and select Time
synchronization between the virtual machine and the ESX Server.
Figure 2-13 VMware Tools Properties Window
VMware Tools
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 29
Chapter 2: VMware Configuration
Virtual Machine Time Synchronization
4. Click Properties.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 30
Chapter 2: VMware Configuration
Virtual Machine Time Synchronization
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 31
Chapter 2: VMware Configuration
Virtual Machine Time Synchronization
7. Click General. In the Startup Policy area, select Start and Stop with Host.
8. Click NTP Settings.
Figure 2-18 NTP Daemon Options ‐ NTP Settings
9. To add a new NTP server (or multiple NTP servers), click Add. Then select Restart NTP
service to apply changes.
10. Click OK.
Changes are applied and NTP service is started.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 32
Chapter 2: VMware Configuration
Virtual Machine Snapshot Management
If no snapshots are
defined, this button Snapshot Manager button
appears disabled
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 33
Chapter 2: VMware Configuration
Virtual Machine Snapshot Management
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 34
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
NOTE
Make sure to install VMware Tools on each virtual machine. These will enable enhanced
network capabilities.
Changing the network interface card (NIC) type involves the following steps:
1. Changing the NIC type:
• Changing the NIC Type to Enhanced VMXNET / VMXNET2 (Enhanced)
on page 37.
-or-
• VoIP Logger’s capture NIC only: Changing the VoIP Logger’s Capture NIC Type to
E1000 on page 40.
2. Virtual machine running the VoIP Logger:
a. VoIP Logger’s capture NIC only: Setting the Priority for the VoIP Logger’s Capture
NIC on page 57
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 35
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
a. Passive VoIP Recording only: Configuring the VoIP Logger’s Sniffing NIC for
Promiscuous Mode on page 59.
b. Increasing the Rx Buffer for the VoIP Logger’s Capture NIC on page 62.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 36
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
3. Select the network adapter that needs to be removed and click Remove.
4. Click Add.
The Select Device Type window appears.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 37
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
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
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.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 40
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
4. Click OK.
5. Reopen the Logger’s Virtual Machine Properties window.
6. Click the Hardware tab.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 41
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
7. Click Add.
The Add Hardware Wizard starts.
Figure 2-28 Add Hardware Wizard - Select Device Type Window
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 42
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
Example only -
select the NIC that
will be used for
capturing audio
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 43
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
Network adapter
designated for
capturing audio
(RTP) is now
configured
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 44
Chapter 2: VMware Configuration
Virtual Machine Network Interface Card (NIC) Configuration
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 45
Chapter 2: VMware Configuration
Virtual Machine with the SQL Database Installation
NOTE
These procedures are relevant to the virtual machine running the Data Mart.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 46
Chapter 2: VMware Configuration
Virtual Machine with the SQL Database Installation
The CPU, Memory, Disk, Network Adapter resource types for the selected virtual machine are
displayed.
4. Click the Resources tab. The CPU, Memory, Disk, and Advanced CPU resource types are
listed.
Figure 2-34 Virtual Machine Properties - Resources
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 47
Chapter 2: VMware Configuration
Virtual Machine with the SQL Database Installation
5. Select Memory. The Resource Allocation area displays the configurable parameters for the
Memory resource.
Figure 2-35 Memory Reservation for the Virtual Machine Running SQL
Example only
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 48
Chapter 2: VMware Configuration
Virtual Machine with the SQL Database Installation
The CPU, Memory, Disk, Network Adapter resource types for the selected virtual machine are
displayed.
4. Click the Resources tab. The CPU, Memory, Disk, and Advanced CPU resource types are
listed.
Figure 2-37 Virtual Machine Properties - Resources
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 49
Chapter 2: VMware Configuration
Virtual Machine with the SQL Database Installation
5. Select Memory. The Resource Allocation area displays the configurable parameters for the
Memory resource.
Figure 2-38 Memory Reservation for the Virtual Machine Running SQL
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 50
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 - each
virtual machine uses a configured section of a LUN.
The best practice for virtual machines running the SQL server is to map disk drives used for SQL
data and logs to Raw LUNs. In this way, the LUN is dedicated to a specific virtual machine. You
can verify whether a virtual machine is configured as Mapped Raw LUN in the Properties window
of a selected virtual machine.
Figure 2-39 Virtual Machine Properties - Mapped Raw LUN
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 51
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
To configure memory reservation for a virtual machine running the NICE VoIP Logger:
1. Log in to the VMware vCenter as described in Logging in to the VMware vCenter
on page 18.
2. In the VMware vCenter, from the Inventory drop-down list, select Hosts and Clusters.
3. Select the virtual machine running the VoIP Logger and click Edit Settings. The Virtual
Machine Properties window appears.
Figure 2-40 Virtual Machine Properties
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 52
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
The CPU, Memory, Disk, Network Adapter resource types for the selected virtual machine are
displayed.
4. Click the Resources tab. The CPU, Memory, Disk, and Advanced CPU resource types are
listed.
Figure 2-41 Virtual Machine Properties - Resources
5. Select Memory. The Resource Allocation area displays the configurable parameters for the
Memory resource.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 53
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
Figure 2-42 Memory Reservation for the Virtual Machine Running NICE VoIP Logger
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 54
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 55
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
Value area
Add Row
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 56
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 57
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
3. In the Connections area, set the network adapter that is designated for capturing your audio
(RTP) to appear second in the list.
4. Click OK.
5. Restart the virtual machine.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 58
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
TIP
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 59
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 60
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
6. Click the Security tab and from the Promiscuous Mode drop-down list, select Accept.
7. Click OK. The ESX server’s dedicated NIC is now configured for Promiscuous mode.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 61
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
IMPORTANT
Make sure that the network interface card designated for capturing audio is approved by
NICE. See Virtual Machine Network Interface Card (NIC) Configuration on page 35.
Increasing the Rx Buffer for the VMXNET2 (Enhanced) Card for ESX V4.0
The Rx buffer must be increased for every network interface card that is configured to capture
voice via sniffing. While the default Rx buffer is 150, the maximum Rx buffer supported by
VMware for adapter type VMXNET2 (Enhanced) for ESX Version 4 is 512. Increasing the network
adapter’s Rx buffer improves the VoIP Logger’s performance and reduces packet loss.
You can increase the Rx buffer for the VMXNET2 (Enhanced) card in one of the two following
ways:
• Increasing the Rx Buffer in the .vmx Configuration File
-or-
• Increasing the Rx Buffer in the Virtual Machine’s Properties Window
TIP
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 62
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
TIP
You can also change the buffer by using the Edit option. However, before the buffer is
changed, you must shut down the virtual machine.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 63
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 64
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
7. Click OK.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 65
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
Increasing the Rx Buffer for the E1000 Card for ESX V3.5
You increase the Rx buffer for the E1000 card in the virtual machine’s operating system.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 66
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 67
Chapter 2: VMware Configuration
Virtual Machine with the VoIP Logger Installation
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 68
Chapter 2: VMware Configuration
VMware High Availability
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 69
Chapter 2: VMware Configuration
VMware High Availability
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 70
Chapter 2: VMware Configuration
VMware High Availability
DRS & HA
have been
enabled
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 71
Chapter 2: VMware Configuration
VMware High Availability
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 72
Chapter 2: VMware Configuration
VMware High Availability
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 73
Chapter 2: VMware Configuration
VMware High Availability
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 74
3
Microsoft Hyper-V Configuration
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 75
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. Infrastructure
specifications, the virtual machines’ resources (disk, CPU, memory, 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.
For supported NICE Perform components, configuration requirements, and specifications, see the
Design Considerations and Certified Servers guides.
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
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 76
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 77
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 78
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 79
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 80
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
NOTE
• To optimize performance, all virtual disks must be created with a fixed size. This is
selected when initially configuring a new virtual machine or when adding new virtual
disk.
• Make sure that Hyper-V Integration Services have been installed on each virtual machine.
• Do not save virtual machine snapshots. Snapshots can compromise the performance of
your virtual machine.
• For supported Nice Perform components and specifications of resources to assign to each
virtual machine, see the NICE Perform Certified Servers Guide.
• After you complete setting up the operating system, it is recommended to install the
Integration Services. To verify if they are already installed, see the virtual machine
Settings > Management.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 81
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 82
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 83
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
Virtual Machine Hard Drive Settings - IDE for the Operating System
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 84
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), the Hard Drive must be added under the SCSI
Controller. The location of this Hard Drive file (VHD) should be on the Shared Storage.
Figure 3-10 Virtual Machine Hard Drive – SCSI for Partitions Without the Operating System
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 85
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
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. Two dedicated LUNs are needed
per database server (one for Data and one for Log).
The list of physical drives contains the LUNs that appear in the disk management in offline status.
Figure 3-11 Virtual Machine Hard Drive for Database Server
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 86
Chapter 3: Microsoft Hyper-V Configuration
Configuring Hyper-V
• In each virtual machine, in the Integration Services window, select Time Synchronization.
Figure 3-12 Virtual Machine Settings - Time Synchronization
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 87
Blank page for double-sided printing.
4
Virtual Desktop Infrastructure (VDI) for
NICE Client-Side Applications
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 89
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. The client device may
use an entirely different hardware architecture than that used by the projected desktop
environment, and may also be based upon an entirely different operating system.
The desktop virtualization model allows the use of virtual machines to let multiple network
subscribers maintain individualized desktops on a single, centrally located computer or server. The
central machine may operate at a residence, business, or data center. Users may be geographically
scattered, but all must be connected to the central machine by a local area network, a wide area
network, 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. VDI is a variation on the client/server
computing model, sometimes referred to as server-based computing (SBC). The term was coined
by VMware Inc.
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.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 90
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, Vista, 7) to the client.
Former versions of VMware View are called VDM (Virtual Desktop Manager).
NICE Network
Perform View
Servers Connection
Server
LAN
VMware
ESX Host vCenter
Server
Virtual Virtual Virtual Virtual
Desktop Desktop Desktop Desktop
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 91
Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications
VMware View
• Open the VMware View Manager and set the Default display protocol to PCoIP.
Figure 4-2 VMware View Manager - Web Interface
NOTE
For information about View Manager administration, see the VMware documentation guide -
http://www.vmware.com/pdf/view40_admin_guide.pdf
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 92
Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications
VMware View
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 93
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).
NOTE
2. Enter the IP address or hostname of the View Connection Server at your site and click
Connect.
The VMware View Client login window appears.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 94
Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications
VMware View
TIP
PCoIP can also be selected during client login to the virtual desktop.
To select PCoIP, press on the VMware View Connection Server name’s arrow and select
Display Protocol > PCoIP.
Figure 4-5 Selecting PCoIP in the Login Window
4. Click Connect.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 95
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, Windows Vista, 7) to the client.
NOTE
The descriptions in this section were taken from the Citrix documentation.
Overview of XenDesktop
Citrix XenDesktop is a desktop virtualization system that centralizes and delivers Microsoft
Windows XP, Vista or 7 virtual desktops as a service to users anywhere. Virtual desktops are
dynamically assembled on demand, providing users with pristine, yet personalized, desktops each
time they log on. This ensures that performance never degrades, while the high speed delivery
protocol provides unparalleled responsiveness over any network. XenDesktop delivers a high
definition user experience over any connection including high latency wide area networks. The
open architecture of XenDesktop offers choice and flexibility of virtualization platform and
endpoints. Unlike other desktop virtualization alternatives, 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.
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.
Desktop Delivery Controller - Installed on servers in the data center, the controller authenticates
users, manages the assembly of users' virtual desktop environments, and brokers connections
between users and their virtual desktops. It controls the state of the desktops, starting and stopping
them based on demand and administrative configuration. Desktop Delivery Controller also
includes Profile management, in some editions, to manage user personalization settings in
virtualized or physical Windows environments.
Virtual Desktop Agent - Installed on virtual desktops, the agent enables direct ICA (Independent
Computing Architecture) connections between the virtual desktop and user devices.
Citrix online plug-in - Installed on user devices, the Citrix online plug-in (formerly "Citrix
Desktop Receiver") enables direct ICA connections from user devices to virtual desktops.
Figure 4-6 on page 97 provides a high-level view of the XenDesktop environment.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 96
Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications
Citrix XenDesktop
NICE Network
Perform DDC -
Servers Desktop
Delivery
Controller
LAN
Xen Server
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 97
Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications
Citrix XenDesktop
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 98
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
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 99
Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications
Citrix XenDesktop
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 100
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, in Citrix Xen
Desktop Delivery Controller server, do the following:
1. Open the Citrix Presentation Server console.
2. Navigate to Farm > Policies.
3. Select a policy and open its properties.
Figure 4-9 Citrix Presentation Server Console - Select Properties
4. Navigate to Client Devices > Resources > Audio > Turn off speakers and select Not
Configured.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 101
Chapter 4: Virtual Desktop Infrastructure (VDI) for NICE Client-Side Applications
Citrix XenDesktop
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 102
A
Converting a Physical Machine into a
VMware Virtual Machine
NOTE
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 103
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.0, using VMware vCenter Converter Version 4.0.1. For server
specifications, see the Certified Servers Guide.
Before performing this procedure, ensure that:
• The network speed between all servers and the ESX is 100Mbp or higher.
• You have administrative privileges to the physical machine.
• You have administrative privileges to the ESX machine.
• The maximum disk size on the physical server is smaller than the maximum disk size that you
will create on the ESX server.
• All NICE services running on the physical machine have been stopped.
Converting a physical machine into a virtual machine involves the following steps:
1. Installing VMware Converter 4.0.1
2. Converting the Physical Machine into a Virtual Machine
3. Defining the New Virtual Machine’s IP Address
IMPORTANT
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 104
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Installing VMware Converter 4.0.1
2. Click Next.
The VMware vCenter License Agreement window appears.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 105
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Installing VMware Converter 4.0.1
3. Select I accept the terms in the License Agreement and click Next.
The Destination Folder window appears.
Figure A-3 VMware vCenter Destination Folder Window
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 106
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Installing VMware Converter 4.0.1
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 107
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Installing VMware Converter 4.0.1
8. Click Install.
The VMware vCenter Converter is installed.
9. Click Finish.
10. Proceed to Converting the Physical Machine into a Virtual Machine on page 109.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 108
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 109
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
4. Enter the connection detail for the physical server and click Next.
The Standalone Agent Deployment window appears.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 110
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
5. Select Automatically uninstall the files when import succeeds. Then click Yes.
A Deploying agent message appears.
6. Click Yes again.
The Specify Destination tab appears.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 111
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 112
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 113
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 114
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 115
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 116
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 117
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Converting the Physical Machine into a Virtual Machine
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 118
Appendex A: Converting a Physical Machine into a VMware Virtual Machine
Defining the New Virtual Machine’s IP Address
NOTE
Domain environment: If the physical machine was already defined as part of the
domain, the new virtual machine will already be a member of the domain.
NICE Perform ® Release 3.1, 3.2, & 3.5: Virtualization Configuration Guide (Rev. A3) 119