Hey Microsoft, sort you documents out ;-). I have had a hell of time trying to find an idiots guide on how to setup Edge in a perimeter network. To start with ISA. Well I found Devin blog on how to setup the ISA Server Rules (http://blogs.3sharp.com/Blog/deving/archive/2007/01/11/2774.aspx) It seems to work okay. The best reference I could find for Edge was in "How to Cheat at Configuring Exchange Server 2007: Including Outlook Web, Mobile, and Voice Access" by Henrik Walther So what I needed now was a step by step guide on how to setup Edge and a related Hub Transport server. Oh also include what I need to do when I hit an error! This was a real up hill struggle! On the Edge Transport Machine I ran the following and said Yes [PS] C:\>New-EdgeSubscription -file "c:\EdgeSubscriptionFile.xml" Confirm Creating an Edge Subscription makes the configuration of this Edge Transport server ready to be managed via EdgeSync. Any of the following types of objects that were created manually will be deleted: accepted domains; message classifications; remote domains; and Send connectors. Also, the InternalSMTPServers list of the TransportConfig object will be overwritten during the synchronization process. The Exchange Management Shell tasks that manage those types of objects will be locked out on this Edge Transport server. You must manage those objects from inside the organization and allow EdgeSync to update the Edge Transport server. EdgeSync requires that this Edge Transport server is able to resolve the fully qualified domain names (FQDN) of the Hub Transport servers in the Active Directory site to which the Edge Transport server is being subscribed. Those Hub Transport servers must be able to resolve the FQDN of this Edge Transport server. You should complete the Edge Subscription inside the organization in the next "1440" minutes before the bootstrap account expires. Yes Yes to All No [L] No to All Suspend [?] Help (default is "Y"):y [PS] C:\> Right I then copied the xml for a hub server and imported it to the Edge Subscriptions Tab for Hub Transport server. That all worked fine, and when I ran this you can see the nice positive response: [PS] C:\>Test-EdgeSynchronization Name : EdgeServer ConnectionResult : Succeeded FailureDetail : LastSynchronized : 01/01/0001 00:00:00 CredentialStatus : NotStarted TransportServerStatus : NotStarted TransportConfigStatus : NotStarted AcceptedDomainStatus : NotStarted SendConnectorStatus : NotStarted MessageClassificationStatus : NotStarted RecipientStatus : NotStarted But when I done this it just didn't work [PS] C:\>Start-EdgeSynchronization Start-EdgeSynchronization : unable to contact EdgeSync service At line:1 char:25 + Start-EdgeSynchronization <<<< What the hell I thought. I had network connectivity and have resolution, what the hell is going on?! .. so that was Friday. I tried again this morning and Start-EdgeSynchronization still said the same. so hey, lets check out the application event log, that would be novel. Today I was getting another error: Event Type: Error Event Source: MSExchange EdgeSync Event Category: Topology Event ID: 1036 Date: 30/04/2007 Time: 10:41:33 User: N/A Computer: HubServer Description: Microsoft Exchange couldn't connect to EdgeServer.MyOrg.com using credentials cn=ESRA.EdgeServer.HubServer.0,CN=Services,CN=Configuration,CN={C29865B1-9E5C-4628-861F-599333745CC1}/%3. This may be because of an expired bootstrap account. Please resubscribe and try again. Ohh. So I discovered this: You must complete the Edge Subscription process inside the organization within 24 hours of exporting the Edge Subscription file on the Edge Transport server. If you don't export the Edge Subscription file on the Edge Transport server within 24 hours, the bootstrap account expires and you must remove the Edge Subscription and start the procedure again. So I reran this: [PS] C:\>New-EdgeSubscription -file "c:\EdgeSubscriptionFile.xml" Confirm The Edge Subscription inside the organization should be completed within the next "1440" minutes before the bootstrap account expires. Yes Yes to All No [L] No to All Suspend [?] Help (default is "Y"):y [PS] C:\> An copied the file to the HubServer. Then removed the Edge subscriptions and added it back. Again, Test-EdgeSynchronization looked good but Start-EdgeSynchronization still didn't work. And nothing in the application event log. So I found the "Microsoft Exchange EdgeSync" service on the HubServer ... Humm what if? I restarted it and yeah baby it get these in app log: Event Type: Information Event Source: MSExchange EdgeSync Event Category: Initialization Event ID: 1059 Date: 30/04/2007 Time: 10:56:12 User: N/A Computer: HubServer Description: EdgeSync is starting Event Type: Information Event Source: MSExchange EdgeSync Event Category: Synchronization Event ID: 1000 Date: 30/04/2007 Time: 10:56:13 User: N/A Computer: HubServer Description: Synchronization successfully completed on server: CN=EdgeServer,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MyOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ExchOrg,DC=local type: Recipients started: 30/04/2007 09:56:13 ended: 30/04/2007 09:56:13 scanned: 3 added: 3 updated: 0 deleted: 0 Event Type: Information Event Source: MSExchange EdgeSync Event Category: Synchronization Event ID: 1000 Date: 30/04/2007 Time: 10:56:14 User: N/A Computer: HubServer Description: Synchronization successfully completed on server: CN=EdgeServer,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MyOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ExchOrg,DC=local type: Configuration started: 30/04/2007 09:56:13 ended: 30/04/2007 09:56:14 scanned: 254 added: 8 updated: 245 deleted: 1 And this sealed it: [PS] C:\>Test-EdgeSynchronization Name : EdgeServer ConnectionResult : Succeeded FailureDetail : LastSynchronized : 30/04/2007 10:56:14 CredentialStatus : Synchronized TransportServerStatus : Synchronized TransportConfigStatus : Synchronized AcceptedDomainStatus : Synchronized SendConnectorStatus : Synchronized MessageClassificationStatus : Synchronized RecipientStatus : Synchronized So the lesson of the day. Restart the "Microsoft Exchange EdgeSync" Service on the Hub Transport server of choice to "force" EdgeSync to work Also if you add a load of users, once it works, you run Start-EdgeSynchronization again [PS] C:\>Start-EdgeSynchronization Result : Success Type : Configuration Name : CN=EdgeServer,CN=Servers,CN=Exchange Administrative Group (FY DIBOHF23SPDLT),CN=Administrative Groups,CN=MyOrg,CN=Micros oft Exchange,CN=Services,CN=Configuration,DC=ExchOrg,DC=local FailureDetails : StartUTC : 30/04/2007 10:33:41 EndUTC : 30/04/2007 10:33:41 Added : 0 Deleted : 0 Updated : 253 Scanned : 254 TargetScanned : 0 Result : Success Type : Recipients Name : CN=EdgeServer,CN=Servers,CN=Exchange Administrative Group (FY DIBOHF23SPDLT),CN=Administrative Groups,CN=MyOrg,CN=Micros oft Exchange,CN=Services,CN=Configuration,DC=ExchOrg,DC=local FailureDetails : StartUTC : 30/04/2007 10:33:41 EndUTC : 30/04/2007 10:33:42 Added : 20 Deleted : 0 Updated : 3 Scanned : 23 TargetScanned : 0 .. the Application event log shows this Event Type: Information Event Source: MSExchange EdgeSync Event Category: SyncNow Event ID: 1040 Date: 30/04/2007 Time: 11:33:41 User: N/A Computer: HubServer Description: Synchronization started now with a load of these Event Type: Information Event Source: MSExchange EdgeSync Event Category: Synchronization Event ID: 1000 Date: 30/04/2007 Time: 11:33:42 User: N/A Computer: SUKMSDHUB02 Description: Synchronization successfully completed on server: CN=Edgeserver,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MyOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ExchOrg,DC=local type: Configuration started: 30/04/2007 10:33:42 ended: 30/04/2007 10:33:42 scanned: 254 added: 0 updated: 253 deleted: 0 And ending with this Event Type: Information Event Source: MSExchange EdgeSync Event Category: SyncNow Event ID: 1041 Date: 30/04/2007 Time: 11:33:55 User: N/A Computer: HubServer Description: Completed synchronization now Hope this helps
Exchange 2007 Edge Transport Server Outlook 2007 indexing issues Distribution List is more locked down
PingBack from http://jesselatestnews.aokhost.com/newedgesubscription.html