Cisco Cisco E-Mail Manager Unity Integration Option

Pagina di 90
4
Release Notes for Cisco IPCC/ICM Enterprise & Hosted Editions Release 7.0(0) Installer Update C November 24, 2008
New IPCC/ICM 7.0(0) Installer Update C Discs
With few exceptions, the defects resolved by IPCC/ICM 7.0(0) Installer Update C are relevant only at 
install or upgrade time. There is no need to immediately install IPCC/ICM 7.0(0) Installer Update C if 
you are already successfully running Release 7.0. However, in all cases (affected or not) you should 
replace your existing ICM software 7.0(0) discs with new ICM software 7.0(0) Installer Update C discs; 
this will help to prevent problems when the discs are used for future ICM upgrades or modifications to 
your installation.
Note
Once you have installed Release 7.0(0) Installer Update C, check the registry key
 
[HKLM]\SOFTWARE\Cisco Systems, Inc.\ICM\SystemSettings\InstallUpdateVersion
 
The value of the key will be 7.0(0)_IU_C where IU means Installer Update and C is the 
version of the Installer built on 7.0(0).
You can request new discs online:
Note
An updated version of the Staging Guide for Cisco ICM/IPCC Enterprise & Hosted 
Editions
 will be available on cisco.com. The updated guide can be recognized by an 
October, 2006 publication date on the cover page. Customers planning to install or upgrade 
to IPCC/ICM 7.0(0) are urged to read the updated Staging Guide before attempting to 
install or upgrade. This updated document contains new guidelines related to Active 
Directory. In particular, the updated Staging Guide warns that customers should use a 
single forest for the IPCC/ICM domain topology. Customers currently using multiple 
forests should migrate their IPCC/ICM servers to a single forest before deployment of 
7.0(0), then continue use of this deployment with any future versions of ICM. Please refer 
to the updated Staging Guide for additional information.
Setup Change in IPCC/ICM 7.0(0) Installer Update C
Prior to IPCC/ICM 7.0(0) Installer Update C, the following could occur on a server running multiple 
IPCC instances, with multiple users having privileges on various instances.
A user, who did not have Setup rights on all the instances, could use Upgrade All. Upgrade All would 
then only upgrade the instances for which the user had setup permission.
However, when this happened, the icm\bin and registry would be updated. In instances for which the 
user did not have setup permission, files might get deleted, user registries might get updated, but service 
accounts would not be updated. This could leave these instances in a poorly defined state.
In IPCC/ICM 7.0(0) Installer Update C, when Upgrade All is used, Setup checks that the user has setup 
permission on ALL instances on the server. This check is done before any instances are upgraded. If the 
user has permission on all instances, then upgrade proceeds. Otherwise, Setup exits with a warning that 
the user has inadequate permission.