Search

Hacken, thanks for this information. Is it possible to manually delete just one of those user mappings? Or must you wait until the timeout period has passed?

Sorry, I realized that you were talking about installing Websense components on the log server, which is why you would need 32-bit. Any possibility you could get a Server 2008 enterprise license? This would allow you to utilize more than 4 GB of RAM. Also, any particular reason you want to install websense compononents on the SQL server? With the number of users you have and the specs of your servers, you should be able to run all Websense components on Machine1 and Machine 2 would be a dedicated

You can run SQL 2008 on a 64-bit OS, you don't need R2 for that. In fact, I think TMG only supports a 64-bit OS based on their system requirements page. Another thought, you probably won't need 80-100 GB of space on the server that isn't the log server/database. Although you can always thinly provision your disks if your environment supports it. http://www.microsoft.com/forefront/threat-management-gateway/en/us/system-requirements.aspx

Hello. I had a few questions regarding distributed deployments of Web Filter in general and specifically for our company's configuration. We have 3 primary locations, each with a Cisco ASA. We have a MPLS WAN connection between these 3 sites. Site 1 has approximately 600 users, sites 2 and 3 have approx. 300 - 400 users. Based on what documentation I've read, here is the set up I am proposing: - Site 1 would host the primary websense web filter server (Windows) with all services running on

Excellent feedback, thank you! I don't see there being a bandwidth issue, and we would just monitor it and adjust and just create local log databses if necessary. So the remote sites do not need a policy server, except for redundancy purposes correct? If the wan was down, the filter service wouldn't be able to reach the central policy server, therefor no filtering? Or are you saying they can cache those policies as well?