Hello,Can anyone tells me why my Recipient status does not synchronized?? Is that because of certificate pb? Could you please help me?If you need further info, please let me know.GraigTest-EdgeSynchronization Name : XXXXP01LeaseHolder : XXXCHP01LeaseType : OptionConnectionResult : SucceededFailureDetail :LeaseExpiry : 06/10/2009 12:07:45LastSynchronized : 06/10/2009 11:07:45CredentialStatus : SynchronizedTransportServerStatus : SynchronizedTransportConfigStatus : SynchronizedAcceptedDomainStatus : SynchronizedSendConnectorStatus : SynchronizedMessageClassificationStatus : SynchronizedRecipientStatus : NotSynchronizedCredentialRecords : Number of credentials 6 Name : XXXXP02LeaseHolder : XXXCHP01LeaseType : OptionConnectionResult : SucceededFailureDetail :LeaseExpiry : 06/10/2009 12:07:45LastSynchronized : 06/10/2009 11:07:45CredentialStatus : SynchronizedTransportServerStatus : SynchronizedTransportConfigStatus : SynchronizedAcceptedDomainStatus : SynchronizedSendConnectorStatus : SynchronizedMessageClassificationStatus : SynchronizedRecipientStatus : NotSynchronizedCredentialRecords : Number of credentials 6

Run Get-Exchangeserver on Edge as well as Other EX2007 server make sure they all are same SP and update level. other factors such as failure to resolve the Edge server name in DNS, a failure trying to connect to port 50636 on Edge server , network connectivity issues, an invalid certificate, or an expired subscription. Please check whether the certificate enabled for SMTP service which has been applied with your server. If not, please enable the certificate for SMTP service, then delete the subscription and create it again. For more information about enable-exchangecertificate, please view the link below: http://technet.microsoft.com/en-us/library/aa997231.aspx Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Hi Graig, Normally, the issue occurs because you have some new users created that would not replicate until the default 2 hours have past, or we have a deleted users that has not been deleted from the Edge database too and so on Therefore, I suggest you run Start-EdgeSynchronization to force the edgesync. Then, please check the result of Test-EdgeSynchronization command again. If the RecipientStatus is still NotSynchronized. I would like to explain the issue occurs some objected cannot be synchronization between internal network (AD) and edge server (ADAM). To find out more, I suggest you perform following steps: 1. Run the command (Test-EdgeSynchronization).RecipientStatus for Edge server and store the result into a variable. For a single subscribed Edge use the command: (Test-EdgeSynchronization).RecipientStatus A typical result would be the following: [PS] C:\>(Test-EdgeSynchronization).RecipientStatus Status Synchronized Org Only Edge Only Conflicts ------ ------------ -------- --------- --------- NotSynchronized 3 1 0 0 In order to avoid running the command for each property we will look at, store the command into a variable: $RcptStatus = @(Test-EdgeSynchronization).RecipientStatus 2. List all the properties of the results obtained in the previous step. $RcptStatus | FL A typical result would be the following: [PS] C:\>$RcptStatus | fl SyncStatus : NotSynchronized SynchronizedObjects : 6 OrgOnlyObjects : {MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e} EdgeOnlyObjects : {} ConflictObjects : {} 3. List the details of the non-empty properties. $RcptStatus.OrgOnlyObjects $RcptStatus.EdgeOnlyObjects $RcptStatus.ConflictObjects NOTE: OrgOnlyObjects lists objects which exist in AD only. EdgeOnlyObjects lists objects which exist in ADAM (edge) only. ConflictObjects lists objects which are different in ADAM and AD. Following the example started in the previous step we should see something similar to: [PS] C:\>$RcptStatus.OrgOnlyObjects Rdn : CN=MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e Parent : Transport Settings Depth : 9 DistinguishedName : CN=MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e,CN=Transport Settings,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=EdgeSync146b,DC=extest,DC=microsoft,DC=com DomainId : EdgeSync146b.extest.microsoft.com ObjectGuid : 00000000-0000-0000-0000-000000000000 Name : MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e The result contains the Distinguished Name of the problematic objects which is enough to identify the object. In out-of-sync recipient conditions, the object GUID is not returned. 4. Identify the object and determine its current status (deleted, disabled, etc.). In Step 3, we are expecting to get the Distinguished Name of the problematic objects. In most cases it will be a contact or a user. NOTE: The recipients remain in ADAM after disabling a mailbox. This behavior will not be changed in Exchange 2007 as it would be operationally too expensive for EdgeSync. Applying the above method can help us determine if some objects are affected by this behavior. For further investigating a single user, we can apply the procedure described in the article: How to Verify EdgeSync Results for a Recipient http://technet.microsoft.com/en-us/library/bb266939(EXCHG.80).aspx Thanks, Mike