Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 683
  • Last Modified:

Remove ISA from an EBS 2008 environment

Dear Experts,

We deployed an EBS 2008 system a fair few years ago.  Had a few problems with it along the way and now its time to migrate it off.

MS dropped development of EBS quickly and we took advantage of the "make it right kit" that they offered.  I have just run through this procedure and the DC, exchange and ISA server are all now separate products.

As per the pre-defined, default configuration of ISA in this environment, it has rules for publishing the OWA site amongst others.  It also  hosts the exchange edge transport services.

I'm planning to migrate off to new hardware and would be keen to see the system - as it stands - running without ISA.  

So I would envisage that it might involve the following:

- remove exchange services from the ISA box
- remove the edge subscription from exchange box and create new send connectors
- remove the ISA box
- create rules in the new hardware firewall for smtp delivery to the exchange box, https etc

Would this sound broadly feasible?  I really want ISA out of the picture with the system as it stands now.  I know it would be easier to migrate off and just not include the ISA in that process but I have a use for the ISA hardware prior to the planned migration.  Also, as a priority, I have been tasked with setting up several site-site VPN tunnels with the hardware firewalls that are being deployed and I KNOW that ISA is going to be a problem.

Thanks
0
tech53
Asked:
tech53
  • 3
  • 2
1 Solution
 
Cliff GaliherCommented:
Unless you already have rules in place and properly configure the exchange hub transport, mail flow will break the moment you try to uninstall TMG (unless you really are running ISA for some bizarre reason...)

So the order of steps you outlines will probably not work for you.
0
 
tech53Author Commented:
Yes it's Tmg of course. I would expect and accept loss of mail flow during a process like this and I will get the order correctly defined before proceeding.

I'm more concerned about the fact that it was once in an EBS environment and the effects that removing it would have when compared to a "standard" environment. EBS was heavily wizard driven and a lot of configuration was done automatically by the system itself.

What would you suggest I do to ensure the clean removal of the tmg box and ensure that we have solid mail flow afterwards?

Thanks
0
 
Cliff GaliherCommented:
As long as you ran the update released as part the discontinuation of EBS, the tight integration has been stripped away. As with any multi-server environment, migrating certain roles must be planned and carefully executed, but there is no special consideration to EBS in this instance.

As far as what I'd do, as I said, I'd prepare the hub transport first, then the replacement edge component, whether that be router or UTM. Then it is a matter of cutting traffic over, verifying flow, and then you can more casually decommission the old edge server and all of its roles.
0
 
tech53Author Commented:
That's sound.

Sidetracking slightly, do you think it would be ok to remove system centre essentials?
0
 
Cliff GaliherCommented:
Yes.
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now