gregarican
IS-IT--Management
Here's my quandary. I think this pertains to a known issue with ISA 2004 ( so perhaps I'm at an impasse.
Our CEO travels between several of our remote sites. Our headquarters has ISA 2004 and his laptop uses the Microsoft Firewall Client for web proxy access and whatnot. This ISA 2004 box has site VPN's defined to connect to the remote sites, which have a mix of Cisco ASA and PIX devices on the other end.
When he visits these remote sites he is still being pointed to the HQ ISA 2004 box for web browsing access. Due to the known issue with ISA 2004 this won't work because he's piping in from a site VPN endpoint. So I have set him up with a couple of batch files he has to manually launch. When he's at a remote site he has to launch one that removes all of the WPAD registry entries from his system so Internet Explorer won't automatically detect the HQ web proxy. Then when he's back at HQ he launches the other batch file that puts these WPAD entries back into effect.
Is there any more elegant way of handling this behind the scenes? I don't want to install a separate caching web proxy at the remote sites since all of the other users don't see or care about the HQ ISA 2004 box. They all just go directly out of their Cisco devices for unrestricted Internet access. If I could do something programatically that would save me face, since batch files are rather crude to ask my CEO to remember each and every visit around
Our CEO travels between several of our remote sites. Our headquarters has ISA 2004 and his laptop uses the Microsoft Firewall Client for web proxy access and whatnot. This ISA 2004 box has site VPN's defined to connect to the remote sites, which have a mix of Cisco ASA and PIX devices on the other end.
When he visits these remote sites he is still being pointed to the HQ ISA 2004 box for web browsing access. Due to the known issue with ISA 2004 this won't work because he's piping in from a site VPN endpoint. So I have set him up with a couple of batch files he has to manually launch. When he's at a remote site he has to launch one that removes all of the WPAD registry entries from his system so Internet Explorer won't automatically detect the HQ web proxy. Then when he's back at HQ he launches the other batch file that puts these WPAD entries back into effect.
Is there any more elegant way of handling this behind the scenes? I don't want to install a separate caching web proxy at the remote sites since all of the other users don't see or care about the HQ ISA 2004 box. They all just go directly out of their Cisco devices for unrestricted Internet access. If I could do something programatically that would save me face, since batch files are rather crude to ask my CEO to remember each and every visit around
