# DCs with all FSMO roles count should be retrievable

FSMO (Flexible Single Master Operations) roles are critical directory services operations that can only be performed by one domain controller at a time:

Source: https://maester.dev/docs/tests/AD-DC-05

<!-- 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 · Domain controllers · <a href="/docs/tests">All checks</a></p>

```powershell title="Run this check"
Invoke-Maester -TestId AD-DC-05
```

## Overview

FSMO (Flexible Single Master Operations) roles are critical directory services operations that can only be performed by one domain controller at a time:

- **Schema Master**: Controls schema updates
- **Domain Naming Master**: Controls domain additions/removals
- **PDC Emulator**: Primary DC for backward compatibility
- **RID Master**: Allocates relative IDs for SIDs
- **Infrastructure Master**: Handles cross-domain object references

Concentrating all 5 FSMO roles on a single DC creates a single point of failure. While not a direct security issue, it impacts:

- **Availability**: If the FSMO role holder fails, certain operations cannot be performed
- **Disaster recovery**: All critical roles are in one location
- **Maintenance**: Updates to the FSMO holder require careful planning

#### Control Type

**Operational**

#### Security Recommendation

Consider distributing FSMO roles across multiple domain controllers for redundancy:

- Place Schema Master and Domain Naming Master in the forest root domain
- Place PDC Emulator, RID Master, and Infrastructure Master in each domain
- Ensure at least one FSMO role holder is in a different physical location
- Document FSMO role locations and transfer procedures

#### How the Test Works

This test identifies which domain controllers hold FSMO roles and counts how many DCs hold all 5 roles. It displays:
- Current FSMO role holders
- Number of unique DCs holding roles
- Whether any single DC holds all roles

#### Related Tests

- `Test-MtAdDcFsmoRoleHolderDetails` - Detailed FSMO role distribution
- `Test-MtAdDomainControllerCount` - Total DC count

## Details

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

| Field | Value |
| --- | --- |
| Test ID | AD-DC-05 |
| Severity | Info |
| Suite | Active Directory |
| Product | Active Directory |
| Feature | Domain controllers |
| Area | Infrastructure hardening |
| Resource type | DomainController |
| MITRE ATT&CK | None |
| PowerShell test | [Test-MtAdDcAllFsmoRolesCount](https://github.com/maester365/maester/blob/main/tests/ad/domain-controller/Test.AD-DC-05.ps1) |
| Services | ActiveDirectory |
| Permissions | ActiveDirectory:Ldap:domainDNS:ReadProperty, ActiveDirectory:Ldap:nTDSDSA:ReadProperty, ActiveDirectory:Ldap:crossRef:ReadProperty |

</details>

## Source

- Test: [`tests/ad/domain-controller/Test.AD-DC-05.ps1`](https://github.com/maester365/maester/blob/main/tests/ad/domain-controller/Test.AD-DC-05.ps1)
- Documentation: [`tests/ad/domain-controller/Test.AD-DC-05.md`](https://github.com/maester365/maester/blob/main/tests/ad/domain-controller/Test.AD-DC-05.md)
