Enterprise Software Thread, Moving from Exchange 2003 to 2010 in Technical; I'm in the process of moving from Exchange 2003 to Exchange 2010sp1 and when I run the Pre-Deployment Analyzer it ...
1st December 2010, 04:57 PM #1
Moving from Exchange 2003 to 2010
I'm in the process of moving from Exchange 2003 to Exchange 2010sp1 and when I run the Pre-Deployment Analyzer it is warning about "SMTP is configured to route all messages to a smart host".
I intend to leave 2003 running while I move the mailboxes over to the 2010 box.
SMTP instance.... is configured to route all messages via smart host 'relay.embc.uk.com'. Remove this option if this SMTP instance wil be set as the source or target transport server of a routing group connector between Exchange Server 2010 and an Exchange Server 2003 routing group.
Is the above error anything to worry about?
1st December 2010, 05:28 PM #2
Don't take this as gospel as 2010 is a fairly new beast to me, but having gone the same route as you (and actually still being there some months later for various reasons!) I recall seeing the message myself.
It should be fine, but I believe 2003 will more than likely still process SMTP traffic.
Thanks to mb2k01 from:
Jobos (1st December 2010)
1st December 2010, 05:58 PM #3
no, keep it as it is - a smart host is just MS talk for sending email via a relay - which you will probably want to do if your going through embc
Originally Posted by Jobos
Thanks to CyberNerd from:
Jobos (1st December 2010)
1st December 2010, 08:48 PM #4
1st December 2010, 10:20 PM #5
As long as the connector between 2003 and 2010 still exists it will send email between them, had this going the other way for a while with 2010 reciving and 2003 storing for a while.
4th December 2010, 09:19 PM #6
- Rep Power
This only means you are routing your mails using an external SMTP server...
13th December 2010, 12:09 PM #7
So I've hit another problem.
I'm following Install Exchange 2010 in an Existing Exchange 2003 Organization: Exchange 2010 SP1 Help and I've got to halfway down the page about Configuring the Client Access Server and I keep getting the error
It doesn't seem to matter if I'm configuring OWA, OAB or any of the other setting listed in this section. It looks like something is not installed but I've followed the guide the best I can and I can't see where I've gone wrong
The operation couldn't be performed because object <SERVER>\OWA couldn't be found on <SERVER>.
20th December 2010, 04:35 PM #8
Right, I've sorted all but one error now but this one has got me foxed.
I've moved a mailbox over to Exchange 2010 and now I can't get Outlook 2003 to connect to it. Encryption is off and I've dropped the firewalls on both the server and client. The error message is:
Everything I can find on Google refers changing the encryption settings but that's already disabled.
Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available
20th December 2010, 04:42 PM #9
Is this Outlook accessing internally or externally?
Also, can you confirm that Microsoft Updates are up to date on the client? I'm fairly sure there were a couple of hotfixes for Outlook 2003 to connect to Exchange 2010 released a while back.
20th December 2010, 05:06 PM #10
Thank for the reply.
The clients are accessing internally and using WSUS for the updates. What classification was the update in WSUS... most likely the one I don't have selected
20th December 2010, 05:30 PM #11
Ah, question I don't know how to answer I'm afraid! I've managed to completely delegate responsibility for WSUS between two of my technicians!
In the traditional Microsoft update sense it would have been a hotfix after sp2 I guess?
21st December 2010, 06:13 PM #12
When you setup the Exchange server you need to specificially tell it if you have Outlook 2003 or older clients connecting to it, did you do this as part of the setup?
21st December 2010, 11:53 PM #13
No, I don't recall doing that. Can this be changed now using power shell or the Exchange console?
21st December 2010, 11:59 PM #14
we didn't require any. although we were running office 2003 sp2. you do need to to either configure the outlook 2003 for secure access to exchange 2010 or configure exchange 2010 not secure.#
Originally Posted by mb2k01
EDIT: sorry just read above posts, but still my post stands it was okay for us with this setup. 77
We found people roaming between outlook 2003 and outlook 2007 more of a problem with the outlook profile getting corrupt.
Last edited by oxide54; 22nd December 2010 at 12:01 AM.
22nd December 2010, 01:04 AM #15
I believe so, I've not got my book here in-front of me but i think it can be set in the Client Access options.
Originally Posted by Jobos
By oxide54 in forum Windows Server 2008 R2
Last Post: 25th August 2010, 11:20 PM
By jmair in forum Windows Server 2008
Last Post: 19th May 2010, 08:35 AM
By RabbieBurns in forum Windows Server 2008 R2
Last Post: 11th May 2010, 03:51 PM
By mb2k01 in forum Windows Server 2008 R2
Last Post: 30th March 2010, 05:28 PM
By Geek_of_HeathMount in forum Windows Server 2008 R2
Last Post: 8th December 2009, 04:09 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)