Active directory reverse dns not updating

Rated 3.86/5 based on 708 customer reviews

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.

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.

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.

This is basically the same process as was used in Office Communications Server except that now there are multiple update packages, which on the surface appear to be identical.

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).

When working with Tanjay devices the Lync Server Client Version Policy by default blocks clients running version 1.0.196 or older.

These are very old beta versions that I have not even had my hands on in a long time and unfortunately cannot test upgrading them directly against Lync Server.

Leave a Reply