When I send an email from outside I get the error message: The error that the other server returned was: 550 550 5.1.1 User unknown. The certificates have been renewed lately and I do not get what shouold be checked now.. Below the result from the test-edge and I noticed that only the hubcas 2 is the LeaseHolder.. Is taht normal? Can you please help me to solve that issue (It works internaly from Exchange to exchnage account) >Test-EdgeSynchronization Name : EDGE02 LeaseHolder : CASHUB02 LeaseType : Option ConnectionResult : Succeeded FailureDetail : LeaseExpiry : 08/09/2010 12:15:00 LastSynchronized : 08/09/2010 11:15:00 CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : NotSynchronized CredentialRecords : Number of credentials 6 Name : EDGE01 LeaseHolder : CASHUB02 LeaseType : Option ConnectionResult : Succeeded FailureDetail : LeaseExpiry : 08/09/2010 12:15:00 LastSynchronized : 08/09/2010 11:15:00 CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : NotSynchronized CredentialRecords : Number of credentials 6

New Users/DLs rejected by Edge Transport. For all the users created it does work outide the company and from outside.

I'd try a new edge subscription. You're not getting the valid recipients updated on the edge servers from AD.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Shall I first create an Edge Subscription File on an Edge Transport Server and then Import an Edge Subscription File to an Active Directory Site ?? Would that generate a service interruption? I did a Get-EdgeSubscription | fl Site : Domain : company.com IsValid : True OriginatingServer : localhost ExchangeVersion : 0.1 (8.0.535.0) Name : EDGE01 ObjectClass : {top, server, msExchExchangeServer} WhenChanged : 08/09/2010 12:08:14 WhenCreated : 26/03/2008 13:13:37 I took the project back but I've heard that all renew certificate and edgesubscription were renew. Would that mean that the edgesubscriptionis well expired?

Yes, you create an edge subscription on the Edge servers, then import the resulting .xml file on the hub servers. There shouldn't be any service interruption, and it does appear that the existing edge subscription has expired.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Thank you very much for the info. So it seems like edge subscriptionlast only 5-6 months. Is there any way to change the lenght? Last thing: New-EdgeSubscription -FileName "C:\EdgeSubscription08092010.xml" When the New-EdgeSubscription cmdlet is run on the Edge Transport server, you receive a prompt to acknowledge the commands that will be disabled and the configuration that will be overwritten on the Edge Transport server. To bypass this confirmation, you must use the Force parameter. This parameter is useful when you script the New-EdgeSubscription cmdlet. The Force parameter is also used to overwrite an existing file with the same name as the file that you're creating when you resubscribe an Edge Transport server. --> What is the Force parameter I should add at the end of the bolow shell command: New-EdgeSubscription -FileName "C:\EdgeSubscription08092010.xml"

-Force is a switch parameter, so it doesn't take any arguments. New-EdgeSubscription -FileName "C:\EdgeSubscription08092010.xml" -Force As far as I know, you cannot change the edge subscription lifetime.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Hello, I did the manipulatio. I export the xml file from the edge1 and the edge 2 to the cashub 1 and 2. On the CASHUB1: I deleted the 2 Edge Subscriptions I had and I created 2 New Edge Subscription based on the xml file from the Edge 1 and Edge2. When I connected on the CASHUB2 to do the manipulation it doesn'y let me delete the 2 Edge Subscriptions! Is that normal? I got: Error : impossible to find the objet "EDGE NAME" on the Domain Controler "DC NAME" Should I had to create the Edge Subscriptions on both Edge servers and create the 2 New Edge Subscriptions only on the CASHUB1?

Further info: On the edge 1: I did [PS] C:\>Get-EdgeSubscription | fl Site : Domain : company.com IsValid : True OriginatingServer : localhost ExchangeVersion : 0.1 (8.0.535.0) Name : EDGE01 WhenChanged : 08/09/2010 15:50:20 WhenCreated : 26/03/2008 13:13:37 --> I did test the mail flow and sent email from outside and it seems like it does WORK!! but I don't get the WhenChanged line :-S Have I missed something? Please let me know if you need more information.

I'm not sure about the error. I think you can only have the Edge subscription on one of the hub servers. I don't think you'd want multiple hub servers trying to push recipient updates to the Edge server at the same time anyway.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

It does work at the end but I wonder why the date hasn't changed on both edge when I run the command Get-EdgeSubscription | fl Would you have any explanation? Thanks again, Graig

Here what I get from the hubcas: [PS] C:\>Test-EdgeSynchronization Name : EDGE01 LeaseHolder : HUBCAS02 LeaseType : Option ConnectionResult : Succeeded FailureDetail : LeaseExpiry : 08/09/2010 16:51:26 LastSynchronized : 08/09/2010 15:51:26 CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : NotSynchronized CredentialRecords : Number of credentials 6 Name : EDGE02 LeaseHolder : HUBCAS02 LeaseType : Option ConnectionResult : Succeeded FailureDetail : LeaseExpiry : 08/09/2010 16:51:26 LastSynchronized : 08/09/2010 15:51:26 CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : NotSynchronized CredentialRecords : Number of credentials 6

Did you create a new subscription .xml file on the Edge servers and then copy that to the Hub servers? If you just re-created a new subscription from the old .xml file it's still going to be expired.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

I did run that command on both Edge: New-EdgeSubscription -FileName "C:\EdgeSubscription08092010.xml" -Force Then I copyied from the Edges servers the "C:\EdgeSubscription08092010.xml" file and paste the file to the HUBCAS at the C;/ From the Hub server I followed that: # In the console tree, navigate to Organization Configuration > Hub Transport. # In the result pane, click the Edge Subscriptions tab. # In the action pane, click New Edge Subscription. On the New Edge Subscription page, complete the following fields: * Active Directory site Click Browse, and then select an Active Directory site in the drop-down list. This field identifies the Active Directory site where the Hub Transport server is connecting to the Edge Transport server for which the Edge Subscription exists. * Subscription file Click Browse, and then select an Edge Subscription file. * Automatically create a Send connector for this Edge Subscription Select this check box to automatically create a Send connector that routes messages from the Exchange organization to the Internet. The Edge Subscription is configured as the source server for the Send connector. The Send connector is configured to route messages to all domains by using Domain Name System (DNS) MX resource records. # Click New to create the new Edge Subscription. # On the Completion page, review the following, and then click Finish to close the wizard: * A status of Completed indicates that the wizard completed the task successfully. --> I managed to remove the edge subscription on the HUB2 server and create a new edge subscription. I am still wondering why the Get-EdgeSubscription does not shows the correct dates. Have I missed something?

Can you get email to your new users now?[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

No I can not :-( It has fixed the new users from this morning but I tried to create a new user and DG and it did not work

It won't accept email for new users until it runs an edge synch and updates the valid recipients on the edge server. By default, this happens every 4 hours. http://technet.microsoft.com/en-us/library/bb310755(EXCHG.80).aspx#EdgeSyncsynchronization[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

I did a start-edgesynch and I received an email from outside to a new DG I have created. I am still worry about the WhenChanged string: [PS] C:\>Get-EdgeSubscription | fl Site : Domain : company.com IsValid : True OriginatingServer : localhost Name : EDGE01 WhenChanged : 08/09/2010 17:00:29 WhenCreated : 26/03/2008 13:13:37 Shall I create the edgesubcription again, just wait to have that WhenChanged date updated or I did miss something? (I have read 4 times the procedure and don't feel like I missed something. Graig

I don't have a definitive answer on the whenchanged property. It looks like we've got the problem fixed. You can test creating another subscription and see what happens to the property, or open an new thread and see if someone else knows. [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "