This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(80, 61%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMZ%3C/text%3E%3C/svg%3E)
We are upgrading Lync server 2013 to Skype for Business 2019, and the Lync 2013 and SFB2019 pools are coexisting.
We use the reverse proxy server to publish Lync2013/SFB2019 external web services and lyncdiscover.contoso.com to Internet, the URL lyncdiscover.contoso.com is now pointing to Lync 2013 front-end server pool on reverse proxy server.
Users host on Lync 2013 can sign in the Skype mobile client successfully, but users host on SFB2019 cannot, what should I do to fix the issue? We want users host on both pools can use the mobile clients.
![](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)
You can also check the configuration of the reverse proxy server to ensure that it is properly configured to handle traffic for both Lync 2013 and Skype for Business 2019. To check the configuration of the reverse proxy server, you can review the settings for the external web services and ensure that they are properly configured for both Lync 2013 and Skype for Business 2019. You may also review the logs on the reverse proxy server to identify any errors or issues that may be occurring.
Additionally, it recommends you review the logs on the Skype for Business 2019 pool to identify any errors or issues that may be occurring.
Hi JimmyYang,
Both Lync2013 and SFB2019 are using the same lyncdiscover.contoso.com, all the functions(AB download/contact group expand/meeting content download etc.) of the SFB2019 on RP server work fine except the mobility, so I think the configurations are correct to SFB2019.
What exact configurations should I check on SFB2019 pool? IIS configurations or some others?
SFB2019 is running on Windows server 2019 STD edition.
Thanks.