Team, I have a customer who is running into this issue. They were told by TAC this is still an issue with Microsoft Server 2016. Microsoft is saying the issue has been fixed and this should no longer been an issue.
Have we been in touch with Microsoft and do we know this issue is resolved?
Thanks!
