BigMickTait

Hi, I don't have a login so I can't debug fully, but I note from using the browser F12 developer tools that they're using a few javascript libraries. I don't know how many will be pertinent, but I would try adding these: cdnjs.cloudflare.com cdn.jsdeliver.net jsmaxmind.com cdn.jsdeliver.net There may well be more, but without the login it's hard to tell. One other thing that catches out a few CensorNet SWG users is the content servers category. It's hidden away in the policies under Categories -> Internet, Software, Media & Ads -> Streaming Media and Content Servers -> Content Servers. It's often desirable to allow this category in your policies as most content delivery networks will fall under these. If the above URLs don't sort out the issue, the best bet would be to contact CensorNet support, as they can do a remote debugging session with you.

No problem. Office activation is a little more tricky as there's a walloping great number of URLs and ranges thanks to office 365. If you let me know which version(s) of office it is, I'll see what I can do though.

Hi Pablo, The problem is normally that the windows activation fails authentication due to running as a different user to the logged in user. The trick is to get the correct bypasses in place and get the bypass configuration set up correctly. In the USS portal, set up a bypass category and add these entries. For the domains, use a full bypass, and for the IP address ranges use "Bypass CIDR completely". Note, you may not need all of these ranges as they change often, however I'm including all that I know of for the sake of completeness. microsoft.com microsoftonline-p.com microsoftonline.com sharepoint.com update.microsoft.com windows.net windowsupdate.com 13.104.0.0/14 13.64.0.0/11 13.96.0.0/13 134.170.0.0/16 157.56.77.0/24 157.56.96.0/24 213.200.108.0/24 217.243.192.0/24 65.55.163.0/24 77.67.30.0/24 78.32.0.0/15 78.33.33.0/24 Once this is done, in the configuration profiles page, you need to make sure that the bypass category has a tick in the box to include it in the information that's sent to your filtering products. Hope this helps, and as commented above, censornet support can help out as well. You can contact them on [email protected].