About how to handle Lync edge replication errors

After Lync edge deployment is completed, many friends recently found that the edge replication result is an error on the topology page of The Lync control panel, as shown in:

650) this. width = 650; "height =" 138 "title =" image "style =" border: 0px currentcolor; background-image: none; padding-top: 0px; padding-right: 0px; padding-left: 0px; "alt =" image "src =" http://www.bkjia.com/uploads/allimg/131228/0105135F7-0.png "border =" 0 "/>

So what is the cause of this problem? In fact, the reason is very simple. Some enterprises prefer to add edge nodes to the domain When configuring Lync. Of course, this is not recommended. We recommend that you refer to the relevant Microsoft planning and deployment guide configuration during deployment) at this time, the Lync edge will certainly not have a replication error, and this method is relatively simple to configure the edge. Microsoft recommends that you deploy the Lync Edge server in the enterprise Lync environment as a working group without adding the LYNC Edge server to the domain. When we deploy the Lync edge in the enterprise as a working group, we also marked the Edge Server Information in the topology, but note that because the Lync edge does not add a domain, how can the edge be obtained when the topology information is updated or changed? I believe many people have come up with the idea that they can search for and publish information through the FQDN name of the Edge Server defined in the topology. In this case, the defined FQND name cannot be queried through DNS, in this case, an error occurs during replication. The solution is simple. Here I will introduce it:

Method 1: manually add records about edge servers to the Host file of each LYNC front-end server. This can also solve this problem.

Method 2: manually create A record on the Edge server on your DNS server, which ensures that the Edge Server can be found smoothly during topology replication and can also solve this problem.

In fact, this problem is not complicated to solve. We still need to pay attention to these small details when configuring Lync, so as to avoid such errors after the configuration is complete, now, I will share my thoughts on how to handle edge replication errors in Lync. I hope to help more friends who encounter such problems.

This article from the "stupid bird first fly" blog, please be sure to keep this source http://tingdongwang.blog.51cto.com/1056852/1241137