none
Changing DC used by Exchange 2010

    Question

  • Hello experts,

    We have only two DCs in our organization. OldDC.ourdomain.com and NewDC.ourdomain.com

    OldDC has Windows 2003 SP2. NewDC has Windows 2008 R2.

    NewDC is hosting Exchange 2010 roles (MB, CAS and HT).

    I want to dcpromo the OldDC. The problem is that Exchange2010 is referring to OldDC as it's domain controller, not referring to itself.

    Both DCs are global catalogs. I have moved the five FSMO roles to the new one. Both DCs are DNS servers also.

    The problem is that, in EMC, I see that (Domain controller servers being used by Exchange) and (Global catalog server being used by Exchange) are referring OldDC.ourdomain.com

    Also when I use: Set-ADServerSettings NewDC.ourdomain.com, the ADServerSettings change only until I exit and login again to the EMS.

    Now I want to dcpromo the OldDC, and I am afraid that Exchange may stop working if I do so. Now, when I try to shut down OldDC, exchange EMC and EMS never open.

    Thursday, June 09, 2011 11:28 AM

Answers

  • In EMC, Oranization Configuration and in the Action Pan you will see Configuration Domain Controller or something (Sorry My Labs are down)
    Click on it and make sure its not pointed to one specific dc. 
    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.blogspot.com
    • Marked as answer by Haythamk Sunday, June 12, 2011 3:12 AM
    Thursday, June 09, 2011 12:31 PM
  • You can also use cmdlet "set-exchangeserver" to force exchange 2010 to use new DC only, but its later we can do. Try to see below post and follow james suggestion. Also try to enable TCP/IP V6 in new DC if not done it.

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/f519fc3b-a562-421f-bd6d-6a17544960fe/

    Set-ExchangeServer cmdlet Detail:

    http://msdn.microsoft.com/en-us/library/bb123716.aspx


    Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2011, My Blog : http://messagingschool.wordpress.com
    • Marked as answer by Haythamk Sunday, June 12, 2011 3:11 AM
    Friday, June 10, 2011 1:21 PM
  • Set-ExchangeServer cmdlet you already did manually from EMC, remember!

    Yes Set them and post the result.

    But reboot the new DC once before you do it. Cause its showing NewDC.ourdomain.com CDG 1 0 0 1 0 0 0 0 0. And its not good.


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    • Edited by Gulab Prasad Friday, June 10, 2011 6:24 PM Update
    • Marked as answer by Haythamk Sunday, June 12, 2011 3:10 AM
    Friday, June 10, 2011 6:22 PM

All replies

  • No it won't stop.
    You can do one thing, shut down the old DC and check the status of Exchange Server and i am sure it will be fine.
    Check the event id 2080 in application log on Exchange Server.

    You have followed the correct procedure. Just need to make sure that Exchange is not hard coded to the Old Domain Controller.

    Cheers, 


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.blogspot.com
    Thursday, June 09, 2011 11:35 AM
  • Exchage is stopping each time I reboot OldDC untill it completes booting.
    Thursday, June 09, 2011 11:44 AM
  • make sure that Exchange is not hard coded to the Old Domain Controller.
    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.blogspot.com
    Thursday, June 09, 2011 12:03 PM
  • Sorry, I didn't understand it. What is (Hard Coded) ?
    Thursday, June 09, 2011 12:04 PM
  • In EMC, Oranization Configuration and in the Action Pan you will see Configuration Domain Controller or something (Sorry My Labs are down)
    Click on it and make sure its not pointed to one specific dc. 
    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.blogspot.com
    • Marked as answer by Haythamk Sunday, June 12, 2011 3:12 AM
    Thursday, June 09, 2011 12:31 PM
  • Sorry for the delay.

    I have checked in EMC for (Modify configuration Domain Controller), it was set to (Use a default domain contorller). I have changed it to NewDC, restarted the server, then it's still configured to use NewDC, but still (Domain controller servers being used by Exchange) is referring OldDC

    Friday, June 10, 2011 12:13 PM
  • Post the event id 2080 from application log.
    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Friday, June 10, 2011 12:55 PM
  • You can also use cmdlet "set-exchangeserver" to force exchange 2010 to use new DC only, but its later we can do. Try to see below post and follow james suggestion. Also try to enable TCP/IP V6 in new DC if not done it.

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/f519fc3b-a562-421f-bd6d-6a17544960fe/

    Set-ExchangeServer cmdlet Detail:

    http://msdn.microsoft.com/en-us/library/bb123716.aspx


    Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2011, My Blog : http://messagingschool.wordpress.com
    • Marked as answer by Haythamk Sunday, June 12, 2011 3:11 AM
    Friday, June 10, 2011 1:21 PM
  • You can also use cmdlet "set-exchangeserver" to force exchange 2010 to use new DC only, but its later we can do. Try to see below post and follow james suggestion. Also try to enable TCP/IP V6 in new DC if not done it.

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/f519fc3b-a562-421f-bd6d-6a17544960fe/

    Set-ExchangeServer cmdlet Detail:

    http://msdn.microsoft.com/en-us/library/bb123716.aspx


    Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2011, My Blog : http://messagingschool.wordpress.com

    @ Anil, he already did that but it didn't worked.
    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Friday, June 10, 2011 1:35 PM
  • Upps !!! I missed the section.
    Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2011, My Blog : http://messagingschool.wordpress.com
    Friday, June 10, 2011 1:42 PM
  • Log Name:      Application
    Source:        MSExchange ADAccess
    Date:          6/10/2011 8:37:30 PM
    Event ID:      2080
    Task Category: Topology
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      NewDC.ourdomain.com
    Description:
    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1776). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
     (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
    In-site:
    OldDC.ourdomain.com CDG 1 7 7 1 0 1 1 7 1
    NewDC.ourdomain.com CDG 1 0 0 1 0 0 0 0 0
     Out-of-site:
     
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ADAccess" />
        <EventID Qualifiers="16388">2080</EventID>
        <Level>4</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-10T17:37:30.000000000Z" />
        <EventRecordID>58033</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>MSEXCHANGEADTOPOLOGYSERVICE.EXE</Data>
        <Data>1776</Data>
        <Data>OldDC.ourdomain.com CDG 1 7 7 1 0 1 1 7 1
    NewDC.ourdomain.com CDG 1 0 0 1 0 0 0 0 0
    </Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    Friday, June 10, 2011 5:54 PM
  • @Gulab: I didn't use Set-ExchangeServer cmdlet yet, I have used SetADServerSettings only.

    Now when I tried Get-ExchangeServer :fl, I received:

    StaticDomainControllers: {}

    StaticGlobalCatalogs: {}

    OriginatingServer: OldDC.ourdomain.com

    Shall I set them ?

    Friday, June 10, 2011 6:02 PM
  • Set-ExchangeServer cmdlet you already did manually from EMC, remember!

    Yes Set them and post the result.

    But reboot the new DC once before you do it. Cause its showing NewDC.ourdomain.com CDG 1 0 0 1 0 0 0 0 0. And its not good.


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    • Edited by Gulab Prasad Friday, June 10, 2011 6:24 PM Update
    • Marked as answer by Haythamk Sunday, June 12, 2011 3:10 AM
    Friday, June 10, 2011 6:22 PM
  • After rebooting NewDC:

    Log Name:      Application
    Source:        MSExchange ADAccess
    Date:          6/11/2011 9:43:01 AM
    Event ID:      2080
    Task Category: Topology
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      NewDC.ourdomain.com
    Description:
    Process MAD.EXE (PID=2752). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
     (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
    In-site:
    OldDC.ourdomain.com CDG 1 7 7 1 0 1 1 7 1
    NewDC.ourdomain.com CDG 1 0 0 1 0 0 0 0 0
     Out-of-site:
     
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ADAccess" />
        <EventID Qualifiers="16388">2080</EventID>
        <Level>4</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-11T06:43:01.000000000Z" />
        <EventRecordID>60086</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>MAD.EXE</Data>
        <Data>2752</Data>
        <Data>OldDC.ourdomain.com CDG 1 7 7 1 0 1 1 7 1
    NewDC.ourdomain.com CDG 1 0 0 1 0 0 0 0 0
    </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    I rebooted the server after using this:

    SetExchangeServer -StaticDomainControllers "NewDC.ourdomain.com"

    SetExchangeServer -StaticGlobalCatalogs "NewDC.ourdomain.com"

    Now Exchange EMC and EMS no longer able to connect !

    There are lot of errors in ApplicationLog:

    Log Name:      Application
    Source:        MSExchange ADAccess
    Date:          6/11/2011 10:43:24 AM
    Event ID:      2114
    Task Category: Topology
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NewDC.ourdomain.com
    Description:
    Process STORE.EXE (PID=4652). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ADAccess" />
        <EventID Qualifiers="49156">2114</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-11T07:43:24.000000000Z" />
        <EventRecordID>60626</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>STORE.EXE</Data>
        <Data>4652</Data>
        <Data>80040a02</Data>
        <Data>DSC_E_NO_SUITABLE_CDC</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSExchange ADAccess
    Date:          6/11/2011 10:43:24 AM
    Event ID:      2102
    Task Category: Topology
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NewDC.ourdomain.com
    Description:
    Process STORE.EXE (PID=4652). All Domain Controller Servers in use are not responding:
    NewDC.ourdomain.com
     
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ADAccess" />
        <EventID Qualifiers="49156">2102</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-11T07:43:24.000000000Z" />
        <EventRecordID>60624</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>STORE.EXE</Data>
        <Data>4652</Data>
        <Data>NewDC.ourdomain.com
    </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSExchangeIS
    Date:          6/11/2011 10:43:17 AM
    Event ID:      5000
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NewDC.ourdomain.com
    Description:
    Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeIS" />
        <EventID Qualifiers="49158">5000</EventID>
        <Level>2</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-11T07:43:17.000000000Z" />
        <EventRecordID>60620</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>0x96f</Data>
        <Binary>5B444941475F4354585D000086000000FF1810000000000000007800000093642010000000009344201000000000937C201000000000935C201000000000936C201000000000934C201000000000E54C201000000000E564201000000000035920100000000072204010010A0480E83540106F090000483040106F090000483440106F090000534D201000000000282B40106F090000</Binary>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSExchangeIS
    Date:          6/11/2011 10:43:17 AM
    Event ID:      1121
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NewDC.ourdomain.com
    Description:
    Error 0x96f connecting to Active Directory.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeIS" />
        <EventID Qualifiers="49158">1121</EventID>
        <Level>2</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-11T07:43:17.000000000Z" />
        <EventRecordID>60619</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0x96f</Data>
        <Binary>5B444941475F4354585D000086000000FF1810000000000000007800000093642010000000009344201000000000937C201000000000935C201000000000936C201000000000934C201000000000E54C201000000000E564201000000000035920100000000072204010010A0480E83540106F090000483040106F090000483440106F090000534D201000000000282B40106F090000</Binary>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          6/11/2011 10:42:42 AM
    Event ID:      2155
    Task Category: Service
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NewDC.ourdomain.com
    Description:
    The Third Party Replication Manager could not access Active Directory. Error: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.. Initialization will be retried automatically.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeRepl" />
        <EventID Qualifiers="49156">2155</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-11T07:42:42.000000000Z" />
        <EventRecordID>60615</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.</Data>
      </EventData>
    </Event>


    • Edited by Haythamk Saturday, June 11, 2011 8:08 AM
    Saturday, June 11, 2011 7:47 AM
  • Is it possible to change back to the old setting now because Exchange is down now and no user is able to use it ??
    Saturday, June 11, 2011 8:02 AM
  • Any help please?
    Saturday, June 11, 2011 4:23 PM
  • hi,

    check here ;

    http://social.technet.microsoft.com/Forums/en/exchange2010/thread/dc37ce70-cd93-4321-b92a-90355fc95f71

    regards,

     


    Mumin CICEK | www.cozumpark.com | Please click Vote As Helpful if it is helpful for you and Propose as Answer!!!
    Saturday, June 11, 2011 7:49 PM
  • Fortunately the startup problem was solved by enabling IPv6 on NewDC, it was disabled before. That changed NewDC.ourdomain.com CDG 1 0 0 1 0 0 0 0 0.

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange ADAccess" />
        <EventID Qualifiers="16388">2080</EventID>
        <Level>4</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-12T02:31:20.000000000Z" />
        <EventRecordID>73870</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NewDC.ourdomain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>MSEXCHANGEADTOPOLOGYSERVICE.EXE</Data>
        <Data>1804</Data>
        <Data>NewDC.ourdomain.com CDG 1 6 7 1 0 1 1 7 1
    </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

     I don't know why Exchange 2010 requires it while it's not used in the organization. Now, Exchange is using NewDC as it's DC and GC. There was a series of errors in application log indicating that at the beginning of startup exchange was unable to find any DC nor GC. Also there are still many errors appearing periodically in the log, I will post a new thread for them.

     

    Sunday, June 12, 2011 3:10 AM
  • Hello Haythamk,

    First of all congratulation for the resolution.

    Sorry that it didn't struck be earlier regarding IPv6 :(

    About IPv6 Enabling worked on this issue. I have seen this situation many time (I still can't stop cursing my self why it didn't struck earlier to me).
    In this kind of situation, sometime Windows Server 2008 running as domain controller requires IPv6 enabled.

    One scenario more is when you are running Exchange 2010 on Domain Controller in that situation also you need to Enable the IPv6 or some of the services like AD Topology, SA doesn't start.

    Cheers,


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Sunday, June 12, 2011 4:42 AM
  • Thank you for all your responses. I will continue getting knowledge from you in other posts :)
    Sunday, June 12, 2011 11:05 AM