?
Solved

New Exngchange 2010 Install on new server  coexistence with 2003 until move complete

Posted on 2011-02-16
3
Medium Priority
?
1,585 Views
Last Modified: 2012-05-11
Hey All,

I have am doing a new Exchange 2010 install that will be  coexisting with the 2003 exchage for a short time, I am getting this warning durning the pre-Install check and have not seen it before and would like to know what I need to do prier to the install so not to have this warning.


SMTP instance 'CN=1,CN=SMTP,CN=Protocols,CN=SCSHSERVER,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=SCSH,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=SCSH,DC=local' is configured to route all messages via smart host 'smtp.comcast.net'. Remove this option if this SMTP instance is set as the source or target transport server of a routing group connector between an Exchange Server 2010 routing group and an Exchange Server 2003 Server routing group.
0
Comment
Question by:CyberxPA
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 58

Accepted Solution

by:
tigermatt earned 2000 total points
ID: 34910670

Basically, what that warning is telling you is that the smart host (SMTP server) for delivery of all email to external recipients is set on your Exchange 2003 SMTP Virtual Server and not in a send connector.

This will cause issues with your Exchange 2010 co-existence, and so the setting needs to be removed.

In Exchange System Manager, go to the path listed in that error (First Admin Group / Servers / SCSHSERVER / Protocols / SMTP / Default SMTP Virtual Server). Go to the fourth tab - Delivery - then click Advanced.

Clear the Smart Host box.

You then need to make a send connector in Exchange 2003 so that email is still sent out via the Smart Host, just by a different method for now. See here for details on doing that: http://www.amset.info/exchange/smtp-connector.asp.

Of course, this is only temporary while Exchange 2003 is still in the equation, but you'll need this for external delivery of email until the 2010 environment takes over that role.

-Matt
0
 

Author Comment

by:CyberxPA
ID: 34910835
Thank you Matt, That fixed it right up.
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 34910913

Great stuff. Thanks for letting me know!
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
In-place Upgrading Dirsync to Azure AD Connect
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses
Course of the Month15 days, 14 hours left to enroll

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question