I’ve deployed a lot of Lync Phone Edition devices. Thing is, I’ve done so mainly in smaller environments where we used either a Standard Edition Front-end server or an Enterprise “pool” that consisted of a single server. Why is this important you ask? Well, let’s go to one of the best articles on DHCP Option 43: http://blog.schertz.name/2012/05/understanding-dhcp-option-43/

In Jeff’s article, he has this paragraph in the middle of it:

If multiple Lync servers are deployed in the environment then the _SipServer _parameter may need to be defined as a Lync Pool FQDN (in the case of an Enterprise Edition deployment).  Additionally if any load balancing is configured on the Front End pool and the Internal Web Services FQDN is different than the Pool FQDN (in the case of DNS Load Balancing) then an additional switch of _WebServer _needs to be used to provide the Web Services FQDN.  If the WebServer swtich is not provided the command uses the _SipServer _value by default for both the registrar and web services location.

Additionally if a Director Server or Pool is in place then the Director FQDN is typically defined as the _SipServer _parameter (and the _WebServer _parameter is not needed).

*** Update 11/27/2014 - It was asked in the comments if this applies to the Lync Phone Edition devices (LPE). LPE is created/maintained by Microsoft but various companies manufacture the devices, including Polycom. The Polycom LPE’s are the CX series phones. This article does not apply to the LPE devices. It only applies to the Polycom phones that run Polycom’s own software such as the VVX line of phones.

Lately, I have found myself having to do the math for the time offset for DHCP Option 002. I decided it was worth just documenting them so I could look them up quickly and what better way to come up with all of them than with Powershell?