Cisco Cisco Unified Provisioning Manager 8.5 White Paper
Deployment Guide
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 28 of 53
Configuring Rules Step by Step
Domains rules need to be configured properly before a sync is performed.
Step 1. Configure how users are placed in the domain.
Select
●
AssociateAllUsersInCallProcessor + AssociateAllUsersInUMProcessor
OR
●
AssociateOnlyExistingUsers
OR any combination of
●
AssociateUsersByDeptCode
●
AssociateUsersByDevicePool
●
AssociateUsersByLocation
Step 2. Configure how services for a user are assigned to service areas.
●
Non-RestrictedDomainSync (disabled by default)
Optional:
●
AssociateAllUsersInUMProcessor
●
TakePrimaryUserInfoFromUMProcessor
Example: Customer has an Active Directory integrated Communications Manager and has
different domains set up for different branches.
Step 1.
Option 1:
●
Set the department in Active Directory for users.
●
Enable the AssociateUsersByDeptCode rule for each domain and specify the department code.
Option 2:
●
Users can be placed using a combination of these rules: AssociateUsersByDevicePool and
AssociateUsersByLocation.
●
This requires that all users have an associated phone.
Option 3:
If the department code cannot be set and some users don’t have an associate phones:
●
Create subscribers in Cisco Unified Provisioning Manager first in the desired domain. The batch action can
be used if there are a lot of users.
●
Enable the AssociateOnlyExistingUsers rule for domains.
Step 2. Enable the Non-RestrictedDomainSync rule to reduce the number of service areas needed. By default there
will be a lot service areas per domain needed for this customer to cover permutations on different calling
search spaces and different device pools.