Manually Lync/Skype for business Enabling of Active Directory contacts


We upgraded recently our Polycom RMX/DMA infrastructure which added the Skype video calling functionality as well as the presence for the DMA rooms in Lync.

According to Polycom official integration guide, they gave two options to enable the presence for the rooms, one automatic using a service account with Domain / Lync administrative privileges (which is not always an option for customers and was not an option also for my company), or there is the other way which is manual method which was not mentioned in the guide.

So I received a request to find a way to enable those contact as a Lync contact without giving this admin privileges to the DMA, if you try to use the Lync control panel you will face a problem when trying to search for the contact object you created and want to use. So following I will show the way to manually enable Active Directory contact objects for Lync 2013, to use it in whatever you need

Using ADSI Edit

Before you start you need to prepare some information

  1. You need the value of the Active Directory Attribute “msRTCSIP-PrimaryHomeServer”
  2. You need the value of the Active Directory Attribute “msRTCSIP-UserPolicies”

The attribute msRTCSIP-PrimaryHomeServer is the Registrar Lync pool you want to host this contact on, so when you have more than one Registrar pool make sure you are using the correct pool.

The msRTCSIP-UserPolicies attribute is where all applied Lync policies e.g. External access, Conference policy, client…etc. on the user are listed, the policy consist of a number xx=yyyyyyy, i’m not going to go deep inside this topic (for more details check this article) but you need to get this value from an enabled user with same assigned policies.

the procedure of enabling the Active directory contact object is very simple:

  • Using the ADSI connect to the default naming context
  • expand your forest and go to the OU where you have an already enabled Lync user with same policies you would like to apply on the contact object.
  • right click it and select “properties”
  • copy and past the values of the required two attributes mentioned previously in this article into a notepad.
  • starting with msRTCSIP-PrimaryHomeServer, locate the attribute and double click it




  • copy the whole string and past it into the notepad, you will need it later
  • do the same with msRTCSIP-UserPolicies but this time you need to take notes yourself, no copy / paste is possible


  • double click it and take notes of the values you will need them later


now that you have all required information close the properties of the the enabled user and make your way to the OU that contain the contact object you want to enable for Lync and do the following steps:

  • right click the contact object and select properties
  • locate the msRTCSIP-PrimaryHomeServer attribute which should show the value <not set> double click it and copy the value you took earlier from the notepad into the dialog window and click “ok”



  • double click on the msRTCSIP-PrimaryUserAddress attribute and put the SIP-URI you assigned to the contact object, it must be in the format sip:abc@sipdomain then click ok


  • locate the msRTCSIP-UserEnabled attribute and set it to “True” by double clicking it and selecting the value “True” then click ok.



  • locate the msRTCSIP-UserPolicies attribute and set it to “Values” you already took notes of previously, double click the attribute and start adding those values one by one



  • once done click ok
  • locate the msRTCSIP-FederationEnabled attribute and set it to value “True” by double clicking on it and selecting “True” then click ok



now that all is set, back to the Prosperities windows click on “Apply” then ok to close it, that all it takes to enable Active directory Contact for Lync to use with DMA rooms or whatever you need it for.

now if you use the Lync control panel and search for the Object in the enabled users, the search will return the contact in the results.

Author: Lyncdude

A Senior Service Engineer with more than 9 years of experience in Microsoft Exchange and Microsoft Lync Server / Skype for Business. Egyptian guy lives and works in Frankfurt - Germany. what is written in this blog is my own opinion and thoughts, not my employer and does not reflect their opinion

2 thoughts on “Manually Lync/Skype for business Enabling of Active Directory contacts”

  1. Hi LyncDude,

    Thanks for the great article.

    I have the same issue here, not much chance of getting the required permissions for the DMA to auto create the virtual meeting rooms in AD.

    Any chance you could answer a couple of questions fo rme please?

    I’m wondering what SIP address the DMA enters into the AD contact it creates for the VMR?

    I’m hoping to be able to call the VMR’s directly from Lync clients using the directory.

    Does it work that way?

    Any help would be appreciated.



    1. Hi Graeme, in my scenario, i had a second SIP domain added to the topology to serve only the DMA rooms, i also added the DMA as a trusted application to the Topology, then i created the required Static routing in Lync for this SIP domain so that calls coming from Lync clients to this SIP address is routed to the DMA.

      in AD i used the SIP domain i planned to use for DMA when enabling the contacts and i could see the presence of the rooms as well as dialing into them from Lync, that’s all hope it helped

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: