Tri co-existence between Lync 2013 , SFB 2015 and SFB 2019– The reality check

First of all,  tri co-existence is not supported by Microsoft. This article doesn’t endorse any unsupported configuration.

I have deployed Lync 2013, SFB 2015 and SFB 2019 servers in the same AD topology. All three deployment are up and running just fine.

Schema update:

SFB 2019 AD preparation was not needed. This step was completed when I opened the deployment wizard.

Topology builder

I could not open topology builder tool in Lync 2013 and SFB 2015 servers after SFB 2019 deployment which is expected.

I have notified below warning when you launch topology builder in SFB 2019. However, it does proceed with loading when you click ok.

Control panel:

I was able to launch control panel from all three servers. I have selected local/respective cscp URL for individual deployments. I haven’t done many tasks from individual control panel though.

Powershell :

I have also tested powershell from all three versions and they seems to working as expected.


Tested user move from SFB 2019 control panel. SFB 2015 to SFB 2019 move was just normal. However, Lync 2013 to SFB 2019 move was failed all times with below error. Connection was timing out every time I initiate a user move. However, same user move from Lync 2013 to SFB 2015 is working from SFB 2015 control panel. This needs more investigation to find the cause.

Client co-existence:

I could sign in all three clients simultaneously. Basic IM, Presence, conference etc seems to be working as expected. Please note , I didn’t test all internal/external scenarios related to the modalities.

How useful was this post?

Click on a star to rate it!

Average rating / 5. Vote count:

2 thoughts on “Tri co-existence between Lync 2013 , SFB 2015 and SFB 2019– The reality check

  1. Everything is very open with a very clear explanation of the issues.
    It was really informative. Your site is very helpful.
    Thanks for sharing!

Comments are closed.