Company A uses ISA server 2004 as the proxy server, a cisco 2950 switch as the central switch.
The topology diagram:

For this kind of topology, we have two solutions:
Notice: By default, WFilter only analysis traffic between local network and the internet. So if you are using a local proxy server, WFilter will not analysis the traffic between the proxy server and the client computers by default. You need to add the proxy server ip address to "Local Servers" in "Monitor Settings" of WFilter to make WFilter work.
As indicated in the above diagram, the ISA server is connected to port 23 of the switch and WFilter is connected to port 22. To make WFilter work, you only need to mirror port 23's traffic to port 22.
monitor session session_number {destination {interface interface-id [, | -] [encapsulation {dot1q}] [ingress vlan vlan id] | remote vlan vlan-id reflector-port interface-id} | {source {interface interface-id [, | -] [both | rx | tx] | remote vlan vlan-id}}
monitor session 1 source interface Fa0/23
monitor session 1 destination interface Fa0/22 ingress vlan 1
By default, the mirror port of cisco 2950 is recv-only. However, WFilter shall be able to send packages to implement block features. So in this example, we add "ingress vlan 1" to enable send of port 22.
Some cisco switch do not support ingress syntax, if your switch does not support ingress, you can set a different "blocking adaptor". Please follow below steps:
monitor session 1 source interface Fa0/23
monitor session 1 destination interface Fa0/22
By now, you can monitor all the computers in network.