Each AD site where Exchange 2007 exist needs a GC that is at least Windows 2003 Sp1 or later.
The following applies to domain controllers:
RODC (Read-only domain controllers)
No version of Microsoft Exchange uses read-only domain controllers or read-only global catalog servers. However, Microsoft Exchange works in environments that include read-only domain controllers or read-only global catalog servers, as long as writeable domain controllers are available. In these environments, Exchange 2007 effectively ignores read-only domain controllers and read-only global catalog servers.
Domain functional level
You should use at least Windows 2000 Server native for all domains in the Active Directory forest where you will install Exchange 2007 or that will host Exchange 2007 recipients.
Forest functional level
If you plan to use any of the following advanced features, the forest functional level must be Windows Server 2003 in each forest that contains Exchange servers:
A disjoint namespace is the scenario in which the primary Domain Name System (DNS) suffix of a computer does not match the suffix of the domain name where that computer resides. Limited tests were performed to validate Exchange 2007 on a computer that has a disjoint DNS namespace. These tests showed that any issues resulting from this configuration may be resolved by ensuring that the DNS suffix search list on an Exchange server references all DNS namespaces that are deployed within the organization. The list of namespaces should include not only Active Directory and Exchange servers, but also the namespaces for other servers with which Exchange may interoperate, such as monitoring servers or servers for third-party applications. For detailed information about supported scenarios with disjoint namespaces, see Understanding Disjoint Namespace Scenarios with Exchange 2007.
Single-label DNS names
Single-label DNS names are not recommended for use with Exchange 2007 or Exchange 2007 SP1. For additional information about single-label DNS names, see Knowledge Base article 300684, Information about configuring Windows for domains with single-label DNS names.
AD Ratios to Mailbox Servers
I had another question today on AD requirements with Windows 2008. The customer has some AD servers that
ingle-label DNS names are recommended I would say
Why Google Should Enable Exchange Support for Android Is virtualizing Microsoft Exchange Server a good
Our company is using a 3rd part appliance for DNS. I have requested them to have a windows DNS server installled. We do not have any issues at the moment. We are using Exchnage 2003 and planing to Exchnage 2007. I Have read it somewhere that a Windows DNS is required when you install Exchange 2007 but I can not seems to find the article. I was wondering if someone from your team can send me some articles explaining what will be the advantages and dis-advantages of using windows DNS and not using Windows DNS. going forward if we do not have a windows DNS in the envirnment what could be the issues.
Please email me at email@example.com
Exchange 2007 does not have a requirement for Windows Server DNS. Here are the requirements:
As long your Active Directory is happy with 3rd party DNS in place then Exchange 2007 will be happy as there is a direct relationship.
I recommend you run Exchange Best Practice Analyzer to determine if your Active Dirctory is ready for an Exchange 2007 rollout:
As far as why use Windows Server DNS vs 3rd party:
Multi-master DNS replication (no Slave/Master concept)
Secure Dynamic DNS
Background Zone loading
Other new DNS enhancements you can read about here: