Antworten

We also get this error after demoting one our older dc's. we demoted an windows 2003dc an still have windows 2008 dc's (and gc). but when we modified the recipient scope in emc from "ou" to an explicit "gc" we can solve the error messages. hope it helps

After using "Collect Organizational Health Data" to refresh the Health Data I was able to change the DC settings from "Use default" to "Select Domain Controller". Borforehand the MMC wasn't able to connect to the domain.

After rebooting the server again the new error message after starting the EMC is:

An error caused a change in the current set of domain controllers. It was running the command 'Get-FederationTrust'.

I can specify a Domain Controller (which is a GC) only after collecting Organizational Health Data. Collecting and saving the Org Health Data runs successfully.

The user is a member of the "Organzational Management" group.

Opening the EMC does not throw an error at all. The error occurs after opening a node like "Recipient Configurations" - "

I've noticed that the registry entry for the local AD schema cache file "%LOCALAPPDATA%\Microsoft\Windows\SchCache\OLDDC.FQDN.COM.sch" reflects the old DC name. The schema master has been changed a few weeks ago. How are those changes reflected on the Exchange server?

The MSExchange ADAccess service finds all DCs with out any error. Only current DC names are being listed in the details fo the event log entry.

ExBPA show onyl one error:Active Directory domain has an unrecognized Exchange signature. Current DomainPrep version: 12639

I am having this error too, also after demoting a DC in my domain...tried all of the above, no dice. Exchange really thinks that my old server is still a DC and tries to talk to it.

Also I am having a problem where users are reporting outlook continually asks for a password trying to update the global address list, possibly related? I would love to get rid of these problems. Right now I have one Exchange server and two DCs.

We also get this error after demoting one our older dc's. we demoted an windows 2003dc an still have windows 2008 dc's (and gc). but when we modified the recipient scope in emc from "ou" to an explicit "gc" we can solve the error messages. hope it helps

i have same problem. After demoting previously default domain controller, EMC keeps throwing these errors. I can make them disappear by setting explicit DC to use / scope to DC, but I wonder why doesn't it work using default values? How do I fix that?

Adam, Thank YOU!You were absolutely right!After removal "%LOCALAPPDATA%\Microsoft\Windows\SchCache\OLDDC.FQDN.COM.sch" and use regedit [HKEY_CURRENT_USER\Software\Microsoft\ADs\Providers\LDAP\....] the situation all the same has not changed. deleting this c:\users\<specific user>\appdata\roaming\microsoft\mmc\Exchange Management Console file solved them!