Cisco Cisco E-Mail Manager Unity Integration Option Installationsanleitung

Seite von 180
servers. Perform the AD and DNS migration well in advance of the actual upgrade to allow
time for implementation and stabilization. Repeat this for all Domain Controllers currently on
ICM servers. Use the Active Directory tools provided with the Windows operating system, and
bring up the new domain controllers on the domain in which the ICM operates. Transfer any
applicable flexible single master operations (FSMO) roles, and then demote the domain
controllers on the Logger to member servers. Refer to "Migrating Active Directory and DNS
to a Non-ICM Server" for additional information.
Note: This process may require the Logger to be down during demotion and transfer of the
domain controller.
The Windows 2000 Operating System is only supported for Common Ground upgrades, but
the operating system must be upgraded to Windows 2003 SP1 on all ICM core components or
Windows XP on client AWs before the upgrade is considered complete.
There are two methods by which you can ensure your systems are hardened:
1. Before engaging in the upgrade of the application, apply the security best practices outlined
in the Security Best Practices Guide for Release 5.0 and the Guide for 6.0 depending on
source release.
2. After upgrading the application on Windows 2000, upgrade the Operating System to
Windows Server 2003 and apply the automated hardening provided by the application at
this OS revision. This can be accomplished by re-running ICM setup and choosing to
apply the hardening when prompted, or by apply the security hardening from the command
line as outlined in the Release 7.0(0) Security Best Practices Guide for Windows Server
2003.
Domain Conversion Tool and Active Directory
The Technology Refresh upgrade method includes the process of migrating users from one
domain server to another using a tool called the Domain Conversion Tool. The new servers
must be in the Active Directory (AD) domain, the Active Directory environment must be set
up, and the instances added to the appropriate ICM organizational unit (OU). IP connectivity
and remote access must be validated.
When Instance Organizational Units are created by the ICM Domain Manager, user accounts
in the old ICM/IPCC security groups are automatically copied to new security groups in the
ICM/IPCC 7.0(0) Instance OU. The old groups are not modified.
Note: If you create new user accounts in the old ICM/IPCC 5.0 or ICM/IPCC 6.0 system after
the new ICM/IPCC 7.0 instance OUs were created, these accounts will not be valid in the new
ICM/IPCC 7.0 system.
ICM Setup verifies that AD configuration is complete and does not proceed until it is. All ICM
Instance information is required to allow you to configure the Active Directory Organizational
Units.
Upgrade Guide Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
46
Chapter 6: - Setting Up the Hardware
Active Directory and DNS Considerations for Upgrades