Windows Server - configuring ISA 2004 on live network

Asked By JiminClevelan
24-Jul-07 03:06 PM
We currently have a 2000 server running ISA 2000 on our network.  I just
installed a 2003 server and want to load ISA2004 on this server.  Since our
internal addressing scheme is 192.168.0.X, when I configure the internal
addressing of the ISA 2004 server, can I also put this on the 192.168.0.X
network without it trying to "take control" of the ISA role on the network?
ISA Server 2004
(1)
Cleveland
(1)
A13630C5ADD9
(1)
Fd6eeb6cfa07
(1)
Edgesecurity
(1)
Differnet
(1)
Isaserver
(1)
ISA2004
(1)
  Mariu replied...
24-Jul-07 04:44 PM
Hi Jim,

don't worry, you can configure the ISA 2004 also on the 192.168.0.x network.
Just make sure it does not has the same IP as the ISA 2000 Server.
Do you want to replace the old ISA Server, or why do you want to have both
on the same subnet?

Regards
Marius
  JiminClevelan replied...
24-Jul-07 05:20 PM
Marius,

Thanks for the reply.  The ISA 2000 server is going to be replaced by the
ISA 2004 server.  They are two, separate physical boxes.  I'm just trying to
get the 2004 server configured as close to the 2000 server as possible.  My
networking skills are not the greatest so I'm not sure of how to do this, i.e
put them on separate subnets.  If you have any other info that can help me
out, I'd really appreciate it.

Thanks,

Jim
  Phillip Windell replied...
24-Jul-07 08:51 PM
Jim, just give the new ISA a differnet IP# on the same subnet (maybe one
number higher or lower).  Do the same on the public side if you have more
public IP#s. All the rest of the TCP/IP specs stay the same.

If you set your network up to use Proxy autodetection then the users can
seelessly move to the new server when ready and they won't know the
difference.  This is especially true if you get the WPAD Proxy Autodetection
working with the old ISA first.  Then when you are ready to make the switch
just change the "A Record" in DNS that the WPAD Alias points (from old
server to new server) and give it about 3 days and most of the user will be
silently and transparently moved to the new ISA.

I just got done yesterday doing exactly the same thing with ours going from
ISA2004 to ISA2006.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------
Create New Account
help
ISA Server 2004 on Domain Controller Windows Server I have installed ISA Server 2004 on Domain Controller running Windowas Server 2003 SP2 standard edition. Since, ISA Server 2004 blocks everything after installation, I am having
ISA Server 2004 EE and Windows Server 2003 SP2 (ADAM component) Windows Server Dear ISA Server 2004 EE users, I would like to draw your attention to a recent issue regarding ISA
Cannot access SMTP server published via ISA server 2004 Windows Server Hi, I'm trying to resolve a situation where an Exchange server is published (for incoming SMTP) via ISA Server 2004, but SMTP connections from the outside world are refused. Any help would be appreciated
Isa server VPN Connectivity Windows Server Hi, I am trying to troubleshot VPN connections. We have a ISA Server 2004. Sometimes the users are not able to connect to our VPN server (ISA Server 2004). Since ping is disabled - how can I get users to troubleshot from their
Problem with MSDE2000 on ISA Server 2004 (HP Appliance) Windows Server I have an HP DL320 Appliance with WIN2003SP1 and ISA Server 2004 SP2. I can't use MSDE Logging, because when I configure the "Firewall Logging Properties I receive this message: Add / Remove Programs applet, select Microsoft ISA Server 2004 and click Change. Then, in the Microsoft ISA Server 2004 Installation Wizard use