[Index]
Overview
You can move users between any hierarchy nodes at or below the hierarchy node where the users were originally created or synced in. Typically, users synced in at a Customer hierarchy node are moved to various customer sites.
When moving a user, you will choose their role at the target hierarchy.
Note
The Move Users page in VOSS Automate can be accessed via:
Alternatively, use the Search function in VOSS Automate to locate Move Users.
You will need to consider the restrictions that apply when moving users:
Scenario | Description |
---|---|
Moving users pushed to CUCM |
|
Moving users between sites |
|
Note
When moving a user for SLC dialplan the lines associated to the agent line and the shared line show warnings in the form of logs.
Related Topics
Create a Filter to Move Users in the Core Feature Guide
Automatically Move Users Synced from CUCM in the Core Feature Guide
Move Users from Customer to Site
This procedure moves users from a Customer to a Site.
Pre-requisites:
To move a user from the customer level to a site:
In the Admin Portal, go to (default menus) User Management > Move Users.
Note
Alternative step: Go to (default menus) Overbuild > Move Users. The procedure is the same regardless of the menu path.
From the Action drop-down, choose an option for moving the user/s:
Action | Description |
---|---|
Move users by filters | Moves users based on one or more user attributes, for example, City or Street.
|
Move users by usernames | Moves multiple users at once, by their username (bulk move).
|
Move user by username | Move a single user, by their username.
|
Related Topics
Move Users from One Site to Another Site
PROVIDER ONLY
As an administrator, you can move users from one site to another with their assigned devices and services intact.
Note
Certain conditions must be met for a site-to-site move to succeed. These conditions differ slightly for users in non-SLC dial plans and users in SLC dial plans.
When moving a user with their devices and services between sites with a non-SLC dial plan configured, VOSS Automate checks the following conditions:
When moving a user from one (non-SLC) site to another (non-SLC) site, the following models and relations are moved with the user:
Various fields are updated for the target site (by the target site's site defaults) for the models that are moved. These fields include (but are not limited to), the following:
The following fields are updated for the device/cucm/Line model:
The following models are updated for relation/Subscriber:
Each of these models contains a Lines field, which in turn can contain individual lines. In a site-to-site move, the E164 Mask and Route Partition Name fields are updated for each line contained in these models.
Additionally, the move updates some fields within these individual models:
You will need to update these values if you wish to use the overbuild with your existing CUCM data in the future.
The following models trigger a warning message when you attempt to move them from one site to another. While VOSS Automate does not prevent you from moving these models, a system message describes the possible implications for moving them:
Note
When using an API for a older version of VOSS Automate (prior to v11.5.1), the Move Users function has the previous behavior. Devices and services do not move with a user.
For moves between non-SLC sites with directory number routing (DNR) configured at either site, a system message is triggered to warn that any lines associated to the user being moved may not work correctly unless you take one of the recommended actions provided. See the Advanced Configuration Guide to perform the first recommended action.
When moving users between sites with a SLC dial plan configured, the required conditions are the same as with non-SLC plans. The only difference is that no error is triggered when the system check detects an SLC dial plan configuration for the customer.
Note
When moving users from a dial plan site to a non-dial plan site, the users are set to a default CSS.
When moving users from one SLC site to another SLC site, the same models and relations are moved as for sites with non-SLC dial plans, with the following exceptions:
These models are not handled when moving SLC dial plans, because the line does not move:
The following models trigger a warning message when you attempt to move them from one site to another. While VOSS Automate does not prevent you from moving these models, a system message notifies you of the possible implications of moving them:
Moving Microsoft Users
Moving a Microsoft user manually (via User Management > Move User), also moves the following models:
These models are moved regardless of the source and target hierarchies.
To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com
You can move users between any hierarchy nodes at or below the hierarchy node where the users were originally created or synced in. Typically, users synced in at a customer hierarchy node are moved to various customer sites.
When moving users, choose an appropriate role for the target hierarchy from the following drop-down: Move To Role
Restrictions that apply when moving users
The table describes restritions that apply when moving users:
Scenario | Restrictions |
Moving users that have been pushed to Cisco Unified Communications Manager |
|
Moving users between sites |
|
Different methods for moving users
The table describes three ways to move users:
Move users by filters | Choose users to move, based on one or more user attributes, for example, City or Street. |
Move users by usernames | Move multiple users at once (bulk move). |
Move user by username | Move a single user. |
Note
Related Topics
Create a Filter to Move Users in the Core Feature Guide
Moving Users from Customer to Site in the Core Feature Guide
Moving Users from Site to Site in the Core Feature Guide
Automatically Move Users Synchronized from Cisco Unified CM in the Core Feature Guide
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. |
|