Lync 2013 Publish Topology Completed with Errors / Failed

While i was working on configuration of Lync i got a error When I do publishing the topology from the Lync 2013 topology builder.

FEB-064

When i check view log i got the exact error message saying:

FEB-065

A trusted server with the type “” and the fully qualified domain name (FQDN) “” was found for a different Transport Layer Security (TLS) target

To fix this issue you have to delete entries in ADSIEDIT.MSC

  • Open ADSIedit
  • Navigate to Configuration > CN=Services > CN=RTC Service > CN=Trusted Services
  • There you will find many entries. Right click an entry and select properties
  • type: “msr”
    • to find the Lync entries
  • Delete each entry concerning your trusted server, make sure it matches type and portnumber

FEB-0661

 

  • Try to Publish the topology again and it should be successful.
  • Here are my results:

FEB-067

  • ADSI entries will be recreated automatically on the same location.

Lync 2013 Management Shell Stuck / not working

While fresh installing Lync, I got a problem on launching Lync 2013 Management shell that it got stucks and didnot show anything on screen. Here is the screenshot:

JAN-0092

 

For solving this: Start Windows Powershell as Administrator

copy and past the correct target of the Management Shell:

cd C:Windowssystem32WindowsPowerShellv1.0
powershell.exe -noexit -command "cd $env:UserProfile; Import-Module 'C:Program FilesCommon FilesMicrosoft Lync Server 2013ModulesLyncLync.psd1'"

now try and open the normal Lync Management Shell, everything should work.

Forest Preparation Failed Lync 2013

While i was installing Lync 2013 on server 2012 R2 i got an error on the step of Forest preparation as given in the screenshot:

JAN-0089

 

To resolve this error i opened Lync powershell from start menu and ran this command:

Enable-CsAdForest -GroupDomain domain.local -GlobalSettingsDomainController dc.domain.local -GroupDomainController dc.domain.local -GlobalCatalog dc.domain.local

After running this command try to run the setup again and it will be fine this time.