Filter Exceptions Required for Chrome Remote Desktop
When BrowseControl is set to No Internet for systems while using Advanced HTTPS filtering, it will be required to create exceptions to the filter for these services to work correctly.
- remotedesktop.google.com
- googleusercontent.com
- accounts.google.com
- googleapis.com
- clients.google.com
- clients1.google.com - clients10.google.com
- gvt2.com
If there are still issues after this, reference the
Blocked URLs log.
Related Articles
Terminal Server/VDI/Remote Desktop Services Compatibility
If you are using Windows-based virtual desktop infrastructure (VDI) or have users in your network remoting into a terminal server or a Remote Desktop service, you can still use CurrentWare to control and track users. CurrentWare applies Internet and ...
Advanced HTTPS Filter Bypass list
Using the AHTTPS Bypass list The Advanced HTTPS blocking method can be aggressive when certain blocks are in place. For example, sometimes blocking a domain can stop functionality of an application when it tries to reach it, like when trying to sign ...
Configure Port Forwarding for Remote Workers (SQL)
Connecting the CurrentWare Clients (Remote workers) To connect your CurrentWare Clients to the CurrentWare Server over the Internet, you will need to port forward the CurrentWare traffic from your network’s router to the CurrentWare Server computer. ...
BrowseControl Filter Configuration – Best Practices
Here are some quick tips that are best practices when dealing with your BrowseControl filtering setup: URL Filtering List (Allow & Block Lists) When adding URLs there are automatically wildcards(*) before and after the entries. Entering “site.com” ...
How do I access the legacy desktop console?
As of version 6.0, the CurrentWare desktop console has been migrated to run the new CurrentWare web console. As it is a new feature addition, there is an additional cost to gain full access to the web console. Please see the change in licensing to ...