How to Check If Your Windows PC Is Joined to a Domain

Isabella Shinn

Updated: May 26, 2025

There is no need to worry! This article will walk you through 4 methods to check domain membership status in Windows.

• Using the System Properties GUI (Easy)
• Using Command Prompt (systeminfo) (Quickest)
• Using PowerShell (Pro)
• Using Task Manager (User Tab)
• Why Does It Matter?
• TL;DR

Using the System Properties GUI (Easy)

Step 1Press Win + R, type the following command, and press Enter.

sysdm.cpl

Step 2In the System Properties window, go to the Computer Name tab and Click Change.

Step 3Look at the "Domain" section:

• If it says something like Domain: corp.example.com, your PC is domain-joined.
• If it says Workgroup: WORKGROUP, your PC is not domain-joined.

Using Command Prompt (systeminfo) (Quickest)

Step 1Open Command Prompt.

Run this command:

systeminfo | findstr /C:"Domain"

Sample output:

Domain: WORKGROUP

If the domain is listed as WORKGROUP, your PC is not part of a domain. If it shows a domain name like company.local, then it is domain-joined.

Using PowerShell (Pro)

Step 1Open PowerShell.

Step 2Run the following command:

(Get-WmiObject Win32_ComputerSystem).PartOfDomain

Step 3This returns:

• True → Your PC is joined to a domain.
• False → Your PC is not joined to a domain.

For more details you can also run this following command:

(Get-WmiObject Win32_ComputerSystem).Domain

Using Task Manager (User Tab)

Step 1Press Ctrl + Shift + Esc to open Task Manager.

Step 2Go to the Users tab.

Step 3Check the format of the logged-in username:

• DOMAIN\username → Domain-joined.
• COMPUTERNAME\username → Local user account.

Why Does It Matter?

Understanding whether your device is domain-joined is essential for:

• IT troubleshooting;
• Software deployment compatibility (e.g., backup solutions via Group Policy);
• Access permissions in corporate environments;
• Policy restrictions such as login limits, app control, or security baselines.

For example, many enterprise backup and recovery solutions require domain membership to enable centralized configuration, policy-based deployment, and user role isolation.

TL;DR