Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange Server 2003 to 2010 Transition

Posted on 2011-03-01
5
Medium Priority
?
413 Views
Last Modified: 2012-05-11
I have built a 2010 Exchange Server (VM) Server 2008 64bit. I chose a typical install to keep it simple for the time being.

I have followed an instruction I found after a heap of research off the net: http://www.simple-talk.com/content/print.aspx?article=882

Anyway, all has gone rather well, I have totally snapshotted both servers, taken BUEX Sys Recovery images of my DC and 2003 Exchange server,a full backup of the mail database to tape and disk just in case I have to reverse anything.

I have moved a test user to Exchange 2010. I have tried emailing myself (internally) from the test user using Outlook 2007. I get nothing. Likewise if I do it from myself (internally) to Test User. If I send a mail to my external email account from test user, I get it and likewise when replying.

Now I read that Exchange 2010 creates a Routing Group Connector when installing in a 2003 environment. We run two domains here. One called domain1.com and the other domain2.com This is where I think it has broken down. I could be wrong but I am thinking that since it has seen two different domains, it has not created a routing group.

I have sort of confirmed my suspicions by opening up Exchange management shell and typing:
VERBOSE: Connecting to MX01.domain1.com
VERBOSE: Connected toMX01.domain1.com
[PS] C:\Windows\system32>Get-RoutingGroupConnector | fl

Low and behold, nothing is returned.

Now I have read that I can run New-RoutingGroupConnector but now I think I am wandering into dangerous territory and starting to mess with stuff that could leave me red faced and restoring mailboxes and DC's like crazy.

My question is, am I on the right track or have I missed something blatantly obvious upon installing Exchange 2010 or configuring it via the Console afterward.

I didn't choose custom installation as I wanted to keep it simple as written above. Should I have since it is not a straight forward install as it needs to co-exist with 2003 until I hit the delete button on the VM once I am done with it?

Also you should know that we don't run ISA here, we just have a Cyberguard  firewall. Therefore, I created a definition to the new server and changed the firewall rule from our existing 2003 server to the 2010 server to see if mail flowed. It didn't... Not even to the account that was moved to the 2010 server.

A bit more info, is we use our ISP as a mail relay, so we just have our ISP send all 25 traffic to our IP, then within the firewall we tell it to on-send any 25 traffic to our internal IP

Also our domain functional and forest functional level was at Windows 2000! However exchange 2010 still installed. I have now brought both functional levels up to 2008, however this has made no difference.

Do I need to reinstall exchange because of this or am I missing something so very obvious?

Any help would be greatly appreciated

0
Comment
Question by:paulwoz
[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
  • 3
  • 2
5 Comments
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35014966
With a domain & forest functional level so low, I am surprised Exchange 2010 even installed...
You can try New-RoutingGroupConnector and see if that is the quick fix to your problem, otherwise either revert your lab or uninstall Exchange 2010, then do
Setup /PrepareSchema
Setup /PrepareLegacyExchangePermissions
Setup /PrepareAD
Setup /PrepareAllDomains
Then install Exchange 2010
0
 

Author Comment

by:paulwoz
ID: 35015090
Hi MegaNuk3,

I think I will revert snapshot and run through those setups again.

I should say that I did run setup /PrepareSchema /PrepareAD /PrepareLegacyExchangePermissions and ran /PrepareDomains but not /preparealldomains.



0
 
LVL 31

Accepted Solution

by:
MegaNuk3 earned 2000 total points
ID: 35015135
If you only have 1 AD domain with Exchange users in it then PrepareDomain is usually sufficient.

You could spend a quick 5 minutes with New-RoitingGroupConnector and that may resolve your problem, that is bound to be quicker than reverting. You can also rerun the setup / switches again even though Exchange is already installed.
0
 

Author Closing Comment

by:paulwoz
ID: 35153062
Thank you. New routing group connector was the issue.
0
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35154214
No problem, thanks for the points
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This video discusses moving either the default database or any database to a new volume.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

730 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