None of your company’s Cisco Jabber clients are able to automatically retrieve configurations from your
company’s UCM 8.6 deployment.
Which of the following is most likely the reason?

A.
A service profile has not been configured in UCM.

B.
The _cisco-uds SRV record has not been configured in DNS.

C.
Automatic configuration is not selected in Jabber’s Advanced settings.

D.
The users have not been configured with the IM and Presence Service.

E.
UCM releases earlier than 9 do not support automatic configuration.

Explanation:
Of the available choices, the most likely reason that your company’s Cisco Jabber clients are not able to
automatically retrieve configurations is that Cisco Unified Communications Manager (UCM) releases earlier
than 9 do not support the automatic configuration of Cisco Jabber clients by using service profiles. Cisco
Jabber’s Advanced settings dialog box features an Automatic option that allows Cisco Jabber to automatically
configure itself as long as all of the following are true:
-UCM is operating at release 9 or later.
-A correct _cisco-uds Service (SRV) record has been configured on the Domain Name System (DNS) server.
-Automatic is selected in Advanced settings.
-An instant message (IM) and Presence Service profile has been configured in UCM.
-The IM and Presence Service profile has been correctly applied to end users in UCM User Management.
There is not enough information in the scenario to determine whether a service profile has not been configured,
whether the DNS record is missing, whether automatic configuration is not selected, or whether the users have
not been configured with the IM and Presence Service. Even if that information were provided, the UCM
deployment in this scenario is running release 8.6, which does not support the automatic configuration of Cisco
Jabber clients.

Cisco: Configure the Clients: Introduction to Client Configuration