Announcement

Collapse
No announcement yet.

Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

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

  • Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

    What should be the course of action? Does one need to take something special into consideration, regarding the Exchange part? Or is it just simply joining the 2008 R2 DCs to the domain, and then demoting the 2003 ones, like one does normally when doing this type of upgrade?

    Does the Exchange server have SRV records in DNS?

  • #2
    Re: Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

    Exchange doesn't care about the domain controllers.
    The DNS records should be AD integrated, so will be replicated.
    The only bit that could cause problems is when you start to remove the old servers. Therefore what you should probably do is move the FSMO roles and then make the new servers global catalogs.
    On the old servers, remove the GC role and restart the Exchange services. Exchange should then detect the new servers and start using them.

    You can then DCPROMO the old servers out.

    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


    • #3
      Re: Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

      Thanks for the feedback. I have actually performed this upgrade, and now I'm struggling with the Exchange Server loosing connection with the DCs and GCs sporadically. Restarting the Exchange Server resolves the problem. But after a while the problem recurs.

      I get the following error messages in Event Viewer on the application log of the Exchange Server

      Process STORE.EXE (PID=6772). All Global Catalog Servers in forest DC=xx,DC=xx are not responding:
      DC001.xx.xx
      DC002.xx.xx


      Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1348 ). All Global Catalog Servers in forest DC=xx,DC=xx are not responding:
      DC001.xx.xx
      DC002.xx.xx


      Process MAD.EXE (PID=5500). All Global Catalog Servers in forest DC=xx,DC=xx are not responding:
      DC001.xx.xx
      DC002.xx.xx


      I get the following error when the processes loose connection with the DCs/GCs, The Microsoft Exchange Information Store service terminated with service-specific error %%-2147467259.

      These messages started to appear after I demoted the old 2003 DCs. The course of action was simple, run adprep, promote 2008 R2 servers to DC/DNS servers, move all FSMO roles to DC001, demote the old 2003 DCs as DC/DNS servers. Remove the 2003 DCs from the domain.

      Everything else is working fine. Exchange is the only service that is causing problems.There is only one site, but two different subnets, at two different locations. No subnets have been defined in AD sites and services, as there is only one site (Default-First-Site). I have checked with Nltest and the Exchange server, the DCs and clients all belong to the same site.

      I have run Get-Exchangeserver -status | fl on the Exchange server, and there are no statically defined GCs. And the GCs and DCs reported as current are correct (the new Server 2008 R2 ones).

      Event 2080 gives the following output when everything is working fine

      Process MAD.EXE (PID=5556). 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:
      DC001.xx.xx CDG 1 7 7 1 0 1 1 7 1
      DC002.xx.xx CDG 1 7 7 1 0 1 1 7 1
      Out-of-site:


      Process MSEXCHANGEADTOPOLOGYSERVICE.EXE and Process STORE.EXE gives the same output.

      Do you know what could be causing this?
      Last edited by Balthier; 4th September 2013, 09:39.

      Comment


      • #4
        Re: Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

        Has Exchange been through a complete restart since the domain controller was demoted? I would also suggest defining a subnet in AD Sites and Services. If you have two subnets, then make sure both are listed.

        Check that all servers involved have the latest network card drivers.

        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


        • #5
          Re: Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

          Thanks, I have defined the subnets, and will see how it goes. But I have another strange problem. I have an AD-Integrated primary DNS zone, which is called webmail. FQDN, and it contains just a cname record pointing to the exchange server. It works fine resolving webmail.FQDN to the ip of the exchange server, and the Name servers on the name server tab are the two new DCs.

          But the SOA record has one of the old DCs defined as the primary server. If I try to change the SOA record, I get the following error Message

          "The SOA record cannot be updated. Node is a CNAME DNS record."

          TTL for the SOA record is 1 hour. I've tried to do the following

          1. Add a random host record to the zone, and then remove the record. This will increment the Serial Number, but the primary server in SOA stays the same.

          2. Tried to just increment the serial number, but then I receive the same error message as when trying to manually change the SOA record.

          3. Tried to make the zone a regular (non AD integraged) zone, but still I am not able to change the SOA record.

          Any suggestions on resolving this problem, or is the only solution to delete the zone and recreate it?

          Comment


          • #6
            Re: Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

            I wouldn't have put a CNAME in the zone. It would have been an A record pointing to the actual IP address of the server. What is the big deal about recreating the zone? Takes all of thirty seconds.

            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: Upgrading DCs from 2003 to 2008 R2 with Exchange 2010 in the domain

              Creating subnet objects did not resolve the Exchange issue. Further troubleshooting revealed that a colleague had raised the domain functional level to 2008R2 the same day the Exchange server started to loose connection with the Global Catalogs. The DCs had not been restarted since that date. So I performed the following actions to solve the problem

              - Raise the FFL to Server 2008 R2
              - Performed Replication between the DCs
              - Checked if replication was succesful with repadmin
              - Restarted DC02, then 15 minutes later, restarted DC01
              - Performed replication between the DCs again, and checked if replication was sucessful

              The Exchange server has not caused any problems ever since. I guess the course of action when migrating from 2003 DCs to 2008R2 DCs with Exchange 2010 in the environment should be following

              1. Check logs, run Dcdiag.exe, repadmin, Dnslint etc. to verify if the condition of 2003 DCs are fine
              2. Run Adprep
              3. Install 2008R2 machines as member servers
              4. Promote them to DCs/GCs and move FSMO roles to 2008R2 servers
              5. Remove 2003 servers as GCs
              6. Perform replication between all DCs, and verify if the replication was successful
              6. Demote 2003 DCs, repurpose or remove them completely from the network

              Then run through the steps I mentioned above, with obviously raising the DFL first.

              Comment

              Working...
              X