Forum Discussion
New "Get-MpPreference" Options
Do you think it was related to overhead vs. the actual parsing being the root cause of the disconnects?
One would assume that WDATP or Defender would just now parse TLS logs (similar to PacketBeat, Microsoft's legacy packet gui, or logger of choice) via it's new packet capture abilities that were released 6+ months ago (20H2 or 20H1?).
I've been wrong in the past when I've applied logic to naming conventions in powershell, which is the reason I made this thread. 🙂
The scenario you ran into would be great for performance gauging too.
I'd be curious over the specifics on network conditions and devices used.
Jonathan Green I am not sure! All I know is that with plenty of packet capturing going on and 0 changes in our environment (excluding these new options and their default settings) within the last few weeks this has been a problem for our users who are utilizing the edge sfb server AND trying to complete a desktop screenshare. The audio call works great, but when one user turns on desktop sharing or video, the STUN binding doesn't complete. Wireshark can't capture a successful binding on either PC unless BOTH users have run this command:
It is also true that failing happens when setting this back to the default "false".
- NetworkRyanJun 23, 2021Copper ContributorPlease note, this command was actually recommended by a microsoft support engineer. There would have been no way for me to find the command as this is the only legitimate page that comes up when googling "disabletlsparsing"... Please give us at least a man page or something...