Skip to main content

How to Get the Full Name and Comment of a Local User in Batch

While usernames like "jdoe" or "admin_01" are easy for computers to process, they often don't tell the whole story. Windows accounts have two additional descriptive fields: the Full Name (e.g., "John Doe") and the Comment (e.g., "Temporary Contractor - Project X"). For IT administrators, being able to "Pull" these details is essential for generating clean user lists, identifying the owner of a forgotten account, or auditing the purpose of service accounts.

This guide explains how to extract and display these detailed attributes using the net user command in a Batch script.

Why Fetch Full Names and Comments?​

  • Employee Identification: Matching a cryptic SamAccountName (username) back to a real person for HR or help desk tickets.
  • Service Account Context: Reading the "Comment" field to understand which application or server is using a specific background account.
  • Reporting Clarity: Generating a staff spreadsheet where names are displayed properly rather than as login IDs.
Local vs. Domain

The net user command queries the Local computer by default. To extract the "Full Name" or "Description" from the company's central directory, you must add the /domain flag to your command.

Method 1: Using Net User (Quick Lookup)​

The basic net user query returns a block of information where you can filter for the Name and Comment fields.

@echo off
setlocal

set /p "USN=Enter Username to audit: "

if "%USN%"=="" (
    echo [ERROR] No username entered.
    pause
    exit /b 1
)

echo [PROCESS] Retrieving metadata for "%USN%"...
echo.

net user "%USN%" 2>nul | findstr /i /c:"Full Name" /c:"Comment" /c:"Account active"

if %errorlevel% neq 0 (
    echo [ERROR] User "%USN%" was not found in the local database.
    echo [TIP] For domain accounts, use: net user "%USN%" /domain
)
pause

Method 2: Extracting Attributes into Variables​

To use these names in an automated email or a larger reporting script, use a FOR loop to isolate the strings.

@echo off
setlocal

set "TARGET=Administrator"

:: Verify the user exists
net user "%TARGET%" >nul 2>&1
if %errorlevel% neq 0 (
    echo [ERROR] User "%TARGET%" not found.
    pause
    exit /b 1
)

echo [PROCESS] Looking up identity for: %TARGET%

:: Extract Full Name
set "F_NAME="
for /f "tokens=1,* delims=e" %%a in ('net user "%TARGET%" 2^>nul ^| findstr /c:"Full Name"') do (
    for /f "tokens=*" %%t in ("%%b") do set "F_NAME=%%t"
)

:: Extract Comment (first occurrence only)
set "U_COMMENT="
for /f "tokens=1,* delims=t" %%a in ('net user "%TARGET%" 2^>nul ^| findstr /c:"Comment" ^| findstr /v /c:"User comment"') do (
    for /f "tokens=*" %%t in ("%%b") do set "U_COMMENT=%%t"
)

:: Provide fallback for empty fields
if not defined F_NAME set "F_NAME=(not set)"
if not defined U_COMMENT set "U_COMMENT=(not set)"

echo.
echo [DATA] Full Name: %F_NAME%
echo [DATA] Comment:   %U_COMMENT%
echo.

pause

Creating a Professional "Identity Card" Tool​

This script allows you to enter a username and provides a clean, professional summary of their identity and account status.

@echo off
setlocal EnableDelayedExpansion

echo ============================================================
echo   Local Identity Lookup Engine
echo ============================================================

set /p "LOOKUP=Username to identify: "

if "!LOOKUP!"=="" (
    echo [ERROR] No username entered.
    pause
    exit /b 1
)

:: 1. Verify user exists
net user "!LOOKUP!" >nul 2>&1
if !errorlevel! neq 0 (
    echo [ERROR] No local account found with name "!LOOKUP!".
    echo [TIP] For domain accounts, use: net user "!LOOKUP!" /domain
    pause
    exit /b 1
)

:: 2. Display key identity fields
echo.
echo [INFO] Account details for "!LOOKUP!":
echo   -----------------------------------------
net user "!LOOKUP!" 2>nul | findstr /i /c:"Full Name" /c:"Comment" /c:"User comment" /c:"Account active" /c:"Last logon"
echo   -----------------------------------------

:: 3. Check for missing Full Name
net user "!LOOKUP!" 2>nul | findstr /c:"Full Name" | findstr /r /v "Full Name *$" >nul 2>&1
if !errorlevel! neq 0 (
    echo.
    echo [WARNING] This account has no Full Name set.
    echo [ACTION] Set one with: net user "!LOOKUP!" /fullname:"First Last"
)

echo ============================================================
pause

Common Pitfalls and How to Avoid Them​

Administrative Rights​

While standard users can often query their own "Full Name," you must run your Batch script (and CMD) as an Administrator to reliably query other users or to pull descriptions from the domain.

Blank Fields​

If an administrator didn't fill out the "Full Name" when creating the account, the field will be blank in the net user output.

SEO and UX Tip

Advise your users that if their script returns an empty variable, it means the field is truly empty in the Windows database. For professional reporting, you can add a fallback: if not defined F_NAME set "F_NAME=(not set)".

Best Practices for User Documentation​

  1. Standardize Comments: Advise your IT team to always use the "Comment" field to track who requested the account and when it should be deleted.
  2. Audit for Consistency: Use your script to loop through all net user accounts and flag any that have a blank "Full Name," as these are often abandoned or unauthorized accounts.
  3. Use for Welcome Scripts: When a user logs in, use your script to pull their "Full Name" and display a professional greeting: echo Welcome back, %F_NAME%!.
User Comments vs. Admin Comments

Note that net user actually has two separate comment fields: "Comment" (generic info) and "User Comment" (often used by legacy systems). Method 2 extracts the primary "Comment" field.

Conclusion​

Querying the full name and comments of a local user via Batch script is a critical skill for maintaining a professional and well-documented Windows environment. By programmatically extracting these descriptive attributes, you can transform cryptic usernames into meaningful identity data, simplifying help desk support, security auditing, and system reporting. This professional approach to system identification ensures that your organization's user accounts are always accurately identified and understood, providing a solid foundation for your identity management and automation strategies across the entire Windows network.

Table of Contents