Hi we have an exchange setup where in we have 2 mailbox servers and one hub transport on which we also have the client access server and one edge transport server.The problem that we are facing is when ever we create a new user we have to run the edge sync command manually until unless the newly created user will not be receiving any kind of email's from external domains. Can anyone please tell me what would be the possible reason for this ???

Its mean EDGE is not being sync with AD DS. Why you don't create new EDGE subscription and import it, then check status.Anil

From the hub, can you please run "Test-EdgeSynchronization." Please post the result.

We had already done this. its imported successfully, but even then we have the same issue.

Name : edgeserver LeaseHolder : hubserver LeaseType : Option ConnectionResult : Succeeded FailureDetail : LeaseExpiry : 2/22/2011 6:19:19 PM LastSynchronized : 2/22/2011 5:19:19 PM CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : Synchronized CredentialRecords : Number of credentials 3

Try this. Create the user/mailbox in Exchange. From the Hub, do a "Start-EdgeSynchronization." At this point, it should propagate its e-mail GUID to the edge. I think what's happening is that edge is not getting the GUID from the Hub. As a result, Edge thinks that the user is non-existent in your domain and the e-mails for the user is being dropped.

Normally when ever we create a user by default the user information is not transferred or updated on to the edge server, So we have to run the start-edgesync command then the user information is updated on the edge server and then the user starts receiving mails from external domains.But this manual process of synchronizing the config every time i create a new user is the main problem. It should automatically be synchronized as there is communication between edge and hub transport servers.

By default, the Hub synchronizes - one-way synchronization - with the Edge once every hour. So you should not have to do it. By forcing you to do the "start-edgesync", I think there is a bigger problem that you have here. Please check that the following ports are open: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server). Source: http://www.exchangelog.info/2007/05/ports-that-need-to-be-open-on-firewall.html.

By default, the Hub synchronizes - one-way synchronization - with the Edge once every hour. So you should not have to do it. By forcing you to do the "start-edgesync", I think there is a bigger problem that you have hear. Please check that the following ports are open: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server). Source: http://www.exchangelog.info/2007/05/ports-that-need-to-be-open-on-firewall.html.

Hi, Please understand that Configuration data is synchronized at one-hour intervals and Recipient data is synchronized at four-hour intervals. Hence, you should wait four hours and check whether the data is synchronized automatically or not. Besides Jos’s suggestions, please restart Microsoft Exchange EdgeSync service on Hub Transport server to check the result. For more information about Synchronized information, please refer to the following article: http://technet.microsoft.com/en-us/library/bb232180(EXCHG.80).aspx Thanks. Novak Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.