Example 1: Mapping a Site

A Service Provider created two sites for a Customer in Management Portal: Ottawa and Nepean.

In Active Directory the City location attribute for a user has the same name as the Site name in Management Portal, they are both called Ottawa.

• On the “Map Fields” form the default mapping for “Site” is ‘‘physicalDeliveryOfficeName” attribute in Active Directory.

• If we look at the user’s information in Active Directory, the attribute ‘‘physicalDeliveryOfficeName” or Office, is called “Kanata Mitel”.

• If you were to keep the current mappings, when you open the “Bulk Import Spread Sheet” the Site location would be empty. This is because Management Portal does not have a Site called “Kanata Mitel”.

• If the current mappings for a filed do not produce the correct output, the field will remain empty in the “Bulk Import Spread Sheet”.

• We need to change the mappings in the Active Directory Association “Map Fields” form.

• Change the “Site” attribute from ‘‘physicalDeliveryOfficeName” to ‘l’ which is the “Active Directory” attribute for “City”.

• This will ensure that all users in “Active Directory” that are in the City of Ottawa or Nepean will be Mapped to the Sites of Ottawa or Nepean in Management Portal.

Example 2: Prime Phone Device Type

• To map a Prime Phone Device Type, the device type in Active Directory must be a Mitel supported device. See Supported Phone Sets for details.

• Active Directory has an attribute called ipPhone. The user information below shows that they have an IP phone with the value of 5330 IP. This is a supported Mitel device.

• On the Map Fields page, enter the Active Directory attribute ipPhone.

• When you open the Bulk Import Spreadsheet it will show all of the users that have a supported Mitel device.

• If the device is not a supported device, the field will be empty and you will be required to select one.