DNS troubleshooting in PowerShell

DNS means domain name server or system you can say that so with the help of DNS in your system whenever you will browse anything like google.com so it will resolver by dns first. It is used for translates human-readable web addresses (like google.com) into computer-readable IP addresses. Anyone around the world can use it as a free alternative to their internet service provider's default DNS server.

The IP address 8.8.8.8 is a public Google Public DNS resolver operated by Google LLC.

DNS troubleshooting with PowerShell

1. Check which DNS server your computer is using

• Get-DnsClientServerAddress

This shows the DNS servers configured on each network adapter.


For example:

  
InterfaceAlias   ServerAddresses
--------------   ---------------
Wi-Fi            {192.168.1.1}
  

2. Check DNS configuration for a specific adapter

• Get-DnsClientServerAddress -InterfaceAlias "Wi-Fi"

For Ethernet:

• Get-DnsClientServerAddress -InterfaceAlias "Ethernet"

3. Test whether DNS can resolve a hostname

This is one of the most useful commands for IT Support:

• Resolve-DnsName google.com

You should get information such as:


Name        Type   IPAddress
----        ----   ---------
google.com  A      xxx.xxx.xxx.xxx



For your AD lab, test your domain:

• Resolve-DnsName test.com

or your Domain Controller:

• Resolve-DnsName dc01.test.com

4. Test DNS using a specific DNS server

This is very useful for troubleshooting.

• Resolve-DnsName google.com -Server 8.8.8.8

You're saying:

• "Ask DNS server 8.8.8.8 to resolve this name."

You can compare it with your configured DNS server:

• Resolve-DnsName google.com -Server 192.168.1.1

This helps determine whether the problem is with the DNS server or your local configuration.

 5. Check DNS cache

• Get-DnsClientCache

This displays DNS records currently cached by the Windows DNS client.


To clear the cache:

• Clear-DnsClientCache

This is useful when troubleshooting situations where an old DNS record is being returned.

 6. Check whether a DNS server is reachable

You can test connectivity:

• Test-NetConnection 8.8.8.8 -Port 53

For your AD DNS server:

Test-NetConnection 192.168.1.10 -Port 53


Look for:

• TcpTestSucceeded : True

Important: DNS normally uses UDP 53, while Test-NetConnection -Port 53 tests TCP connectivity. So this is a connectivity check, not a complete DNS functionality test.

 7. Check the DNS client service

Windows has a DNS Client service.

• Get-Service -Name Dnscache

Example:


Status   Name       DisplayName
------   ----       -----------
Running  Dnscache   DNS Client


If necessary:

Restart-Service -Name Dnscache

Be careful with restarting services on production machines.

 A real IT Support troubleshooting scenario

Suppose a user says:

"I can connect to Wi-Fi, but I can't open websites."

Don't immediately assume it's an internet problem.

You could troubleshoot:

Step 1 — Check IP configuration

• Get-NetIPConfiguration

Step 2 — Check configured DNS

• Get-DnsClientServerAddress

Step 3 — Test DNS resolution

• Resolve-DnsName google.com

Step 4 — Test another DNS server

• Resolve-DnsName google.com -Server 8.8.8.8

Step 5 — Check DNS cache

• Get-DnsClientCache

Step 6 — Clear DNS cache if appropriate

• Clear-DnsClientCache

Then test again:

Resolve-DnsName google.com
For your Active Directory lab

This is particularly important for your System Engineer preparation.

Your lab should look roughly like:

On the Windows 10 client:

• Get-DnsClientServerAddress

Check that the DNS server points to your Domain Controller's IP, not an external DNS server such as 8.8.8.8.


Then:

• Resolve-DnsName yourdomain.local

And:

• Resolve-DnsName dc01.yourdomain.local

This is a much better lab exercise for your GitHub documentation because it demonstrates the relationship between DNS + Active Directory + Windows client troubleshooting, rather than simply showing individual commands.

Commands:

• Get-DnsClientServerAddress
• Get-DnsClientCache
• Resolve-DnsName
• Test-NetConnection
• Get-NetIPConfiguration
• Get-Service -Name Dnscache
• Clear-DnsClientCache

Software Installation Checker in Batch Scripting | Check if a Program is Installed

As an IT Support Engineer or System Administrator, you may need to verify whether a particular application is installed on a computer. Instead of searching manually, you can automate this task using a simple Batch Script.

In this tutorial, we'll create a **Software Installation Checker** that checks whether **Google Chrome** is installed on a Windows computer.

Batch Script

  
@echo off

where chrome

if %errorlevel%==0 (

echo Google Chrome Installed

) else (

echo Google Chrome Not Installed

)

pause
  

How the Script Works

#Step 1: Turn Off Command Display
@echo off


This hides the commands while the script runs, making the output cleaner.


#Step 2: Search for the Software

• where chrome

The `where` command searches for the executable file (`chrome.exe`) in the system's PATH.

• * If found, Windows displays the file location.
• * If not found, the command reports that it could not find the file.

#Step 3: Check the Result Using ERRORLEVEL

• if %errorlevel%==0 (

If the `where` command successfully finds Chrome, `ERRORLEVEL` is set to **0**.

Output:

• Google Chrome Installed
• Otherwise, the script displays:
• Google Chrome Not Installed

#Step 4: Pause the Script

• pause

This keeps the Command Prompt window open so you can read the result.

Sample Output (Installed)

• C:\Program Files\Google\Chrome\Application\chrome.exe

Google Chrome Installed
Press any key to continue . . .




Sample Output (Not Installed)

INFO: Could not find files for the given pattern(s).

Google Chrome Not Installed

Press any key to continue . . .

Why Use a Software Installation Checker?

This script helps you:

• * Quickly verify software installation
• * Save troubleshooting time
• * Avoid manual searching
• * Automate routine IT tasks
• * Simplify software audits

Checking Other Applications

You can replace `chrome` with the name of another executable.

Examples:

• where notepad
• where python
• where java
• where git
• where code

This makes the script reusable for checking different software.

Real-World Uses

IT Support Engineers use similar scripts to:

* Verify required software during system setup
* Troubleshoot missing applications
* Check developer tools
* Validate software before deployment
* Perform inventory checks

Commands Used

Interview Questions

#What does the `where` command do?

• It searches for an executable file in the directories listed in the system PATH.

#What does `ERRORLEVEL` indicate?

• It stores the result of the previously executed command.

#What does `ERRORLEVEL = 0` mean?

• The command executed successfully.

#Can this script check software other than Chrome?

• Yes. Replace `chrome` with the executable name of the software you want to check.

#Why is automation useful for software verification?

• It speeds up repetitive tasks and reduces manual effort during troubleshooting and system maintenance.

Limitations

The `where` command only finds programs whose executable files are available in the system PATH. Some installed applications may not appear if their installation directory isn't included in PATH. For those cases, more advanced methods such as checking the Windows Registry or using PowerShell are often used.

Conclusion

A Software Installation Checker is a simple yet practical Batch Scripting project that automates software verification on Windows systems. By combining the `where` command with `ERRORLEVEL`, you can quickly determine whether an application is available.

This project is an excellent addition to your Batch Scripting portfolio and demonstrates a real-world automation task that is useful for IT Support Engineers, Desktop Support Engineers, and System Administrators.

Folder Backup Automation in Batch Scripting | Automatically Backup Any Folder

Backing up important folders is one of the most common tasks performed by IT Support Engineers and System Administrators. Instead of copying files manually every day, you can automate the process with a simple Batch Script.

In this tutorial, we'll create a Folder Backup Automation script that copies a selected folder to a backup location automatically.

Batch Script

@echo off

set SourceFolder=C:\Users\%USERNAME%\Documents

set BackupFolder=D:\Backup

if not exist "%BackupFolder%" (
    mkdir "%BackupFolder%"
)

xcopy "%SourceFolder%" "%BackupFolder%\Documents" /E /I /Y

echo.
echo Folder Backup Completed Successfully.

pause

How the Script Works

#Step 1: Turn Off Command Display

@echo off

This hides the commands while the script runs, making the output cleaner.


#Step 2: Set the Source Folder

• set SourceFolder=C:\Users\%USERNAME%\Documents

The variable `SourceFolder` stores the folder you want to back up.

The `%USERNAME%` environment variable automatically inserts the name of the currently logged-in Windows user.



#Step 3: Set the Backup Location

• set BackupFolder=D:\Backup

This defines where the backup will be stored.

You can change this location to another drive or folder if needed.



#Step 4: Create the Backup Folder

if not exist "%BackupFolder%" (
    mkdir "%BackupFolder%"
)


If the backup folder doesn't already exist, the script creates it automatically.


#Step 5: Copy the Files

xcopy "%SourceFolder%" "%BackupFolder%\Documents" /E /I /Y

The `xcopy` command copies all files and folders.

#XCOPY Options

| Option | Description                                 |
|  | - |
| `/E`   | Copies all folders, including empty folders |
| `/I`   | Creates the destination folder if needed    |
| `/Y`   | Overwrites existing files without asking    |



#Step 6: Display Success Message
echo Folder Backup Completed Successfully.


This informs the user that the backup process has completed.


#Step 7: Pause the Script
pause


Keeps the Command Prompt window open until a key is pressed.

Sample Output

Folder Backup Completed Successfully.

Press any key to continue . . .

Why Automate Folder Backups?

Automating backups helps you:

• * Protect important files
• * Save time
• * Reduce manual work
• * Minimize the risk of data loss
• * Keep regular backups without repeating the same steps

Real-World Uses


IT Support Engineers and System Administrators commonly use folder backup scripts to:

* Backup user Documents before Windows reinstallation
* Copy project files to another drive
* Protect company data
* Create backups before software upgrades
* Automate daily maintenance tasks

Customize the Script

You can back up other folders by changing the `SourceFolder` variable.

Examples:

Desktop
C:\Users\%USERNAME%\Desktop


Downloads
C:\Users\%USERNAME%\Downloads


Pictures
C:\Users\%USERNAME%\Pictures


You can also change the destination folder to another drive, external USB device, or network location if accessible.

Commands Used

Interview Questions

#What does `xcopy` do?

• It copies files and folders from one location to another.

#Why is `if not exist` used?

• It checks whether the destination folder exists before creating it.

#What does `%USERNAME%` represent?

• It stores the name of the currently logged-in Windows user.

#What is the purpose of `/E` in `xcopy`?

• It copies all folders, including empty ones.

#Why should folder backups be automated?

• Automation saves time, reduces manual effort, and helps protect important data.

Conclusion

Folder Backup Automation is a practical Batch Scripting project that demonstrates how to automate one of the most common Windows administration tasks. By combining variables, folder checks, and the `xcopy` command, you can create a reliable backup solution for personal or professional use.

If you're preparing for an IT Support Engineer, Desktop Support Engineer, or System Engineer role, this project showcases your ability to automate routine maintenance tasks and is a valuable addition to your Batch Scripting portfolio.
 

IT Support Toolkit in Batch Scripting | Build Your Own Windows Troubleshooting Tool

IT Support Engineers perform many repetitive tasks every day, such as checking system information, troubleshooting network issues, opening Windows tools, and cleaning temporary files. Instead of running each command manually, you can automate these tasks using a single Batch Script.

In this tutorial, we'll build a simple **IT Support Toolkit** in Batch Scripting that displays a menu and lets you choose common troubleshooting tasks.

Batch Script

@echo off
title IT Support Toolkit
color 0A

:menu
cls
echo =====================================
echo         IT SUPPORT TOOLKIT
echo =====================================
echo.
echo 1. System Information
echo 2. Network Information
echo 3. Ping Test
echo 4. Flush DNS Cache
echo 5. Open Device Manager
echo 6. Open Task Manager
echo 7. Open Event Viewer
echo 8. Clean Temp Files
echo 9. Exit
echo.

set /p choice=Select an option (1-9): 

if "%choice%"=="1" goto systeminfo
if "%choice%"=="2" goto network
if "%choice%"=="3" goto pingtest
if "%choice%"=="4" goto flushdns
if "%choice%"=="5" goto devicemanager
if "%choice%"=="6" goto taskmanager
if "%choice%"=="7" goto eventviewer
if "%choice%"=="8" goto cleantemp
if "%choice%"=="9" exit

echo Invalid choice!
pause
goto menu

:systeminfo
systeminfo
pause
goto menu

:network
ipconfig
pause
goto menu

:pingtest
ping google.com
pause
goto menu

:flushdns
ipconfig /flushdns
pause
goto menu

:devicemanager
start devmgmt.msc
goto menu

:taskmanager
start taskmgr
goto menu

:eventviewer
start eventvwr.msc
goto menu

:cleantemp
del /q /f /s "%temp%\*.*"
echo Temporary files cleaned successfully.
pause
goto menu

How the Script Works

Step 1: Display the Main Menu

The script starts by displaying a menu with different troubleshooting options.

• 1. System Information
• 2. Network Information
• 3. Ping Test
• 4. Flush DNS Cache
• 5. Open Device Manager
• 6. Open Task Manager
• 7. Open Event Viewer
• 8. Clean Temp Files
• 9. Exit

The user enters a number to choose the required task.


Step 2: Read User Input

• set /p choice=Select an option (1-9):

The selected option is stored in the variable `choice`.


Step 3: Execute the Selected Task

The script uses IF statements to jump to the appropriate section.

Example:

if "%choice%"=="1" goto systeminfo
If the user enters **1**, the script displays detailed system information.

Features Included

1. System Information

• systeminfo

Displays:

• * Windows version
• * Computer name
• * BIOS information
• * Installed memory
• * System boot time

2. Network Information

• ipconfig

Shows:

• * IP Address
• * Default Gateway
• * Subnet Mask
• * Network Adapter Details

3. Internet Connectivity Test

• ping google.com

Checks whether the computer can reach the internet.


4. Flush DNS Cache

• ipconfig /flushdns

Clears the local DNS cache, which can help resolve certain website or name resolution issues.



5. Open Device Manager

• start devmgmt.msc

Launches Windows Device Manager.


6. Open Task Manager

• start taskmgr

Opens Task Manager to view running processes and system performance.



7. Open Event Viewer

• start eventvwr.msc

Launches Event Viewer to review Windows logs and errors.


8. Clean Temporary Files

• del /q /f /s "%temp%\*.*"

Deletes temporary files from the current user's Temp folder.

Why Build an IT Support Toolkit?

Creating a toolkit provides several benefits:

• * Saves time during troubleshooting
• * Combines multiple utilities into one script
• * Reduces repetitive work
• * Improves productivity
• * Makes common administrative tasks easily accessible

Real-World Uses

IT Support Engineers and System Administrators use similar toolkits to:

• * Diagnose user issues
• * Collect system information
• * Check network connectivity
• * Troubleshoot Windows problems
• * Perform routine maintenance
• * Speed up daily support tasks

Interview Questions

What is an IT Support Toolkit?

• It is a collection of scripts or tools that automate common troubleshooting and administrative tasks.

Which command displays system information?

• systeminfo

Which command checks internet connectivity?

• ping

What does `ipconfig /flushdns` do?

• It clears the DNS resolver cache stored on the local computer.

Why should IT professionals automate repetitive tasks?

• Automation improves efficiency, reduces manual effort, and minimizes the chance of human error.

Conclusion

An IT Support Toolkit is one of the most practical Batch Scripting projects for beginners. It combines multiple Windows commands into a single, menu-driven application that simplifies troubleshooting and routine maintenance.

If you're preparing for roles such as **IT Support Engineer**, **Desktop Support Engineer**, **Help Desk Engineer**, or **System Engineer**, this project demonstrates your understanding of Windows administration and automation. It's also an excellent addition to your GitHub repository and technical portfolio.

Network Troubleshooting Tool in Batch Scripting | Automate Basic Network Diagnostics

Network issues are among the most common problems faced by IT Support Engineers and System Administrators. Instead of running multiple commands manually, you can create a simple Batch Script that gathers important network information in one place.

In this tutorial, we'll build a **Network Troubleshooting Tool** using Batch Scripting.

Batch Script

How the Script Works

# Step 1: Display a Heading

• echo ===== NETWORK INFORMATION =====

This makes the output easier to read and identifies the purpose of the script.



# Step 2: Display IP Configuration

• ipconfig

The ipconfig command shows:

• * IP Address
• * Subnet Mask
• * Default Gateway
• * Network Adapter Details

Example:

• IPv4 Address . . . . . . : 192.168.1.10
• Default Gateway . . . . : 192.168.1.1

# Step 3: Test Internet Connectivity

• ping google.com

The ping command checks whether your system can communicate with another device or website.

Successful result:

• Reply from 142.250.xx.xx

Failed result:

Request timed out.



# Step 4: Check DNS Resolution

• nslookup google.com

The nslookup command verifies whether DNS is resolving domain names correctly.

Example:

• Name: google.com
• Address: 142.250.xx.xx

This helps identify DNS-related issues.


# Step 5: Trace the Network Path

tracert google.com


The tracert command shows the path packets take to reach a destination.

This is useful when:

• * Websites are slow
• * Connections are dropping
• * Network routes need troubleshooting

# Step 6: Keep the Window Open

pause


This allows you to review the results before the Command Prompt window closes.

Sample Output

===== NETWORK INFORMATION =====

• Windows IP Configuration
• Reply from google.com
• DNS Lookup Successful
• Tracing route to google.com

Why Use a Network Troubleshooting Tool?

Instead of running commands individually, this script:

• * Saves time
• * Collects diagnostic information quickly
• * Simplifies troubleshooting
• * Helps identify common network issues

Real-World Uses

IT Support Engineers and System Engineers use similar scripts to:

• * Verify internet connectivity
• * Check DNS resolution
• * Troubleshoot user network complaints
• * Collect diagnostic information
• * Perform initial network health checks

This type of script is especially useful during Help Desk and Desktop Support operations.

Common Commands Used

Interview Questions

# What does ipconfig do?

• It displays network configuration details such as IP address, subnet mask, and default gateway.

# What is the purpose of ping?

• It checks whether a device or website is reachable over the network.

# Why is nslookup used?

• It verifies whether DNS is resolving domain names correctly.

# What does tracert do?

• It displays the path packets take to reach a destination.

# Why should network diagnostics be automated?

• Automation saves time and helps troubleshoot issues more efficiently.

Conclusion

A Network Troubleshooting Tool is a practical Batch Scripting project that combines several important networking commands into a single script. By using ipconfig, ping, nslookup, and tracert, you can quickly gather information needed to diagnose common network problems.

For aspiring IT Support Engineers, System Administrators, and future System Engineers, this is an excellent project to practice and add to your scripting portfolio.
 

PC Health Check Script in Batch Scripting | Monitor Your Windows System

Monitoring your computer's health is an important task for every IT Support Engineer and System Administrator. Instead of checking system details manually, you can automate the process using a simple Batch Script.

In this tutorial, we'll create a PC Health Check Script that displays useful system information such as the computer name, current user, operating system details, CPU information, and installed memory.

Batch Script

  @echo off

echo ===== PC HEALTH REPORT =====

echo

hostname

echo

whoami

echo

systeminfo

echo

wmic cpu get name

echo.

wmic memorychip get capacity

pause

  

How the Script Works

Step 1: Display the Report Title

echo ===== PC HEALTH REPORT =====

This displays a heading so the output is easy to identify.



Step 2: Display the Computer Name

• hostname

This command shows the name of the computer.

Example Output

DESKTOP-ABCD123




Step 3: Display the Current Logged-in User

• whoami

Example Output

• systeminfo

• * Windows Version
• * OS Build
• * System Manufacturer
• * BIOS Version
• * Total Physical Memory
• * System Boot Time
• * Installed Hotfixes

Step 5: Display CPU Information

wmic cpu get name

This command displays the processor model.

Example Output

Intel(R) Core(TM) i5-1135G7 CPU



Step 6: Display Installed RAM

wmic memorychip get capacity
This command shows the capacity of each installed RAM module in bytes.



Example Output

• 8589934592
• 8589934592

Sample Output

• Computer Name
• Current User
• Windows Information
• CPU Information
• Memory Information
• Press any key to continue...

Real-World Uses

• * Verify computer specifications
• * Collect diagnostic information
• * Troubleshoot user issues
• * Prepare systems before upgrades
• * Generate system reports during maintenance

Commands Used

Interview Questions

What does the hostname command do?

• It displays the computer name.

What information does systeminfo provide?

• It displays operating system, hardware, memory, BIOS, and other system details.

What is the purpose of whoami?

• It shows the currently logged-in user.

Which command displays CPU information?

• wmic cpu get name

Why is a PC Health Check Script useful?

• It automates system diagnostics and quickly gathers important information for troubleshooting.

Note

The wmic command is deprecated on newer versions of Windows and may not be available on future releases. On modern Windows systems, PowerShell is the recommended tool for retrieving hardware information. However, wmic is still commonly found on many Windows 10 and Windows 11 installations, making it useful for learning Batch Scripting.

Conclusion

A PC Health Check Script is a practical Batch Scripting project that combines several built-in Windows commands into a single diagnostic tool. It helps IT professionals quickly collect system information and simplifies troubleshooting.

If you're preparing for a career in IT Support, System Administration, or System Engineering, this project is a great addition to your Batch Scripting portfolio and demonstrates your ability to automate routine system checks.
 

Windows Backup Script in Batch Scripting | Automatically Backup Your Files

Creating regular backups is one of the best ways to protect important files from accidental deletion, hardware failure, or system issues. Instead of manually copying files every time, you can automate the process using a simple Batch Script.

In this tutorial, we'll create a Windows Backup Script that automatically copies the Documents folder to a backup location.

Batch Script

@echo off

set BackupFolder=C:\

Backup if not exist "%BackupFolder%" (

mkdir "%BackupFolder%"

)

xcopy "%USERPROFILE%\Documents" "%BackupFolder%\Documents" /E /I /Y

echo Backup Completed Successfully.
pause

How the Script Works

Step 1: Turn Off Command Display

@echo off

This hides the commands while the script is running, making the output easier to read.


Step 2: Set the Backup Folder

set BackupFolder=C:\Backup

This creates a variable named BackupFolder and stores the destination path where the backup will be saved.


Step 3: Check Whether the Folder Exists

The script checks if the backup folder already exists.

• If it exists, the script continues.
• If it doesn't exist, a new folder named Backup is created automatically.

Step 4: Copy the Documents Folder

xcopy "%USERPROFILE%\Documents" "%BackupFolder%\Documents" /E /I /Y

The xcopy command copies the contents of the Documents folder to the backup location.

XCOPY Options

 The %USERPROFILE% environment variable automatically points to the current user's profile folder.

Step 5: Display Success Message

echo Backup Completed Successfully.
This lets the user know that the backup process has finished.


Step 6: Pause the Window

pause
Keeps the Command Prompt window open until a key is pressed.

Sample Output

Backup Completed Successfully.

Press any key to continue . . .

Why Use a Windows Backup Script?

Automating backups offers several benefits:

• Saves time
• Protects important files
• Reduces manual work
• Creates a consistent backup routine
• Improves data safety

Real-World Uses

System Engineers and IT Support Engineers often use backup scripts to:

• Backup user documents before system upgrades
• Protect important company files
• Create scheduled backups
• Prepare systems before maintenance
• Copy project files to a secure location

Tips

Change the backup location if needed. For example:

D:\Backup

or

E:\OfficeBackup

You can also replace the Documents folder with other folders such as:

• Desktop
• Downloads
• Pictures
• Project folders

Interview Questions

What is the purpose of the xcopy command?

• It copies files and folders from one location to another.

What does %USERPROFILE% represent?

• It is an environment variable that points to the current user's profile directory.

Why is if not exist used?

• It checks whether a folder exists before creating it.

What does the /Y option do in xcopy?

• It overwrites existing files without prompting for confirmation.

Why should System Engineers automate backups?

• Automation saves time, reduces human error, and ensures important files are backed up consistently.

Conclusion

A Windows Backup Script is a simple yet practical Batch Scripting project that automates one of the most important maintenance tasks—backing up files. By using commands like if not exist, mkdir, and xcopy, you can quickly create reliable backup scripts for personal or professional use.

If you're learning Batch Scripting for a career in IT Support or System Engineering, this is an excellent project to practice and include in your portfolio.