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

Similar Messages

  • 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 :) 

  • 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

  • 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

  • Business Package for Communication with NW04 and Exchange 2003?

    Hi, we are evaluating opportunities to realize a groupware integration in the SAP Portal EP60SP2. A upgrade to Netweaver is planned, so the possible solution should work with Netweaver too. Our Exchange version is 2003.
    I'm thinking about the standard SAP Groupware-Integration in combination with the Business Package for Communication.
    <b>Has anyone expirences with the Business Package for communication, Netweaver and Exchange 2003, yet?</b>
    I know, it's not officially supported, but maybe it works.
    With the OWA-iViews we've got problems to implement our Styleguide and to devide into different iViews. The informations shown in the iViews of the Business Package are adequate and we would save ActiveX.
    <b>Is there another solution that works?</b>
    <b>Are there other iViews from 3rd party developers, that show Outlook informations?</b> Has anyone realized something like this in a project yet?
    I would be grateful for any ideas.
    Sandra

    Hi Sandra,
    Please note that the Business Package for Communication was only available for SAP EP 5.0. Newer releases of SAP EP contain the groupware (GW) functionalities and some GW iViews automatically as soon as KM is installed with the EP. The integration with MS Exchange 2003 should work. If you look for iViews such as Send EMail, Create Appointment, Show availability and Room Calendar, you can use the iViews shipped by SAP. If however you need the EMail inbox or the personal calendar and tasks, then the native OWA iViews are the way to go. For further details please refer to the SAP NetWeaver admin guide http://help.sap.com/saphelp_nw04/helpdata/en/0c/30d624a0fae949902f7a4b2a8f98bd/frameset.htm.
    Hope that helps
    Christian Stadler

  • Single Inbox on Unity Connection 8.5 and Exchange 2003 SP2

    Hi,
    We have Unity Connection 8.5 (with SU2) and Exchange 2003 SP2
    We want to setup the Single Inbox feature that works well with Exchange 2007 and 2010, but my customer is running Exchange 2003 SP2.
    We met all of the requirements outlined in: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp459928
    I configure a new "Unified Messaging Services" profile for Exchange using Exchange 2003 and enabled for Single Inbox.  When I run "Test" it displays the following errors (other validation is successfully)
    The service port for IMAP is not functioning.      
    The system failed to connect to the server with a socket connection through port beatles.clubone.com:993. The error is error:0200206F:system library:connect:Connection refused. Refer to the tomcat log file for more details. If you are using secure connection, confirm that SSL is enabled on the server.
    Why is it trying to connect using IMAP, that wasn't the case when I used for Exchange 2007 or 2010 when IMAP was not enabled.
    Is there something else I'm missing for configuration with Unity Connection to support Single Inbox with Exchange 2003 SP2?
    Thank you!
    -rya

    Hi Rya,
    I just wanted to add my +5 vote for this great catch by Aaron (nice work "A")
    If you are going to upgrade to Unity Connection 8.6
    Check out this great doc from Saurabh for the refresh upgrade notes to 8.6.
    https://supportforums.cisco.com/community/netpro/collaboration-voice-video/unified-comm-application/blog/2011/08/11/checklist-before-upgrading-to-unity-connection-86
    Cheers!
    Rob
    "Show a little faith, there's magic in the night" - Springsteen

  • How to migrate public folders from legacy (exchange 2003 ) to exchange 2010

    How to migrate public folders from legacy (exchange 2003 ) to exchange 2010 . Please suggest ?
    Aditya Mediratta

    Hi Aditya,
    please find the answer in
    http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
    Please ensure you have a working mailflow from Exchange 2003 to 2010, vice versa, before you begin. 
    Basically it's the same procedure as adding some PF Database in E2K3; just
    run .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
    Wait until some initial data started to replicate; after that run
    Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
    After replication has finished you can do a
    .\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
    Please let me know if it worked.
    Kind regards,
    Martin

  • SAP Business One 8.8 PL 12 of Windows 2003 and SQL 2003

    Dear All,
                 My client has a present server with windows server 2003 and SQL server 2003 installed can we succesfully install SAP Business One 8.8 PL 12 and Higher PL OR will it be a constrain.

    Hi,
       Let me rephase my QUES
    My client has a server with the following installations
    windows server 2003 (5 CAL)
    MS SQL 2003
    We will be installalling SAP Business One 8.8 PL 12 on the server
    are ther any issues for installing SAP 8.8 on MS Server 2003 and SQL 2003
      or do we need higher Version I mean (windows 2005 or windows 2008)

  • Migrate from Standard 2003 domain with seperate Exchange 2003 to SBS 2011 - possible? how-to?

    Hi there,
    I am currently planning on replacing two servers (one server 2003 standard (DC) and one server 2003 standard with exchange 2003) with a single machine running SBS 2011.
    I already did several migrations SBS 2003 to SBS 2011, SBS 2008 to SBS 2011 - and I am wondering if the same can be done from 2003 Standard with separate exchange server 2003 to a single SBS 2011. Technically I can see no reason why this shouldn't work -
    but so far I have been unsuccessful in finding guidelines or at least some success-stories from other users.
    Did anyone do something like that? Any caveats I have to be aware of? Or is it supposed to be flawless as the SBS to SBS migrations I did so far?

    Hi,
    From the problem description, I understand that you would like to migrate Exchange server 2003 on Windows Server 2003 to SBS 2011.
    At first, I would like to clarify one thing. Microsoft doesn’t have the official documentation towards this scenario. And Microsoft doesn’t
    recommend dealing with that.
    I noticed that there are two servers in your organization. One is Windows server 2003 for DC; the other one is Exchange server 2003. So it can’t
    be the same as the documentation (Migrate to Windows Small Business Server 2011 Standard from Windows Small Business Server
    2003).
    I got your key point that you would like to know the detailed procedures (HOW TO). I suggest that you could visit the
    SBSmigration.com to get further information you need. Since it’s not the Microsoft official method,
    please do the test before your put it into your production environment.
    Regards,
    James
    James Xiong
    TechNet Community Support

  • AD DS 2012 R2 and Exchange 2003

    First, yes I understand that Exchange 2003 is no longer supported. :) However, in the real world there are still companies running Exchange 2003 in production. Hopefully not for long.
    The client I am at is in the middle of a Exchange 2003 to O365 migration.  They are a few months from wrapping the project up.  I am in the middle of doing an Active Directory upgrade from 2003 functionality to 2012 R2.  Currently all their
    domain controllers in the forest that Exchange is in are running Windows 2003 and of course it is set at 2003 functionality.  They had a few NT 4.0 domains left that we finally decommissioned during this project.  Yuck!
    My question is, I have read that Exchange 2003 isn't supported with 2012 R2 domain controllers.  However, I can not find what will happen if we start to introduce 2012 R2 domain controllers.  The plan is to bring up all of the DC's and then cut
    over to 2012 R2 functionality. 
    Does anyone have or know what exactly will happen if we go ahead with deploying 2012 R2 domain controllers.  I can't find any information documented except for it isn't supported.  We have other projects waiting the AD upgrade to be complete and
    can't wait for the O365 project to be completed.
    Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

    Hi Kristopher,
    As you mentioned that Exchange 2003 does not support Windows Server 2012 Domain Controllers, which will lead to unexpected issues.
    Here is a similar thread below for you:
    Adding Windows 2012 DC to 2003 Level Domain (with Exchange Server 2003)
    https://social.technet.microsoft.com/Forums/en-US/29301f55-531e-40e7-9a9d-bab4d0b05b33/adding-windows-2012-dc-to-2003-level-domain-with-exchange-server-2003
    Best Regards,
    Amy

  • 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

  • SBS Server 2003 and Exchange Server - need to access but only have HDD

    Hi,
    I have been redirected here from a Microsoft Community Forum. I am reasonably conversant with windows systems but am not a computer professional, just trying to see if I can solve a problem without spending a great deal of cash at this stage as
    our office has been completely flooded out and we are still struggling to regroup....Here is the original question.
    A couple of years ago our sever died completely, we kept the HDD's, but unfortunately not the CD's with the software on or the software keys. So I have now 2HDD's, the original boot partition and one with data on. both clean and fully working and
    connected now to an old desktop. I can see everything fine, but I cannot boot from the original boot drive (I have tried simply disconnecting the desktop's boot drive and the windows logo shows for 1 second an d then chucks me back to the initial (DOS?) load.
    The point is that I need to boot into SBS2003 with the exchange server installed in order to access a handful of old emails which have become extremely important, and also to run an old version of Filemaker server which will not run on any newer O.S.
    I have tried, incidentally, a converter for the exchange files and I can see the directories but I think that unless I pay $xxx for something, which I cannot afford now, then I will not get the emails and all attachments back.
    So my question is this - is there anyway I can use the original boot disk in a new hardware environment to restore both sbs 200 and exchange to working condition? I have paid vast sums for both so I do feel that I should be able to use them still!
    Many thanks
    Gor

    Hello
    tip:
    get one pc with hyper-v or VMware. with enough memory.
    install 2003 OS with sp2
    run dcpromo  add same domain name wich is old.
    install exchange 2003  /with same ORG name / and install exch 2003 sp2
    open exch console and Enabling the database to be overwritten on mailbox database
    dismount database, rename database, and copy old database to new and mont database
    run clean mailbox
    create new user without mailbox.
    select disconect mailbox and connect to new user.
    sorry my english

  • Account Lockout issue between Apple devices and Exchange 2003

    I have been having an ongoing issue for a couple of months with a few different users Apple devices locking out their accounts in AD when they try to authenticate to ActiveSync.  This doesn't happen every time they authenticate, it seems to be random,
    while the rest of the time they have access to their email.  It might occasionally happen with an Android, but not on a repetitive basis like this.
    Primarily this has been four different iPads, running different versions of iOS, and an iPhone running the latest release of iOS 7.  Other iPhones and iPads function without having the problem, including iPhones on iOS 7.  
    The user accounts in question are set to never have their passwords expire, but again, they aren't the only users that are set like this, and those other users, even with Apple devices are not having the same problem.
    I used NetWrix to trace out the source machine, which is my Exchange 2003 server and times, and I've checked the W3SVC1 log file, and come up with the following as an example with identification details masked:
    <internal IP>, <Domain\Username>, 4/30/2014, 8:10:04, W3SVC1, <ServerName>, <internal IP>, 15, 329, 3367926, 200, 0, GET, /exchange-oma/<[email protected]>/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplV50462*****/eb53cd5d5b9fcf40****************-20ef44,
    As I was typing this, the owner of the iPad from the log file above came by my desk, so I asked a couple more questions.  He's never had another iPad, it's a gen 1, and he's never updated the iOS on it.  I know one of the other iPads in question
    has the most up to date iOS, and the other one is brand new, replacing one that was broken, but the owner of that one had the same issue on a 3 year old iOS.  
    There is nothing special about the user accounts, no special privileges or restrictions.
    Has anyone encountered this before?  Exchange 2003, Server 2003 in a 2008 domain.  Promotion to the 2008 domain was 2 years ago.

    Hi Brian,
    I am so sorry for the delay.
    Do you have any progress by now?
    Since there are lots of devices which use user accounts to log on, failed logon attempts on these devices could be the cause for account lockout.
    If this issue persists, I suggest you refer to these troubleshooting articles below:
    Troubleshooting account lockout the PSS way
    http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx
    Troubleshooting Account Lockout
    http://technet.microsoft.com/en-us/library/cc773155(v=WS.10).aspx
    In addition, you can also get efficient support at Active Sync forum below:
    http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobilitylegacy
    Best Regards,
    Amy

  • 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

  • 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."

Maybe you are looking for