Configure Microsoft Lync
Server 2013 or Skype for Business for the Presence service
Microsoft Lync
Server
2013 or Skype for Business
for the Presence
serviceEnvironments configured to use
Microsoft Lync
Server
2013, or Skype for Business
on-premises that are using trusted application mode use the Unified Communications Managed API (UCMA) software for the Presence
service to communicate with the instant messaging server. Environments configured to use Skype for Business
on-premises that are using non-trusted application mode use Unified Communications Web API (UCWA) software for the Presence
service to communicate with the instant messaging server. - If your environment usesSkype for Businesson-premises using non-trusted application mode, make sure that theSkype for Businesson-premises root CA certificate is imported. For instructions, see "Import the CA certificate into the Java certificate store" in the BEMS-Core configuration content.
- If your environment usesSkype for Businesson-premises using non-trusted application mode theGood Technology Presenceservice is not used.
- If your environment uses multipleSkype for Businesson-premises servers using trusted application mode or non-trusted application mode, have theSkype for Businessservers load balanced with a load balancer. For more information about load balancing requirements, visit https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/load-balancing.
- In theBlackBerry Enterprise Mobility Server Dashboard, underBlackBerry Services Configuration, clickPresence.
- If necessary, clickService Accountand type the login credentials for theBEMSservice account.
- ClickLync 2013orSkype for Business. The system queries the instant messaging server to verify that the appropriateBEMSinstant messaging server topology is added. This can take a few moments to complete.
- Complete one of the following tasks:Instant messaging server in environmentTaskMicrosoft Lync Server2013
- In theApplication IDdrop-down list, select<.appid_connect.mycompany.com>If the drop-down list is empty, either theBEMS<instant messaging server type> topology is not set up correctly or the service account does not have permissions to query these settings.
- In theApplication Endpointdrop-down list, select the corresponding application endpoint.
Skype for Businesson-premises using trusted application modeUsing this configuration, thePresenceservice is trusted bySkype for Businessand can impersonate a user. End user authentication is not required on the device to view the presence status.- Select theSkype for Business On-Premisescheck box.
- SelectTrusted Application Mode.
- Beside theApplication IDdrop-down list, clickBrowse. This step can take up to a minute to complete.
- In theApplication IDdrop-down list, select the app ID forPresenceto use the correct configuration information registered with theSkypetopology. For example,<.appid_connect.mycompany.com>If the drop-down list is empty, either theBEMS<instant messaging server type> topology is not set up correctly or the service account does not have permissions to query these settings.
- In theApplication Endpointdrop-down list, select the appropriate endpoint for thePresenceservice to use when subscribing to a user's presence status in theSkypetopology.
Skype for Businesson-premises using non-trusted application modeUsing this configuration, the- Presenceservice is not trusted bySkype for Businessand cannot impersonate a user. End user authentication on the device is required.
- Presenceservice passes through the web proxy if it is defined but doesn't use the bypass list even if theSkype for Businessservers are added to the bypass proxy list. In some cases, authentication toSkype for Businessmight fail. For more information on configuring the web proxy, see "Configure a web proxy server" in the BEMS-Core configuration content.
- Select theSkype for Business On-Premisescheck box.
- SelectNon-trusted Application Mode.
- Complete one or both of the following actions:
- Select theAuto discover serverscheckbox to haveBEMSdiscover theSkype for Businessservers in the environment.
- Enter the defaultSkype for Businesson-premises FQDN or the complete URL to theSkype for Businessserver forBEMSto use if autodiscovery is not enabled or fails. For example, http(s)://<FQDN_of_the Skype_front_end_pool>/Autodiscover/AutodiscoverService.svc/root/oauth/user.
- Verify theAzureinformation is valid and log in to the user account:
- If you configure the environment to useSkype for Businesson-premises:
- Enter a user email address and password.
- ClickTest.
- ClickSave.
- Complete one of the following actions:
- If you configured thePresenceservice forMicrosoft Lync Server2013, orSkype for Businesson-premises using trusted application mode, start theGood Technology Presenceservice. Make sure that you save the configuration in the Dashboard prior to starting the service.
- If you configured thePresenceservice forSkype for Businesson-premises using non-trusted application mode only, you do not need to start theGood Technology Presenceservice.Skype for Businesson-premises using non-trusted application mode don't require thePresenceservice to view users' presence status. If you try to start the service, the following error message is displayed.Windows could not start the Good Technology Presence service on Local Computer. Error 5: Access denied.
- If you configured thePresenceservice forSkype for Businesson-premises using non-trusted application mode only, restart theGood Technology Common Servicesto enable theBEMScache to use memory instead of Redis.