-->

Sunday, August 16, 2015

Lync 2010 Edge replication issue with Front-end server.

 

Introduction



Lync 2010 edge role is synchronized with the (CMS) which is running on front-end pool and due to this replication between front-end and edge server everything on edge works correctly. Assuming that we do not have other problem with edge such as configuration issue in Topology.

All information from Central Management Store is replicated to Edge server. But if Lync 2010 edge is Out-of-Sync with CMS( Central Management Store) we experience lot of issues and it;s very hard to trace those problems.

One way, you may argue is to start troubleshooting Lync edge by checking replication status at the beginning itself. You are in thinking in right direction.



Here is what we can do to solve these replication problems.


Resolve replication issue with Lync edge

Verify Replication Status

Lync 2010 Central Management Server keeps updated replication status information. You may also view this information in Lync 2010 control panel > Topology.

The easier way is to check the replication status in Lync 2010 Management Shell. Open the Shell and run following command.
 
Get-CsManagementStoreReplicationStatus |Fl

 It will list all the Lync 2010 server with current replication status which may be either 'True' or 'False'. When it is false, then we have a problem with CMS replication.

Force Central Management Store replication


Lync 2010 management shell is a great tool, use it to force the CMS replication between front-end and edge server.To force the CMS replication do the following

Invoke-CsManagementStoreReplication 

But it is not fool proof as we may have other issues due to which replication is not working.


Port Requirement


One important thing to remember is ports requirement because Lync 2010 edge is always deployed in DMZ . Do when edge replicates on port TCP 4443 , it should not be blocked in both directions - Inbound and Outbound.
To convince your itself that the ports are working, use telnet client and verify if the ports are open in both directions.If replication issue still persist, check for certificate related issues, DNS query etc.

Export and Import Configuration


This is the same step which we follow during Lync edge deployment. First we need to export CMS configuration and import to Lync edge server.

Run the following command on any of your front-end servers, 

Export-CsConfiguration –filename <somename.zip> 


Now copy the zip file on the edge server and start the Lync 2010 deployment wizard. 

 Import the configuration file (hard way)

 


We need to run Step 2 from the deployment wizard. However, it will not allow us to do so, because it is still in sync with the front-end servers.

Open the Edge server local computer system properties and remove the domain suffix. We can reboot the server now.

Note: This is the step you need to be very careful and do it at your own risk or run it on a test lab before implementing in production environment.

Import the configuration (easy way)

 

There is an easy way to import the configuration information. To import the CMS configuration on the Local Configuration Store of the Lync edge server.
Run the following command,


Import-CsConfiguration -filename <filename.zip>

After performing the above step restart all the edge services once and verify if the issue got resolved.

Conclusion

 

These are some basic things which we need to consider if replication issue happens between Lync 2010 front-end and Lync 2010 edge server. It is very important to take a backup of any settings or configurations
on front-end or edge server before making any major changes.  

Poor network connectivity, firewall or migration these are common reasons that affect CMS replications.


No comments:

Post a Comment