Controlling Skype for Business Contact Card


When displaying the contact card, the Skype for Business client merges contact data from different sources. The merged data performs name resolution when performing a user search. In a more complex deployment scenario where an email domain name is in shared use in two Active Directory forests, you might run into a situation where the Skype for Business client tries to use the wrong target address.

Such a scenario would look like as follows.

Forest A is used as a dedicated infrastructure for developers. When logged on to the development network, the users should be able to Skype with colleagues currently connected to the default office client network.

Forest B is the default office client network.

Clients logged on to Forest A and connected to Forest B’s Skype for Business infrastructure as external clients. Forest A is used for user account authentication, while Forest B uses Skype for Business connection and authentication. 

Forest A

Forest A runs an Exchange Server 2013 organization.

  • Active Directory domain:
  • SMTP domains:,

Forest B

Forest B runs an Exchange Server 2013 organization and a full Skype for Business 2015 server deployment.

  • Active Directory domains:
    • root.internal – Forest root, resource domain with Skype for Business 2015, Exchange 2013
    • – user domain, primary email domain
  • SMTP domain:

Both Active Directory forests do not have trust of any sort established.

Such a configuration would result in Forest A users trying to contact a Skype for Business user using the wrong address. Instead of using, the Skype for Business client of Jane (logged on to forest A) would try to contact As no endpoint is defined for a connection could not be established. Therefore, no availability information is available, and no call or chat connection can be established.


The Skype for Business client uses merged data from the Skype for Business address and the local (Forest A) Active Directory (GAL). This results in a connection attempt to

Forest A object attributes

  • proxyAddresses:
  • proxyAddresses:
  • msExchShadowProxyAddresses:
  • msExchShadowProxyAddresses:
  • msExchShadowProxyAddresses:
  • msRTCSIP-UserEnabled: TRUE
  • msRTCSIP-PrimaryUserAddress:

Forest B object attributes

  • proxyAddresses:
  • proxyAddresses:
  • msRTCSP-InternetAccessEnabled: TRUE
  • msRTCSIP-UserEnabled: TRUE
  • msRTCSIP-PrimaryUserAddress:


  • Create a new text file named ocapi_test.config.xml using notepad
  • Add the following Xml text
  • Save the file in same directory as Lync.exe
  • Terminate the Skype for Business client
  • Delete all files from the users SIP folder
    • e.g.
  • Restart the Skype for Business client

Enjoy Skype for Business

%d Bloggern gefällt das: