Active Directory design is often neglected during Exchange Server 2007 deployments because administrators lack the authority to make significant changes. This results in less-than-optimal performance.
Requires Free Membership to View
When you register, you’ll also receive targeted alerts from my team of editorial writers and independent industry experts with the latest news, tips, and advice to help you do your job more efficiently and effectively. Our goal is to keep you informed on the hottest topics and biggest challenges faced by Exchange professionals today working with Exchange, Outlook and other related technologies.
Margie Semilof, Editorial Director
 |
||||
|
|
|||
|
||||
This tutorial gets you one step closer to a properly designed Active Directory. Start by examining your existing architecture to ensure that it accurately represents your network topology and then ease the burden on your domain controllers.
EXCHANGE SERVER 2007 ACTIVE DIRECTORY
DESIGN CONSIDERATIONS
Home: Introduction
Reevaluate Exchange 2007 Active Directory architecture
Set-ExchangeServer cmdlet eases domain controller workloads
How NOT to overload Exchange Server 2007 domain controllers
| ABOUT THE AUTHOR: |
| Brien M. Posey, MCSE Brien M. Posey, MCSE, is a six-time recipient of Microsoft's Most Valuable Professional award for his work with Exchange Server, Windows Server, Internet Information Services (IIS), and File Systems and Storage. Brien has served as CIO for a nationwide chain of hospitals and was once responsible for the Department of Information Management at Fort Knox. As a freelance technical writer, Brien has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit Brien's personal website at www.brienposey.com. |
This was first published in May 2010