subject: Connection-type Considerations [print this page] Connection-type considerations include the following:
IPSec policies can specify that, if triggered, all such traffic will be negotiated or that only remote or only LAN connections will be negotiated.
Use the remote choice if remote connections introduce a higher level of risk.
Negotiation policies must exist on both computers that need to communicate
using IPSec.
Negotiation policies must match for successful connection and communication to
occur.
For optimum network response time and application availability, designate at least one domain controller in each site as the global catalog server. A global catalog server in each site provides users with a local computer that can service query requests for their domain over LAN connections. When considering which domain controllers to designate as global catalog servers, base your decision on the ability of your network structure to handle replication and query traffic. Network traffic related to global catalog queries generally requires more network resources than normal directory replication traffic. MCSE
Off the Record As you learned in earlier chapters, domain member computers use DNS servers to locate domain controllers. Therefore, you should consider placing a DNS server in each site. If you use Active Directory integrated DNS and you already have domain controllers in each site, you could install the DNS server service on one or more domain controllers in each site. DNS record replication would follow the same replication as Active Directory. If you cannot use that option, you might choose to create standard secondary DNS servers or caching-only DNS servers in each location. MCSE Certification
To optimize replication in a multiple site environment, you might need to consider adding global catalogs for specific sites. Table 5-2 shows some reasons for adding a global catalog, along with their consequences.
