Hi,
We are trying to test websense hybrid enpoint using the blackspider service and have found a weird problem, in certain situations the client will pick up the wrong configuration and point at the wrong pac file.
What happens is that the client software is installed on to a laptop and it pulls down a config that points to the pac file the first time it connects to the Internet. This will work normally if the laptop is connected using our internal network or an external internet connection, but if the laptop is connected to our public wireless that uses Websense Cloud service for filtering it gets configured to connect to the cloud service rather than the blackspider one.
I have tested this and when a laptop is connected to our public wireless immediately after the hybrid client software is installed the registry shows that the pac file reference is for our cloud subscription (the pac reference matches the one on our cloud administration page and not our triton administration page).
Additionally, we cannot use our hybrid anti tamper password to uninstall the client software.
Has anyone come across a similar situation before? If so, is there a premanent fix for this?
Cheers
Andy