User guide

of existing MOH server—server association/annunciator—server association. You can edit the TAR
file to make sure that the csv file has the valid association before importing. Cisco recommends that you
import the server first; then, based on the association created, you can edit the csv file and do an Import
with Override.
• Device Defaults
• Credential Policy Default
• Certificate—Import/Export supports only update of existing certificates as new certificates cannot be
created/uploaded from Cisco Unified Communications Manager Administration. Only the Duration in
Cache parameter from the certificate can be updated.
Upgrade from Cisco Unified CallManager 4.x releases
Keep the following points in mind when you import entities after an upgrade from Cisco Unified CallManager
4.x releases:
• BAT supports Import/Export between the same versions of Cisco Unified Communications Manager
only. After the upgrade from a 4.x release of Cisco Unified CallManager, make sure that you have the
same Cisco Unified Communications Manager version on both the source and target servers.
• Some user groups associated to application users that are relevant to the erstwhile Cisco Unified
CallManager 4.x version that was running on the source server before the upgrade, may not be relevant
to the Cisco Unified Communications Manager version running on the target server. Import transaction
for such user groups will fail.
Topics related to Import/Export menu
• Export configuration data, on page 483
• Edit .tar File, on page 490
• Log files, on page 490
• Override only, on page 496
• Upgrade from Cisco Unified CallManager 4.x releases, on page 497
• Find downloadable file on server, on page 17
• Download file off server, on page 18
• Upload file to server, on page 19
• Delete file from server, on page 19
Cisco Unified Communications Manager Bulk Administration Guide, Release 9.1(1)
OL-28580-01 497
Upgrade from Cisco Unified CallManager 4.x releases
REVIEW DRAFT - CISCO CONFIDENTIAL