Cisco Cisco IP Contact Center Release 4.6.1 Release Notes
35
Release Notes for Cisco IPCC/ICM Enterprise & Hosted Editions Release 7.0(0) Installer Update C November 24, 2008
New and Changed Information
–
Click on "Add", then click on "OK".
–
Click on "OK" to close the properties dialog.
–
Configuration is complete. Close the AD MMC application (saving MMC configuration on exit
is optional).
is optional).
MCS-7845I / MCS-7845-I1-CC1 NIC Controller PnP Issue
The way that Windows enumerates the dual NICs on the MCS-7845-I1-CC1 with a particular revision
of the Broadcom chipset is incorrect. A command line patch can be run to fix this issue so that when
events show up through the hardware monitoring software, you have the right NIC identified. Running
the utility works fine whether the issue is present or not. The utility only changes settings if it detects
things are wrong.
of the Broadcom chipset is incorrect. A command line patch can be run to fix this issue so that when
events show up through the hardware monitoring software, you have the right NIC identified. Running
the utility works fine whether the issue is present or not. The utility only changes settings if it detects
things are wrong.
The problem is somewhat different on Windows Server 2003 (versus Windows 2000), but the remedial
patch is equally effective. When additional NICs that have standard Windows drivers are installed prior
to installing Windows, they will appear first, before the Broadcom NICs. Once the patch is run, you may
now have two connections labelled Local Area Connection, and two named Local Area Connection #2.
Functionality will not be impaired, but the system will be confusing. At this point, the additional NICs
should be manually renamed using Network Connections in Windows and right clicking Rename to
name these Local Area Connection #3 and #4. They can be identified by right clicking the individual
connections and selecting properties.
patch is equally effective. When additional NICs that have standard Windows drivers are installed prior
to installing Windows, they will appear first, before the Broadcom NICs. Once the patch is run, you may
now have two connections labelled Local Area Connection, and two named Local Area Connection #2.
Functionality will not be impaired, but the system will be confusing. At this point, the additional NICs
should be manually renamed using Network Connections in Windows and right clicking Rename to
name these Local Area Connection #3 and #4. They can be identified by right clicking the individual
connections and selecting properties.
After running the patch, you will need to reboot. The patch does not send back any messages after it is
run, but the system needs to be rebooted following it.
run, but the system needs to be rebooted following it.
The patch can be accessed from
Download and read the file Readme_NicNameX-Utility_PCD.txt.
Download nicnamex.zip and unzip it. Then, in accordance with the instructions in the Readme file, run
NicNameX.exe.
NicNameX.exe.
Removal of Support for Ataman Telnet Daemon
The Ataman Telnet Daemon is not supported, and has been removed, in Release 7.0(0).
New Global Performance Monitor Collection Feature
With Release 7.0(0), the Node Manager process captures performance related data from the machine.
This includes any machine on which one or more ICM node(s) are installed. This feature is turned on by
default. The logs are captured in a CSV format in ICMROOT\log folder. Counters are captured at every
one minute interval. Configuration settings for file size and number of files to keep in the log directory
can be changed through the registry. By default the following counters are captured:
This includes any machine on which one or more ICM node(s) are installed. This feature is turned on by
default. The logs are captured in a CSV format in ICMROOT\log folder. Counters are captured at every
one minute interval. Configuration settings for file size and number of files to keep in the log directory
can be changed through the registry. By default the following counters are captured:
\Memory\Page Faults/sec
\Memory\Committed Bytes
\Memory\Pages/sec
\Process(_Total)\Handle Count
\Processor(_Total)\% Processor Time
\System\Threads
\System\Processor Queue Length
\System\Processes