This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 10%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKD%3C/text%3E%3C/svg%3E)
If I test a single proxy address with Test-EdgeSynchronization the recipient stats shows the following message:
NotSynchronized - Recipient exists in target Edge Server but attributes are not synchronized.
There are about 20.000 objects and for 12.000 it shows the above message, but for the others I get 'Synchronized'.
We are using the Edge server for a recipient validation process with our mail gateway provider, as far as I can see that is working without problems, also for the recipients that are failing the test-EdgeSynchronization.
The mailboxservers and the Edgeserver version is Exchange 2016 - RU 17
Anyone an idea ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 82%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Fould an old thread and it was due to DNS server issue, have you operated any changes to your DNS servers?
Since it's not affecting the recipient validation process, I would keep monitor those logs and see if it will be fixed after next CU installed.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@Eric Yin-MSFT : Can you share the DNS problems in the thread you mentioned?
I still have the same problem, but can not reproduce it in a test environment, no clue what and why this is happening
You might have seen this thread.
You said test edge sync with a single proxy address, could you expain about this?
Yes, I saw that thread. But that was about connection problems during the synchronization. All synchronizations are successful
To test I run the next commands:
Start-EdgeSynchronization -ForceFullSync
When complete:
Test-EdgeSynchronization -VerifyRecipient <MailboxAlias>@<domain>.<ext> |fl SyncStatus, RecipientStatus,LastSynchronizedUtc
SyncStatus : Inconclusive
RecipientStatus : NotSynchronized - Recipient exists in target Edge Server but attributes are not synchronized
LastSynchronizedUtc : 11/12/2020 10:09:12 AM
The last sync was a few minutes ago, but it is still showing 'NotSynchronized….'
The synclog (.\TransportRoles\Logs\EdgeSync) shows for this specific object:
2020-11-12T10:06:38.055Z,073514a79b144306bf05c0e8ca96ce97,171515,,<EdgeServerFQDN>,50636,TargetConnection,Medium,"Updated:<UserDistinguishename>",Succcessfully Updated Entry,,,
All seems correct except test-EdgeSynchronization command...
Can find any differences when checking the attributes of same mailbox from mailbox and edge server?
Indeed, that's the problem, No errors, no bad logging, but a strange result of the test.
I tried t compare the objects but it hard to say if there is anything missing. Not all properties are replicated and al 'personal' and ID sensitive information is hashed. But, as far as I can see everything is good.
Does the mailbox in your command exist in mailbox server side?
Anyway, the command is just a kind of simulation of Edge sync. It's hard for us to track how this command works.
Keep watching if any issue exist, and ignore this error temporarily.
I am writing here to confirm with you how the thing going now?
If you need further help, please provide more detailed information, so that we can give more appropriate suggestions.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Eric,
Thank you for your reply.
No, as far as I can see there is no problem with DNS, also, nothing changed there.
Because we do not use the edge server for actual mail flow (only for the validation process of the provider), both Mailbox and Edge servers are on the internal LAN and the Edge server is a Domain member.