• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 230
  • Last Modified:

default SMTP connector during swing

exchange 2003- exchange 2003, old hardware to new hardware.  i have on my old exchange setup a connector folder with a default SMTP.  if i right-click and go to properties the server that is listed here is the source server(the original, server1)   should this be changed at any point of the migration or will this work itself out????
also in the protocols folder, SMTP/SMTP virtual server/properties... on the delivery tab/advanced, my fully-qualified domain name is the server1.domain.com.  how about this one, should this be changed at any point or will this work itself out.>>???
0
dtooth71
Asked:
dtooth71
  • 2
  • 2
  • 2
2 Solutions
 
lausengdnCommented:
The short answer is that it will work itself out.
Once you bring the new server online and Exchange is fully configured and you give the new server the TCPIP address of the old server and the old server is no longer online the new server will take over.
You will need to make sure you make any MX record changes that will need to be made.
If the name of the server is different you will need to make this change to your MX records.
IE:
Old server = mail.yourdomain.com
New server = new.yourdomain.com
You will have to update your MX records, If the two servers have the same name you don't have to change your MX records.
0
 
dtooth71Author Commented:
there has been no MX changes or anything,  this is a new server, new nqame new TCPIP settings.
0
 
SembeeCommented:
For the SMTP connector, you can simply add the new server to list of bridgeheads. Then both servers will deliver email in accordance with the SMTP connector settings.
If you don't add the new server as a bridgehead then all outbound email will go via the server that is listed. Not a problem until you come to remove the original server.

Not sure what the above post regarding MX records is about as SMTP Connectors are for outbound email whereas MX records are for inbound email.
You also don't need to do anything with IP addresses - that can actually cause more problems. When you come to move the server receiving the email from the internet, just tweak the firewall slightly.

Simon.

--
If your question has been answered, pleased remember to accept the answer and close the question.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
lausengdnCommented:
The MX references I made came from a previous project where we wanted to have both servers running for a while so we added a MX record to accomplish this.
That is also where my TCPIP comments came from... 2 machines can't have the same IP...
Sometimes you want to test things out before you roll it out.
0
 
dtooth71Author Commented:
so for the bridgeheasd should i leave the old server and add the new server, or should i remove the old and add the new?
0
 
SembeeCommented:
When I am setting up the server I will have both servers list as bridgeheads. Then when preparing to remove the old server, only at that point will I remove the bridgehead.

On the MX records point above, you don't need to add a second MX record to do this. Email can be delivered to any Exchange server in the org. Once Exchange has the message it will ensure that it is delivered to the correct server.

Simon.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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