Announcement

Collapse
No announcement yet.

User connecting to wrong server

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

  • User connecting to wrong server

    Hi guys,

    We're currently migrating from Exchange 2003 to 2010 ... a project I haven't been involved in thus far. Unfortunately I'm now involved as it's been dumped on me to sort out some problems ... and I am NOT up to speed on Exchange 2010 or what has and hasn't been done.

    We have a head-office and three regional offices.

    At each office is a Exchange 2003 server and a newly commissioned Exchange 2010 server.

    All users in the head office have now been migrated to the Exchange 2010 server, but the old 2003 at that location is still operational at this time. Outlook Anywhere is working.

    In one of our regional offices we've migrated five users to the new Exchange 2010 server. Three of the users have no complaints ... however they are laptop users and consequently they are running in Cached Mode. Two of the users are on desktops and therefore NOT running cached mode (and we don't want to run cached mode for desktop users) and they getting VERY slow performance.

    When we configured Outlook for the users in the regional office we noted that the server option points to the head office Exchange 2010 server (which is our CAS) ... and even if we change it it will reset to that entry.

    When I check Outlook's Connection Status for one of the two users who are complaining it shows connectivity to the head office Exch 2010 server for Directory and mail ... in other words it certainly LOOKS as if my user on one side of the country is talking to her mailbox (at the same location) via a server in the head office which is on the other side of the country.

    I not surprised that the regional user is connecting to the head office server for some things as I haven't gotten public folder replication working yet. I've found out where the previous guys went wrong, and should have that resolved in a few hours.

    Test E-mail Autoconfiguration on the users PC results in some stuff which confuses me further - I can post the result of that if necessary.

    So - the questions:

    How do I actually verify WHICH server this user is getting her email from. IF it's coming via our head office what should I look for as a probable cause for this?

    Can anyone point to some documentation which might be of help? All the microsoft documentation I've found is great IF you are doing the whole thing from scratch ... but not so helpful if you're jumping into the middle of something that's been mostly done.

  • #2
    Re: User connecting to wrong server

    is the exchange 2010 server in HEad Office the only Client Access Server ?
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: User connecting to wrong server

      Originally posted by tehcamel View Post
      is the exchange 2010 server in HEad Office the only Client Access Server ?
      Looking at Server Configuration > Client Access I see that all of the Exch 2010 servers are Hub Transport, Client Access and Mailbox.

      Outlook Anywhere is enabled only on the Head Office server.

      Comment


      • #4
        Re: User connecting to wrong server

        Have you configured a CAS array? If you haven't, I would recommend it even if you only have the one CAS box. If the CAS array was created after the mailboxes were migrated and the databases created within Exchange 2010, you will need to ensure that the database(s) are configured to point at the CAS array name as oppose to the CAS server name.

        Comment


        • #5
          Re: User connecting to wrong server

          Originally posted by Virtual View Post
          Have you configured a CAS array? If you haven't, I would recommend it even if you only have the one CAS box. If the CAS array was created after the mailboxes were migrated and the databases created within Exchange 2010, you will need to ensure that the database(s) are configured to point at the CAS array name as oppose to the CAS server name.
          Heh - I'm not adverse to setting up a CAS array if it will clarify things. I haven't even looked at exchange since I set up our 2003 servers, and I'm well and truly under the pump to get it sorted quickly.

          To be honest I'm finding the whole auto discovery a problem I'd love to just turn off so that I could get this resolved ASAP ... then I could set up a lab and install from scratch and get my head around everything at leisure.

          I can find docs on setting up an array, I'm sure ... but might I trouble you for a reference which tells me which databases to reconfigure and how? The only databases I've had a hand in on this deployment have been the public folder db's I created on each server today - and I prefer some guidance so I don't screw up 300 users worth of our head office DBs lol

          Comment


          • #6
            Re: User connecting to wrong server

            The first place I would be looking is AD sites and services.
            Exchange 2010 is AD site aware, and uses tha tinformation to decide which CAS role server the user should connect to. If AD Sites and Services hasn't been setup correctly then you will have problems.

            An RPC CAS array I consider mandatory, and you will need one for each AD Site. Unfortuantely retrofitting it client side is not automatic, so will need a visit to each desktop. The clients will continue working, and of course as workstation gets rebuilt, replaced, Windows profiel recreated etc they will start to use the new address. A lack of RPC CAS Array could bite you later on when you try to move users or have any kind of high availability solution.

            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


            • #7
              Re: User connecting to wrong server

              While I was researching setting up a CAS array I stumbled upon something which looked interesting.

              Specifically the RPCClientAccessServer property for each database.

              I did a check and found that all the mailbox databases which were created prior to my involvement in the task were configured with that property pointing to the CAS in our head office.

              From what I have read in the past week, Outlook 2010/Exchange 2010 are built on the premise that all communications will take place via the CAS. However given that all the Exchange 2010 servers have the Client Access role enabled ... logic suggests that they can communicate to Outlook.

              So I created a new Mailbox database on one of our regional office Exchange 2010 servers and dove into powershell and changed the property with the following:

              Set-MailboxDatabase testdatabase -RpcClientAccessServer servername

              I then created a new user account and mailbox. I must note that I rather foolishly got excited at this point and didn't point the mailbox to the new database ... so I had to move it over to the new mailbox database. Once I moved it, however, I was able to log in as that user and fire up Outlook ... I manually configured (which is necessary because we don't used cached mode for desktop users) and the results are very encouraging.

              I've checked Microsoft Exchange Connection Status and it shows all connections to the local server.

              Unless anyone tells me that what I've done is going to cause problems, I'll do a trial with a live user tomorrow.

              Comment


              • #8
                Re: User connecting to wrong server

                The mailbox databases would take on the name of 1 CAS server. If you had a CAS array configured prior to creating the mailbox store, it probably would use the CAS array name instead. Sounds to me you are along the right lines.

                Comment


                • #9
                  Re: User connecting to wrong server

                  If you are going to make the change, then I would suggest creating CAS Array addresses instead of using the actual server name.

                  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


                  • #10
                    Re: User connecting to wrong server

                    Time to bite the bullet.

                    I've created a CAS Array at each of our regional offices, and new Mailbox Databases on each of the regional servers, and have set RPCClientAccessServer for each of those databases to the appropriate array. DNS etc has been addressed appropriately so it all looks good.

                    I'll start moving a couple of test users into the new DB's and we'll see how it goes.

                    I don't anticipate any problems. I'll report back :P

                    This brings me to the next issue, however.

                    I have about 300 staff in the existing Mailbox database on the head office server. There is no CAS Array set up in that location at the moment.

                    I would like to continue this process and clean up the head office by creating a CAS array there. Of course I can't just change the RPCClientAccessServer property on the existing databases ... As Sembee noted this wouldn't update automatically at the client.

                    But I'm wondering ... if I moved all the users from a given database to a temporary DB, changed the RPCClientAccessServer setting for the original DB, and then moved them back - from what I've read that should result in Outlook being correctly configured. Can anyone confirm?

                    Comment


                    • #11
                      Re: User connecting to wrong server

                      Refer to point 5 at this article http://blogs.technet.com/b/exchange/...ct-part-2.aspx.

                      Your proposed solution will not work.

                      Depending on the number of users I would either write a handout for correcting the profile manualy or take one of the more centralized solutions.

                      Comment


                      • #12
                        Re: User connecting to wrong server

                        Set all of the databases on the server to use the same RPC CAS Array address. The clients will then update naturally over time. The only way you can get the clients to update automatically is to move servers.

                        However I suggest that you read this blog posting if you haven't already.

                        http://blogs.technet.com/b/exchange/...y-changes.aspx

                        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: User connecting to wrong server

                          Sorry to be slow responding ... I returned to my roots on the weekend and did some much needed network maintenance

                          It's a shame that switching the user back and forth across databases won't cut it.

                          I'll present my boss with the options ... push a PRF, or manually reconfigure.

                          Many thanks to everyone who assisted me in this - rough as it is to be handed the tail end of a deployment someone else screwed up ... it's good to know that there are people out there to get you pointed in the right direction.

                          Comment


                          • #14
                            Re: User connecting to wrong server

                            That's why this forum is here and thanks for posting back. Glad it is now resolved.

                            Comment

                            Working...
                            X