RE: ISA Server 2004 Standard Edition SP1

  • From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Tue, 1 Mar 2005 21:16:16 -0600

Hi Dan,
 
I haven't tested the group policy software deployment option yet, but
the update.bat is quite painless and you can put that log on script in
group policy.
 
HTH,
 
Tom
www.isaserver.org/shinder <http://www.isaserver.org/shinder> 
Tom and Deb Shinder's Configuring ISA Server 2004
http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> 
MVP -- ISA Firewalls

 

________________________________

From: Ball, Dan [mailto:DBall@xxxxxxxxxxx] 
Sent: Tuesday, March 01, 2005 9:11 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: ISA Server 2004 Standard Edition SP1


http://www.ISAserver.org


I was waiting to see how your update went before I attempted it, and
maybe for good reason.  Due to our network configuration, a good half of
our domain might not be able to reach the Internet if the FWC gives out.


 

So, that leaves us with "How do we force a re-install of the client?"
If you're in a position like I am, I have over 1200 computers that I
will need to update with the new FWC almost immediately upon upgrade.
Since logging onto each of these computers and doing it manually is out
of the question, I have to figure out a way to automate it as much as
possible.

 

(please bear with me, I'm trying to work this out as I type...)

 

Let's see, according to the readme file, there is a batch file to do the
upgrade, or you could run msiexec /feumsv \\ISA\Mspclnt\MS_FWC.msi.  

 

Since the FWC share was "upgraded", there is no reason to believe that
running the setup from the mspclnt share wouldn't do a complete install
on a fresh computer.  Since the MS_FWC.msi file is basically the same
thing setup program, using group policy to install on a fresh computer
should work fine also.

 

The question then that arises is that if you re-deploy the group policy,
does it do an upgrade?  The /feumsv switch listed in the readme file
basically says to re-install, overwrite all files, etc, but running the
MS_FWC.msi file (the one used in group policy deployment) without those
switches, well...

 

Thus, I would think there are a few options:

-          Re-deploy the group policy, see if that works (I'm assuming
you already did that)

-          Re-create the group policy software entries to include the
/feumsv switch, then re-deploy it.  (It probably wouldn't hurt to use
this switch all the time, to replace old software.)

-          Remove the current group policy from use (don't delete it),
and create a new replacement group policy.  This will uninstall the
software in the old one (assuming you selected to force un-installation
in old policy), and install the new one.  

-          Put the upgrade batch file into a login script, or force it
to run via group policy. (I'd go with the other methods before this one
though, as you have to leave it in place long enough to make sure every
computer gets upgraded (could take a loooong time), and I don't like
having useless batch files in a login script.)

 

Does this help?

 

Let me know how your upgrade goes so I can plan for it also.

 

________________________________

From: Ara [mailto:ara@xxxxxxxxxxxxx] 
Sent: Tuesday, March 01, 2005 18:17
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: ISA Server 2004 Standard Edition SP1

 

http://www.ISAserver.org

Hello Tom,

I haven't contacted the yet. Not a problem for me yet but anything is
possible

By the way Tom, do you have any advice how to push everybody a new
version of client? The group policy didn't work for me.

Thank you

 

Other related posts: