Data sync between exchange 2003 and exchange 2013

Need assistance on a general direction.
There is a 2003 domain with exchange 2003 currently in use. On this domain there is also a contact management application that is heavily integrated and cannot be update at this time.  I would like to bring up a new 2013 exchange server.
Is there a method that I could have user data synchronized between the 2013 exchange data and the 2003 exchange? In this manner users could use the 2013 exchange as primary and the Contact manage application could use the sync copy of exchange 2003. For
now I am only concerned about he the calendar however I am sure the other information will need to be sync as well.
Please let me know.  Thank you.

Hi There,
Once you install Exchange 2013 it will use the same data your Exchange 2003 is using \ seeing because both of them use Active directory for Directory information.
Exchange 2013 will see all the users that are 2003 without you needing to sync \ move data.
If you need to users to be on Exchange 2013 and keep Exchange 2003 all you need to do is move the mailboxes to Exchange 2013.
Cheers,
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Similar Messages

  • Connector help ( Coexistence Exchange 2003 and Exchange 2010)

    Dear all,
    we are in a Coexistence state where all the mailboxes are not yet migrated to Exchange Sever 2010.
    On Exchange server 2003 we have two connectors 1) Internal 3) External
    1) Internal connector is used to have mail flow between postfix mail and Exchange server.
    2) External Connector is used for sending/receiving emails from External domains (like gmail,yahoo etc...)
    3) when we added first Exchange 2010 that time it created one RGC used for sending/receving emails between Legacy and new server.
    What I want to achieve is created new two more connectors on Exchange server which will act as Internal & External connector.
    if these works then delete connectors on legacy server and go ahead with for rest migration
    is it possible if not then how do it ? 
    TheAtulA

    Hi AtulA,
    Thank you for your question.
    Internal:
    To support coexistence between these two routing topologies, all Exchange 2010 servers are automatically added to a single routing group when Exchange 2010 is installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange
    2003 as Exchange Routing Group within Exchange Administrative Group.
    During the installation of the first Exchange 2010 Hub Transport server in an existing Exchange organization, we must specify an Exchange 2003 bridgehead server to which to establish the first routing group connector. We recommend that you select a bridgehead
    server located in a hub routing group or in a routing group that has many mailboxes. The routing group connector links the routing group where the Exchange 2003 server resides and the Exchange 2010 routing group. The Exchange 2010 routing group includes all
    Exchange 2010 servers, regardless of the Active Directory site in which they reside.
    Notice: Don't move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR), and don't rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Neither action is supported. Exchange 2010 must use
    this routing group for communication with Exchange 2003.
    External:
    We could create send connector and receive connector to send/receive email from Internet, we should modify the firewall setting to point to Exchange 2010.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Removing dead Exchange 2003 and Exchange 2000 Server from the domain

    Hi Team,
    I have come across a client who wants to migrate to O365 from existing Exchange 2003 environment through the Hybrid Model. I am trying to introduce 2010 Sp3 to the environment. While checking the environment using Exchange pre-deployment found 2 servers
    in the environment which is not present on the network now. Client has no clue what they are.
    One is Exchange 2003 and the other is Exchange 2000. The problem here is i cannot introduce Exchange 2010 Sp3 unless all the Exchange servers are running minimum Exchange 2003 Sp2. 
    At present i find only 2 exchange 2003 Sp2 server which are in production. Need kind assistance to move forward.

    Hi,
    I recommend you follow the steps below:
    1. Please upgrade Exchange 2000 and Exchange 2003 to Exchange 2003 SP2 at first.
    2. Deploy Exchange 2010 servers in this order: CAS, Hub, UM and Mailbox. For more information, here is an article for your reference:
    Exchange 2003 - Planning Roadmap for Upgrade and Coexistence
    http://technet.microsoft.com/en-us/library/aa998186(v=exchg.141).aspx
    3. Install Exchange 2010 SP3.
    Here is an article for your reference.
    Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
    http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
    About a hybrid deployment with Microsoft Office 365 using Microsoft Exchange Server 2010 servers, here is an article for your reference. 
    Understanding Upgrading Office 365 Tenants for Exchange 2010-based Hybrid Deployments
    http://technet.microsoft.com/en-us/library/jj945383(v=exchg.141).aspx
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange 2003 and Exchange 2010 Coexistence Activesync Issue

    Hello,
    I am currently on the progress of migrating mails from Exchange 2003 SP2 to Exchange 2010 SP3. Before I can do actual migration, I need to make sure that OWA and Activesync works when Exchange 2010 becomes Internet facing.
    Right now Exchange 2003 is Internet facing while Exchange 2010 is internal LAN only. OWA login from Exchange 2010 to a mailbox in Exchange 2003 works fine. However, trying to open a mailbox in Exchange 2003 from Exchange 2010 Activesync fails.
    Activesync login from Exchange 2010 to a mailbox in Exchange 2010 works fine, as well as logging in from Exchange 2003 to mailbox in Exchange 2003.
    Tests using AccessMyLAN ActiveSync Tester using Exchange 2010 as entry point are inconclusive. The test shows the app successfully contacting ActiveSync version 6.5 which is Exchange 2003, but results in "Activesync detected, but not correctly configured."
    Tests using Test-ActiveSyncConnectivity from Exchange 2010 reveals Error HTTP 400 when contacting Exchange 2003. The cmdlet also shows it successfully contacting Activesync version 6.5 (Exchange 2003).
    I have searched around, installed hotfix KB937031, enabled Integrated Windows Authentication on Exchange 2003 Microsoft-Server-Activesync, disabled Require SSL for Microsoft-Server-Activesync and exchange-oma, yet I still can't connect to a mailbox inside
    Exchange 2003 through ActiveSync 2010. Website Multiple Identities for port 80 has been set correctly. Exchange 2003 has Forms-Based Authentication Enabled and is the one thing we haven't tried disabling yet.
    We want to make sure everything works first, then make Exchange 2010 Internet facing, and finally do the mail migration. We do not want to migrate everyone in a single sitting. Please if anyone have ideas any help is welcomed!

    Exchange 2010 will proxy ActiveSync for Exchange 2003.  For OWA, it will redirect, so you need a legacy redirect URL.  You can test all of this internally without changing your Internet connection.  For ActiveSync you can use a WiFi connection.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Data sync between on-premise and azure database

    HI, I am not able to setup data sync between my on-premise database and azure database. Following is the error I am getting after it ran for almost 36 hours...
    Sync failed with the exception "GetStatus failed with exception:Sync worker failed, checked by GetStatus method. Failure details:An unexpected error occurred when applying batch file C:\Resources\directory\4c6dc848db5a4ae88265ee5aa1d44f40.NTierSyncServiceWorkerRole.LS1\DSS_7b1d73b4-d125-466f-94ab-eaa4553ea0ae\ed19f805-3d50-466a-96b3-861c4f22d8a4.batch.
    See the inner exception for more details.Inner exception: Failed to execute the command 'UpdateCommand' for table 'dbo.Transactions'; the transaction was rolled back. Ensure that the command syntax is correct.Inner exception: SqlException Error Code: -2146232060
    - SqlError Number:10054, Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) "    For more information,
    provide tracing ID ‘e6a1fad1-f995-4ffe-85db-0c6dc02423f1’ to customer support.

    Hi, sorry it has been a long time since your last post. Are you still using SQL Data Sync and hitting any issue which we could help with?
    Linda

  • Legacy integration between Exchange 2003 and Exchange 2010

    Dear Team,
    we are using Microsoft Exchange 2003 & 2010 Server for Emails, now we have both servers are connected, we want to raise new Single incident request for doing this activity, we want disconnect 2003 server from 2010 server so accordingly need support,
    we are ready to pay for this incident, 
    pls do the needful,
    Thanks & regards
    Anteshwar Bhosale

    Hi Anteshwar,
    If you want to remove Exchange 2003 from your coexistence environment, please perform the following procedure:
    1. Move all mailboxes to an Exchange 2010 server in the organization.
    2. Move all content from the public folder database on the legacy Exchange 2003 server to a public folder database on an Exchange 2010 server in the organization.
    3. On Exchange 2003 servers, for each offline address book (OAB), move the generation process to an Exchange 2010 server.
    4. Verify that Internet mail flow is configured to route through your Exchange 2010 transport servers.
    5. 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.
    If all above steps have been prepared, we can remove the last Exchange 2003 server from the Exchange 2010 organization from ADSIEdit. For detailed steps about this, please refer to:
    https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • How to block for data sync between web cloud and each PC.I want control for all user's pc as administrator.

    I already blocked as below url.
    Sync/Store/Share Core Creative Cloud
    https://creative.adobe.com/api/assets
    https://creative.adobe.com/api/collections
    hptts://creative.adobe.com/api/share
    But one of user create file on C:\Users\Administrator\Creative Cloud Files it is sync with web cloud and another pc.
    I saw  sync on or off function in set up tap.
    but I want block sync for all users as administrator.

    Moving the discussion to File Hosting, Syncing, and Collaboration.
    Thanks,
    Atul Saini

  • Error when trying to configure sync between Outlook 2003 and Blackberry Desktop Software 4.6

    I am unable to configure the Blackberry Desktop Software (version 4.6) to sync with my Outlook 2003.  I used to have an older version of the desktop software and it worked just fine.  I got a new phone and updated the software and am unable to configure the sync.  I get the following message when I try to configure it: "Runtime Error: folder is no longer part of the system data source or the folder could not be found."
    Please help.  I need these to sync.

    HI and Welcome to the Forums!
    I suggest trying a clean DTM uninstall:
    KB02206 How to perform a clean uninstall of BlackBerry Desktop Software
    followed by reinstalling from scratch. You should be able to go to the latest v5.0 with Outlook 2003...it's available here:
    http://na.blackberry.com/eng/services/desktop/#tab_tab_overview
    Cheers!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Migrate windows 2003r2 AD to windows 2012r2 AD and exchange 2003 to exchange 2013 Steps

    Hi
    requesting advice,
    how can i migrate windows 2003 ad + windows 2003 exchange to windows 2012r2 AD+ exchange 2013 DAG (planing to implement 2 mail box and 2 hub+cas hyper-v  vm servers ) 
    kindly guide me how can i migrate and what is the best practice method
    requesting step by step procedures to follow
    Regards
    Ratheesh
    Ratheesh

    Hi Ratheesh,
    Migrating AD from Windows Server 2003 domain to Windows Server 2012 R2 domain:
    Introducing the first Windows Server 2012 Domain Controller (Part 1 of 2)
    http://blogs.technet.com/b/askpfeplat/archive/2012/09/03/introducing-the-first-windows-server-2012-domain-controller.aspx
    Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2
    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
    Since we cannot migrate Exchange 2003 to 2013 directly, you can either migrate to Exchange 2007 or Exchange 2010 then to Exchange 2013.
    Checklist: Upgrading from Exchange 2003 and Exchange 2007
    http://technet.microsoft.com/en-us/library/ff805038(v=exchg.141).aspx
    Checklist: Upgrading from Exchange 2003
    http://technet.microsoft.com/en-us/library/ee332309(v=exchg.141).aspx
    Part 1: 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
    Checklist: Upgrade from Exchange 2010
    http://technet.microsoft.com/en-us/library/ee332309(v=exchg.150).aspx
    I hope this helps.
    Amy

  • Exchange 2003 to Exchange 2007

    Hello,
              I have inherited a network where the transition was not complete. It Consists of Exchange 2003 and Exchange 2007 Server. Currently all the mailboxes are moved  to the Exchange 2007 Server, now I have to remove the
    exchange 2003 server and related to that I have few Question to be asked.
    1) Exchange 2003 server is also having Active Directory Installed in the Server, is it possible to remove the exchange server without removing the active directory ?
    2) Is it possible to shutdown all the exchange 2003 services and creating the send and receive connector on the exchange 2007 server to route the emails. I will delete the old exchange server when every thing works fine with exchange 2007.
    3) Currently Exchange 2003 is having public ip and people cannot access there mailboxes as they are located on exchange 2007 how can route people to new exchange 2007 server keeping the public ip on the exchange 2003 server.
    4) Do I really have to purchase the certificate in order to run the exchange 2007 server ? 
    http://www.arabitpro.com

    Hi,
    I agree with Eric and Andres's suggestion. Before removing your Exchange 2003, please make sure the following points have been successful:
    1. All mailboxes have been moved to Exchange 2007.
    2. All Public folders are moved to Exchange 2007.
    3. OAB generation has been pointed to Exchange 2007.
    4. Mail flow is routing through Exchange 2007 transport server.
    5. All services (OWA, ECP, Availability service, autodiscover, OOF, OAB etc.) are working well in CAS 2007.
    If everything is working well in Exchange 2007, then we can remove the Exchange 2003 from the organization.
    Winnie Liang
    TechNet Community Support

  • Exchange 2003 to Exchange 2013

    Instead of going from Exchange 2003 to 2010 to 2013. I have decided to remove Exchange 2003 from the organization and install 2013 since I don't have too many users.
    I have removed Exchange 2003 from the Organization (http://tutorial.programming4.us/windows_server/Removing-an-Exchange-Server-2003-Server-from-an-Organization.aspx).
    When I install Exchange 2013, it doesn't ask me for the organization name. Is it using the data that was left in Active Directory from Exchange 2003? I ran the setup to uninstall Exchange 2003, doesn't that remove the Exchange 2003 data in Active Directory
    as well?
    Thanks

    So, have you migrated all the data from exchange 2003 to 2013 before it has been removed ?
    If not, I am really wondering how you have removed exchange 2003 without installing 2013 and migrating users mailboxes data from previous one.
    By the way, please walk through this well described blog that seems to be helpful in your circumstance and provides step-wise instruction for the same : http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2003-exchange-2013-part1.html
    If you wish to achieve this goal automatically, you may also consider on this automated application (http://www.exchangemigrationtool.com/) that could be an appropriate solution to migrate mailboxes directly from exchange 2003 to 2013 by skipping intermediate
    version. 

  • Migration of domain 2003 and exchange 2003

    dear sir,
    presently  we have    domain controller win2003 std sp2  and exchange server 2003 sp2  ,installed on domain controller
    we need to migrate from  exchange 2003 to exchange 2010 and then to  exchange 2013. please suggest the procedure step by step
    can i migrate exchange 2003 to   exchange 2010 with  win2012 R2 std  in domain 2003
    or we need to first upgrade  domain controller  or exchange server.

    Hi,
    First, we should note that only Exchange 2013 SP1 is supported on Window 2012 R2. And it is not recommended to install Exchange server on DC server.
    Since both Exchange 2010 and Exchange 2013 can run at least Exchange 2003 domain/forest functional level, we can upgrade Exchange first and then raise the functional level.
    Because Exchange 2013 can't coexist with Exchange 2003, you need to remove Exchange 2003 server before you decide to upgrade to Exchange 2013.
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Free/Busy availability and Out of Office not working after Exchange 2003 to Exchange 2010

    We just migrated from Exchange 2003 to Exchange 2010 as an intermediate step before we get to Exchange 2013.  I want to make sure everything is working OK before we start the migration to Exchange 2013.  
    The users have Outlook 2010, and there are 2 issues.  They can't view free/busy times for other people using the scheduling assistant, and they can't set their Out of Office messages.  If they go in through Outlook Web Access, then these features
    work!
    I've searched the forums, and I see a few similar issues, but I don't think this is related to the .Net issue on the CAS server.
    Any suggestions?
    Thanks!
    --Kent 

    Hi Kent,
    Try checking the free busy info Outlook 2010 with running  /cleanfreebusy switch
    Check the Free/Busy System Public Folder and pointed out to the correct server on each mailbox DB in Exchange 2010
    Find the public folder replica database
    get-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" -Recurse | fl name,Replicas
    In E2k10 check if the exchange 2003 is added in the replica list. If not try adding them and check.
    force Public folder content replication.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.
    That will encourage me - and others - to take time out to help you.
    Regards,
    Sathish

  • Server 2003 and Exchange 2003 upgrade.

    Spin upa new VM as a domain controller and Global Catalog Server. Transfer the FSMO roles to it and let it sit overnight. Do NOT demote the Server 2003 domain controller or you will break Exchange 2003. Exchange 2003, when installed on a domain controller, doesn't properly configure itself to find domain controllers on the network. Instead, it goes into it's SBS configuration where it will only look at the current host for domain services.Next, determine which version of Exchange you want to go to. If migrating to an on-premises Exchange keep in mind that Exchange 2003 works with Outlook 2010 and earlier and that Outlook 2003 and earlier don't work with Exchange 2013. This means you need to upgrade to Exchange 2010 and enable non-secure Outlook connections on it, then upgrade Office to 2007 or later, and then upgrade to Exchange 2013.I...

    I'll ask why Server 2012 and not r2 & why exchange 2010 and not 2013?  I'll assume budget.
    The only difference I think I'd have with Gary is that I'd leave the demotion and removal of the old DC until the end.
    New DC, transfer the fsmo roles.  Make sure that replication is working properly.
    New Exchange box.
    Look up the requirements for removing the last exchange 2003 server, there are specific steps for this.Then demote and remove the old DC.Start by checking the Domain and Forest Function Levels :) 

  • I bought a new imac running Loin and Office 2011. The server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software.

    I bought a new imac running Loin with Office 2011. I am the only mac in the office and the Server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software other than webmail access through our website. It looks as though 2011 is not compatible with 2003 per some searches online, but what are some options I have to gain full access again? I purchased parallels in hopes that this my help and I am able to use remote desktop connection to log on to server but can not drag and drop files I need. There is a shared drive on that Server we all use to exchange files.
    The two main issues are gaining access to my email again and ability to drag and drop files from mac to pc. I hope this is enough info to get some solutions.
    PS - IT person says my iMac's IP is what his server does not understand so that is why I can not login.

    Office 2011 is not compatbile with Exchange 2003.
    I suggest you post further Office related questions on Microsoft's own forums for their Mac software:
    http://answers.microsoft.com/en-us/mac

Maybe you are looking for