Problem You’ve successfully installed the Lync 2013 client on your Citrix XenApp 6.5 servers but noticed that when you launch the published application through the Web Interface portal, it crashes with the following output: Microsoft Lync has stopped working Windows can check online for a
Problem You’ve configured federation between two Lync Server 2013 environments and noticed that one of the organizations can send instant messages and see presence information but the other one cannot. The following is the organization that can send instant messages and see presence: While the
Problem You’ve completed a new greenfield deployment or successfully migrated from Lync Server 2010 to Lync Server 2013 with Windows Server 2012 servers as the base operating system but noticed that your Lync Edge servers are not replicating and executing the Invoke-CsManagementStoreReplicationStatus cmdlet then the
I’ve been meaning to blog about an issue I noticed in environments with disparate namespaces (internal domain name is different than external) where no matter how I configured the DNS for the internal or public forward lookup zones, I could not get around the following
Those who may be familiar with the following KB explaining why having a SIP domain for Lync that is different than the internal domain FQDN would present the user with the following message upon logging into their Lync 2010 client: “Lync cannot verify that the
As indicated in one of my earlier posts: Lync Server 2010 or 2013 IM (Instant Messaging) conference no longer works with RCC (Remote Call Control) configured with a PBX https://blog.terenceluk.com/2013/03/lync-server-2010-or-2013-im-instant.html …. the instructions provided by the guide: Implementation notes on Integration of Avaya Aura Application
Problem You’re performing a greenfield deployment of Lync Server 2013 in a environment and have completed defining a standard server in the topology then proceed to publish the topology: … but notice that it errors out: Reviewing the logs show the following error: ACLError: Access
I’ve been called a few times in the past to look at the issue where Lync Server 2010 or 2013 IM (Instant Messaging) conference no longer works when RCC (Remote Call Control) is configured with a PBX and as simple as the root cause is
Problem You attempt to export the IM logs from a Lync Server 2010 archive database with the cmdlet: Export-CsArchivingData -Identity “ArchivingDatabase:svrsql200801.contoso.internallyncarc” -StartDate 1/1/2010 -OutputFolder “C:ArchivingExports” … but receive the following error: PS C:Userstluk> Export-CsArchivingData -Identity “ArchivingDatabase:svrsql200801.contoso.internallyncarc” -StartDate 1/1/2010 -OutputFolder “C:ArchivingExports”Export-CsArchivingData : A parameter cannot be
I have had quite a few clients who continually ask me as to when the Skype and Lync federation details are going to be available and it was not until a week ago when Microsoft officially released a statement that it would be around June
