Domanite and submessive chat rooms for teens - Updating background
Microsoft continues to release semi-quarterly Cumulative Updates of firmware for the various LPE models.In the round of releases in December 2012 and January 2013 (aka CU7) official support for Lync Server 2013 was added, as well dropping the ‘2010’ from the previous name of .
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.
This article is a brief update to the process previously documented for Lync Server 2010.
In Lync Server 2013 the Device Update service is unchanged and the steps shown in that article are still applicable, so why the need for a new post on this subject?
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.
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.
This confirms that the device does not inherently trust the certificate assigned to the Lync server so the root CA certificate which signed the Lync server certificate must be downloaded to the phone.