The software is not supported in that configuration.
You'd be surprised how often that is said in this line of work. Websense software is tested in specific methods and certain technologies are not tested, nor even planned for during the development phase.
Lets take some examples. In one case, the customer is trying to install Websense Client Policy Manager client on a Vista Enterprise 64bit SP2 system. Websense 6.3.2, which the customer is using, does support using Vista, however not with 64bit systems. In fact, *none* of our software currently works as designed on 64bit systems. I'm sure there are some enterprising individuals who have gotten it to work by smoothing out wrinkles. I know of at least one component that will absolutely fail on a 64bit server. That's the Network Agent, which uses code to access network card level information and open the communications for promiscuous traffic. In 64bit systems, these "low level" access requires signed drivers which isn't in place. Therefore, the Network Agent can't even detect the network cards and can't even install.
In another case, the customer plans to use Websense filtering with a Blackberry Enterprise Server. Blackberries and other phone type devices have historically been unable to display the blockpage because Websense uses frames, where those devices can't. For another reason, the Blackberry Enterprise Server is essentially a proxy server for these handhelds. In some proxies, such as the Websense Content Gateway, we have a plugin which will pass user information to the filter service. There is no such plugin for Blackberry servers. The best the user can do is to use another proxy server (like Websense Content Gateway) which *is* supported and *will* pass usernames if configured to do so.
Websense will not document what it doesn't support. It only documents what *is* supported. So, if the installation that you're planning to do isn't in the documentation, don't assume you can do it.
