07-24-2018 09:30 AM
07-24-2018 09:30 AM
I just want to welcome everyone who has read the blog - SfB Server 2019 preview is ready for you to try. Be sure to post ALL your questions, comments, and feedback here.
07-24-2018 12:02 PM
03-26-2019 04:33 AM
Already running SfB 2019 Server - but discovered some bug's that should be fixed in an upcoming CU.
Can you give any hint about the release of the CU or any hotfixes for SfB 2019?
03-26-2019 09:08 AM
@Karsten_Stolten We are working on the first CU. Can you share what the problem is?
03-26-2019 09:51 AM
03-26-2019 09:52 AM
03-27-2019 02:01 AM
@Karsten_Stolten We are aware of it, and working to include it in the first CU that comes out later this year. Hope this helps.
03-27-2019 03:00 AM
Thanks again for getting back.
Great to hear that the issue is addressed.
Any workarounds/hacks/hotfixes are much appriciated! :o)
"Later this year" - is that like Within a few days, weeks or months?
03-27-2019 10:51 AM
@Karsten_Stolten I'm afraid there's no workaround at the moment. As for the timelines, we're talking months. Apologies, but I can't share more than that at this time. Please stay tuned.
03-27-2019 01:54 PM
04-17-2019 01:48 AM - edited 04-17-2019 01:49 AM
@Paul CannonHi, we also deployed Skype for Business Server 2019 but run into two strange problems, we don't know what they are related to, cause we see no network issues with the VMs and SQL back-end.
1. Skype 2019 pool in another region sometimes once a day, sometimes 2-3 times a week has problems with communication with back-end in primary site (where the monitoring DB sits), which causes Front End Service to restart sometimes:
04-17-2019 08:02 AM
Oh and one more, that just recently ocurred (maybe cause of Windows Updates for Windows Server 2019?), we cannot share PowerPoint presentations when homed on Skype for Business Server 2019.
It is working on Skype for Business Server 2015 with same OOS servers (I even updated OOS servers to latest version and Skype 2015 nor Sharepoint 2013/2016 have no issues with it).
But when trying to share in Skype 2019 it gets uploaded to the server but client is constantly showing Loading… or sometimes shows cannot connect to presentation server.
It worked before, but maybe after some Windows Server 2019 update it stopped, dunno. Anything you know about?:)
04-17-2019 08:48 PM
@Krzysztof Sienkiewicz , We tried to reproduce the issue you met yesterday, and ever things worked well. For investigate completely ASAP, we need further information, Cloud you help me to resolve the following confuses:
1.One of Strange problems that you met, Dose it look like this scenario?(I have 2 site New York and Washington, and they own a single one monitoring DB in New York, but now Washington's site Front End pools can not work .)if so, could you please tell me how other Server roles you have deployed with? or you can tell me what you did before the error occurred (such as restart primarysiteSQLBackEnd.domain.com and so on).
2.The other problem is operation has timed out, you mean it can not
upload specifically QoE metrics (which is from second site to primary site SQL) successfully, thus did you configure the firewall or Check the connection that all servers ping to DC?
04-17-2019 10:28 PM
Let me provide you with our setup:
Like with Skype for Business Server 2015 we deployed pools in two sites (Denmark (pri) and U.S. (sec))
3 Front Ends colocated with Mediation (prisiteFE01.domain.com, prisiteFE02..., prisiteFE03...)
1 SQL Back-End (with CMS DB, pool DBs and Monitoring DB) (prisiteSQLBackEnd.domain.com)
3 Front Ends colocated with Mediation (secsiteFE01.domain.com, secsiteFE02..., secsiteFE03...)
1 SQL Back-End (with pool DBs only) (secsiteSQLBackEnd.domain.com)
so US pool sends monitoring data to Denmark pool.
Like mentioned this is the same setup like we had in Skype 2015, we opened same ports, it's configured same and of course part of same topology.
I've been digging into problem nr 2 for few hours yesterday and it seems this is not ocurring constantly, only once in a while when a call completes in US it tries sending QoE metrics and times out and (as I read "by design") does not retry this ever again, jut goes to the next job. Sometimes it times out sometimes it does not. What is the timeout time exactly, do you know?
Firewall (Windows and Cisco) is configured same like it was for Skype 2015 so should be no issues there.
I managed to capture CLS logs when timeout happened and yeah, it shows that it sends the metrics (as it is SIP, it sends through the pool) but does not receive answer 202 OK, in all traffic captured when this one timeout occurs, this is the only SERVICE Out message that does not receive return message 202 OK, so it logs timeout.
I have NetMon logs, but will have to show it to a network guy to really understand it. I only see that one front end in US pool sends the metrics to another front end in the US pool (why?), maybe this other front end is then responsible for sending the metrics to Monitoring DB in pri site?
All servers ping DCs:)
In regards to issue nr1, I am still trying to reproduce, like I said it works sometimes for a few days then suddenly has a problem for 2-3 minutes, then back to normal, but nothing logged in SCOM from today yet.
04-18-2019 01:28 AM
So, I know more now, after understanding the flow of traffic.
It maybe that there are too many hops between new Skype 2019 pool in US and monitoring DB in Denmark.
To make it simple. User that made a call/received a call is still on Skype 2015, but for all mediation traffic it's Skype 2019 that is the primary pool now:
1. Skype 2019 in US initiates and controls the call until it ends
2. Since user calling/called is still on Skype 2015 in US, it sent the QoE metrics from First 2019 FE to Third 2019 FE in US (Hop 1)
3. Third 2019 FE sends QoE metrics to Second 2015 FE in US (Hop 2)
4. Second 2015 FE in US sends QoE metrics to whichever (don't have logs from this pool) 2015 FE in DK (Hop 3)
5. 2015 FE in DK sends data to Skype 2015 Monitoring DB
Since many calls (tens or hundreds) are happening on the mediation pool, and only few QoE metrics don't get delivered to the monitoring DB, it seems not to be a big issue and might be related to network latency since so many hops are in the path.
But the problem described as Nr 1 (with failing connection to backend) and PowerPoint sharing problems (let's call it problem nr 3) in Skype 2019 are still there. Apart from that we noticed another problem in Skype 2019 (let's call it problem nr 4):
4a) It starts with LS Protocol Stack Warning (EventID 14397):
04-18-2019 11:32 AM
@Krzysztof Sienkiewicz Can you upload the CLS logs to some location and share the link?
04-18-2019 06:28 PM
Have you ever tried rerun Deployment Wizard for 1~3 steps on your 2019 pool?
04-18-2019 10:18 PM
For which of my described problems? Cause the one with QoE metrics, like I said, probably too many hops and after investigation it seems to be happening only sporadically, probably will go away when we move users to new Skype pool, if not, I will get back on that. Other problems I described are more of a show-stopper for us (PowerPoint presenting, services going down because Cert Store cannot be opened, etc.)
04-18-2019 10:49 PM