I have read through several of the threads posted about ISA capturing usernames rather than IP addresses, but am still having difficulties getting this to work/understanding how to configure it.
Our setup is as follows: 2003 Server with ISA 2004 Standard, Single Network Adapter mode (this box is still in testing, so it can be changed) that is a member server on the domain. (2000 domain) We are not using the FW client, but are piping people through the web-proxy in IE/Firefox. This is not being used as a FW, but only as a proxy server.
90% of our employees are on Thin Clients and go through windows 2003 terminal servers.
Currently we are only seeing information about IP addresses, which wouldn't be that big of a deal except that all we see are the IPs from the server, so we can't exactly tell who the offender was. Like others have said, there is so much confusing/conflicting information out about the capabilities of ISA that I needed to once again post this question. The kicker seems to be the thin client aspect of the equation. For the most part, when I mention that, people tell me that we won't be able to truly use AD integration on ANY proxy service.
Thoughts? Is ISA the best choice for proxying, or is something like Linux/Squid a better choice given what I would like to see? (pretty new to ISA if you couldn't tell!)