Active directory reverse dns not updating
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.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.Lync Server 2010 now has multiple versions of the update package, as they are both different clients (with different interfaces and features) as well as different device designs between vendors.
(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.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.My advice is to upgrade these using an OCS environment with this process documented by Rui Silva. As with all software updates it would be prudent to first test one a single device before blasting it out to all of the phones in the organization.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.