If you're using W2k domains, you should look at group policy managed installations. <http://www.microsoft.com/windows2000/techinfo/planning/management/verit as.asp> will give you the steps for creating a package, and <http://www.microsoft.com/windows2000/techinfo/planning/management/swins tall.asp> will give you instructions for using group policy to distribute applications. (think these are right). The machines will have to be rebooted if you use machine installations, or if you use user installations, the user will have to log off and log on. I've found that specifying the machine, rather than the user, will make things a little easier - esp. if you have users logging onto servers (not a good thing, but sometimes it can't be avoided :( *DO* take your time with the package creation - and TEST TEST TEST!. The one thing that you get wrong = 200 things wrong on every other computer in the company. -- Anthony Michaud Network Administrator eLogix Corporation Pty Ltd You've got an anti-anti-antimissile missile? Well, we've got an anti-anti-anti-antimissile missile!" - Get Smart! > -----Original Message----- > From: Frank Phan [mailto:fphan@xxxxxxxxxxx] > Sent: Wednesday, 15 August 2001 03:30 > To: [ISAserver.org Discussion List] > Subject: [isalist] firewall client install > > > http://www.ISAserver.org > > > Hi everyone > I have to install firewall client for 200 workstations > is there the better way to distributed the client remotely > from my server when the connect. > please help > thank a lot > > > > > > > > > ------------------------------------------------------ > You are currently subscribed to this ISAserver.org Discussion > List as: anthonym@xxxxxxxxxxxxxx > To unsubscribe send a blank email to > $subst('Email.Unsub') >