I've noticed the application log is recording MSExchange ADAccess 2080 errors every 15 minutes.
There are 2 DC's here, Server-B and Server-C.
Server-B is an old 2003 box which is going soon but Server-C is a new 2008 r2 box running Exchange 2010. Both servers are GC’s
Process MAD.EXE (PID=4236). 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)
Server-B.<domain> CDG 1 7 7 1 0 1 1 7 1
Server-C.<domain> CDG 1 0 0 1 0 0 0 0 0
Looking at EMC/Server Configuration/Properties/System Settings Server-B is listed as both the domain controller and global catalog server being used with Exchange when it should be Server-C.
All the roles were moved to Server-C when its predecessor was decommissioned earlier this year.
1. What did you transfer over ? The FSMO roles?
2. Exch canr discover your new GC.
3. How long has that GC been up for?
4. Is that GC working? Replication working?
5. Check event logs on that new GC.
6. Run ExchBPA and ADBPA and see what they come back with.
Jobos (6th December 2011)
Thanks Sukh but I've enabled IPv6 on Server-C so now Exchange is using that server as its GC. I'll be interested to see if this remains the case after a reboot or if the fun and games start again.
There are currently 1 users browsing this thread. (0 members and 1 guests)