Topology publishing fails because Trusted Server and FQDN already exists for a different TLS target

When upgrading our Lync infrastructure from 2010 to 2013 I encountered some errors upon the first time I would publish the Lync Server 2013 Enterprise pool, consisting of three Front End servers and a fresh SQL server instance.

Diving into the resulting log file can quickly lead you to think that almost everything failed, as every parent category of the action point that actually went wrong will also be labeled “Completed with errors” or “Failed”. Therefore it is important that you (for your own mental well-being) filter out those things and drill down to the action point that is causing the problem, often with the “Execution result” column simply indicating “Error”.

Advertisement

Adding DFS Shares in Topology Builder

​Today I ran into an issue, as a customer I am currently installing Lync Server 2010 for was looking to use their already established DFS file share with Lync. This feature has been supported since the dawning of OCS14, but funny enough not something that could be accomplished in the TB.

Since CU5 in February this was something that MSFT fixed, as stated in the KB article. Nevertheless, I could not get it working. Entering a DFS root and the share name (Share name = dfsroot\share) only resulted in an error. This was despite that CU5 had been applied to the Administrative Tools, TB included.