The Office Communicator window will close but the application will continue to run, and the Office Communicator icon will still be displayed in the taskbar.
The Welcome to Office Communicator window is displayed, and you are signed out of Office Communicator.
If you close Office Communicator without signing out Office Communicator will continue to run in the background (you can still receive instant messages and others can still view your presence status).
To sign out you must use the menu in the Office Communicator title-bar.
Do not open tickets on our trac about these plugins.
Many other people have noted success in the comments.
With Installer: CLICK HERE TO DOWNLOAD (374.91 k B) (12656 downloads so far) Without Installer: (Portable Edition) CLICK HERE TO DOWNLOAD (17.22 k B) (6992 downloads so far) Just run the installer and the program will be installed in the Start Menu (and Desktop if you want it there! A note on compatibility: It should run on Windows XP, Windows Vista, and Windows 7. It’s been tested by me on Windows XP Professional and Windows 7 Ultimate (64bit).
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.
Some plugins are distributed in packages for specific operating systems.