Avatar of barrymccann79
 asked on

Exchange Active Directory not replicating with Domain Controller


I have a problem with our Exchange Server replicating with our Domain Controller. I can create a new account in Active Directory on the Domain Controller. but when I go to create a mailbox for the user on the Exchange server I cannot see the newly created account. I deleted a number of old users from the Active Directory on the Domain Controller yesterday and while they are no longer present on the DC they are still in the Active Directory on the Exchange. I have checked through the logs on both and the only errors I get are below. This is my first post so let me know if I need to provide any more information.

Source : MRxSmb
Event ID : 8003
The master browser has received a server announcement from the computer LNC03 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{E09ADBEA-4CA7-496E-ABA. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

(Domain Controller)
Source : SceCli
Event ID : 1202
Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.

Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".

Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID.  This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO.  To resolve this event, contact an administrator in the domain to perform the following actions:

1.      Identify accounts that could not be resolved to a SID:

From the command prompt, type: FIND /I "Cannot find"  %SYSTEMROOT%\Security\Logs\winlogon.log

The string following "Cannot find" in the FIND output identifies the problem account names.

Example: Cannot find JohnDough.

In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").

2.      Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:

a.      Start -> Run -> RSoP.msc
b.      Review the results for Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment and Computer Configuration\Windows Settings\Security Settings\Local Policies\Restricted Groups for any errors flagged with a red X.
c.      For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.

3.      Remove unresolved accounts from Group Policy

a.      Start -> Run -> MMC.EXE
b.      From the File menu select "Add/Remove Snap-in..."
c.      From the "Add/Remove Snap-in" dialog box select "Add..."
d.      In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add"
e.      In the "Select Group Policy Object" dialog box click the "Browse" button.
f.      On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g.      For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1.

For more information, see Help and Support Center at
Active DirectoryExchangeMicrosoft Legacy OS

Avatar of undefined
Last Comment

8/22/2022 - Mon

Which version of Exchange and Active Directory do you use?

It's Windows Server 2003 Active Directory (Version: 5.2.3790.3959) and Exchange 2003 (Version: 6.5.7638.1)
Coolie Sheppard

Active Directory replicates with other servers within the network that are domain controllers

Is your Exchange Server a DC?
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck

No, the Exchange server is not a DC.
Coolie Sheppard

Unless someone corrects me if I'm wrong, you will need to promote your Exchange Server to a DC.  (Although not recommended and blah blah).  Mine is a DC because I wanted AD to replicate

you will have to run dcpromo (Start, Run > dcpromo) and promote it to the DC

This was working correctly up to about a week ago. I'm not too sure what changed. I would like to leave the set up as it is without promoting the Exchange server to a DC. I have also heard it is not a good idea to have the Exchange server as a DC.
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Coolie Sheppard


here's a crazy question

in your services, is Microsoft Exchange Site Replication Services turned on?

Just checked and yes it is turned on

We've been using our Exchange without promoting it to a DC. It seems to work fine.
When creating a new Mailbox we normaly use Active Directory Users and Computers
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.