# Computer per OU average should be retrievable

Understanding the distribution density of computers across OUs helps identify:

Source: https://maester.dev/docs/tests/AD-COMP-08

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

<div class="test-byline"><div class="test-byline-avatars"><a class="test-byline-avatar test-byline-avatar--author" href="/contributors/soulemike" title="Michael Soule · Original author"><img src="https://github.com/soulemike.png" alt="Michael Soule" width="28" height="28" loading="lazy" decoding="async" /></a></div><div class="test-byline-meta"><span class="test-byline-text">Contributed by <a href="/contributors/soulemike">Michael Soule</a></span><a class="test-byline-link" href="/contributors">All contributors →</a></div></div>

<p class="test-part">Part of <a href="/docs/tests/ad">Active Directory</a> · Active Directory · Computers · <a href="/docs/tests">All checks</a></p>

```powershell title="Run this check"
Invoke-Maester -TestId AD-COMP-08
```

## Overview

Understanding the distribution density of computers across OUs helps identify:

- **Overloaded OUs**: OUs with too many computers may indicate poor structure or policy bottlenecks
- **Underutilized OUs**: Many OUs with very few computers may indicate unnecessary complexity
- **Policy application issues**: Uneven distribution can lead to inconsistent security policy application
- **Administrative burden**: Poor structure increases management overhead

The average, minimum, and maximum computers per OU provide metrics for assessing organizational efficiency.

#### Control Type

**Operational**

#### Security Recommendation

- Aim for a balanced OU structure that:
  - Supports your Group Policy design (each OU should have a clear policy purpose)
  - Enables delegated administration without excessive granularity
  - Can be easily understood and navigated by administrators
- Investigate OUs with unusually high computer counts
- Consider consolidating OUs with very few computers if they serve similar purposes
- Document the OU design rationale for future administrators

#### How the Test Works

This test groups all enabled computers by their parent container and calculates:
- Average computers per OU
- Minimum computers in any OU
- Maximum computers in any OU
- Distribution across the top containers

#### Related Tests

- `Test-MtAdComputerOUCount` - Counts the total number of OUs with computers
- `Test-MtAdComputerInDefaultContainer` - Identifies potential OU structure gaps

## Details

<details>
<summary>Every attribute of this check</summary>

| Field | Value |
| --- | --- |
| Test ID | AD-COMP-08 |
| Severity | Info |
| Suite | Active Directory |
| Product | Active Directory |
| Feature | Computers |
| Area | Infrastructure hardening |
| Resource type | OrganizationalUnit |
| MITRE ATT&CK | None |
| PowerShell test | [Test-MtAdComputerPerOUAverage](https://github.com/maester365/maester/blob/main/tests/ad/computer/Test.AD-COMP-08.ps1) |
| Services | ActiveDirectory |
| Permissions | ActiveDirectory:Ldap:computer:ReadProperty |

</details>

## Source

- Test: [`tests/ad/computer/Test.AD-COMP-08.ps1`](https://github.com/maester365/maester/blob/main/tests/ad/computer/Test.AD-COMP-08.ps1)
- Documentation: [`tests/ad/computer/Test.AD-COMP-08.md`](https://github.com/maester365/maester/blob/main/tests/ad/computer/Test.AD-COMP-08.md)