Is that like wrapping a towel around your head to avoid the gaze of the Ravenous Bugblatter Beast of Traal? t On 12/15/06 9:08 AM, "Amy Babinchak" <amy@xxxxxxxxxxxxxxxxxxxxxxxxxx> spoketh to all: > What I end up doing is hiding the client from the users. If they can¹t see it, > they won¹t make the effort to disable it. > > > Amy Babinchak > Harbor Computer Services > > > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Ball, Dan > Sent: Friday, December 15, 2006 11:56 AM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > Nope, doesn¹t look like it. From a configuration standpoint, it doesn¹t > appear to be all that much different than the old version. > Here is one way you could do that though: > http://www.microsoft.com/technet/isa/2004/plan/troubleshooting_fwc.mspx#Users > > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of D PIETRUSZKA USWRN INTERLINK INFRA ASST MGR > Sent: Friday, December 15, 2006 10:49 AM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > Tell me please that the new version include a way to don¹t allow the users to > disable the client. > > > Regards > Diego R. Pietruszka > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Ball, Dan > Sent: Friday, December 15, 2006 10:45 AM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > Sorry, those questions weren¹t necessarily for you, just ones I was thinking > of at the time? > > As another option, (while testing this more before implantation) I discovered > that the fwctool is now included in the FWC installation (used to be a > separate download). Using that, you can make almost all the settings changes > via command-line. This might be a smoother way to force the settings back on. > > I guess I¹ll have to do more testing? > > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of D PIETRUSZKA USWRN INTERLINK INFRA ASST MGR > Sent: Friday, December 15, 2006 10:37 AM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > 1) Please be aware that I have firewall client 2004, I don¹t know if the new > one is still using the same folder name. > 2) Windows XP 32bits and 64bits, and Windows 2003 EE 32bits and 64bits use the > same folder. > 3) Not planning to migrate > > > Regards > Diego R. Pietruszka > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Ball, Dan > Sent: Friday, December 15, 2006 10:27 AM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > Thanks, I just found that same information. It took me (us) awhile to figure > out the right words to search on? > > Anyways, I found two reasonably good articles on this: > http://www.microsoft.com/technet/isa/2004/plan/troubleshooting_fwc.mspx > http://www.internetaccessmonitor.com/eng/support/docs/isaserver/SR_C_CfgFWClie > nt.php > > It looks like a common.ini file with this info in the All Users area will do > the trick: > [Common] > Disable=0 > Autodetection=1 > > After reading these articles, I think if I copy this file to the ³All Users² > area during the startup process, and then delete the matching files in the > %userprofile% area during the login process it will recreate the user setting > from the ³All Users² generic settings? > > The next questions are: > 1. Why is the newest version still using the folder name of ³Firewall Client > 2004²? > 2. Is this the same folder name that will be created regardless of ISA version > or OS version? > 3. What will happen in Vista when the Documents and Settings folders are being > phased out? (I¹ve had mixed success with this so far.) > > > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of D PIETRUSZKA USWRN INTERLINK INFRA ASST MGR > Sent: Friday, December 15, 2006 10:02 AM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > If I¹m not wrong it is > > %HOMEPATH%\Local Settings\Application Data\Microsoft\Firewall Client > 2004\common.ini > > > Regards > Diego R. Pietruszka > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Ball, Dan > Sent: Friday, December 15, 2006 8:55 AM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > Anyone know where the settings for the FWC are stored on the local computer? > I¹d like to find a way to force all FWCs to the ³enabled² mode. I still > haven¹t found a common denominator on why a bunch of them are defaulting to > ³disabled². > > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Ball, Dan > Sent: Thursday, December 14, 2006 1:34 PM > To: isalist@xxxxxxxxxxxxx > Subject: [isalist] Re: Vista Firewall Client > > I haven¹t tried it with Vista yet, our lab is in use today. > > However, I did push it out to the XP workstations, and a significant number of > them are defaulting to the FWC being disabled by default, which is causing a > bit of a problem? > > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Steve Moffat > Sent: Thursday, December 14, 2006 1:29 PM > To: ISA Mailing List > Subject: [isalist] Re: Vista Firewall Client > > Got it?had to add it to the allowed program list in Vista Firewall??manually?. > > > From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On > Behalf Of Steve Moffat > Sent: Thursday, December 14, 2006 2:10 PM > To: ISA Mailing List > Subject: [isalist] Vista Firewall Client > > Has anyone got it to work successfully with Vista yet???? As soon as I install > it?all network connectivity stops?including local. > > S >