This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
How does the meetings internals work for enterprise edition of Skype for business 2015/2019?
We are in the middle of the migration from 2015 to 2019 , everything works as expected except meetings are showing latency to connect on 2019 servers?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hi @Khoj Sahiwala ,
In my experience, when you deploy Skype for Business Server, IM conferencing capabilities are automatically deployed. If you need other kinds of meeting such as web, A/V, and dial-in conferencing, you should do some extra deployment in Skype for Business topology Builder. For more details about conference topology requirements, you can learn it from:
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks Jimmy,
However how the Simple urls are to be defined during migration? MS Tech rightly says all urls should point to the new pool and not legacy pool. in our enterprise edition it is giving issues.
Migration to 2019 makes meeting slow.
there is one more thing?
In enterprise edition localhost/meet points to localhost for 2015 , however the same goes to VIP on 2019 ?
There appears to be an issue related to DNS.
as we are in Migration n Co-existence phase , we are having same webinternal FQDN for both pools.
we need to have two webint records pointing to corresponding HLB VIP.
also we may need to have 7 DNS records for Front end pools, each ent server pointing to itself and to VIP.
We will check it and update if we are facing issues with meetings
In my experience, after migrating to Skype for Business Server, you must be aware of how the change impacts your DNS records and certificates for simple URLs. If the legacy Skype for Business Server Director remains in use in the topology, no changes to your simple URLs are required. If the Skype for Business Server Director is removed from the topology after migration, the simple URL DNS records must be updated to point to one of the Skype for Business Server pools.
@Khoj Sahiwala ,
I copied your question from External Web Services URL as below:
side by side migration 2015 to 2019.
single site, single edge and RP with two ent pools, is there a requirement for SEPARATE External Web Services URL for both the pools?
the topology does except same External Web services URL , So what difference does it make if we choose the same one?
Jimmy will continue to help you on this topic.
Hi @Khoj Sahiwala ,
If you have more than one Front End pool or Front End Server, the external Web services FQDN must be unique. For example, if you define the external Web services FQDN of a Front End Server aspool01.contoso.com, you cannot use pool01.contoso.com for another Front End pool or Front End Server.