Welcome to ISAserver.org

Upgrading ISA2k Enterprise to ISA2K4 Standard

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Installation >> Upgrading ISA2k Enterprise to ISA2K4 Standard

Page: [1]

Message

<< Older Topic Newer Topic >>

Upgrading ISA2k Enterprise to ISA2K4 Standard - 27.Sep.2005 3:40:00 AM

Posts: 18
Joined: 4.Sep.2003
Status: offline

I am looking for advice on upgrading ISA 2K Enterprise (no array) to ISA 2K4 Standard.

I've just purchased an HP server/appliance with ISA 2004 ST. preinstalled. I need to import the configuration from an old W2K3 / ISA2K ENT. machine.

What is the best procedure to follow?

Thank you all.

[ September 27, 2005, 02:28 PM: Message edited by: AN ]

Post #: 1

Featured Links*

RE: Upgrading ISA2k Enterprise to ISA2K4 Standard - 28.Sep.2005 10:31:00 AM

EJansen

Posts: 25
Joined: 1.Feb.2003
Status: offline

On the ISA 2004 CD there is a SUPPORT directory where you will find a very nice tool that exports your ISA2K configuration into an XML file that imports rather nicely into ISA2K4 with a minimal amount of fuss.

(in reply to AN)

Post #: 2

RE: Upgrading ISA2k Enterprise to ISA2K4 Standard - 29.Sep.2005 3:18:00 PM

Posts: 18
Joined: 4.Sep.2003
Status: offline

Thank you. Will it work in the Enterprise-to-Standard migration ?

(in reply to AN)

Post #: 3

RE: Upgrading ISA2k Enterprise to ISA2K4 Standard - 30.Sep.2005 8:27:00 AM

EJansen

Posts: 25
Joined: 1.Feb.2003
Status: offline

I haven't tried it from Enterprise to Standard, but I don't see why it wouldn't work. To my knowledge, it only exports your rules, filters, destination sets, etc. If it were to export your AD settings as well, it would pose a security risk.

I must also correct myself. To export your ISA2K settings, use the export tool on the ISA2K CD. The tool on the ISA2K4 CD only works on ISA2K4 setups. Still the same process, but there seems to be a version issue. If you still have problems, Jim wrote a handy little tool to export settings into VBS file.

(in reply to AN)

Post #: 4