Hi everyone,I have Exchange 2007 set up with three servers,2 x MB's (1 running as a dialtone for recovery) and 1 HT/CAS server. All runnng Win 2003 x64 Standard and Exchange 2007 StandardSP1.We had a problem with one of our two domain controllers and had to quickly demote it from being a domain controller, re-prepare the server with a new installation of Windows etc and re-promote it back as a domain controller once again. Everything went well until I noticed Exchange is now using only one of the two available domain controllers (the one that was not rebuilt).When I look in Exchange I find only the one domain controller under the following headings:- Domain controllers servers being used by Exchange- Global catalog servers being used by ExchangeBoth our domain controllers are global catalog servers.I have pasted a recent 'MSExchange ADAccess' log below but was wondering if anyone could kindly point me in the right direction so I can get the missing domain controller back in the list of those available to Exchange.Any help really appreciated.Regards,Phil.---Event Type:InformationEvent Source:MSExchange ADAccessEvent Category:Topology Event ID:2080Date:05/02/2009Time:14:52:20User:N/AComputer:EXCHANGEHTCASDescription:Process IISIPM3B069209-CAAA-4E10-B7B2-E61E725A8178 -AP "MSEXCHANGEOWAAPPPOOL (PID=3540). 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:trinity.originpublishing.co.ukCDG 1 7 7 1 0 1 1 7 1elmerfudd.originpublishing.co.ukCDG 1 7 7 1 0 1 1 0 1Out-of-site:---Phil

Hi Phil,Can you run below command and see the DC/GC being used by Exchange server and it is not configured as a static? Please post the result here...Get-ExchangeServer -Status | FLBTW, what's the names of DC/GC which is demoted and newly promoted in the event log?Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Hi,Thank you for helping. I ran the command and have pasted the results below. I have two DC's called Elmer Fuddand Trinity. Both are 2003 Standard R2, fully updated and service packed and both are set to be GC's. Elmer Fudd is the DC that was demoted, repaired and re-promoted and was set up with exactly the same configuration as before other than it is now running Print Manager. I checked the Windows event logs and found nothing strange going on. Likewise, I have tested the replication services and everything appears to be fine so very confused. As for Exchange, everything appears to be working perfectly other than it's relying on only one DC.Regards,Phil.

Hi Phil,Looks like Exchange DSAccess is not able to connect to NetLogon service of DC ElmerFuddover RPC because that colum shows value 0 instead of 7.(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)In-site:trinity.originpublishing.co.ukCDG 1 7 7 1 0 1 1 7 1elmerfudd.originpublishing.co.ukCDG 1 7 7 1 0 1 1 0 1~ Do you get any error when you run DCDiag?~ Did you reboot the serverElmerFuddafter making DC/GC and when it is fully replicated?Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Morning, Thanks for getting back to me. I ran DCDiag and the results further below. The server was rebooted following re-promotion and again later, but Ive rebooted once more about half an hour ago just to be sure. There are one or two other errors as well but not sure what they are or if they are related. Any thoughts welcome. I also found the following error in the Windows event viewer on Elmer:- Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13565 Date: 06/02/2009 Time: 08:51:14 User: N/A Computer: ELMERFUDD Description: File Replication Service is initializing the system volume with data from another domain controller. Computer ELMERFUDD cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. To check for the SYSVOL share, at the command prompt, type: net share When File Replication Service completes the initialization process, the SYSVOL share will appear. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Regards, Phil.