TL;DR: Semperis's analysis of Active Directory migration cutovers finds some service and machine accounts keep working in the source domain while failing in AES-default targets because standard tooling copies NTLM hashes without regenerating AES keys. Identity teams need to validate key material and dependencies before cutover to avoid Kerberos failures.
Editorial analysis by NHI Mgmt Group, based on content published by Semperis: “RC4 and AD Migration: Uncover the Break Scenarios Hiding in Your Source Domain”.
Key questions
Q: Why do RC4-to-AES cutovers create outage risk in Active Directory migrations?
A: They change the enforcement baseline at the same moment identities cross domains.
Q: How can teams tell whether an RC4 dependency is real or just hidden by steady-state use?
A: Look for accounts that authenticate successfully only because their tickets are already cached or because they rarely re-authenticate.
Q: What breaks when service accounts are migrated without regenerating AES keys?
A: Kerberos authentication can fail even when the account still exists, has the right group membership, and appears to support AES.
Practitioner guidance
- Inventory service accounts by key-state, not just attribute-state Check whether accounts with AES bits set actually have AES keys in the target domain, and prioritise old or never-reset accounts first.
- Correlate directory data with Kerberos event evidence Use authentication and service-ticket events to find accounts that claim AES support but still request RC4, then validate those identities before cutover.
- Map migration-specific dependencies by application and host Walk Linux, Java, appliance, and trust-based dependencies to find keytabs, hardcoded encryption settings, and other RC4-pinned paths that AD queries will not reveal.
Bottom line: The article’s core risk is a Kerberos mismatch where migrated accounts still look valid in Active Directory but fail once the target domain enforces AES expectations.
Glossary terms: Kerberos Key Material, AES-Default Domain, RC4 Dependency, Key-State Validation
What's in the full article
Semperis' full analysis covers the operational detail this post intentionally leaves for the source:
- A six-phase discovery methodology for finding RC4-dependent accounts before cutover
- PowerShell and event-log query examples for separating configuration drift from real authentication failures
- The account types and environment patterns that most often surface breakage during migration
- Practical guidance on where to start this week if your migration crosses the July 2026 enforcement deadline
👉 Read Semperis' analysis of RC4-to-AES migration risk in Active Directory cutovers →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →