May 20, 2011 by in IT Infrastructure
Wadeware had an issue with our Common Area Phone that prevented it from logging on to our Lync Server. We verified that our settings, cabling, and network connectivity were fine, but it still wouldn’t log on the network. To troubleshoot the issue, we ran the following command on our Lync Server:
Test-CsPhoneBootstrap –PhoneOrExt 200 –PIN 12345
We got this result:
In response to the output results of the test, we recreated the Wadeware Lync DHCP options but still got the same error after running the test again. (For instructions on creating the Lync DHCP options, see below in this blog post). I again reviewed the results of the Test-CsPhoneBootstrap command, and noticed that the DHCP server IP address it was hitting was incorrect.
The command was querying our Windows Deployment Server. When I stopped the Windows Deployment Server service on this server, the phone was able to log on to the Lync Server!
Turns out our Windows Deployment Server was giving out DHCP addresses in the same subnet as our domain. We changed this and that resolved the issue. I thought it would be worth sharing this in hopes of helping others out who may encounter the same issue.
If this fix doesn’t solve your Common Area Phone issue, review the results of the command above, as they may give you other hints about how to arrive at your solution. Good Luck!
To create the Lync Server DHCP options:
- On your Lync Server, start the Lync Server Management Shell, and then run the following command: C:\Program Files\Common Files\Microsoft Lync Server 2010> .\DHCPUtil.exe -sipserver PoolName.Domain.com -webserver PoolName.Domain.com
- Replace poolname with your pool name (for the Enterprise Edition) or the front-end server name (for the Standard Edition), and domain.com with your domain name. The output of this command will produce a command for you to run on our DHCP server.
- Copy the output from the above command and bring it to your DHCP server. Also, copy over C:\Program Files\Common Files\Microsoft Lync Server 2010\DHCPConfigScript.bat to your DHCP server.
- On your DHCP server, at an elevated command prompt, run the command you produced in the earlier step . (It is one long command) It will look something like this: “C:\DHCPConfigScript.bat” Configure MS-UC-Client 0005706F6F6C3031082761646227617265036E617400 4A532D57832D436B69629E74 6871547073 706F0F6C30312E886161657761704352E6E6344 343411 2E4365727453696F762F4365727450725C766123696F6E696E67536572766789652E737366
Completing these steps will create the necessary DHCP scope options that the Lync devices will use, including common area phones and conference room phones. The DHCPUtility.exe creates the values for options 120 and 43. The DHCPConfigScript.bat uses the output of the DHCPUtility.exe to configure Windows DHCP with options 120 and 43, tests the DHCP server configuration, and cleans up the configuration.