The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The interface for the tool contains integrated help content on each window. This help content will guide you through device owner assignment tasks. The tool also provides tooltips to explain the matching rules that you can run.
On the Select Rules window, you can select the rules that you want to run to make user-device matches. The right column of the window shows a default selection of the top three recommended matching rules. The tool will run these rules in the specified order. Because the tool runs these match rules on unassigned devices, the first rule is run and owner user ID assigned with the best match resulting from the rule. The tool runs the next rule on the remaining unassigned devices from the first match rule, and so on, until the tool runs all the rules in the order that you choose.
Note | The order of the rules are used mainly to prioritize the matches. You can change the order of the rules to influence the matching results. |
If only one End User Configuration window references a device as a "Controlled Device," this user will be set as the owner.
If a Device Configuration window lists a number for line 1 that matches the primary extension listed on an End User Configuration window, then that user is set as the owner for this device.
If line 1 of a device lists only one user under Users associated with line, then that user will be set as the owner.
If a Device Configuration window lists a number for line 1 that matches the telephone number listed on an End User Configuration window, then that user is set as the owner for this device.
Options—Last (3–10) digits
If a Device Configuration window lists an alerting name for line 1 that contains the user ID, extension number, or first name and last name listed on an End User Configuration window, then that user is set as the owner for this device.
Options—Last (3–10) digits, First name, Last name
If a Device Configuration window lists a display name for line 1 that contains the user ID, extension number, or first name and last name listed on an End User Configuration window, then that user is set as the owner for this device.
Options Last (3–10) digits, First name, Last name
If a Device Configuration window lists a device description that contains the user ID, extension number, or first name and last name listed on an End User Configuration window, then that user is set as the owner for this device.
Options—Last (3–10) digits, First name, Last name
You can save the resulting match file to your hard drive. You should review the file for quality and quantity of matches. If your system contains greater than 65,000 device entries, your match file will contain multiple sheets.
You can run Step 1 as many times as you want with different rules and different priorities. You can also edit the match file for manual user ID assignments to the Owner User ID field.
Common area, public space, and shared devices are assigned to users IDs just like any other device. The Device Assignment Tool does not differentiate between the types of devices; if a device matches a rule, then an assignment is made.
As you review the match file, keep the following points in mind:
Manual assignments to the Owner User ID field in the match file are not imported into the Unified Communications Manager database until you run Step 2. If you run subsequent match rules through Step 1, manual assignments are not saved in the match file.
Tip | Before import, note the server name and time and date stamp of the match file with the final results, so that you apply the correct file to the Unified Communications Manager database in Step 2. |
From the Update System window, you can take the match files you created and import them into your Unified Communications Manager publisher node. This action will assign the unassigned devices with user IDs that are listed in the match file.
In a multiple cluster environment, you can run the tool for a specific publisher in a cluster each time to retrieve the devices that have no owner user ID.
Tip | We recommend that you run the tool outside of regular business hours, so that the updates do not affect your system operation. You cannot schedule automatic updates, because running the updates is a manual process that you must initiate. |
Please read the following points before you update the system:
The Device Assignment Tool will default to the Unified Communications Manager that you used to create the matches. However, you can select a different Unified Communications Manager to upload a match file.
The latest match file that was created in Step 1 will be preloaded in the tool for Step 2.
If the match file does not match the current Unified Communications Manager, you will see a warning, after which you can proceed and attempt the update.
After a user-device match is updated in the Unified Communications Manager database, that operation cannot be reversed.
While the upload is in progress, you can stop or continue the update operation.
The tool provides an error message if an update step contains invalid data.
After the match process is completed or you stop the update operation, you can see the log file which contains unmatched device information. A device reset is not required.
The tool provides an error message if you upload a match file to a Unified Communications Manager that is out of compliance.
Caution | If you cancel the import, the updates to the database are canceled. But you cannot reverse the updates that were made while the import ran. |