Communicator 2016 status not updating
The server hosting our local category database was offline for several hours.
During that time, our Proxy SG's accumulated update errors for the Local Database subscription service and exceeded the Critical threshold.
For example:) is 1 so Communicator marks it as an invalid number and did not show the number in the Directory tab. CAS add in was not enabled and then the test number used was in the wrong format.
Updates provide a great way to communicate what you're up to by using a quick, specific message, such as "My car broke down!
Even video conference and screen sharing work very well for a Microsoft product.
The only thing that was really painfull was that everytime I disconnect my Mac from LAN and come back again, Communicator just stays in it’s “error” mode and I never think of manually reconnect.
While googleing for ways to detect network changes on mac OS, I found a very nice and useful Blog post that explaining how to just do that.
It’s not very complicated, but it’s not that really straight forward to have it setup.
So will start be listing common problems that I faced in my day – to – day work Before going any deeper in what is causing the problem, make sure that Lync – outlook is integrated before wasting any time trying to locate the problem while it might be that Lync add-in not installed correctly.
Lync client depend on the Exchange web services for the integration with Outlook and it will use the user’s SMTP domain to search for the DNS records for the Autodiscover and web services, so it will look for: https:///autodiscover/As well as your autodiscover SRV record (_autodiscover._tcp.smtpdomain) It is often that Lync client configuration status don’t shows the internal and external URL of the EWS and the EWS information shows “EWS Not Deployed”, and this causes some integration problems between Lync and Outlook like prompting for username and password, not populating your presence information from outlook calendar You can check the EWS status via registry key For Lync 2010 Client Locate HKCU\Software\Microsoft\Communicator\address\Autodiscovery For Lync 2013 Client Locate HKCU\Software\Microsoft\office.0\Lync\address\Autodiscovery Make sure the following enteris are correct External Availability Server Url Internal Availability Server Url External Ews Url Internal Ews Url External Oof Server Url Internal Oof Server Url If this key does not exist on your machine this mean Lync was unable to locate DNS records or SRV for the Autodisvoer services, so go ahead with checking your Exchange server side You will need to check 1.
The udpates can be deployed using Apple Remote Desktop or most other deployment tools.