Updated Active Directory Capacity Planning Guidance Available (adsizer.exe Be Gone!)
Every good Active Directory Domain Services implementation started with sizing Domain Controllers appropriately for the environment in which they needed to be able to service clients for a period of four to five years.
For years, we’ve been using adsizer.exe, a part of the Windows 2000 Resource Kit for this purpose. This tool was released for Windows 2000 Server and provides ballpark estimates for number of Domain Controllers, Active Directory Database (ntds.dit) sizes for both non-Global Catalogs and Global Catalogs, processor requirements and network bandwidth:
However, 2000 is a long time ago and all this time, adsizer.exe was never updated with the new bandwidth- and database-minimalizing technologies in newer Windows Server versions or with newer hardware configurations. (its estimates are based on Domain Controllers, equipped with Intel Pentium 2 and Pentium 3 ranging from 400 MHz to 933 MHz)
Although adsizer.exe feels quite antiquated, you can still install it on the most recent versions of Windows and Windows Server.
Last week, the Active Directory team introduced new information on sizing Domain Controllers for an Active Directory environment, titled Capacity Planning for Active Directory Domain Services.
This information is not published in the form of a new adsizer.exe or a Microsoft Excel document (as the Exchange guys seem to prefer), but instead as an online resource, accessible without any required download.
I’m excited with this new information, since capacity planning guidance for scale-up systems in general has changed dramatically in the last years.. Changes in system architectures, such as the change from 32-bit to 64-bit server platforms, virtualization versus non-virtualized scenarios, attention to power consumption, the industry moving from spindle-based to SSD storage, and cloud scenarios have challenged fundamental assumptions about designing and scaling a service. The new information, thus, contains pointers to size virtualized Domain Controllers, to analyze the impact of multiple cores and hyper threading and to determine required iops to choose between normal spindle-based disks and SSDs.
When sizing Windows Server 2012-based Domain Controllers, use the information on TechNet to perform capacity planning for Active Directory Domain Services.
Related KnowledgeBase Articles
Windows 2000 Resource Kit Tools for administrative tasks
Active Directory Sizer
Updated Active Directory capacity planning guidance published
Microsoft Adsizer tool works out your Active Directory domain
Active Directory Sizing tool for Windows 2008 R2
Active Directory Sizer Tool