ScreenMeet Enterprise Deployment Guide

HTTP Forward Proxies

• If you use an HTTP forward proxy, it's highly recommended to configure your network to allow traffic to *.screenmeet.com to egress directly, bypassing the proxy.

• While ScreenMeet can work with forward proxies on Windows, it's not recommended because it can degrade performance.

• Using a forward proxy can lead to connection failures if it doesn't support WebSockets. It might also force WebRTC to use TCP instead of the more optimal UDP protocol, which adds latency and jitter.

Virtual Private Networks (VPN)

• If your remote workers use a VPN, a “split-tunnel” configuration is recommended. This allows traffic to *.screenmeet.com to go directly to the internet instead of through the VPN.

• Routing ScreenMeet traffic through a VPN can cause connectivity issues and performance degradation by creating traffic hair-pinning and using sub-optimal server regions.

TLS/SSL Inspection (decryption)

• If your company uses a security solution that decrypts TLS traffic, we recommend adding an exception for traffic to and from *.screenmeet.com.

• While ScreenMeet can function with TLS inspection active, users will typically see a “not secure” warning due to our use of certificate pinning.

• Please note: ScreenMeet Beam (unattended) will NOT connect if TLS inspection is enabled. This is an intentional security design choice.

AV / Binary Blockers

If you use a binary blocker (like Carbon Black), you'll need to white-list the ScreenMeet binaries.

• On Windows: ScreenMeetSupport.exe and the bundled DLL file webrtcnative-x64.dll.

• On macOS: ScreenMeetSupport.app.

macOS Entitlements

• ScreenMeet needs permissions for “Screen Recording” and “Accessibility” to enable screen sharing and remote control.

• Although users are prompted for these permissions on first use, they'll need admin rights on the device to grant them.

• For the best experience, it's recommended to distribute a profile via your MDM solution to grant these entitlements automatically.

Firewalls

• Allow UDP and TCP traffic for *.screenmeet.com.

• We support connections over IPv4; IPv6 is not supported.

• For more details, please see the Firewall White-List Documentation.

Data Integration / Egress IPs

• For customers who get data from ScreenMeet in their CRM or through Webhook integrations, API requests to your destination will come from specific IP addresses.

• Please see the list of ScreenMeet’s Egress IP addresses.

WebRTC Troubleshooting Tool

• You can use this tool on production machines to check that ScreenMeet services will work correctly. If the tool fails, one of the configurations mentioned above is likely the cause.

• Tool Link: https://integration.screenmeet.com/webrtctest/index.html

Tanium Troubleshooting

ScreenMeet does not open at all:

• Ensure that the ScreenMeet support binary is whitelisted: ScreenMeetSupport.exe and the bundled DLL file webrtcnative-x64.dll.

ScreenMeet does not connect:

• Check if tools like Zscaler are intercepting ScreenMeet traffic and replacing the SSL certificate. This can affect unattended sessions and increase connection time.

ScreenMeet takes a long time to connect:

• Make sure that your VPN, HTTP Forward Proxies, and Firewalls allow both UDP and TCP traffic for *.screenmeet.com.