locked
Echange 2007 ADAccess issue RRS feed

  • Question

  • Hello,

       We have a global AD network setup with Exchange 2007 servers in several offices around the world.  The Exchange Servers in the remote offices are running off the domain controller in each office.  It seems in each office, the event logs are showing for the MSExchange ADAccess event cannot see the local in-site server it is running on properly.  I get the events where it says there is no Global Catalog Server and No Domain Controller up in the local site but it sees the other remote servers fine.  Then the characteristics for the server it is running on show as CDG 1 0 0 1 0 0 0 0 0.

      Exchange is running fine with mail flowing in out of each server.  And the Exchange server that's on the local network I am working on in the US, sees all the servers and characteristics fine as well.  However, on the local network Exchange runs on a member server. 

      All the servers are in the proper groups so it doesn't look like it is the Default Domain Controller Policy issue I have read about, but I don't know why each Exchange server does not see itself as a GC/DC and can't see the proper characteristics.

    Wednesday, November 5, 2014 5:39 PM

All replies

  • Common Unsupported Exchange 2007 Configurations - http://technet.microsoft.com/en-us/library/dd577077(v=EXCHG.80).aspx

    If you install Exchange 2007 on a global catalog server, and if you restart the server, you may need to start the required Exchange services manually.  For more information, see Knowledge Base article 940845, Exchange 2007 services cannot start automatically after you install Exchange 2007 on a global catalog server.  (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=940845)

    Active Directory domain controllers are not supported as Exchange Server cluster nodes - http://support.microsoft.com/kb/898634

    In short, while you can get it running, there are many things that can go wrong when you run an Exchange server on a domain controller.


    Wednesday, November 5, 2014 6:20 PM
  • Yeah, I know all that.  I don't have any of those problems.  The services start fine when the server is rebooted and mail flows without issue.  It's been working ok except for this recent issue for years now.
    Thursday, November 6, 2014 12:17 PM
  • You can probably try to increase the logging level on DSaccess to see why the discovery fail somehow, however that might be an expected bug/limitation (since an update/patch of your servers maybe?).

    If you restart the AD topology service, do you still have the issue? I assume that DNS/DCDIAG check are ok?

    • Proposed as answer by Amy.Wang Tuesday, November 18, 2014 2:01 AM
    Thursday, November 6, 2014 1:02 PM