13.07.2015 Views

TRITON - Web Security Help, Version 7.7 - Websense

TRITON - Web Security Help, Version 7.7 - Websense

TRITON - Web Security Help, Version 7.7 - Websense

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

TroubleshootingRecategorized sites are filtered according to the wrong category<strong>TRITON</strong> - <strong>Web</strong> <strong>Security</strong> <strong>Help</strong> | <strong>Web</strong> <strong>Security</strong> Solutions | <strong>Version</strong> <strong>7.7</strong>.xRecategorized URLs affect only the clients managed by role in which the URLs areadded. For example, when a Super Administrator recategorizes URLs, clientsmanaged by delegated administration roles continue to be filtered according to theMaster Database category for those sites.To apply the recategorization to clients in other roles, the Super Administrator canswitch to each role and recategorize the sites for that role.I cannot create a custom protocol<strong>TRITON</strong> - <strong>Web</strong> <strong>Security</strong> <strong>Help</strong> | <strong>Web</strong> <strong>Security</strong> Solutions | <strong>Version</strong> <strong>7.7</strong>.xOnly Super Administrators are able to create custom protocols. However, delegatedadministrators can set filtering actions for custom protocols.When Super Administrators create custom protocols, they should set the appropriatedefault action for most clients. Then, inform delegated administrators of the newprotocol so they can update the filters for their role, as appropriate.Log Server and Log Database issues<strong>TRITON</strong> - <strong>Web</strong> <strong>Security</strong> <strong>Help</strong> | <strong>Web</strong> <strong>Security</strong> Solutions | <strong>Version</strong> <strong>7.7</strong>.x Log Server is not running, page 483 Log Server has not received log files from Filtering Service, page 483 Low disk space on the Log Server machine, page 486 No Log Server is installed for a Policy Server, page 486 Log Database was not created, page 488 Log Database is not available, page 489 Log Database size causes reporting delays, page 490 More than 100 files in the Log Server cache directory, page 490 Last successful ETL job ran more than 4 hours ago, page 492 Configure Log Server to use a database account, page 492 Log Server is not recording data in the Log Database, page 493 Updating the Log Server connection account or password, page 493 Configuring user permissions for Microsoft SQL Server, page 494 Log Server cannot connect to the directory service, page 495 Wrong reporting page displayed, page 495482 <strong>Web</strong>sense <strong>Web</strong> <strong>Security</strong> Solutions

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!