Configure Microsoft Lync Server 2013 or Skype for Business for the Presence service Skip Navigation

Configure
Microsoft Lync Server
2013 or
Skype for Business
for the
Presence
service

Environments 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.
  1. In the
    BlackBerry Enterprise Mobility Server Dashboard
    , under
    BlackBerry Services Configuration
    , click
    Presence
  2. If necessary, click
    Service Account
    and type the login credentials for the
    BEMS
    service account.
  3. Click
    Lync 2013
    or
    Skype for Business
    . The system queries the instant messaging server to verify that the appropriate
    BEMS
    instant messaging server topology is added. This can take a few moments to complete.
  4. Complete one of the following tasks:
    Instant messaging server in environment
    Task
    Microsoft Lync Server
    2013
    1. In the
      Application ID
      drop-down list, select
      <
      appid_connect.mycompany.com
      >
      .
      If the drop-down list is empty, either the
      BEMS
      <
      instant messaging server type
      > topology is not set up correctly or the service account does not have permissions to query these settings.
    2. In the
      Application Endpoint
      drop-down list, select the corresponding application endpoint. 
    Skype for Business
    on-premises using trusted application mode
    Using this configuration, the
    Presence
    service is trusted by
    Skype for Business
    and can impersonate a user. End user authentication is not required on the device to view the presence status 
    1. Select the
      Skype for Business On-Premises
      check box. 
    2. Select
      Trusted Application Mode
      .  
    3. Beside the
      Application ID
      drop-down list, click
      Browse
      . This step can take up to a minute to complete.
    4. In the
      Application ID
      drop-down list, select the app ID for
      Presence
      to use the correct configuration information registered with the
      Skype
      topology. For example,
      <
      appid_connect.mycompany.com
      >
      .
      If the drop-down list is empty, either the
      BEMS
      <
      instant messaging server type
      > topology is not set up correctly or the service account does not have permissions to query these settings.
    5. In the
      Application Endpoint
      drop-down list, select the appropriate endpoint for the
      Presence
      service to use when subscribing to a user's presence status in the
      Skype
      topology.
    Skype for Business
    on-premises using non-trusted application mode
    Using this configuration, the
    • Presence
      service is not trusted by
      Skype for Business
      and cannot impersonate a user. End user authentication on the device is required.
    • Presence
      service passes through the web proxy if it is defined, but doesn't use the bypass list even if the
      Skype for Business
      servers are added to the bypass proxy list. In some cases authentication to
      Skype for Business
      might fail. For more information on configuring the web proxy, see "Configure a web proxy server" in the BEMS-Core configuration content.
    1. Select the
      Skype for Business On-Premises
      check box.
    2. Select
      Non-trusted Application Mode
    3. Complete one or both of the following actions:
      • Select the
        Auto discover servers
        checkbox to have
        BEMS
        discover the
        Skype for Business
        servers in the environment.
      • Enter the default
        Skype for Business
        on-premises FQDN or the complete URL to the
        Skype for Business
        server for
        BEMS
        to 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.
  5. Verify the
    Azure
    information is valid and log in to the user account:
    • If you configure the environment to use
      Skype for Business
      on-premises:
      1. Enter a user email address and password.
      2. Click
        Test
        .
  6. Click
    Save
  7. Complete one of the following actions:
    • If you configured the
      Presence
      service for
      Microsoft Lync Server
      2013, or
      Skype for Business
      on-premises using trusted application mode, start the
      Good Technology Presence
      service. Make sure that you save the configuration in the Dashboard prior to starting the service.
    • If you configured the
      Presence
      service for
      Skype for Business
      on-premises using non-trusted application mode only, you do not need to start the
      Good Technology Presence
      service.
      Skype for Business
      on-premises using non-trusted application mode don't require the
      Presence
      service 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 the
      Presence
      service for
      Skype for Business
      on-premises using non-trusted application mode only, restart the
      Good Technology Common Services
      to enable the
      BEMS
      cache to use memory instead of Redis.