• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Event ID 2080 Domain Controller used

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2007] >> Installation >> Event ID 2080 Domain Controller used Page: [1]
Login
Message << Older Topic   Newer Topic >>
Event ID 2080 Domain Controller used - 17.Oct.2007 9:39:21 AM   
mhutchesson

 

Posts: 3
Joined: 17.Oct.2007
Status: offline
We have two domain controllers (central-ad1 and central-ad2) but Exchange 2007 only seems to be seeing and using 1 of them

What would be preventing the Exchange server from using both domain controllers

(both Windows 2003 R2)

Event Type: Information
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2080
Date:  9/28/2007
Time:  11:33:01 AM
User:  N/A
Computer: EXCHANGE
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1188). 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:
central-ad1 CDG 1 7 7 1 0 1 1 7 1
Out-of-site:

Thanks
Michael
Post #: 1
RE: Event ID 2080 Domain Controller used - 18.Oct.2007 7:18:33 PM   
Mad_deamon

 

Posts: 19
Joined: 22.Jul.2006
Status: offline
Can you run a

dcdiag /s:central-ad2

from the Exchange server after putting in the Windows 2003 support tools on that box?

If something is failing there we need to check that out.

thanks,

(in reply to mhutchesson)
Post #: 2
RE: Event ID 2080 Domain Controller used - 20.Oct.2007 1:21:43 AM   
mhutchesson

 

Posts: 3
Joined: 17.Oct.2007
Status: offline
I ran this for both DC's from the Exchange 2007 box, it looks fine (see below)
 
I also found that shortly after the original install it did see all our domain controllers but then after a few minutes this came up in the log and since then its only seeing Central-ad1, it looks like a command was entered to force it that way
 
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1560). Exchange Active Directory Provider will use the servers from the following list:
Domain Controllers:
central-ad1.cancersa.local

Global Catalogs:
central-ad1.cancersa.local

The Configuration Domain Controller is set to central-ad1.cancersa.local.
 
Process MAD.EXE (PID=5676). 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:
central-ad1.cancersa.local CDG 1 7 7 1 0 1 1 7 1
exchange.cancersa.local CD- 1 6 6 0 0 1 1 6 0
central.cancersa.local CD- 1 6 6 0 0 1 1 6 0
central-ad2.cancersa.local CDG 1 7 7 1 0 1 1 7 1
 
 
 
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.CANCERSA>dcdiag
Domain Controller Diagnosis
Performing initial setup:
  ***Error: central-exch is not a DC.  Must specify /s:<Domain Controller> or
  /n:<Naming Context> or nothing to use the local machine.

C:\Documents and Settings\Administrator.CANCERSA>dcdiag /s:central-ad2
Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.

Doing initial required tests
   Testing server: Default-First-Site-Name\CENTRAL-AD2
     Starting test: Connectivity
        ......................... CENTRAL-AD2 passed test Connectivity

Doing primary tests
   Testing server: Default-First-Site-Name\CENTRAL-AD2
     Starting test: Replications
        ......................... CENTRAL-AD2 passed test Replications
     Starting test: NCSecDesc
        ......................... CENTRAL-AD2 passed test NCSecDesc
     Starting test: NetLogons
        ......................... CENTRAL-AD2 passed test NetLogons
     Starting test: Advertising
        ......................... CENTRAL-AD2 passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... CENTRAL-AD2 passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... CENTRAL-AD2 passed test RidManager
     Starting test: MachineAccount
        ......................... CENTRAL-AD2 passed test MachineAccount
     Starting test: Services
        ......................... CENTRAL-AD2 passed test Services
     Starting test: ObjectsReplicated
        ......................... CENTRAL-AD2 passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... CENTRAL-AD2 passed test frssysvol
     Starting test: frsevent
        ......................... CENTRAL-AD2 passed test frsevent
     Starting test: kccevent
        ......................... CENTRAL-AD2 passed test kccevent
     Starting test: systemlog
        ......................... CENTRAL-AD2 passed test systemlog
     Starting test: VerifyReferences
        ......................... CENTRAL-AD2 passed test VerifyReferences

   Running partition tests on : ForestDnsZones
     Starting test: CrossRefValidation
        ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
        ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
     Starting test: CrossRefValidation
        ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
        ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
     Starting test: CrossRefValidation
        ......................... Schema passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
     Starting test: CrossRefValidation
        ......................... Configuration passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : cancersa
     Starting test: CrossRefValidation
        ......................... cancersa passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... cancersa passed test CheckSDRefDom

   Running enterprise tests on : cancersa.local
     Starting test: Intersite
        ......................... cancersa.local passed test Intersite
     Starting test: FsmoCheck
        ......................... cancersa.local passed test FsmoCheck

C:\Documents and Settings\Administrator.CANCERSA>dcdiag /s:central-ad1
Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.

Doing initial required tests
   Testing server: Default-First-Site-Name\CENTRAL-AD1
     Starting test: Connectivity
        ......................... CENTRAL-AD1 passed test Connectivity

Doing primary tests
   Testing server: Default-First-Site-Name\CENTRAL-AD1
     Starting test: Replications
        ......................... CENTRAL-AD1 passed test Replications
     Starting test: NCSecDesc
        ......................... CENTRAL-AD1 passed test NCSecDesc
     Starting test: NetLogons
        ......................... CENTRAL-AD1 passed test NetLogons
     Starting test: Advertising
        ......................... CENTRAL-AD1 passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... CENTRAL-AD1 passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... CENTRAL-AD1 passed test RidManager
     Starting test: MachineAccount
        ......................... CENTRAL-AD1 passed test MachineAccount
     Starting test: Services
        ......................... CENTRAL-AD1 passed test Services
     Starting test: ObjectsReplicated
        ......................... CENTRAL-AD1 passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... CENTRAL-AD1 passed test frssysvol
     Starting test: frsevent
        ......................... CENTRAL-AD1 passed test frsevent
     Starting test: kccevent
        ......................... CENTRAL-AD1 passed test kccevent
     Starting test: systemlog
        ......................... CENTRAL-AD1 passed test systemlog
     Starting test: VerifyReferences
        ......................... CENTRAL-AD1 passed test VerifyReferences

   Running partition tests on : ForestDnsZones
     Starting test: CrossRefValidation
        ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
        ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
     Starting test: CrossRefValidation
        ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
        ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
     Starting test: CrossRefValidation
        ......................... Schema passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
     Starting test: CrossRefValidation
        ......................... Configuration passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : cancersa
     Starting test: CrossRefValidation
        ......................... cancersa passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... cancersa passed test CheckSDRefDom

   Running enterprise tests on : cancersa.local
     Starting test: Intersite
        ......................... cancersa.local passed test Intersite
     Starting test: FsmoCheck
        ......................... cancersa.local passed test FsmoCheck

C:\Documents and Settings\Administrator.CANCERSA>
 

(in reply to Mad_deamon)
Post #: 3
RE: Event ID 2080 Domain Controller used - 21.Oct.2007 8:36:18 AM   
Mad_deamon

 

Posts: 19
Joined: 22.Jul.2006
Status: offline
Yes you are right.. Maybe you could have hard coded the DC's
 
You can define a static set of domain controllers for use by a particular Exchange server (using the set-ExchangeServer cmdlet). This lets you keep Exchange from using domain controllers dedicated to other applications.
 
Maybe you can check that.
 
thanks,

(in reply to mhutchesson)
Post #: 4

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2007] >> Installation >> Event ID 2080 Domain Controller used Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter