Configuration Profile Deployment

With the Polycom Device Management Service for Enterprise , you can deploy configuration profiles and provisions devices by editing a device, device group, or site.

You can also associate profiles on the Profile Deployment page that manages the association of configuration profiles to different containers.

For example, you have a call.autoAnswer.SIP parameter enabled in configuration profile A and disabled in configuration profile B. Profile A applies to specific Site. Profile B applies to Global. The call.autoAnswer.SIP parameter is enabled for the phones belonging to the site since Site has higher priority.

Software updates follow the same rule. For example, you select UC software 5.5 in profile A and select UC software 5.4 in profile B. You apply profile A to device group 1 and apply profile B to Global. The phones in device group 1 upgrade to 5.5. Other phones in Global upgrade to 5.4.

Profile deployment uses five containers to apply configuration profiles to managed devices. The following list shows the priority of the containers from the highest to the lowest.

  • Device: Configuration profiles in this container apply to the corresponding device that you specify. For example, you know a specific device needs a specific configuration or call server. You can select the device to receive the required configuration profiles.
  • Site: Configuration profiles in this container apply to the devices in the corresponding site. Geographical location is the typical use case for site.
  • Device Model: Configuration profiles in this container apply to the devices of the corresponding device model. For example, you can apply a customized configuration profile to all Polycom VVX 500 devices.
  • Device Group: Configuration profiles in this container apply to the devices in the corresponding device group.
  • Global: All devices are part of Global regardless of model, site, or device group. Configuration profiles in this container apply to all devices.