none
Adding second exchange server to domain RRS feed

  • Question

  • Hi Folks, My situation is as follows.

    - i have an existing 2007 exchange server running SP2 running on server 2003 R2. it has the CAS, HUB, MB roles

    - i want to migrate to exchange 2013

    - whenever i try to update my 2k7 server to SP3 so i can run in coexistence mode, something breaks and the only way for me to get the server functioning properly again is to uninstall the update

    - so. now I want to add a fully patched 2008 R2 server running fully patched exchange 2k7 SP3 to my domain to run with the first exchange 2k7 server.

    My questions are.

    1. can i add my second fully patched 2k7 server into the organization running the same CAS, HUB, MB roles without causing any grief?

    2. can i move maiboxes to the new exchange server even though it will be running a higher SP and different OS than the first?

    3. when i have moved all the mailboxes to the new server, what do i need to do to decommission the first server and have all my users running from the new 2k7 server without having to reconfigure outlook (is it as simple as just pointing the DNS for the old sever to the new one)?

    4. is there a way to transfer the config for owa, outlook anywhere, virtual directories to the new server when im ready to take the first one down, or does adding the new one to the organization pick up all those configs for me?

    i appreciate any insight


    Colin Stewart

    Thursday, October 23, 2014 2:55 PM

Answers

  • Hi Colin,

    I'll try to answer your questions in order but if you have doubts or I forget anything please let us know,

    1 - Yes absolutely without any issues, once you've installed the server you'll want to configure it with specular settings as the "old" server (same certificates, same OWA settings etc.)

    2 - Not a problem at all, once the new server is up and running you can just move mailboxes across SP and OS are not an inssue in this scenario.

    3 - When you move a mailbox to the new Exchange server Exchange itself will udpate AD attributes so internal users will be connecting to the new server straight away, of course if you're using OWA or Outlook anywhere you will need to update your external DNS records/Firewall rules accordingly.

    4 - OWA wise apart form the certificate I cannot really think of anything that needs to be moved among the servers, unless you have a very customized setup that's it.

    Something you will want to do when the new server has been deployed is configure Send and Receive connectors so that the new server can correctly send and receive emails.

    I think this is pretty much it, should you need further details or any other information just ask.

    Hope this will help-

    Thursday, October 23, 2014 7:42 PM
  • Hi,

    For Exchange certificate, just make sure the certificate which is assigned with IIS service has included all namespaces used for Exchange internal and External URLs.

    Therefore, if your original certificate is still valid and not expired, you can just export the certificate from the old Exchange 2007, import it in your new Exchange 2007 and assign IIS service. Please change the DNS record for exchange.domain.com to point to your new Exchange 2007 and published external. Alternatively, you can use the new wildcard certificate for new server.

    For mobile users, they are using Exchange ActiveSync instead of Outlook Anywhere for mailbox accessing. Please make sure the ActiveSync virtual directory is configured properly in your new server. Then after you move all mailbox to the new server, the mobile users would connect to new server.

    Regards,


    Winnie Liang
    TechNet Community Support

    Sunday, October 26, 2014 9:06 AM
    Moderator

All replies

  • Hi Colin,

    I'll try to answer your questions in order but if you have doubts or I forget anything please let us know,

    1 - Yes absolutely without any issues, once you've installed the server you'll want to configure it with specular settings as the "old" server (same certificates, same OWA settings etc.)

    2 - Not a problem at all, once the new server is up and running you can just move mailboxes across SP and OS are not an inssue in this scenario.

    3 - When you move a mailbox to the new Exchange server Exchange itself will udpate AD attributes so internal users will be connecting to the new server straight away, of course if you're using OWA or Outlook anywhere you will need to update your external DNS records/Firewall rules accordingly.

    4 - OWA wise apart form the certificate I cannot really think of anything that needs to be moved among the servers, unless you have a very customized setup that's it.

    Something you will want to do when the new server has been deployed is configure Send and Receive connectors so that the new server can correctly send and receive emails.

    I think this is pretty much it, should you need further details or any other information just ask.

    Hope this will help-

    Thursday, October 23, 2014 7:42 PM
  • HeloCheck, 

    Thank you very much for your reply. A couple more questions.

    1.  Given your answer to #1 above, i have a new wildcard certificate for our email domain that i would like to use on the new server, if i do, will it cause issues? the cert on the current server is exchange.domain.com. Or would it be a better idea just to use the same one and then use the new one when i'm ready to go to 2013?

    2.  Given your answer to #3 above, does it make sense to move all of my mobile users that rely on outlook anywhere last and at the same time or will the old server act as a proxy (i think i read that somewhere) and still connect mobile users to their mailboxes on the new server until i take it down, at which point i can change my DNS/NAT rules?

    Again, thanks for your insight.


    Colin Stewart

    Thursday, October 23, 2014 8:17 PM
  • Hi,

    For Exchange certificate, just make sure the certificate which is assigned with IIS service has included all namespaces used for Exchange internal and External URLs.

    Therefore, if your original certificate is still valid and not expired, you can just export the certificate from the old Exchange 2007, import it in your new Exchange 2007 and assign IIS service. Please change the DNS record for exchange.domain.com to point to your new Exchange 2007 and published external. Alternatively, you can use the new wildcard certificate for new server.

    For mobile users, they are using Exchange ActiveSync instead of Outlook Anywhere for mailbox accessing. Please make sure the ActiveSync virtual directory is configured properly in your new server. Then after you move all mailbox to the new server, the mobile users would connect to new server.

    Regards,


    Winnie Liang
    TechNet Community Support

    Sunday, October 26, 2014 9:06 AM
    Moderator