The IIS logs are extremely useful; Jeff Schertz has excellent blog posts on Configuring LPE for Lync and Updating LPE devices which go into reviewing the IIS logs.
In summary, it enables you to confirm whether devices are communicating with the device update site running on within the front-end pool, or in our case – NOT.
The process is even simpler to support, except for the case that a pre-release beta device is in question. The reboot simply triggers the phone to look for an update without waiting as long.
The large majority of Aries devices in existence today will have at least the Release Candidate version (4.0.7457), if not already at RTM. While waiting the IIS server logs on the Lync Server can be viewed to see what the phone is up to, as well as keep an eye out for the update version check.
Also note that the device’s specific hardware revision ( Less than 10 minutes later a second entry from the same device appears, this time reporting that it is running the latest 7577 build.
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.
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).
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.