7-31
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
OL-13844-01
Chapter 7 VPIM Networking
Procedures for Setting Up Cisco Unity to Use VPIM Networking
Step 10 Click the Save icon.
Using the Cisco Unity Bulk Import Wizard to Configure VPIM Subscriber Creation Settings
After you have created delivery locations and reviewed the considerations for creating subscriber
accounts, you can customize the subscriber creation settings that control automatic VPIM subscriber
directory updates for multiple existing delivery locations by using the Cisco Unity Bulk Import wizard.
Or, you can create new delivery locations and customize the subscriber creation settings for the new
locations at the same time. In either case, you configure each of the subscriber creation settings by
including an optional column in the CSV file that you create for use in the wizard (the columns are not
required when creating or modifying a delivery location, but if you include any one of the subscriber
creation columns, you must include them all).
See the Cisco Unity Bulk Import wizard Help for a description of each of the optional columns that
control subscriber creation. For more information on using the wizard to create or modify delivery
locations, see the “Using the Cisco Unity Bulk Import Wizard to Create VPIM Delivery Locations”
section on page 7-20 or the “Modifying Existing Delivery Locations by Using the Cisco Unity Bulk
Import Wizard” section on page 7-22.
Changing the AD Location in Which Automatically Created VPIM Subscribers Are Created (Optional)
By default, all automatically created VPIM subscribers are placed in the Active Directory container that
was specified in the Message Store Configuration wizard during Setup. If you want to have auto-created
VPIM subscribers created in a different location, you can configure Cisco Unity to use any properly
configured container or organizational unit. Separating the auto-created contacts from other AD objects
allows you to more easily monitor and control these objects. However, we do not recommend that you
attempt to change the container used for subscriber creation unless you are familiar with Active
Directory objects and permissions.
If you choose to change the container for auto-created contacts, note the following:
• New VPIM subscribers that are created manually by using the Cisco Unity Administrator will still
be created in the default AD container that was selected in the Message Store Configuration wizard.
• Existing VPIM subscribers that have been manually created will not be relocated to the container
selected for auto-created contacts. However, if an automatic modification or deletion is initiated for
one of these accounts, Cisco Unity will update the account properly in the default container.
• If auto-created VPIM subscribers have already been created in the current container, or you wish to
move existing manually created VPIM subscribers, you can move the existing contacts to the new
container by using Active Directory Users and Computers.
Use the following task list to set up the container or organizational unit and to configure Cisco Unity to
use it when automatically creating VPIM subscribers:
1. Identify the Active Directory location in which the auto-created contacts will be created. This can
be an object of the class Container or Organizational Unit (OU). To create a new container, use a
tool such as ADSI Edit. Or, to create a new OU, see the “To Create a New Organizational Unit”
procedure on page 7-32.
2. Set applicable permissions for the Cisco Unity service account on the Active Directory container or
OU that you selected in Task 1. To set up permissions by using the Permissions wizard, see the “To
Set Permissions on the AD Location by Using the Permissions Wizard” procedure on page 7-32. Or,
to manually set the specific permissions required on the container, see the “To Set Permissions on
the AD Location by Using Active Directory Users and Computers” procedure on page 7-32.