This client looks nearly identical to the previous version but has a few tweaks (most prominently a Lync Server branded background).
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.
(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.
But unless a device ‘checks-in’ for an update nothing will appear in these logs so starting with the IIS logs is a good troubleshooting habit.
Within the log two distinct entries should be seen for the specific CX500 device which was updated.
The first line shows the device on it’s original 7457 build asking for the internal and external URLs to download an approved update from.
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.
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.
If a device has the slightly newer beta version 1.0.452 or 1.0.522 then this process also documented by Rui can be used. The Test Device configuration in Lync Server allows for a single device to automatically download the latest version of the software available regardless of whether it has been approved yet or not.
In most cases the latest OCS 2007 R2 software (3.5.6907) will be installed on a Tanjay and this version is capable of signing directly into Lync Server given that the required DHCP options are configured. At this point a reboot of the phone can help kick things off a bit quicker as well as make it easy to track the progress though server logs which may be full of activity from other devices in use on the network.
When updating Aries device there are no legacy hostnames used and as these devices only operate with Lync Server. Download and install the update package on to the Lync Server. Configure a test device to first validate a successful update and working installation. Trigger an update on the test device (or just wait). But understand this is not necessary and now that the Test Device is created the associated device will update on it’s own after a period of inactivity (typically 10 minutes).