Migration Exchange 2003 to 2010 routing connector

Hello
At least we deside to migrate from 2003 to 2010 Exchange now i'm preparing and stuck around one question.
In our Exchange 2003 organization we have couple backend servers and one frontend on which OWA is installed.
OWA server placed to second routing group others backend server in first routing group.
Roitung group connected to each other by connector.
So the question - when i install CAS Exchange 2010 he asked me with which Exchange 2003 server i want to create connector - which server i should choose? Backend or Frontend which placed in different RG?

It doesn't really matter, it is a connector between your 2010 and 2003 servers.
You can choose the backend servers as it will reduce one hop in your case. Do make sure that you make the connector redundant by adding atleast two 2003 and 2010 servers as source and target servers in both connectors.
There will be two connectors - one from 2003 to 2010 and another from 2010 to 2003.

Similar Messages

  • Migrating exchange 2003 to 2010 while everyone is running SMTP, POP3 and IMAP on the old exchange 2003

    Hi all
    We have a legacy Exchange 2003 running with more than 800 users and with a very mixed configuration for client access. Most of users are running POP3/SMTP on the Exchange, some are running IMAP/SMTP and some are running MAPI access. 
    Please note that THERE IS NO WAY that we move all users to MAPI access before the installation (due to deadlines).
    We plan to install a new Exchange 2010, starting with a CAS/HUB server. We do not need to migrate users automatically, and we can proceed later to move them individually to the new Exchange 2010 infrastructure in a non-transparent way. 
    More importantly, we need to maintain that everyone receives their e-mail and all communication through the exchange 2003 continues uninterrupted. 
    My question is can we install the new CAS/HUB server, while maintaining the old exchange server running with it's old name and create new names for the CAS/HUB server. In such a configuration, will all the Exchange 2003 services continue to run as usual
    (POP3/IMAP/SMTP/MAPI)?

    In addition, you may also spend some times at below mentioned helpful resources to check the prerequisites before moving all mailboxes from exchange 2003 to 2010 :
    http://exchangeserverpro.com/wp-content/uploads/2011/02/Exchange-Server-2003-to-2010-Migration-Guide-V1.3-Planning-Chapter.pdf
    http://technet.microsoft.com/en-us/library/dd638130(v=exchg.141).aspx
    https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
    Moreover, to avoid any interruption  during the completion of migration process, you can also take a look at this application(http://www.exchangemigrationtool.com/) that could be a good alternate approach
    for you.

  • Migrate from 2003 to 2010 - Receive Connector Authentication

    I'm in the process of upgrading a remote office from Exchange 2003 to Exchange 2010.  Today, we changed the IP's on their firewall so that 2010 Hub Transport is handling mail.  Normally, I always create a new Receive Connector for receiving mail
    from the internet.  I leave it as Anonymous users only and receive on internal IP of the server.
    When I send an e-mail from the internet to a 2010 user, the mail is delivered fine, I'm assuming through the new "Anonymous" access connector I created.  However, when I send e-mail from the internet to a 2003 user, I get the following NDR
    with this error:
    Reason: 530 5.7.1 Client was not authenticated
    I was able to fix the problem by adding Anonymous authentication to the Default receive connector.  I'm wondering why this connector is being chosen over the Internet connector though, and why only for 2003 users?  Is it bad to leave the Default
    Connector allowing anonymous access?  I've always left that connector alone and created a new Internet connector which has seemed to work in the past.

    Hi,
    According to your description, exchange 2010 like a relay server, and relay the email to exchange 2003 when you send a email from the internet to a 2003 user.
    As Ed mentioned, when you add the correct IP address where the traffic comes from on the receive connector, then it would ensure that the correct receive connector would be used.
    The following article for your reference:
    Resolve 530 5.7.1 Client was not authenticated
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Unity 8.0 and Migrating Exchange 2003 to 2010

    In the coming months I hope to be upgrading from Exchange 2003 (sp2) to Exchange 2010 (sp3) running on Windows Server 2012.  I currently have Unity 8.0(3.1) running on Server 2003.  We hope to be upgrading to Exchange 2013 at the end of the year if that is supported.
    Before I contact my Cisco partner about this upgrade I would like to know what to expect.  Any advice and suggestions would be appreciated.
    Thanks!
    Nick

    The integration is completely different than with legacy Unity.  High-level: Unity leverages MAPI integration and is completely dependent upon AD and Exchange to function properly.  Hence, the schema extensions, Permissions Wizard (and associated permissions), and etc.  Unity Connection leverages web-based APIs for integration.  Specifically it uses WebDav for Exch 2003 and EWS for Exchange 2007/2010.  It is a dual message store synchronization architecture, which means that 1) it can function independently without AD and/or Exchange integration and 2) no schema extensions and 3) less complicated permissions requirements.  With Unity Connection, the users have a mailbox on the server and then a copy of that message is synchronized into the user's corporate Exchange mailbox.  You get MWI synchronization between phone and email and etc (hence, you get Unified Messaging).  Another nice thing is that you can handle requirements for voicemail only scenarios locally on Unity Connection without having to create dummy or "resource" AD/Exchange accounts in the corporate systems.  You can read up more on this integration here and hit me back up if you have questions.  I'll be glad to help if I can.
    http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg010.html
    As for the fax part, OK - that's a problem in your scenario.  Personally, I've never been a big fan of using Unity for that (and don't) but then again, I don't really like "fax" anyway.  Personal opinions aside, I'll go with relay of facts.  Unity Connection supports integration with 3rd-party fax systems.  You can take a look at that here:
    http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg080.pdf
    In terms of Unity though, the reality is that it's days are (and have been) numbered.  See below:
    http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps5745/ps6509/end_of_life_notice_c51-681593.html
    Hailey
    Please rate helpful posts!

  • Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

    I wasn't prepared for this task, and it was thrown at me to do...  Eyes are bleeding from planning reading and planning, would LOVE any input from you guys.  First time posting, here and have heard great things about these forums.  The Company
    I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
    Scenario:
    Old Domain/Server: (To be decommissioned)
    Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
    Exchange 2003 SP2 (6.5.7638.1)
    Server is a domain controller and exchange server.
    Migrating to:
    Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
    VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality 
    VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
    VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
    These are probably not ideal conditions, but I have to work with what I'm given.
    Host server (2012 R2) is in work group mode.  Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2.  I had intended starting at a lower functionality level and raising
    it later, but.... ya I forgot to change it.  If needed I can spool up a new DC with a lower functional level.
    DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain.  The concern is migrating the mailboxes from Exchange 2003 on the old domain to
    Exchange 2013 on the new domain.  The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
    I had some ideas, but I'm not sure if they will work.  This is something I have never done before (Senior Engineer Quit).
    My thoughts:
    - Establish a two way trust relationship between the two domains.
    - Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
    - Create the users on the new domain
    - Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013 
    - Link Exchange accounts to the correct user accounts on the new DC.
    Can this be done cleanly? Am I going about this the correct way?  Any feedback would be GREATLY appreciated.
    Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

    Hi,
    Base on my experience, your idea is feasible.
    However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link: 
    http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
    After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
    Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
    Exchange 2010/2007 to 2013 Migration and Co-existence Guide
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Exchange 2003 to 2010 migration issues

    Hello,
    I have installed exchange 2010 in my legacy 2003 environment six months ago.
    i have moved all the mailboxes, Public folders to exchange 2010 and created routing group connectors between 2003 -2010.
    now unfortunately the legacy server got crashed. now the problem is we are unable to receive emails.
    Can somebody help on this.
    Thanks,
    Sanjay.

    you need to verify that mail flow is configured for exchange 2001
    Verify that Internet mail flow is configured to route through your Exchange 2010 transport servers. For more information, see the following topics:
    Configure Internet Mail Flow Directly Through a Hub Transport Server - https://technet.microsoft.com/en-us/library/bb738138(v=exchg.141).aspx
    Configure Internet Mail Flow Through a Subscribed Edge Transport
    Server - https://technet.microsoft.com/en-us/library/bb738158(v=exchg.141).asp
    To verify that all inbound protocol services (Microsoft Exchange ActiveSync, Microsoft Office Outlook Web App, Outlook Anywhere, POP3, IMAP4, Autodiscover service, and any other Exchange
    Web service) are configured for Exchange 2010, see Managing Client Access Servers. - https://technet.microsoft.com/en-us/library/aa997850(v=exchg.141).aspx
    For other steps follow the article: https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
    Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
    question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

  • Exchange 2003 to 2010 Migration OAB Generation Issue

    Hi
    I am in the process of migrating from 2003 to 2010. All mailboxes are moved across and email in and out are moving through the 2010. However I cannot move the oab generation server as when i go to change the generating server my New 2010 server is not listed
    only the two old 2003 servers. This is a child domain in a large organization and is one of a large number of exchange servers forestwide. I have created a new oab and asigned to the mailboxes on the new 2010 server. The old 2003 server is off for over a week
    and there are no issues.
    I now need to remove both 2003 servers, what issues will not being able to move the generation server cause (If any if i am using a new oab). Also I am following the remove last exchange server line as this is the last 2003 server in this child domain are
    there any issues with this in this scenario?

    Hi,
    According to your description, I understand that all mailboxes have been moved to Exchange 2010 and a new OAB is created for all users in your environment.
    Please make sure the new created OAB is generated by Exchange 2010 and Enabled Web-based distribution. If there are any Outlook 2003 users in your environment, the public folder distribution should also be enabled. Then we can set the new one as default.
    If so, all users in Exchange 2010 would use the new created OAB by default.
    If you want to double check the OAB configuration, we can run the following command to check it:
    Get-OfflineAddressBook | FL
    Additionally, if your migration is complete and successful, we can follow the article below to remove the last legacy Exchange server from your Exchange 2010 organization:
    http://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
    Best Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2003 to 2010 Migration Active-Sync & OWA

    I am in the process of migrating from Exchange 2003 to Exchange 2010. I have a co-existence running currently. I have moved 1 mail box over to the new exchange server (a test account I created). I have 2 questions, one about OWA and the other about Active-Sync/Mobile
    access.
    1. When I log into my internal OWA site I can access the webmail just fine. However when I try to go to my external OWA site I get a HTTP Error 404. I have setup the weblink https://webmail.company.com in my external DNS record. However the internal link
    says it is https://webmail.company.com/owa. Is there something additional that needs to be setup in IIS for the external site to work or only after the migration is completed?
    2. I tried adding the account I migrated to my cell phone for mail but I just get a "Connection to server has failed" message. The internal and external link for mobile access is both the same and setup in external DNS https://mail.comapny.com.
    Is this a feature that only works after the migration is completed? I have ports 80,443,143,25,993 open in my sonicwall for e-mail services. However the IP is still set to my old exchange server. Is it possible to have 2 settings the same in sonicwall with
    2 different IP's? Last time I tried it with migrating my VPN neither VPN server worked after that.
    Any help and insight would be greatly appreciated. I am new to systems administration and this is my first exchange migration

    Hi,
    Here are my answers you can refer to :
    1. To deploy OWA in the Exchange 2003 and 2010 coexistence, we need a legacy namespace for the Exchange 2003 server.
    For more information, you can refer to the following article:
     http://blogs.technet.com/b/exchange/archive/2009/12/02/3408921.aspx
    Additionally, for the 404 error, I recommend you check the IIS log to find the root cause:
    http://support.microsoft.com/kb/943891
    2. I recommend you deploy Exchange 2010 in the "Internet Facing AD Site" and Exchange 2003 server in the "Non-Internet facing AD site": set the external URL in CAS 2010 and point mail.company.com to Exchange 2010 server IP address.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2009/12/08/3408985.aspx
    thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2003 to 2010 migration move public folder

    Hello.
    I'm on the road to Exchange 2010 migration and stuck at on question
    All tutorial says then you want to replicate system PF and Public Folders you need to add PF 2010 in ESM and set replication to Urgent,that's all
    But then  i view my system PF replication on Exchange 2010 i see checkbox Use public folder is checked and replication shedule on Exchange 2010 is set to Never run(greyed out)
    Is this right? Or i need to uncheck it and then shedule is set to Always run automaticly? 
    Do i need to do it for all PF? (system and non-system)?

    Hi stevemaystr,
    Don’t worry about the replication of PF, we can use the MoveAllReplicas.ps1 and ReplaceReplicaOnPFRecursive.ps1 script to move all public folder and all replicas to another database, please refer to:
    http://technet.microsoft.com/en-us/library/bb331970(v=exchg.141).aspx
    Additional,  I find an similar thread about Migrate PF from Exchange 2003 to Exchange 2010, for your reference:
    https://social.technet.microsoft.com/Forums/exchange/en-US/2dc27efa-d19c-4929-a2f1-54523c847d2a/moving-public-folders-from-exchange-2003-to-2010?forum=exchange2010
    Best Regards,
    Allen Wang

  • Shared mailbox access from exchange 2003 to 2010 users

    We'd successfully migrated from exchange 2003 to 2010. still some of the users are yet to be migrate.
    The issue is only in MAC (Apple) Migrated users was unable to access the shared folder residing in 2003 environment.
    but the migrated 2010 users are able to access the shared folders in the windows environment.
    Any one can assist or suggest this issue.
    Awaiting for ur reply.
    Regards
    kart26

    Hi Kart26,
    Please install certificate in your MAC App Client.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Public folders are not in sync after settting up Replicas between Exchange 2003 and 2010

    I have setup Public Folder replicas between the 2 Exchange servers and I can see all the top and sub level folders.
    For those mailboxes that were migrated over to Exchange 2010,  I have noticied  a lower number of item contents in these fodders when views from an Outlook client whose mailbox had been migrated over to Exchange 2010.
    On Exchange 2003 System Manager, if I properties one of the Public Folders, under the Replicataion tab, I can see the old and new server there. On the Exchange server 2003 box, I can see the last update reviced was a few weeks ago.
    I did see an option to synchronize content but I am not sure which server to run this one from. The Exchange 2003 or 2010 server.
    There is also a Resend Changes... option. Should I use this instead?
    Can anyone advise?

    Hi,
    The "Resend changes" and "Synchronize content" options in Exchange 2003 ESM are used to initiate hierarchy and content replication.
    To update public folder hierarchy and content from Exchange 2010 side, you can use the following commands.
    Update-PublicFolderHierarchy
    Update-PublicFolder
    Please run the Get-publicfolderstatistics cmdlet to get public folder details such as item count, this information will help you compare content replicated between the source and destination servers.
    Besides, here is a blog about public folder replication troubleshooting for your reference.
    http://blogs.technet.com/b/exchange/archive/2006/01/17/417611.aspx
    Hope this is helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Migrate Exchange 2003 to Office 365

    Dear all,
    We are going to migrate Exchange 2003 to Office 365. Because of the large number of mailboxes and mail databases, we decide to build hybrid to support coexistence during the migration period.
    According to "Exchange Server Deployment Assistant" I found that we can build more Exchange 2010 for that requirement
    http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-BwAIAAAAQAAAAAEAiFIAAAA~
    I just wonder that after deploying the Exchange 2010, can we move directly the mailboxes from Exchange 2003 to Office 365 or we need to move to Exchange 2010 first (as a "buffer") before moving to Office 365
    Thanks a lot !!!

    Hello,
    The main goal of a staged migration is to migrate Exchange on-premises servers when:
    1. You have more than 2000 mailboxes.
    2. You plan to migrate over a few weeks and months rather than in a single batch.
    3. You want to migrate to the Cloud completely and remove your on-premises Exchange deployment.
    Hybrid scenarios are useful when you do not want to remove your on-premises deployment. In some cases there is no technical possibility, it is not cost-effective etc. to move a whole organization to Office 365. In these situations you may decide that moving
    only some mailboxes to Office 365 is a good option and create a hybrid deployment.
    You need to consider all pros and cons, especially when Exchange 2003 has gone out of support lifecycle and then choose the better option for your organization.
    Hope it helps,
    Adam
    CodeTwo: Software solutions for Exchange and Office 365
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

  • Migrate Exchange 2003-2013 and AD 2000-2012

    We are in the process of migrating from Exchange 2003 to Exchange 2013. We currently have 4 Domain Controllers in Windows Server 2000. Two of them host also Exchange Server 2003 in an A-P mode configuration.
    The double hop migration to 2010 was not possible as it requiered a minimal functional level of Windows Server 2003. This lead us to consider the double hop migration to 2007 first, even though it is not the recomended path. We have more
    than 400 mailboxes with a size than often passes 1TB.
    Is this scenario possible and may be the risks? Do you think using a third party tool to pass data to Exchange 2013 would be a safer solution?
    Looking forward to your ideas.
    Thank you,
    Megi

    Hi,
    As far as I know, same with the Exchange server migration, we cannot also directly migrate AD 2000 to AD 2012. Thus, I recommend you directly upgrade to AD 2008 and then migrate Exchange 2003 to 2007 to 2013.
    Here are more references you can refer to :
    Exchange 2000/2003 to Exchange 2007 migration guidelines:
    http://blogs.technet.com/b/mbaher/archive/2008/06/04/migrating-exchange-2000-2003-to-exchange-2007-guidelines.aspx
    Step-by-Step Exchange 2007 to 2013 Migration:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2003 to 2010 error

    Hello I have been working through a upgrade of exchange 2003. I am at a point where when I try to send from exchange 2003 to 2010 I get the following error
    You do not have permission to send to this recipient.  For assistance, contact your system administrator.<My2003server.COM #5.7.1 smtp;550
    5.7.1 Unable to relay for [email protected]
    I have set the relay settings on my 2003 smtp server to allow all as a test with no luck any ideas?

    Anyone? I have hit a wall on this. Any help would be greatly appreciated.

  • Running Unity with both Exchange 2003 and 2010?

    My company is planning to upgrade from Exchange 2003 to 2010.  We are
    currently using Unity 7.0.  We'd like to run the two in parrallel for a bit and take our time switching users over.
    Now I've read that Unity can support Exchange 2010, but I haven't found anything about running Unity using both Exchange 2003 and 2010 in parrallel.
    Is this something Unity can handle?

    We're doing something similar, but we have an in-place Unity 7 and Exchange 2003 environment; we are putting some users from an org we support on an Exchange 2010 server, but do not want that to be the partner server (yet).  The instructions seem to point you to making 2010 the partner; I'm wondering why Step 13 (of your link) we are uninstalling the Exchange Server 2003 System Management Tools, if it’s a mixed environment and 2003 will still be the partner server.  I also saw somewhere that you don’t have to move the unitymsgstoresvc account to Exchange 2010 if you are in a mixed environment.  Is that true?  Thank you.

Maybe you are looking for