Share via

Adding secondary exchange server

ron hofstede 1 Reputation point
2021-08-29T22:03:06.387+00:00

Hi all,

I'm having difficulties with adding a secondary Exchange 2013 server and removing the first Exchange 2013 server.

I did install a secondary Exchange server on a member server (in the same domain, all running Windows Server 2012 R2). Moved all the mailboxes, adjusted the connectors etc.
Everything went fine. No problem with that.

However when I shut down the first Exchange server, Outlook clients can't connect to the new Exchange server.
The strange part is also, that I stopped all the Exchange services and IIS and World wide web service also on the old server.
Still no problems with connecting Outlook to the new server (as long as the old Exchange server keeps running).

But when I shut down the first Exchange server (or stop the netlogon service), Outlook clients can't connect to the new Exchange server. The first Exchange server is running on a Domain Controller and the secondary on a member server.

I do have another Domain Controller running and in my test lab, both the first and secondary Exchange servers are Domain Controllers with DNS.

Any help would be welcome :-)

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,503 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yuki Sun-MSFT 41,016 Reputation points
    2021-08-30T06:42:16.407+00:00

    Hi @ron hofstede ，

    However when I shut down the first Exchange server, Outlook clients can't connect to the new Exchange server.

    What's the exact symptom or if there's any error message in Outlook clients when this occurs?
    Any potentically relavent events recorded in the Event Viewer on the new Exchange server?

    Besides, considering that the first Exchange server is running on a Domain Controller, please run the command below to verify the fsmo roles have being migrated to the correct DC: 

    netdom query fsmo

    127496-1.png

    Then run the following command and confirm it shows the correct DC as well: 

    Get-ADServerSettings | fl

    By the way, although it works to have Exchange server installed on a domain controller, this is officially not recommended. So it's suggested that you install Exchange on a member server, especially if it's a production environment. For more information, see Installing Exchange on a domain controller is not recommended.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Helpdesk Helpdesk 1 Reputation point
    2021-09-09T15:21:28.567+00:00

    Hi @Yuki Sun-MSFT

    Sorry for the late response (I forgot to adjust the settings when receiving answers).

    The life environment (at the customer site) is:

    First primary Exchange server "SRV01" is indeed a Domain Controller
    The second newly installed Exchange server "SRV02" is a member server without Active Directory.
    I did move all the mailboxes to the secondary Exchange server

    Shutting dowen the first Exchange server does result in that Outlook clients can not connect anymore to their Excange "home server SRV02". Although webmail and synchronizing phones from the outside isn't a problem with the new server.

    In my test lab, both servers are Domain controllers.

    I will check your answer and run the commands.

    Kind regards,
    Ron

    0 comments