Skip to main content

Lync Server 2013 Pool failover process

Lync Server 2013 Pool failover process.

Pool failover is very important in disaster recovery situation. You must failover primary Pool to backup pool site and vice versa every six month as an best practice that way if in case disaster situation occurs then you will be ready for pool failover.  

Pool failover process involves failing over the Central Management store, if it requires. This is important because the Central Management store must be functional when the pool’s users are failed over to backup pool. 

Additionally, if a Front End pool fails but the Edge pool at that site is still running, you must know whether the Edge pool uses the failed pool as a next hop pool. If it does, you must change the Edge pool to use a different Front End pool as failed over Front End pool. How you change the next hop setting depends on whether the Edge will use a pool at the same site as the Edge pool, or a different site. 

Below mentioned pool failover steps include CMS move, pool failover and pool failback.

Pool failover pre-requisite:
Before pool failover make sure below: 

1.    Check CMS replication status, it must true for all your servers: MS Management Replication status: is True for all server.

Get-CsManagementStoreReplicationStatus | fl UpToDate,ReplicaFqdn

Check if Backup Relationship is correctly showing backup pool FQDN.

Get-CsPoolBackupRelationship -PoolFqdn


2.    Check users pool server information shows primary and backup pool machines, simply the run below command let.
Get-CsUserPoolInfo to see pool information

3.    Verify CMS service connection points and validate the connection parameter points to the current pool's primary SQL store (and SQL mirror if applicable)

4.    Finally check backup service sync status:
Get-CsBackupServiceStatus -PoolFqdn ""


If you are failover Lync pool which hold Central Management Store (CMS) then you have move CMS first before invoking pool failover. 

In this document I will show both with CMS and without CMS pool failover. 

1.    Failover pool With CMS:
Example: Pool failover with CMS. I have pool1 ( which hold CMS and pool2 ( is backup pool.

Note: The CMS must be moved to another pool if the source pool being failed over is currently hosting the active CMS.
Assuming that both pool available however doing failover test for DR purpose.
A.    Do above all test and make sure the both pool is in “NormalState” and healthy condition to invoke failover test.
Log to Front End on Backup Pool FE11 and run below command: (when CMS is offline/down then use Invoke-CsManagementServerFailover -Force ) confirm the screen to allow change. 

In my testing scenario CMS is online and working state hence not using “Force”.

The failback will be automatically performed, primary FEs hydrated, and services started.
Current server - Central Management Store SCP:
Proposed State: Central Management Store SCP:

Check the connection point using Get-CsManagementConnection which will show SQL server as failover server name.
CMS server new SqlServer:

Wait for 5 min and Invoke-CsManagementStoreReplocation and check the replication status.
Now failover actual pool to backup pool:
Finally run the pool failover command:
Invoke-CsPoolFailover -PoolFqdn  

Below screenshots shows pool failover process

Get services and stop Lync services.

Front End services stopped on all servers.

You can see event 32155 “Pool fail over complete”.
Pool fail over is complete.

Now update edge pool to use next hop as backup Front End pool.
This must be changed via PowerShell via Set-CsEdgeServer and pointed to a registrar in the target/destination site. Command Let:
Set-CsEdgeServer -Identity EdgeServer: -Registrar Registrar: 

Example command:
Set-CsEdgeServer -Identity -Registrar

Finally check the user’s pool information and see if user register to backup pool (
Once all test done.
Failback to Primary pool back to primary site:
Invoke-CsPoolFailback -PoolFqdn
Failback takes time so once you the failback command do your other work.
Generally failback takes an hour time.
Refer below screenshot to know how pool failback happen:
1.    Once pool failback process start it shows to get and start services to target pool (in our test scenarios primary pool FE services getting started).

Failback process…

If you open event viewer, you will see,
Warning event 32174 " Server startup is being delayed because fabric has not finished initial placement of users.
Cause: This is normal during cold-start of a Pool and during server startup.

User experience:

While pool failover, Skype for Business client status will change to “Presence Unknown” and it will show error message “A network or server issue is temporarily limiting features.”

User status automatically change to correct status after pool failover completes. 

Thank you.




Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: ·User name: orgname\bilag ·Password: ************
Note: is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…