9.3 Managing Existing Users

After performing a work order, the driver can update a user’s information with the results. For example, the driver can add a new extension to the user's list of phone numbers, or remove an extension that has been deleted, as described in Section 7.0, Workforce Tree Configuration.

This functionality works for new and existing users, if the following conditions are met:

This means that your ability to manage existing users (perform work orders for their extensions and update their phone information after a work order is performed) is dependent on the accuracy with which the ObjectID is specified in the work order. This is a contrast to some other Identity Manager drivers, which require the user object to have an Identity Manager association with the driver before you can manage existing users.

Unlike some Identity Manager drivers, it is not necessary to use the Migrate into NDS command before being able to manage existing users. In fact, for this driver, the Migrate into NDS command does not affect user objects (unless you create custom policies or tools to do so).

The Migrate into NDS command allows you to import data from an application into Identity Vault. For the Identity Manager Driver for Avaya PBX, the Migrate into NDS command causes all extensions that are configured in the PBX to be created as pbxExtension objects in eDirectory™.

This action does not create associations between existing User objects in eDirectory and existing extensions. However, this list of existing extensions could be used for the following purposes as part of a manual effort or with custom tools you create: