This took a little time to narrow down, we have 4 edge servers all were recently built at the same time but the 4th one. Today we tried to do the Edge Subscription on our new Hub Transport server. After some troubleshooting we realized that 1-3 had the same SCW policy applied, but 4 didnt even have a policy applied yet. 1-3 will not work, but 4 works. Also it kicks a very odd error about time syncing. So we decided to do an SCW new policy on the 4th server we checked every box there was, but skipped the network, registry, and auditing settings. Crossing our fingers we created a new Edge SubScript and it worked! We took that SCW policy from 4 and applied it to 1-3 and they still didnt work....Id hate to have to rebuild 1-3, plus we need to lock down 4 better all options is pointless, and here is the very odd error we get about time stuffDoes anyone know what exactly the HT is doing and looking for during an Edge sync, I need to find out what is stopping 1-3, but works fine on 4.Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:00 Edge SubscriptionFailed Error:The clock setting for the Edge Transport server to be subscribed and the computer on which you are running this task are not synchronized. Make sure the clocks on all Exchange servers in your organization and your Edge Transport servers are synchronized. Exchange Management Shell command attempted:new-EdgeSubscription -FileName 'C:\edge01subscript.xml' -Site 'site' -CreateInternetSendConnector $true -CreateInboundSendConnector $true Elapsed Time: 00:00:00

I would be interested in knowning what time the Edge Servers have and the Hub Server has. Are they similar or off by 5 or 10 minutes etc?SF - MCITP:EMA, MCTS

Time on both the servers are good, if I run an w32tm /query /statusSource:HT - returns the PDCEdge - local CMOS clockThat is the same on 01-04

So you added a new Hub Transport Server into the org correct? In the event of adding a new Hub Transport server to the organization in the same AD site you need to resubscribe the Edge Transport server(s). Managing Edge Subscriptionshttp://technet.microsoft.com/en-us/library/bb124096.aspxResubscribe an Edge Transport serverIf Hub Transport servers are added to an ActiveDirectory site after an Edge Subscription to that site is created, they do not participate in the EdgeSync synchronization process. To have those servers participate in the EdgeSync synchronization process,you must resubscribe the Edge Transport server. You must also resubscribe the Edge Transport server if errors occur during authentication of the EdgeSync replication account credentials.SF - MCITP:EMA, MCTS

Got it fixed, turns out the time was right on 3 of the4but one of the servers wasnt (someone else built) it was off by by 12 hours am/pm, because when you install SP2 on Server 2008 it removes theday light saving time check box from Baghdad time zone.Corrected and created a new edge subscription and worked, over looked it the first time.Thanks

Glad I could help.SF - MCITP:EMA, MCTS

i have been trying to configure a new Edge Subscription on the Hub Transport server, when i put the edge Subscription created on the edge transport server, it returns the below error message. can anyone help with this issue? thanks Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:00 Edge Subscription Failed Error: The clock setting for the Edge Transport server to be subscribed and the computer on which you are running this task are not synchronized. Make sure the clocks on all Exchange servers in your organization and your Edge Transport servers are synchronized. Exchange Management Shell command attempted: new-EdgeSubscription -FileName 'C:\Users\exadmin\Desktop\subsEdge.xml' -Site 'Lagos' -CreateInternetSendConnector $true -CreateInboundSendConnector $true Elapsed Time: 00:00:00 MCITP Ent, Messaging

i got it fixed. i am installing the Edge Transport server on a Virtual machine, the Parent partition clock was not set right and also the Windows Time service was not started so i guess the virtual machine was getting clock setting from the parent partition. 1.i started the window time service on the parent partition, 2.uncheck the time synconisation with the internet on the parent patitions 3.started the window time service on the virtual machine 4.uncheck the time synconisation with the internet on the virual machine 5. manually reset the time on both parent patition and the virtual machine i was able to get pass the problem of clock setting sycronisation i am now faced with compatibility issue with Edge Transport 2010 and Hub Transport 2007 does anyone know how this can be resolved? MCITP Ent, Messaging