Forum Widgets
Latest Discussions
cannot open skype control panel 2019 after migration side by side from Lync 2013
Existing Environment- We have Lync server 2013 with pool enterprises with 3 Front-end. I just upgraded from Lync 2013 to Skype for Business 2019. (the new Existing Environment on windows server 2019 and we doing migration side by side ). Everything seems to be working fine except I cannot log into the Control Panel from anywhere the web interface (PoolName/CSCP) or from the app : ”skype for business control panel”. When I connect I get - Error 503 service unavailable. Also the new MACP (the new control panel with Html 5 not working). Thanks for the help!
Skype for Business 2019 - Silverlight
I installed SfB Server 2019 Preview in lab and see the same old Control panel on dead Silverlight. It will be the same in release? Not changed to HTML5 in 2018? Comparing, looks like SfB Server 2019 is a copy of 2015 version with removed features. No any new features. Disappointment.
Pool Pairing Standard Edition Skype for Business
Hi, I have 1 site with 1 Front End Enterprise Edt SFB 2015, We would like to install SFB 2019 and moving user to SFB 2019. We planning to install Std Edt 2019 and customer want pool pairing. It's possible to have 2 Front end std edt in 1 central site? This customer have 1 site only. Please advice.Migration from SFB 2015 to SFB 2019
Hello Every one, We have a customer that want to migrate from SFB 2015 to SFB 2019. But we have found the next blockers to start. 1.) Checking requirements we see that SFB 2019 Enterprise edition requires SQL server 2016 or 2017 standard (64bit) for the Back End. Nowadays customer want to reuse the SQL server 2014 that is installed for the SFB 2015 deployment. Do you know if it is possible?. Other option is that customer has other SQL servers 2016 working for other purposes but does not have more SQL server 2016 licenses available. Can we configure a separate instance for the SFB 2019 deployment on those SQL 2016 servers? or it needs to be a dedicated SQL server for the SFB 2019 deployment? 2.) Checking requirements we see that SFB 2019 need Domain controllers, Domain functional level and Forest functional level on Windows Server 2019 Windows Server 2016 Windows Server 2012 R2 Windows Server 2012 Customer has Domain controllers, Domain functional level and Forest functional level on Windows Server 2008 R2. Customer is not going to update this on near future so my questions are, any of you know if SFB 2019 could work on this customer scenario? and the other question is, is better to inform customer to first update the DC and functional levels before trying to make the migration? 3.) There are many users with the Lync 2010 client yet, and searching in our documentation Lync 2010 client does not apear as a supported client, so my question is, it just does not work? or it work but is not supported? Sorry for the large consultation but those are important points to define if start the process or postpone the migration while customer meet the requirements? Please let me know your comments, Gabriel.
