Additionally Microsoft plans to release new versions of the Lync Phone Edition client quarterly as Cumulative Updates (CU).
Just last week CU1 was released and CU2 is slated for release in Q2 2011.
The device is again asking for a download package, but since it is now on the latest approved no URL response is given by the Lync Server.
After some time has passed and sufficient testing has been completed in the environment then each of the supported device updates should be approved so any device can be updated automatically.
So there are now three separate packages which can be downloaded: one for the original Tanjay devices, a second for Polycom’s Aries devices, and a third for Aastra’s Aries devices.
These packages unfortunately are all identically named as so be careful when downloading more than one at a time.
Previously the only supported devices that used the Office Communicator Phone Edition client were the Microsoft reference-design “Tanjay” family of devices: the Polycom CX700 and LG-Nortel IP8540.
Both phones were identical and used the exact same software so a single installation package was distributed and updated on a regular basis.
Within the log two distinct entries should be seen for the specific CX500 device which was updated.
There are two different logs which will contain device request details, the IIS logs and the Lync Device Update logs.
(Microsoft Lync 2010 Phone Edition) 200 0 0 36 2011-01-23 192.168.103.23 POST /Request Handler/– 443 – 192.168.103.105 Microsoft UCPhone Device (lcs_se_w14_main:824410/10/:00) 200 0 -01-23 192.168.103.23 POST /locationinformation/liservice.svc/Web Ticket_Bearer – 443 – 192.168.103.105 The Device Update Update server logs can also be used, which show even more detail.
Secondly there is a brand new Lync Phone Edition client which only runs on the new Aries family devices: the Polycom CX500, CX600, CX3000 and Aastra 6721ip, 6725ip.
Although the client features are identical between the Aries devices the firmware is unique between the different manufacturer’s devices in order to support differing hardware components and physical features.