Re: SBS03 - ISA 2004 re-install - Apply SP, backup, and FW clients

It worked!

Base install of ISA 2004 from CD. Apply settings as in documentation from
http://download.microsoft.com/download/c/a/b/cab5c8cd-d0f9-4b37-93c3-f36d976c86a2/PremiumInstallSteps.htm
and restart. Apply Service Pack 3. At this point, I was at the same place
I was previously, Microsoft Firewall would not start.

Changing logging for firewall, web proxy & smtp to file in default location,
restarting all 3 ISA services, then trying to start MSFW worked.

Then, I imported (not including user settings and cache), then applied
backup configuration. I'm back up and running like a champ. No FW clients
installed - clients are connected via proxy. So far no issues *kow*.

Thanks!

"g3po" wrote:

Thanks again Cris- I think the safest route since the config is from SP3 is
to apply your method and install, sp, then apply config. Hopefully less
breaks.

Thanks for the clarification on FW client - I think the proxy took care of
most clients and that must be why the minority had a FW client running.
Hopefully I can get this thing back on its feet - will post reply with
success/failures for others in similar predicament.

"Cris Hanna [SBS-MVP]" wrote:

in full disclosure, I've not restored a configuration file when reinstalling
ISA

As to the firewall client
Its required if you wish to access anything other than HTTP outside the lan
Otherwise you can manually configure the proxy on the Browser, but if you
need FTP, news, pop3, etc. You need the FW client installed

For my customers I install the FW client and then remove proxy info

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"g3po" <g3po@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9CC67364-9093-4981-B547-55EF6E828089@xxxxxxxxxxxxxxxx
Thanks for the quick response Cris!

So then I understand that to build in the config to initial install is not
recommended.
----------------
If you want to reinstall ISA Server 2004 by using a configuration file
that
you saved previously, type the following syntax at the command prompt:

Sbsisa2k4setup /IMPORTFILE "C:\importfile.xml"

where C:\importfile.xml represents the name of the configuration file.
Make
sure you use quotation marks around the name of the configuration file.
----------------

Install ISA 2004, apply SP3, then import backup config.

Also, why "should" FW client be installed? Is it required for clients to
communicate internal and external? As I mentioned we were not operating
this
way previously - 30% of clients had it installed, why now? Just trying
not
to complicate my troubleshooting later and avoid pitfalls!

"Cris Hanna [SBS-MVP]" wrote:

Generally if you have the SP3 for ISA installed now
You would reinstall base product, reinstall SP3, import config
There is no need to apply SP1 and 2...SPs are cumulative

And FW client should be installed on all workstations where Internet
Access
is required

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"g3po" <g3po@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0346C2A1-ABEE-4FEC-88A8-14903E333994@xxxxxxxxxxxxxxxx
Problem:
I had issues with ISA 2004 after latest june Windows updates - reboot
"corrupted the firewall". 6 hours of support with MS didn't provide
any
insight - and solution was to uninstall the product because I was
unable
to
locate the disk.

Now that I have the correct disk (I did all along - long story) I need
to
reinstall ISA 2004. In the environment previously, not all clients had
FW
installed, 30% did. Documentation here:

http://download.microsoft.com/download/c/a/b/cab5c8cd-d0f9-4b37-93c3-f36d976c86a2/PremiumInstallSteps.htm

Says that it is required on all clients. Q1. Is this true?

Q2. I have found little to no documentation on applying service packs
in
relation to applying the backup of configuration I have. Backup is
taken
from SP3 applied - so do I apply all 3 SP in order, then backup
configuration? Or, install, apply backup config, then run SP in order?
Any
help is appreciated!
.

Relevant Pages

  • RE: companyweb and Outlook stop working after ISA Install
    ... you install ISA 2004. ... The wizard will create access rules in ISA ... server automatic and make internal clients access SBS smoothly. ... Is there any error message when you access Exchange or companyweb? ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrade from trial to full version
    ... "Paul De Bie" schreef: ... > All you are supposed to do is run the install from your ISA-server CD ... > Your old configuration will be preserved but I strongly suggest ... > exporting your ISA config to a safe place first. ...
    (microsoft.public.isa)
  • Re: Issues after installing ISA 2004 SP1
    ... We have a couple of clients who have Windows server 2003 premium servers installed. ... The only thing i waited with was SQL SP4 and ISA 2004 because i was waiting for some confirmation on SQL SP4 from one software vendor. ... After installing the ISA 2004 update according to the install notes the following issues where encoutered at 2 customer locations. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems with SBS Premium Upgrade
    ... Are your clients running Office 2007? ... If so you will need to to an update that deals with not being able to connect to a Windows 2003 server. ... Install ISA ... Since this had already been a long day and I did not have much time to trouble shoot, I came to the conclusion that there was a problem with ISA. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA and RWW
    ... Install, update and run a scan with the SBS 2003 BPA to see if it can find ... anything wrong with your configuration. ... Since I have never installed ISA how will I find out how this all was ...
    (microsoft.public.windows.server.sbs)