I am attempting to deploy the Firewall Client to my staff to replace the Proxy Client. I am having no problem with the actual deployment of the software, it installs fine through group policy. However, while the software is installed and seems to be functioning properly, any rule that has security applied to it results in a "403 forbidden" error (regardless of whether it is allowed or prohibited). What I have found is that if the software is installed (or repaired using add/remove software) with the user logged on, everything works fine FOR THAT USER. Anybody else logging on will have the same problem, until the software is installed under the context. (I have also installed the software manually with the same result--deploying through group policy does not seem to make a difference.) This is causing me a big problem. It would be bad enough if it had to be installed under the user context, but it's an absolute show stopper that everyone that uses the computer has to have it done. I have been unable to pinpoint what changes when it is re-run under the user's logon; everything looks the same. The client machines are running Windows 2000 SP2, and the ISA Server has SP1. Thanks in advance for any help you can provide, Bill Mayo Pitt County MIS