Cisco Unified Communications Manager Bulk Administration Guide, Release 8.6(1)
Deleting IME Exclusion Group Configuration
Downloads: This chapterpdf (PDF - 335.0 KB) The complete bookPDF (PDF - 12.19 MB) | Feedback

Deleting Exclusion Group Configuration

Table Of Contents

Deleting Exclusion Group Configuration

Related Topics

Deleting Exclusion Group Configuration

Use this procedure to delete Exclusion Group from the Cisco Unified Communications Manager database.

Before You Begin

1. Create a text file that lists the name of the Exclusion Group that you want to delete:

2. Upload the custom files to the Cisco Unified Communications Manager server first node. See "Uploading a File" section on page 2-3.

To delete Exclusion Group that are listed in a custom file, use the following procedure.

Note Do not use the insert transaction files that are created with bat.xlt for the delete transaction. Instead, you must create a custom file with details of the Exclusion Group records that need to be deleted. Use only this file for the delete transaction. In this custom delete file, you do not need a header, and you can enter values for name.


Step 1 Choose Bulk Administration > Intercompany Media Services > Exclusion Group > Delete Exclusion Group.

The Delete Exclusion Group Configuration window displays.

Step 2 From the Delete Exclusion Group where Name in custom file drop-down list box, choose the filename of the custom file for this delete.

Step 3 Click Find.

Step 4 The Exclusion Group matching your search criteria displays.

Step 5 Click Submit to create a job to delete the Exclusion Group.

Use the Job Scheduler option in the Bulk Administration main menu to schedule and/or activate this job. For more information on jobs, see the Chapter 82, "Scheduling Jobs."

For information on log files, see "BAT Log Files" section on page 83-3.

Additional Topics

See the "Related Topics" section.

Related Topics

Inserting Exclusion Group Configuration, page 75-1

Uploading a File, page 2-3

Scheduling Jobs, page 82-1

BAT Log Files, page 83-3