Posted in Lync Server 2010, Lync Server 2013, Polycom, Skype for Business

Setting up DHCP Server Options for Lync Phone Devices

This guide will set the DHCP options using DHCPUtil.exe command to support Lync Phone Devices and other Lync related UC devices. Options include 1, 2, 3, 4, 5, 6, 15, 42, 119 and 120. Copy below files from Lync server C:\Program Files\Common Files\Microsoft Lync Server 2013

  • DHCPConfigScript.bat
  • DHCPUtil.exe
  1. Setting of Time Server and NTP Server
    • Go to DHCP Scope Options -> Configure Options
    • Set Option 4 Time Server
    • Set Option 42 NTP Server

Note: The time server should be the PDC emulator and the NTP server is found by w32tm /query /configuration

  1. Setting of DHCP option 119
    • R-click the IPV4 -> Set Predefined Options
    • Click Add button
    • Enter below details:
      • DNS search
    • Click OK.
    • Option 119 should now be available from Configure Options list
    • Go to DHCP Scope Options -> Configure Options
    • Type;contoso.local; at the String value section
      • DNS search 2
  2. For DHCP Server 64-bit
    • Copy the files (DHCPConfigScript.bat and DHCPUtil.exe) to temp location in DHCP server like e.g.  C:\DHCPFolder
    • Run from windows command shell as Administrator in DHCP server:
      • C:\DHCPFolder>DHCPUtil.exe -SipServer Lyncpool.contoso.local –WebServer Lyncpool.contoso.local –RunConfigScript
  3. For DHCP Server 32-bit
    • DHCPUtil.exe will not work with 32-bit server. So we have to run the DHCPUtil.exe command from Lync Server or any 64-bit server and paste the result to DHCP server.
      • Copy the file (DHCPUtil.exe) to temp location in Lync server like e.g.  C:\LyncFolder
      • Copy the file (DHCPConfigScript.bat) to temp location in DHCP server like e.g.  C:\DHCPFolder
      • Run from windows command shell as Administrator in Lync server:
        • C:\LyncFolder>DHCPUtil.exe -SipServer Lyncpool.contoso.local –WebServer Lyncpool.contoso.local
      • Output looks like:
      • dhcp 32-bit
      • Copy the output above from .\DHCPConfigScript.bat …..up to …37663, make sure copy as it is without deleting or adding spaces (I suggest to copy it first to notepad).
      • On the 32-bit DHCP server, run the command like below:
        • C:\DHCPFolder>DHCPConfigScript.bat Configure MS-UC-Client 0000….up to 7663
  4. Both 64 bit and 32 bit will have a result of additional options from the DHCP server like below.
    • DHCP options

Hope it helps!

Posted in Lync Server 2010, Lync Server 2013, Skype for Business

Failed while updating destination pool.

Failed while updating destination pool

You will encounter this issue when:

  1. The user you are trying to make change/s has elevated rights in Active Directory e.g. Domain Admins
  2. The account login in Lync Control Panel has lower rights compared to the user you are making change/s.


Use Lync Management Shell to make change/s on the user properties. And your account used to run Lync powershell should at least have same rights or higher.

Posted in Lync Server 2010, Lync Server 2013, Polycom, Skype for Business

Polycom PIN Authentication Not Working

When you are sure and confident that you have already configured DHCP server to support Lync phones however PIN authentication still not working with Polycom CX and VVX series, try to check the version of your NTP servers in the environment.

I had an issue before that AudioCodes 4xxHD phones are surprisingly working with PIN auth while Polycom CX and VVX weren’t.

Wireshark Trace from NTP version 3.NTPv3

With all the NTP servers listed, all of them replied version 3 only. And from the packet, it seems the clock is not synced.

Wireshark Trace from NTP version 4

NTPv4One NTP server is on version 4 and from the packet, clock has no warning.


By standard, NTP version 4 should be compatible with version 3, but for some reasons version 3 does not works well on Polycom phone. So ask your customer to setup a new NTPv4 to support your VVX or CX phones and add it to your DHCP configuration. PIN authentication should work after that.


Posted in Lync Server 2013

Topology Builder could not copy the topology from the Central Management store. Cannot read topology. Verify that the topology data is accessible.

Cannot download topology

Sometimes you will encounter this error upon installation of Lync Server 2013 Standard Edition and the Central Management Store (CMS) is hosted on other sites. And basically you used a different user to install the Standard Edition server which don’t have access or right into the XDS database.


  1. Open the xds database
    • XDS issue
  2. Add the user used to download the topology. Assign as db_owner.
    • db_owner
  3. Log off and login again from Lync SE and download of topology should be successful at this time.