Announcement

Collapse
No announcement yet.

Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Server

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

  • Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Server

    I plan to carry out the transition of an Exchange 2003 organisation to Exchange 2007 64 bit tomorrow. I have one Exchange 2003 server and will end up with one 64 bit Exchange 2007 server on a 64 bit Windows 2003 Standard R2 with the Exchange 2003 uninstalled.

    A few questions, at what stage during the transition will Outlook clients be unable to connect to their mailboxes, if at any?

    How will the existing Outlook Clients, 2003 and 2007, know the new name of the server. Will manual mapping be required?

    I assume that I will need to change the shortcuts of OWA users manually or through Group Policy?

    Thanks in advance.

  • #2
    Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

    Outlook clients will have problems while you are moving their mailboxes between the servers. I usually find it best to do this during the evening unless it is a small amount and then lunch time.
    AD keeps a note of a property called HomeMDB which is the name of the mailbox server the users mailbox is located on. When you move a mailbox this gets updated so when Outlook next tries to connect it detects this and automatically connects to the correct server.

    OWA users should, once moved, connect to newexchange/owa not /exchange. Depending on what these shortcuts are depends on what you need to change. Make sure externally your inbound https points to the new server.

    There are quite a few things involved as part of a 2003/2007 migration, what background info do you have? MsExchange.org has some good steps including upgrading address lists etc. Do you have the info to hand?
    Personally I would not decommission the 2003 tomorrow (today?) but leave it for a few days. You need to make sure things are working correctly before you try.
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

    Comment


    • #3
      Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

      The redirection of the clients to the new server ONLY occurs if both the old and the new server are alive. Therefore you should not even consider removing the Exchange 2003 server until you are sure that all clients have connected at least once so that Outlook is redirected.

      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


      • #4
        Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

        Thanks both for your comments.

        I am carrying out the first part of the upgrade tonight. I have used the Technet Virtual training for this first stage.

        Just a couple more questions before I do it.

        (1) I am carrying out upgrade in accordance with msexchange.org articles.

        http://www.msexchange.org/tutorials/...007-Part1.html

        When I was using the swtich to prepare the w2k3 domain, Setup.com /PrepareAD from the only 64bit W2k3 R2 server in the domain, the Exchange seems to start an unattended install. I stopped it. Is this supposed to happen? Do I need to run this or does the Exchange Install disk do this automatically?

        (2) Once Exchange 2007 is installed in accordance with the article above, can I start to move mailboxes straight away? I was going to carry out a test move on a few test mailboxes. I assume that once this move has taken place, the Client machines Outook profiles will automatically map to the new Exchange 2007 server, so therefore, say the Exchange 2003 server was turned off, they would still access email.

        (3) Referring to 2, i asume that remaining tasks left after having moved mailboxes is to replicate the Public folder to the new box. We don't use the Public folder so is this required? And of course set our Firewall rule to redirect SMTP traffic to the new server. Then decommission the Exchange 2003 server in accordance with msexchange.org article Part 3.

        (4) When Exchange 2003 and 2007 are alongside each other, I assume that all external internet emails will flow through the existing w2k3 Exchange server and then be forwarded to the Exchange w2k7 server.

        Any horror scenarios will also be appreciated.

        Thanks in advance.
        Last edited by Virtual; 15th August 2008, 12:22.

        Comment


        • #5
          Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

          I don't know why those instructions state to prepare the domain manually. That simply isn't required unless you are in a multiple domain scenario. In most cases I just run setup.exe from the Exchange 2007 SP1 download (SP1 DVD) and then let setup do the rest. It will prep the domain and install Exchange for me. I just sit back and watch.

          I would not recommend moving mailboxes straight away. If you are using Outlook 2003 anywhere then you need to replicate the public and system folders to the new server first, before any mailboxes. You are using public folders whether you want to or not, as public folders (and system folders which are stored in the public folder store) are used by Outlook to store data. You can only drop public folders if you are exclusively on Outlook 2007.

          When you do come to move mailboxes, the first mailbox you move is your own. If you don't have confidence to move your own mailbox then why inflict it on anyone else.

          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


          • #6
            Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

            Thanks Sembee. Great, sounds straight forward. I have done extensive research on this and this is the first time that I have re-assurance that it is actually quite straight forward.

            How do I replicate the System Folders and Public Folders from w2k3 Exchange to W2k7?

            Am I right in saying that say I have an Outlook 2003 client mapped to my Mailbox and I move my mailbox to the new server, my Outlook client the next time I use it will have the new Server name rather than the old, of course after initial connection to the old server?

            Say I also have other mailboxes attached to mine that I have permission to access but the mailboxes are on the old server, will these still map ok to the old server?

            I will be testing these scenarios before moving most of the mailboxes (which will be on a Friday night, so I always have the entire weekend to put it right if need be) but thought I would ask before doing so.

            Thanks.

            Comment


            • #7
              Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

              To replicate the public and system folders you simply right lick on the folders in ESM and choose the replica tab and add the new server to the list. Then wait. If you are not sure which folders to replicate then I suggest you look at Technet, particularly the sections about decommissioning the legacy Exchange servers. That will tell you what to replicate across.

              Permissions to the mailboxes do not matter. You do not need to have access to the mailbox to move it, as you are not accessing the content. As long as you use an account with the relevant permissions to Exchange you can move accounts around quite happily. As long as both the old and the new server are alive when the users first connect then Outlook will redirect.

              Mailbox move and the swing migration is completely risk free. There is never a point where you cannot back out. That is why it is the only method I will do. You don't have to big bang or ruin your weekend. Move the mailboxes during the evening. Remember the process is multithreaded but throttles itself. You can select as many mailboxes as you like, it will only move four at a time, and will tell you which ones fail. I have gone shopping in the past while leaving the mailboxes to move.

              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


              • #8
                Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                Thanks Simon once again. Will be carrying this out tomorrow and then gradually moving mailboxes during the week. Will update this during the transition.

                Comment


                • #9
                  Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                  Now I have Exchange 2007 up and running. I have gone to Exchange 2003 System manager and requested to Move all Replicas to the w2k7 Exchange server. However, Public Folder instances are showing after a few hours.

                  I have read an article stating that they had the same problem and found it to be the fact that SSL was not configured for SMTP on the Exchange 2007 server.

                  Comments would be appreciated.

                  Comment


                  • #10
                    Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                    Public folder replication is very slow.
                    If you have only waited a few hours, you haven't waited long enough. If nothing is happening after a few days then you have a problem.
                    While you can force the data across, it will flog your bandwidth and there is no guarantee that everything will go across.

                    I am not sure what you are referring to about SSL, as Exchange doesn't use SSL for inter-server traffic. Do ensure that you do not have anonymous disabled on the SMTP virtual server and you do not have a smart host set either.

                    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


                    • #11
                      Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                      I am starting to trouleshoot the Public folder issue. I have noticed that the Exchange 2007 Public Folder Store does have replicas of the Public Folder stores that are on Exchange 2003.

                      I also looked at the queue viewer in Exchange 2007. Three queues are present. One is Submission with no objects. THe other is 'servername.domain.local', which seems to come and go all of the time and the other a long reference to the Routing Group location in AD, delivery type RelayToTiRg, status is retry and the last error is reported as:

                      451.4.4.0 primary target ip address responded with ".". attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

                      424 messages are in the queue. It is full of Public Folder messages.

                      From '[email protected]'our registered domain name'. The recipient is down to be the 'Exchange2k3[email protected] registered domain name'

                      Status of all the messages are set to retry and the number of messages are increasing.

                      I also noticed that running the Get-RoutingGroupConnector command in Powershell does not bring anything up. The command you can use for Moving Public folders from the Exchange 2003 to 2007 box also does not function. You just get another PS> after atempting to run it from the scripts location.

                      This makes me think there is something up with the Routing Group Connector.

                      Thanks in advance.
                      Last edited by Virtual; 18th August 2008, 21:18.

                      Comment


                      • #12
                        Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                        Before you pull the routing apart, check the servers can actually see each other. Telnet to port 25 of the other server and ensure that it is Exchange that is answering. Have you made any changes to receive connector configuration on the Exchange 2007 server?

                        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


                        • #13
                          Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                          Thanks for the reply Simon.

                          I ran from the Command prompt: Telnet Nameof2k3Server 25.

                          Telnet states: Connecting to 'name of 2k3 server'...could not open connection to the host, on port 25: Connection Failed'.

                          I suppose i had better start to looking in to the reasons why I can't connect from the Exchange 07 server.

                          The same occurs from a Client machine so I am assuming it must be a setting on the Exchange 2003 server. The only thing I have changed on the receive connector is allowing anonymous access in preparation for routing external email through the Exchange 07 server when all Public folders, mailboxes and OAB have been moved. etc etc.

                          The 2k3 box is still the server used for all incoing email and is routing fine. No users have reported problems either.

                          Further suggestions would be appreciated.
                          Last edited by Virtual; 19th August 2008, 11:28.

                          Comment


                          • #14
                            Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                            If you can't telnet to port 25 then something is blocking it. AV software for example. I would also check that they are listening on port 25 and not some custom port setting.

                            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


                            • #15
                              Re: Exchange 2003 Transition to Exchange 2007 - Outlook Client auto mapping to new Se

                              Thanks for the post.

                              Have checked the antivirus software and found that it was blocking Port 25 for anything suspected as being a Mass Mailer Worm. All the messages have now been cleared down and the queue has disappeared. However, the Telnet still doesn't allow a connection. Could that be why the Public Folders haven't moved? They are certainly replicated to the 07 server.

                              Also, the Powershell commands to Routing Connector in 07 does not function. Another concern of mine.

                              Comment

                              Working...
                              X