Hence, after completing a manual configuration, you should have the connectors configured on the
Edge Transport server shown in Figure 9 - 7 . Note that the only connector created automatically was
the Default Internal Receive Connector.
Figure 9-7
Part II: Working with Server Roles
250
The second scenario, which is the one that is recommended , is where edge subscription and EdgeSync will
be performed. The following tasks are performed to fully integrate and associate the Edge Transport
server with the Exchange organization. This process ensures that the organization takes full advantage
of the message hygiene and anti - virus protection built into the Edge Transport server role. It also
requires the least administrative effort:
1. Ports: Verify that the perimeter network firewall that separates the Edge Transport server from
the Exchange organization is configured to enable communications on ports 25 and 50636.
Because EdgeSync replicates data between Active Directory and ADAM, secure LDAP port 50636
for TCP communication must be opened on the firewall to enable directory synchronization from
the Hub Transport to ADAM on the Edge Transport server. Recall that synchronization is single
directional, hence the port can be opened one - way from the Hub to the perimeter network.
Pages:
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361