Just installed Exchange 2010

Posted on 2011-05-10
Last Modified: 2012-05-11

I just installed Exchange 2010 on a Windows Server 2008 R2 computer. The installation was successful, I believe, because I did not receive any errors. I have not performed any post installation tasks except to register/license Exchange, and to install updates.

This Exchange Server is on an existing 2003 Server domain with Exchange 2007. Currently, my Exchange 2007 server is on Windows 2003. It is active and my users are using it. I want to begin transitioning my users to Exchange 2010, but I am not sure what the next steps are. What is the easiest thing to do? Do I just tell the Exchange 2010 server to accept my domain emails, route incoming traffic to it, and setup my smtp connector? Is that it?


PS: I will worry about certificates after the server is functional.
Question by:jhieb
    LVL 10

    Expert Comment

    LVL 16

    Accepted Solution


    For the next steps you'll have to do will be to move mailboxes on the new server and modify messages routing so that the new server receive directly incoming messages and also can send messages directly to internet.

    You can decide to move mailboxes first and then modify routing, or modify routing and then move mailboxes... as you prefer.
    Personnaly I prefer modify routing after mailboxes moving.

    Moving mailboxes is very easy. You do that from the Exchange 2010 console, under the "Recipients" container. You'll see all the mailboxes that exist in your organization, event the Exchange 2007 mailboxes. You make a right-click on a mailbox and then choose "Local move".
    Exchange 2010 creates a "move" job and a specific service of Exchange 2010 is in charge to process these jobs. That means that you can close the Exchange console, the jobs will complete in background. If you come back in the console later, under "Recipients", under "move jobs" you can see status of jobs. You can remove "completed" jobs because they won't automatically be removed.

    About changing message routing, you should start preparing the "receive connector" so that your new Exchange 2010 server The receive connector shoud accept anonymous SMTP connections for incoming messages (by the way, when I say "incoming" messages I mean messages coming from outside your organization... message coming from Exchange 2007 mailboxes are implicitly accepted).

    Personnally, I use TELNET commands to verify that receive connectors are ready and accept incoming mails.

    After ensure the receive connector accept SMTP incoming anonymous traffic you can decide to "switch" the routing for incoming SMTP messages. Operzations here depend of what is present between your server and Internet: Is there a SMTP relay server (then you'll have to configure this relay to deliver incoming messages to your new server) ? Is there external world directly (in this case you 'll have to ask your provider to modify MX record to point to your new server IP address) ?

    Finally, you can crate a new "send connector" in your Exchange organization to allow the Exchange 2010 server to send messages to external recipients. There again, the send connector configuration depends of what is between the server and Internet... If there is a SMTP relay you must configure the send connector to use this relay as a smarthost to deliver all outgoing messages. If there is Internet directly then you'll configure the send connector to resolve DNS names of target SMTP domains.

    Only the new Exchange 2010 server should be declared as a source server in the send connector "source servers" tab.

    As soon as the send connector is created the Exchange 2010 mailboxes will use this connector when they send messages to external recipients, whatever the costs are configured on the Exchange 2007 and Exchange 2010 send connectors.
    So at this time you must be careful and monitor the routing to ensure all is ok.

    You should not have to configure SMTP accepted domains as they should already be declared in your Exchange 2007 organization... Exchange 2010 use the same organization parameters as the Exchange 2007 organization when you make a transition to Exchange 2010.

    Have a good day
    LVL 1

    Author Closing Comment

    This is exactly what I needed. Thank you.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Live - One-on-One Exchange Help from Top Experts

    Solve your toughest problems, fast.
    Exchange experts are online now and ready to help you.

    Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
    Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
    This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

    737 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

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now