Announcement

Collapse
No announcement yet.

Exchange 2007 SP 1 and Windows 2008 R2 DCs

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

  • Exchange 2007 SP 1 and Windows 2008 R2 DCs

    Hi,

    Might be a bit long, so sorry in advance

    Background:

    I'm in the middle of a project replacing our old 2003 DCs with 2008 R2. I currently have both sets running (2 of each), and have transferred all services off the old DCs including fsmo roles. The old 2003 DCs are now down to AD/DNS and global catalogs, one still has a few old fileshares but that will be gone soon.

    Problem:

    Today I decided to go the next step and drop the GC roles from the two old DCs. No issues reported except for Exchange 2007 SP1. Exchange threw a wobbly and continuosly complained that it couldn't find various AD resources.

    I sent it down for a reboot, googled a bit and found this: http://forums.msexchange.org/m_18004...htm#1800463281

    On reboot I had the same errors so I implemented the above pointing it to a 2008 R2 DC, this made no difference either side of reboot.

    Under pressure from users I reinstated the old GCs, rebooted again and things eventually settled down and worked again.

    I've since googled a bit more and found this: http://forums.msexchange.org/m_18005...htm#1800539492

    Question(s):

    Given that 2008 R2 is supported as an install base for Exchange 2007 SP1 would it also not be supported if only 2008 R2 global catalogs were available despite being installed on 2003? If it is supported how can I force a change in the GC server used, as the information I've found so far doesn't seem to work? .

  • #2
    Re: Exchange 2007 SP 1 and Windows 2008 R2 DCs

    Ok more research done.

    I found the support matrix for Exchange and my described configuration is supported.

    I also found that following the death of a domain controller some time ago we had similar issues and worked around it by statically assigning a DC and GC server to Exchange.

    I figure that unsetting these values or statically setting them to a 2008 R2 DC/GC server will resolve the issue. My plan is therefore to try this tonight and drop the 2003 GC servers again tomorrow providing all ok.

    Comment


    • #3
      Re: Exchange 2007 SP 1 and Windows 2008 R2 DCs

      It is also worth running the Exchange BPA as it will catch a lot of similar (AD related) issues and suggest the best fix
      Tom Jones
      MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
      PhD, MSc, FIAP, MIITT
      IT Trainer / Consultant
      Ossian Ltd
      Scotland

      ** Remember to give credit where credit is due and leave reputation points where appropriate **

      Comment


      • #4
        Re: Exchange 2007 SP 1 and Windows 2008 R2 DCs

        While it may well be a supported combination, why are you still on Exchange 2007 SP1? SP3 is the current version and it resolves a lot of issues. You are years behind.

        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: Exchange 2007 SP 1 and Windows 2008 R2 DCs

          Cheers guys. Following the changes I made via the command shell it looks a lot happier. The BPA showed no domain related issues, correctly identified the the fsmo role holders and reported only a few issues most of which are minor or plain wrong.

          The reason we are still on SP1 is not a particularly good one, but essentially I am the Exchange expert in our company, however, my experience on Exchange 2007 (or any version in fact) in hours could be counted on your fingers and if not deffinitely with toes counted as well and most of those involve taking backups . When I'm in a situation like that I usually fall back on 'if it aint broke don't fix it'.

          Comment


          • #6
            Re: Exchange 2007 SP 1 and Windows 2008 R2 DCs

            fair call, however, you realise that service packs are designed to fix things that are broke, right?

            just cause you may not necessarily see them.. doesn't mean they ain't broke
            Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

            Comment


            • #7
              Re: Exchange 2007 SP 1 and Windows 2008 R2 DCs

              Yeah I get that and will eventually upgrade to the latest SP. The way I see it is a degree of risk vs the ability to solve an issue should one arise and should SP3 cause an issue what impact to services vs no clear gain for doing the work in the first place. It becomes even harder then to justify the overtime to business when all they see is risk.

              However, that said, I'm doing some work this weekend and will see if I have time over to look at it. It needs some windows updates anyway covered by the work.

              Comment


              • #8
                Re: Exchange 2007 SP 1 and Windows 2008 R2 DCs

                Unfortunately in this security environment, the "if it ain't broke don't fix it" cannot be used unless the system is completed isolated from the Internet.

                As soon as updated are released the bad guys are looking at them to find ways to attack the products that have been fixed. Patching should be kept up to date.

                Exchange 2007 SP1 isn't even supported any longer. That means if you were to have a problem, you would be limited on the support you could get from Microsoft. Exchange 2007 SP3 has gone in correctly and cleanly on every site I have done it on and I would encourage you to install it as soon as possible.

                Being reactive to risk is a poor attitude to take in my opinion. I have cleaned up many many servers that have been managed in that way, and it has cost the client more in the long run because it took longer to clean up the mess. If the server had been maintained correctly, then the issue normally would not have occurred.

                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

                Working...
                X