Exchange 2003 servers can benefit from an Active Directory design that utilizes site architecture to isolate Exchange. This is best achieved through creating a dedicated Active Directory site w...
Updated Jul 01, 2019
Version 2.0
Blog Post
Kevin,
In the case of dedicating an AD Site for Exchange, you are typically dedicating it to that sole application. Adding in additional applications that utilize the directory could potentialy increase the lookup and response times and impact Exchange (which is what you want to avoid).
IP scheme doesn't matter. Remember the AD Site topology is a logical representation of the physical. Creating a new AD site doesn't require you to change your IP subnet architecture. You can create a new AD Site and specify each server you want to reside in that site by specifying the server's IP address with a 32-bit subnet mask as the AD Site subnet.
They don't need to hold any FSMO roles.
Also, this article may help - http://www.microsoft.com/technet/itsolutions/msit/operations/adforexchangenote.mspx
Ross
In the case of dedicating an AD Site for Exchange, you are typically dedicating it to that sole application. Adding in additional applications that utilize the directory could potentialy increase the lookup and response times and impact Exchange (which is what you want to avoid).
IP scheme doesn't matter. Remember the AD Site topology is a logical representation of the physical. Creating a new AD site doesn't require you to change your IP subnet architecture. You can create a new AD Site and specify each server you want to reside in that site by specifying the server's IP address with a 32-bit subnet mask as the AD Site subnet.
They don't need to hold any FSMO roles.
Also, this article may help - http://www.microsoft.com/technet/itsolutions/msit/operations/adforexchangenote.mspx
Ross