Announcement

Collapse
No announcement yet.

Exchange 2000 to 2007

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exchange 2000 to 2007

    I have a network that I inherited in which the previous tech was fired (I cannot find him to ask any questions). I have an Exchange 2000 server (only one) and I would like to migrate to a 2007 Exchange environment. The past week I have been pouring over information here and on TechNet. I have a Server 2008 server up and running for the new Exchange box. During the initial install review, I found out that Active Directory Connector is installed on my Exchange 2000 box and I need to uninstall it to continue. Some research has shown that this is used between Exchange 5.5 and Active Directory. I do not have 5.5 on the network (I am guessing that it was updated to Exchange 2000).

    Am I safe in uninstalling this service since I do not have a 5.5 box or am I at risk of royally messing things up?

  • #2
    Re: Exchange 2000 to 2007

    If you do not have any Exchange 5.5 servers then remove the connector. You will be unable to migrate until you do. It isn't used by any part of Exchange 200x.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Exchange 2000 to 2007

      Thanks Sembee!

      I realize that the ADC needs to be removed for 2007 to install. The deeper I get into this the larger the mess gets. Apparently the person before me wanted to update to Exchange 2003 and did a partial install on a different server. The ADC on my Exchange 2000 box is the 2003 version and I have reminants of the 2003 install floating about Active Directory. When I ran the best practices tool it listed two existing Exchange servers and I only have one. Some permissions were messed up on the mailbox and public folder entries, but I got those straightened out. I have mail services scheduled for down time this next week so hopefully things will start to go better.

      Thanks to everyone here for your help!

      Comment


      • #4
        Re: Exchange 2000 to 2007

        Today I installed Exchange 2007 on a 2008 server after getting the ADC and rogue server issues cleaned up. Using the best practices tool, I got everything ready and the actual install went fine (I used Henrik Walther's Transitioning from Exchange 2000/2003 tutorial) . My public folders replicated great but now I have a problem. After getting the server finalized, I moved two mailboxes over to the new server for testing. I can send email to them from an account on the 2000 server and from outside email. I cannot send email from those accounts, either to each other or an account on the other server. When I fire up OWA, my messages are dropped into the Drafts folder. If I use a client (Outlook 2002 or 2007) they just sit in the Outbox.

        My Exchange 2007 server has the CAS, Hub transport, and Mailbox roles on it. I can telnet from the 2000 server to the 2007 server without problem (a solution to another problem I read about here). I only have one domain and am using a Barracuda filter that sends email onto my Exchange 2000 server. The connector between the Exchange installs looks correct and the best practices analyzer does not bring up any red flags.

        Does anyone have any ideas?

        Comment


        • #5
          Re: Exchange 2000 to 2007

          Telnet means squat in this scenario, as your client doesn't use SMTP to send messages.
          What does the best practises tool say? Does that confirm that everything is setup correctly?

          Are all of the Exchange services started?

          It could be a bad installation - I operate on the simply practise that if the server doesn't work straight out of the box and it isn't a mistake on my part, then Exchange is removed using add/remove programs and the server is dropped in to workgroup and wiped. If something as basic as email delivery doesn't work then who is to know what else isn't working correctly, something I don't want to find out three weeks after going in to production. I prefer to spend a few more hours getting it to work before it is the production system.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment

          Working...
          X