Those who are familiar with the certificate warning message: Lync cannot verify that the server is trusted for your sign-in address. Connect anyway? … that is presented by the Lync 2010 client when signing into a domain that is different than your sign in address:
I recently completed a Lync Server 2010 to 2013 migration and found that setting up RCC integration between Lync Server 2013 and Avaya AES (Application Enablement Services) was exactly the same as Lync Server 2010. Avaya has yet to provide an updated guide for the
One of the tricks I use most over the years while working or troubleshooting issues with OCS and Lync was to manually force the Lync 2010 and 2013 client because waiting for the address book to download can take quite a bit of time. As
I’ve recently been asked several times to look at why a Lync Server 2013 server’s LS Address Book Server consistently logs the event ID 21054 error whenever the address book is updated with Update-CsAddressBook cmdlet or after the maintenacne that is ran every day: The
I’ve had to do quite a bit of troubleshooting with an Avaya and Lync Server 2010 RCC integration last year which was when I realized that simply selecting S4 and SIPStack as components in the logging tool did not provide any useful information. Fast forward
At the time of writing this post, Exchange Server 2010 SP3 was finally released 2 days ago but the final component required for organizations to migrate their Exchange Server 2010 infrastructure to Exchange Server 2013 is to wait for Microsoft to release Exchange 2013 CU1
I’ve recently been asked to resolve some issues for the Lync Mobility service after recent migrations from Lync Server 2010 to 2013 were completed and I have composed a list of items administrators tend to miss. Note that the official deployment guide on TechNet can
As many may know, Lync Server 2013 no longer requires separate servers for the Monitoring and Archiving role as they are now collocated directly on the front-end server. This is definitely a welcome changed as it reduces the amount of servers required for a Lync
I’ve been asked quite a few times in the past about how an administrator can export archived IM messages from a Lync Server archiving database and while I faintly have an idea of the PowerShell cmdlet used, I find that I can never remember exactly
Similar to one of my previous posts: Moving Central Management Server from Lync Server 2010 enterprise front end pool to 2013 enterprise front end poolhttps://blog.terenceluk.com/2013/01/moving-central-management-server-from.html … this post serves to demonstrate the process of moving the Central Management Server from a Lync Server 2010 Standard
