Bliesner
asked on
Installing message labs on Exchange 2007 in parrallel to existing SMTP solution
Hi all,
Long story short, but we have an overly complicated exchange setup for our requirements, and are looking to simplify things.
Part of this is to eventually build a simpler Exchange environment, and move our inbound email to filter through messagelabs. However, the subscription on our old anti spam service (GFI) has expired, and we need to cut over to messagelabs ASAP.
Before doing this however, and given we are not that confortable we understand the existing Exchange Setup 100%, we were thinking to try testing messagelabs via a 2nd test domain.
So, the idea would be as follows:
1) Test domain account set up
2) MX records pointed to messaglabs
3) Messagelabs setup for our test domain
4) Set up Exchange 2007 for the new domain name
5) Set up Exchange 2007 to accept incoming emails from messagelabs (in addition to it already working as is).
We have completed steps 1 through 4, but step 5 is where we need help/advice.
Current setup is as follows:
2 x Exchange 2007 servers (each on a different subnet), configured as Client Access Server/Hub (HTTPS. IMAPS, SMTP)
2 x Mailbox servers (each on a different subnet)
Some kind of failover/load balancing I assume, because of the duplicate servers
1 x SMTP/Webmail server running GFI (subscription now expired)
1 x Blackberry server
1 x Calandar Sync Server
(I think that's it!?!)
We were thinking to NAT one of the boxes (one of the Client Access Servers presumably?), and configure the server from there. We didn't want to use the existing SMTP server (although that would make it simple from a NAT perspective), because we are already experiencing terrible delays on receiving emails due to the overly complicated setup!
If the above idea is feasible, could you please list out the basic config instructions to make this happen, or, suggest an alternative idea - keeping in mind we don't want to disturb what's working there today.
Thanks in advance for your assistance.
Long story short, but we have an overly complicated exchange setup for our requirements, and are looking to simplify things.
Part of this is to eventually build a simpler Exchange environment, and move our inbound email to filter through messagelabs. However, the subscription on our old anti spam service (GFI) has expired, and we need to cut over to messagelabs ASAP.
Before doing this however, and given we are not that confortable we understand the existing Exchange Setup 100%, we were thinking to try testing messagelabs via a 2nd test domain.
So, the idea would be as follows:
1) Test domain account set up
2) MX records pointed to messaglabs
3) Messagelabs setup for our test domain
4) Set up Exchange 2007 for the new domain name
5) Set up Exchange 2007 to accept incoming emails from messagelabs (in addition to it already working as is).
We have completed steps 1 through 4, but step 5 is where we need help/advice.
Current setup is as follows:
2 x Exchange 2007 servers (each on a different subnet), configured as Client Access Server/Hub (HTTPS. IMAPS, SMTP)
2 x Mailbox servers (each on a different subnet)
Some kind of failover/load balancing I assume, because of the duplicate servers
1 x SMTP/Webmail server running GFI (subscription now expired)
1 x Blackberry server
1 x Calandar Sync Server
(I think that's it!?!)
We were thinking to NAT one of the boxes (one of the Client Access Servers presumably?), and configure the server from there. We didn't want to use the existing SMTP server (although that would make it simple from a NAT perspective), because we are already experiencing terrible delays on receiving emails due to the overly complicated setup!
If the above idea is feasible, could you please list out the basic config instructions to make this happen, or, suggest an alternative idea - keeping in mind we don't want to disturb what's working there today.
Thanks in advance for your assistance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
just want to add on because i saw your reason is to look for indepth
In order to achieve this in a normal world, you will do NLB
Exchange 2007 sp1 (and up) AND Exchange 2010 natively support NLB for CAs and HUB
http://technet.microsoft.com/en-us/library/bb125239.aspx
In order to achieve this in a normal world, you will do NLB
Exchange 2007 sp1 (and up) AND Exchange 2010 natively support NLB for CAs and HUB
http://technet.microsoft.com/en-us/library/bb125239.aspx
http://technet.microsoft.com/en-us/library/bb125239.aspx
READ High Availability and Load Balancing for Hub Transport Servers
ASKER