Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
How can I configure my Exchange 2010 to become the main SMTP server
I Started with a new client.
The other day an old server (lets call it SRV1) crashed. I figured no problem, all apps and data have been removed, until I noticed that my Windows 2008 R2 Exchange 2010 server lost it's ability to send emails out.
It appears that the Exchange server is relying on SRV1 for SMTP. How do I undo this? How do I set my healthy Exchange server to send/receive emails for the domain?
I can't seem to find any configuration on the Exchange side linking it to SRV1. I do see within the connection logs that it is attempting to connect to SRV1. Srv1 shows that it has two routing groups: 'Exchange Routing Group' associated to the new Exchange server and 'First Routing Group' associated to SRV1. I see an extra connector associated to the 'Internet' within the SRV1 'First Routing Group'. I don't want to screw this up, but, I'm running out of time - SRV1 is failing.
History:
SRV1 is a Small Business 2003 server with a build in Exchange version 6.5.7638.1. I believe the previous IT guy was performing some type of migration between the old SBS 2003 domain to the new Win 2008 RD domain - including Exchange mailboxes. It's just my guess. The Win 2008 RD Exchange version is 14.00.0722.000.
The other day an old server (lets call it SRV1) crashed. I figured no problem, all apps and data have been removed, until I noticed that my Windows 2008 R2 Exchange 2010 server lost it's ability to send emails out.
It appears that the Exchange server is relying on SRV1 for SMTP. How do I undo this? How do I set my healthy Exchange server to send/receive emails for the domain?
I can't seem to find any configuration on the Exchange side linking it to SRV1. I do see within the connection logs that it is attempting to connect to SRV1. Srv1 shows that it has two routing groups: 'Exchange Routing Group' associated to the new Exchange server and 'First Routing Group' associated to SRV1. I see an extra connector associated to the 'Internet' within the SRV1 'First Routing Group'. I don't want to screw this up, but, I'm running out of time - SRV1 is failing.
History:
SRV1 is a Small Business 2003 server with a build in Exchange version 6.5.7638.1. I believe the previous IT guy was performing some type of migration between the old SBS 2003 domain to the new Win 2008 RD domain - including Exchange mailboxes. It's just my guess. The Win 2008 RD Exchange version is 14.00.0722.000.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Hi,
Verify the send connector and make sure that source server is configured with Exchange 2010 server.
Verify the send connector and make sure that source server is configured with Exchange 2010 server.
I verified on my Exchange 2010 server, in my Organization Configuration - Hub Transport - Send folder that the connector is set for Internet. Yet It Is still relying on my SRV1 server to send out emails. If I turn off SRV1, I am unable to send email
Again, I'm trying to make my Exchange server the sole entity for email for my security domain. I don't think I need to point to a smart host. Am I wrong?
Well first of all. Your build of Exchange is RTM. It looks like no updates have ever been applied.
You are almost 5 years out of date with your Exchange version.
Current version is SP3 RU10 which is version 14.03.0248.002.
Check your A and MX records to make sure they are configured correctly.
Read through this article.
Setup DNS for Outgoing Email in Exchange
http://www.tomsitpro.com/articles/exchange_server-mx_records-dns,2-135.html
But most importantly get up-to-date. It's going to be rough. There are always issues when making huge jumps in versions.
The previous guy left you with a mess that you are going to have to clean up.
Microsoft Exchange Support wouldn't even talk to you with a version of Exchange this old.
You are almost 5 years out of date with your Exchange version.
Current version is SP3 RU10 which is version 14.03.0248.002.
Check your A and MX records to make sure they are configured correctly.
Read through this article.
Setup DNS for Outgoing Email in Exchange
http://www.tomsitpro.com/articles/exchange_server-mx_records-dns,2-135.html
But most importantly get up-to-date. It's going to be rough. There are always issues when making huge jumps in versions.
The previous guy left you with a mess that you are going to have to clean up.
Microsoft Exchange Support wouldn't even talk to you with a version of Exchange this old.
Good call ScottCha
I was starting to feel no one wanted to touch this subject, and rightfully so. Imkottees was brave enough to start the dialog. I thank you both for your replies.
I like your thinking ScottCha, that was the 1st thing I checked - how out of date is the new exchange server. I am also aware of the potential for disaster while performing the much needed MS updates. I also had already reviewed the suggested article for DNS setup - you and I are on the same page. I'm holding off on the above, until I can gather more info on my SMTP routing issue
Let me tell you where I am today - THE PLOT THICKENS:
I personally would not have done this type of setup. I would have created a fresh AD on the Windows 2008, along with a fresh install of Exchange 2010. There are only 10 users on this network. I would have backed up the PST'S and created new desktop profiles pointing to the new AD.
They (previous tech guys) choose to migrate from an operating system (SBS 2003) that doesn't want to relinquish (built in it's DNA) control of the root of the forest. Yes ScottCHA, they left me in a world of hurt. Aside from the fact that my two servers are caught in a vicious SMTP routing loop, a good portion of my security AD is about to die. They ultimately left me in the middle of a crucial migration.
So....I believe my next move is to delete the Exchange routing connectors, uninstall the old SBS 2003 Exchange, transfer all the FSMO roles, demote the SBS 2003 and shut the failing server down. Then I would proceed to fully upgrade the new Exchange 2010 server.
I found an excellent article on the web regarding the migration from SBS2003 to Windows 2008 R2:
Any thoughts or comments are welcome. If you fore see any pit falls in my plan, please advise.
This is going to be hairy!
I was starting to feel no one wanted to touch this subject, and rightfully so. Imkottees was brave enough to start the dialog. I thank you both for your replies.
I like your thinking ScottCha, that was the 1st thing I checked - how out of date is the new exchange server. I am also aware of the potential for disaster while performing the much needed MS updates. I also had already reviewed the suggested article for DNS setup - you and I are on the same page. I'm holding off on the above, until I can gather more info on my SMTP routing issue
Let me tell you where I am today - THE PLOT THICKENS:
I personally would not have done this type of setup. I would have created a fresh AD on the Windows 2008, along with a fresh install of Exchange 2010. There are only 10 users on this network. I would have backed up the PST'S and created new desktop profiles pointing to the new AD.
They (previous tech guys) choose to migrate from an operating system (SBS 2003) that doesn't want to relinquish (built in it's DNA) control of the root of the forest. Yes ScottCHA, they left me in a world of hurt. Aside from the fact that my two servers are caught in a vicious SMTP routing loop, a good portion of my security AD is about to die. They ultimately left me in the middle of a crucial migration.
So....I believe my next move is to delete the Exchange routing connectors, uninstall the old SBS 2003 Exchange, transfer all the FSMO roles, demote the SBS 2003 and shut the failing server down. Then I would proceed to fully upgrade the new Exchange 2010 server.
I found an excellent article on the web regarding the migration from SBS2003 to Windows 2008 R2:
Any thoughts or comments are welcome. If you fore see any pit falls in my plan, please advise.
This is going to be hairy!
Sorry, I see my link didn't reflect in my last comment.
https://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
https://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
Why not go directly to 2012 R2? I recently did a 2003 ---> 2012 R2 migration. FSMO roles transferred, DNS, DHCP all went without a hitch. The only issue I ran into was I created the new computer account ahead of time and ran into a bug where the NETLOGON directory wasn't shared.
Here are my OneNote files on that...
Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx>
Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 network
From <http://blogs.technet.com/b/canitpro/archive/2013/05/05/step-by-step-adding-a-windows-server-2012-domain-controller-to-an-existing-windows-2003-network.aspx>
Migrating Windows Server 2003 FSMO Roles To Windows Server 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2015/02/11/step-by-step-migrating-windows-server-2003-fsmo-roles-to-windows-server-2012-r2.aspx>
Migrating DHCP From Windows Server 2003 to 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2014/11/26/step-by-step-migrating-dhcp-from-windows-server-2003-to-2012-r2.aspx>
Very cool command to make sure you are getting DHCP from the right server.
ipconfig /all | find /i "DHCP server"
Migrating a Windows Server 2003 file server, NTFS and Share Rights to Windows Server 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2014/10/30/step-by-step-migrating-a-windows-server-2003-file-server-ntfs-and-share-rights-to-windows-server-2012-r2.aspx>
You don't want to do this any more than you have to. Server 2008 is 7+ years old already.
Since it's only 10 users, you might want to consider standing up a standalone Exchange server, get it working properly, then export the data to PSTs, and import it into new mailboxes.
Might be less of a mess. Just a thought.
Here are my OneNote files on that...
Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx>
Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 network
From <http://blogs.technet.com/b/canitpro/archive/2013/05/05/step-by-step-adding-a-windows-server-2012-domain-controller-to-an-existing-windows-2003-network.aspx>
Migrating Windows Server 2003 FSMO Roles To Windows Server 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2015/02/11/step-by-step-migrating-windows-server-2003-fsmo-roles-to-windows-server-2012-r2.aspx>
Migrating DHCP From Windows Server 2003 to 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2014/11/26/step-by-step-migrating-dhcp-from-windows-server-2003-to-2012-r2.aspx>
Very cool command to make sure you are getting DHCP from the right server.
ipconfig /all | find /i "DHCP server"
Migrating a Windows Server 2003 file server, NTFS and Share Rights to Windows Server 2012 R2
From <http://blogs.technet.com/b/canitpro/archive/2014/10/30/step-by-step-migrating-a-windows-server-2003-file-server-ntfs-and-share-rights-to-windows-server-2012-r2.aspx>
You don't want to do this any more than you have to. Server 2008 is 7+ years old already.
Since it's only 10 users, you might want to consider standing up a standalone Exchange server, get it working properly, then export the data to PSTs, and import it into new mailboxes.
Might be less of a mess. Just a thought.
Was that a migration from small business server 2003 to 2012 R2 standard?
I agree with your thoughts, but, it appears the gun has already been shot before my arrival and my client already feels a choke hold on cost. I was thinking, if I could get them to a safe place with their existing windows 2008 R2 without to much trouble, I would buy them time. Then I would make the suggestion to upgrade or just get a new 2012 server.
Your right. I would like to just start fresh. Issues have probably been drag over to the new 2008 DC, that I have yet to reveal.
Thank you for all your support
I agree with your thoughts, but, it appears the gun has already been shot before my arrival and my client already feels a choke hold on cost. I was thinking, if I could get them to a safe place with their existing windows 2008 R2 without to much trouble, I would buy them time. Then I would make the suggestion to upgrade or just get a new 2012 server.
Your right. I would like to just start fresh. Issues have probably been drag over to the new 2008 DC, that I have yet to reveal.
Thank you for all your support
I would like to also add to my previous thought, SRV1 (the original SBS 2003 server) is failing every couple of days. I need to ensure my AD is intact with all it's FSMO roles in a hurry.
It wasn't SBS 2003, just plain 2003, but that shouldn't make any difference.
I stood up the 2012 server and had the FSMO roles transferred in 2 days. I could have done it in less but I wasn't under the gun like you are.
I stood up the 2012 server and had the FSMO roles transferred in 2 days. I could have done it in less but I wasn't under the gun like you are.
I'm following the link I mentioned above. I'm at the point where it asks if we use recipient policies that are manage mailbox policies or if we have recipient policies that are used for both e-mail address definition and mailbox management. It is suggested that we access the ADSI edit and remove the above entries. I don't believe the previous support guy did anything special in the previous 2003 Exchange environment. Is it OK to leave this item alone? After I perform the above action, I'm to remove the routing group connectors
Ultimately the instructions are preparing me to completely remove the old SBS 2003 Exchange service on my old server.
Do you think I should regain the SMTP functionality (ability to email out) from the new server 2008 R2 Exchange server after I remove the routing group connectors from the old SBS 2003 Exchange, or do I have to completely pull the old SBS 2003 exchange service out of the domain?
If the new 2008 exchange server is functioning (clients are able to connect and get emails) , how screwed am I going to be if I completely uninstall the old exchange software from the old server?
Ultimately the instructions are preparing me to completely remove the old SBS 2003 Exchange service on my old server.
Do you think I should regain the SMTP functionality (ability to email out) from the new server 2008 R2 Exchange server after I remove the routing group connectors from the old SBS 2003 Exchange, or do I have to completely pull the old SBS 2003 exchange service out of the domain?
If the new 2008 exchange server is functioning (clients are able to connect and get emails) , how screwed am I going to be if I completely uninstall the old exchange software from the old server?
You need to figure out the Send Connector /smarhost issue.
Here is how to configure the Send Connector.
https://technet.microsoft.com/en-us/library/Aa997285%28v=EXCHG.141%29.aspx?f=255&MSPPError=-2147217396
Here is how to configure the Send Connector.
https://technet.microsoft.com/en-us/library/Aa997285%28v=EXCHG.141%29.aspx?f=255&MSPPError=-2147217396
Sorry for my delay.
I received info from another Exchange IT person. He kind of rattled my cage about deleting the recipient policies. He stated that If I don't follow the proper procedure in decommissioning this old 2003 Exchange server I have the potential of losing the ability to create new mailboxes on my new Exchange 2010 - after the old 2003 is gone. So I have been in research mode.
I might just try to delete the connectors first on the old 2003 server and attempt to regain my SMTP service from the 2010. If I lose my ability to send out email, I will reroute my MX to a on-line email service temporarily while I troubleshoot the issue. I'm not connecting to a smart host. It is just a simple SMTP out to the internet.
I also noticed that all the 2003 Exchange services are disabled except for the SMTP. Do I have to turn everything back on in order to properly uninstall?
Thank you for all your help
I received info from another Exchange IT person. He kind of rattled my cage about deleting the recipient policies. He stated that If I don't follow the proper procedure in decommissioning this old 2003 Exchange server I have the potential of losing the ability to create new mailboxes on my new Exchange 2010 - after the old 2003 is gone. So I have been in research mode.
I might just try to delete the connectors first on the old 2003 server and attempt to regain my SMTP service from the 2010. If I lose my ability to send out email, I will reroute my MX to a on-line email service temporarily while I troubleshoot the issue. I'm not connecting to a smart host. It is just a simple SMTP out to the internet.
I also noticed that all the 2003 Exchange services are disabled except for the SMTP. Do I have to turn everything back on in order to properly uninstall?
Thank you for all your help
You are correct ScottCha
The previous IT Guys left me with a major mess. This is beyond frustrating!
I was given a great step-by-step procedure to decommission my old SBS 2003 Exchange server. This procedure addresses my SMTP connectivity issue along with some vital must do steps to regain some type of health in my exchange and AD environment. I unfortunately got stuck at step one - replication of my Public folder. I am getting the following errors:
Event ID: 3089
Error 0x80040107 occurred while processing an incoming replication message on public folder store 'Public Folder Database 0216379931'
Event ID: 3079
Unexpected Replication thread error 0x80040107 on database "Public Folder Database 0216379961"
I do get some messages that state the replication was successful, but, it always gets followed by the above messages.
I was afraid to upset the original environment during this process with new service packs, being that I'm dealing with an old SBS 2003. I though I might push past the point of no return fully updating my 2008 exchange 2010. Maybe it's time to revisit that concept.
Should I fully update the 2010 Exchange service packs?
The previous IT Guys left me with a major mess. This is beyond frustrating!
I was given a great step-by-step procedure to decommission my old SBS 2003 Exchange server. This procedure addresses my SMTP connectivity issue along with some vital must do steps to regain some type of health in my exchange and AD environment. I unfortunately got stuck at step one - replication of my Public folder. I am getting the following errors:
Event ID: 3089
Error 0x80040107 occurred while processing an incoming replication message on public folder store 'Public Folder Database 0216379931'
Event ID: 3079
Unexpected Replication thread error 0x80040107 on database "Public Folder Database 0216379961"
I do get some messages that state the replication was successful, but, it always gets followed by the above messages.
I was afraid to upset the original environment during this process with new service packs, being that I'm dealing with an old SBS 2003. I though I might push past the point of no return fully updating my 2008 exchange 2010. Maybe it's time to revisit that concept.
Should I fully update the 2010 Exchange service packs?
First to resolve the e-mail send issue ,
Disable any existing Send Connector (Right Click to Disable)
Create New Send connector
Click on add type “*” in address space , This is by Default
After that there will be 2 options
1) Use Domain Name DNS mx record to send mail directly
2) Route mail through following smart host
Select 1 Option this will directly send e-mail to internet and there is requirment for SRV1
Letme know if you have any further query's.
Disable any existing Send Connector (Right Click to Disable)
Create New Send connector
Click on add type “*” in address space , This is by Default
After that there will be 2 options
1) Use Domain Name DNS mx record to send mail directly
2) Route mail through following smart host
Select 1 Option this will directly send e-mail to internet and there is requirment for SRV1
Letme know if you have any further query's.
I assume you want me to do this on the new 2010 Exchange server. There is one Send connector. I also assume the reason to disable is to have the ability to get back to functionality if the process fails, correct? I could just delete the newly created connector an enable the recently disabled connector - correct?
I don't see the ability to disable the connectors within the 2003 Exchange server. I have a routing group associated to both the new and the old world that contain connectors. The SBS 2003 Exchange server has a Internet connector that the new 2010 Exchange server appears to be relying on for outgoing email.
I don't see the ability to disable the connectors within the 2003 Exchange server. I have a routing group associated to both the new and the old world that contain connectors. The SBS 2003 Exchange server has a Internet connector that the new 2010 Exchange server appears to be relying on for outgoing email.
Every move I make, I run into a problem.
I attempted to disable the 'Send Connector' on the 2010 Exchange server and received the following error:
Property enabled can't be set on this object because it required version 0.1(8.0.535.0) or later. The object's current version is 0.0(6.5.6500.0).
I attempted to disable the 'Send Connector' on the 2010 Exchange server and received the following error:
Property enabled can't be set on this object because it required version 0.1(8.0.535.0) or later. The object's current version is 0.0(6.5.6500.0).
The logical place to create an SMTP connector is on the server(s) with the Hub Transport role. The other place to configure these Exchange 2010 send and receive connectors would be on the Edge Server.
Launch the Exchange Management Console.
Check the Organizational Configuration node.
Observe the Hub Transport node.
Check the Server Configuration.
Click on this second Hub Transport node.
This is where you create or edit the Send and Receive Connectors.
Exchange 2010 Hub ConnectorsExchange 2010 Hub Connectors
Receive Connectors
Receive connectors represent a gateway through which all inbound messages are enter your Exchange 2010 Server. You need a receive connectors for each server, and they control how that server takes delivery of messages from the Internet or email clients.
Luckily, the receive connectors required for internal mail flow are automatically created when you install the Hub or Edge Transport server role.
Once you create a Receive Connector you can tweak its Properties. Suppose you have a partner company, you can specify the source IP addresses from where you receive messages. Also, in the Limits tab you can adjust the maximum size of messages and configure permissions. And for troubleshooting messages, you could enable protocol logging on the General tab of Exchange 2010 SMTP connector.
http://www.tomsitpro.com/articles/exchange_2010-smtp_connectors,2-132-2.html
Launch the Exchange Management Console.
Check the Organizational Configuration node.
Observe the Hub Transport node.
Check the Server Configuration.
Click on this second Hub Transport node.
This is where you create or edit the Send and Receive Connectors.
Exchange 2010 Hub ConnectorsExchange 2010 Hub Connectors
Receive Connectors
Receive connectors represent a gateway through which all inbound messages are enter your Exchange 2010 Server. You need a receive connectors for each server, and they control how that server takes delivery of messages from the Internet or email clients.
Luckily, the receive connectors required for internal mail flow are automatically created when you install the Hub or Edge Transport server role.
Once you create a Receive Connector you can tweak its Properties. Suppose you have a partner company, you can specify the source IP addresses from where you receive messages. Also, in the Limits tab you can adjust the maximum size of messages and configure permissions. And for troubleshooting messages, you could enable protocol logging on the General tab of Exchange 2010 SMTP connector.
http://www.tomsitpro.com/articles/exchange_2010-smtp_connectors,2-132-2.html
I apologize for my delay.
I ignored the error messages while attempting to disable the existing connector and took a stab at just creating a 2nd new connector. It worked with two connectors activated. At least at this point, when the original SBS server fails it doesn't take down my activate 2010 exchange functionality.
This doesn't solve my global problem of removing SBS and making my 2008 the primary AD, along with the proper transfer of exchange functionality, but it does address my SMTP issue (my Expert Exchange question).
Thank you all for your help
I ignored the error messages while attempting to disable the existing connector and took a stab at just creating a 2nd new connector. It worked with two connectors activated. At least at this point, when the original SBS server fails it doesn't take down my activate 2010 exchange functionality.
This doesn't solve my global problem of removing SBS and making my 2008 the primary AD, along with the proper transfer of exchange functionality, but it does address my SMTP issue (my Expert Exchange question).
Thank you all for your help
Premium Content
You need an Expert Office subscription to comment.Start Free Trial