locked
User Migration - Exchange 2010 to Exchange 2010 RRS feed

  • Question

  • Our older Exchange 2010 server was running out of disk space so we purchased and installed a new server with Exchange 2010. I've moved all of the user mailboxes to the new server as well as the Public Folder DB and verified replication. I dismounted and removed the stores on the old server and also cleanly removed the Public Folder store on the old server. Everything seems to be functioning perfectly with one exception. All of the user's Outlook 2010 Mail Profiles are still pointing at the old server. As a test I changed my default Outlook Mail Profile to point to the new server and it is functioning well. How do I easily change all of the user's mail profiles to also point to the new server? As it stands now, with the user mail profiles still pointing at the old server, if I stop the Exchange Services on the old server, Outlook gets disconnected.

    Thanks.

    Wednesday, September 19, 2012 9:02 PM

All replies

  • Hi
       which server name does your outlook profile point to? If it point to exchange 2003,  Outlook will get disconnected.
       The easiest way is to remove email profile and connect to exchange by autodiscover.  You modify server name is also ok.
      

       TechNet Subscriber Supportin forum
      If you have any feedback on our support, please contact
    tnmff@microsoft.com   


    Terence Yu

    TechNet Community Support

    Thursday, September 20, 2012 2:25 AM
  • The Outlook Profile points to the old email server name. I would like to change them to point to the new email server name but I don't want to have to touch each client manually. Is there a way to automate the process? Thanks.
    Thursday, September 20, 2012 6:37 PM
  • Hi

    You either need to do a profile repair on each machine or deploy a PRF file using a GPO or script: http://www.howto-outlook.com/howto/deployprf.htm

    Cheers, Steve

    • Proposed as answer by Terence Yu Monday, September 24, 2012 1:51 AM
    Thursday, September 20, 2012 6:46 PM
  • You're running into this because you didn't create a cas array name, this is one of the reasons you want to create a cas array name even though you have a single server. You have to manually touch every profile or push a prf file gpo.

    6. A CAS array object should be configured even if you only have one CAS server or one multi-role server.
    Reflect for a moment about what was discussed in the prior item. A client will not update itself to use a CAS array object if you add one at a later time. Well what if you only have one CAS? You may think it doesn’t matter. I guess one could argue it doesn’t matter at that very moment, but why not future proof things if you can and save some cycles and frustration later? What if a year from now you find yourself in need of replacing that CAS? If you’re clients profiles are all pointing to a CAS name then you have no clean way to transition them without some kind of outage or manual work. You will have to repair their profiles with one of the means already mentioned after adding a new CAS, or you will have to decommission the existing CAS and introduce a new CAS with the same hostname which will require some downtime. To me none of those options are acceptable.

    The profile will not update itself because the client will not receive an ecWrongServer response from CAS. It will not receive this response because any CAS is a valid connection point for any mailbox database via RPC (over TCP) so clients can survive datacenter switchover/failover events without being reconfigured and all an admin has to do is flip the CAS array object DNS record to point to a surviving pool of CAS.

    Currently the only way to fix mailbox profiles would be a manual profile repair within Outlook, by publishing an Office PRF file via GPO (not going to work for non-domain joined machines), or by decommissioning the CAS server named in the users’ profiles so the endpoint is no longer available. This last option should (test test test!!) trigger a full profile repair by Autodiscover in Outlook 2007 or Outlook 2010. Outlook 2003 is only repairable with a profile repair or a PRF file.


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    • Proposed as answer by Terence Yu Monday, September 24, 2012 1:51 AM
    Thursday, September 20, 2012 6:48 PM
  • Hi
      Do you have anything update on your issue ?

    Terence Yu

    TechNet Community Support

    Monday, September 24, 2012 1:52 AM
  • Hi James

    Thank you very much for the info. This thread is the first I've heard about a "CAS Array". I'll take a look at creating one, as you suggest, to avoid this issue in the future. I appreciate you pointing me in the right direction.

    My reading leads me to believe that, as you say, I can decommission the old CAS Server to allow the clients to trigger an AutoDiscovery repair but I don't see how to test such a thing before taking that step. You said, "test, test, test" and I'm a believer but I'm not certain how to do so.

    Since I started this thread I have also updated my local DNS Servers and changed the "autodiscover.domain.name" record to point to the new server and changed MX records to point to the new server as well. I've also tested that new Outlook clients get pointed to the new Exchange Server so that seems to be working well.


    Anyway, thanks again for the info. I appreciate your time.

    Monday, September 24, 2012 10:49 PM