Dns reverse lookup not updating

23 Feb

This signals the intent to provide a single LPE client for both Lync platforms and not have separate 2010 or 2013 clients with different interfaces.What this all means is that to utilize any Lync Phone Edition devices with Lync Server 2013 the phone firmware may need updated to at least the CU7 release, which is version 4.0.7577.4363 / .4366 / .4372 for different device families.Lync Phone Edition will only attempt to retrieve the root certificate from the internal, Active Directory published CA during registration attempts, it was not programmed to perform this same action automatically upon bootup.So in this case user-intervention is required by attempting to sign-in to the Lync Server.The registration does not need to actually succeed so if the phone is running a vey old version incapable of registering to the Lync server for some reason, or an invalid PIN is used simply to speed up the process it does not matter.Simply initiating the registration process is sufficient to trigger the root certificate retrieval process via DHCP Option 43.

An AD-integrated Enterprise CA must be used to issue the certificate to the Lync Server.How can a device which cannot register to the server download an update from the server when it needs to first register to be provided the device update server information?This might mean that the device would instead need to be connected to and registered to Lync 2010 server first, then updated to CU7 or higher, no? There is one alternative which would allow any previous version of Lync Phone Edition to download an update package directly from a Lync 2013 server without even the ability to first successfully register to it.This little-known behavior is hardcoded into all firmware releases.The phones are programmed to look for a specific hostname which is not typically included in the Lync topology, but if it is added manually to the environment then phones will be able to update without signing in.