Active Directory Domain Services requires a Windows Server operating system (such as Windows Server 2022 or 2025).

While Windows 11 can technically host Active Directory Domain Services via PowerShell scripting, it remains a non-server OS with severe functional limitations. For production environments, dedicated Windows Server is mandatory. However, for isolated labs, legacy software testing, or learning AD administration, the methods described provide a viable, low-resource solution. Administrators should always prefer virtualization (e.g., running Windows Server in Hyper-V on Windows 11) over installing AD DS directly on the host client OS.

The system will automatically restart and become a domain controller for the lab.local forest.

While Microsoft Windows 11 is classified as a client operating system (OS) and is not designed to be a domain controller, it is possible to install the Active Directory Domain Services (AD DS) role for development, lab, or legacy compatibility purposes. This paper outlines the technical prerequisites, the step-by-step process using the Remote Server Administration Tools (RSAT) and manual installation methods, and the critical limitations of running AD DS on Windows 11.

Before proceeding, the following conditions must be met: