[Index]
You can move users between any hierarchy nodes at or below the hierarchy node where the users were originally created or synced in. A common practice is to move users synced in at a customer hierarchy node to various customer sites.
Note
The following restrictions exist when moving users that have been pushed to Cisco Unified Communications Manager:
Important
The following restrictions apply when you move users between sites:
You can choose the users to be moved in the following three ways:
Note
When you move users, choose a Move To Role from the drop-down for the users that is appropriate for the target hierarchy node.
Moving Users from Customer to Site
Use this procedure to move users from Customer to Site.
When you move users, choose a default role for the users that is appropriate for the target hierarchy node.
Log in at the appropriate hierarchy level.
Choose User Management > Move Users, or Overbuild > Move Users.
In the Action drop-down, choose the move method.
If you choose Move users by filters:
From the Move From Hierarchy drop-down, choose the hierarchy node from which you are moving the user.
A note appears stating that only users at the hierarchy you chose will be moved.
From the Available list, choose one or more Move Filters and click Select to move them to the Selected list. You can choose filters in a different order to change the order in which they are applied.
Click Save to move the filtered users.
If you choose Move users by usernames:
If you choose Move user by username:
Choose User Management > Users to verify that the users are moved to the target hierarchy.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
Action | The type of Move action to perform. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Action | The type of Move action to perform. This attribute is deprecated and move_action should be used instead. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User | Name of individual user who will be moved. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Note | Information regarding the specified action. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Move From Hierarchy | The name of the hierarchy node from which the user will be moved if the conditions are satisfied. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Move From Hierarchy Count | The number of the hierarchy nodes that match the from username. Default: TBD |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Move To Hierarchy | The name of the hierarchy node to which the user will be moved if the conditions are satisfied. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Set Default Role | The default role to assign to the moved user (if no other LDAP Custom Role Mappings are applicable for the moved user, then this fallback/default role will be applied) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Move All Users | Move all the users at the move from hierarchy. Default: false |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Filters | Select move filters to be applied when the transaction is submitted. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Users | Names of users who will be moved. |
|