PowerShell for Windows Server Administration: Commands, Help, Modules &
Practical Guide
If you are preparing for a System Engineer, Infrastructure Engineer,
Systems Administrator, or Windows Server Administrator role, PowerShell is one
of the most useful skills you can learn.
Windows administrators
traditionally perform many tasks through graphical tools such as Server
Manager, Computer Management, Active Directory Users and Computers, Event
Viewer, and Control Panel. However, PowerShell provides a powerful
command-line environment that allows administrators to automate repetitive
tasks, manage servers, retrieve system information, troubleshoot problems, and
work with Microsoft technologies.
In this article, I will cover the
fundamentals of PowerShell for Windows Server Administration, including the
PowerShell versions, basic commands, help system, modules, profiles,
functions, and some practical commands that I tested during my learning.
What Is PowerShell?
PowerShell is Microsoft's command-line shell and scripting
language designed for system administration and automation.
Unlike
traditional Command Prompt, PowerShell works with objects rather than
only text.
For example:
This command retrieves running processes from the computer.
You
can then use other PowerShell commands to filter, sort, export, or manipulate
that information.
This object-based approach makes PowerShell extremely
useful for Windows administration.
Why Should a System Engineer Learn PowerShell?
PowerShell is particularly useful for system engineers and
administrators because many administrative tasks can be automated.
Some common tasks include:
- Managing Windows servers
- Managing users and groups
- Working with Active Directory
- Managing services
- Checking running processes
- Managing disks
- Checking system information
- Managing Windows features
- Working with networking
- Troubleshooting Windows
- Managing Microsoft 365
- Managing Azure resources
- Automating repetitive administrative tasks
Instead of manually performing the same task through a GUI hundreds of
times, PowerShell can often complete the task with a command or script.
Alternative Job Titles for System Engineer
When searching for IT infrastructure jobs, don't search only for System
Engineer.
Organizations may use different job titles for similar
infrastructure responsibilities.
1. Infrastructure Engineer
An Infrastructure Engineer generally works with:
- Servers
- Networking
- Storage
- Virtualization
- Cloud infrastructure
- Enterprise hardware
2. Systems Administrator
A Systems Administrator is responsible for the day-to-day administration
of systems.
Typical responsibilities include:
- User management
- Server maintenance
- Software installation
- Troubleshooting
- Backup management
- Security configuration
3. Site Reliability Engineer — SRE
An SRE focuses heavily on reliability, availability, monitoring,
automation, and software-based infrastructure management.
SRE roles generally require stronger knowledge of:
- Linux
- Cloud
- Programming/scripting
- CI/CD
- Monitoring
- Automation
4. DevOps Engineer
A DevOps Engineer works between development and operations.
Common technologies include:
- Git
- CI/CD
- Docker
- Kubernetes
- Cloud platforms
- Infrastructure as Code
- PowerShell/Bash/Python
5. Platform Engineer
Platform Engineers build and maintain internal platforms and
infrastructure used by development teams.
Checking the PowerShell Version
The first command I recommend running when learning PowerShell is:
$PSVersionTable
This displays information about the currently installed
PowerShell environment.
You can see information such as:
- PowerShell version
- Edition
- Operating system
- Compatible versions
- Platform information
For example:
The important property for beginners is:
This tells you which version of PowerShell you are currently using.
PowerShell 5.1 vs PowerShell 7
There are two important PowerShell versions you will encounter.
Windows
PowerShell 5.1
Windows PowerShell 5.1 is the traditional Windows
PowerShell version that comes with Windows.
You can normally launch it using:
- powershell.exe
- PowerShell 7
PowerShell 7 is the newer, cross-platform version of PowerShell.
You can launch it using:
PowerShell 7 can run on:
However, when working with Windows Server administration, you should
understand that PowerShell 5.1 and PowerShell 7 are not identical.
Some
older Windows administration modules were designed specifically around Windows
PowerShell 5.1.
Installing PowerShell 7 with Winget
If PowerShell 7 is not installed, you can search for it using
Windows Package Manager:
- winget search Microsoft.PowerShell
Then install it using:
- winget install --id Microsoft.Powershell --source winget
After installation, you can launch PowerShell 7 with:
You can then verify the version:
Tip: When following older Windows Server administration tutorials,
always check whether the instructor is using Windows PowerShell 5.1 or
PowerShell 7.
How to Find PowerShell Commands
- PowerShell contains thousands of commands and cmdlets.
- Trying to memorize all of them is unnecessary.
- Instead, learn how to find commands.
The most useful command is:
It displays commands available in your current PowerShell
environment.
For example:
If the output is long, you can pipe it to:
This allows you to view the results page by page.
Understanding PowerShell Verb-Noun Naming
PowerShell commands generally follow a Verb-Noun naming convention.
Examples:
- Get-Process
- Get-Service
- Get-Disk
- Get-Date
- Set-Date
- New-Item
- Remove-Item
- Start-Service
- Stop-Service
This naming convention makes PowerShell commands easier to
understand.
For example:
means:
Get information about processes.
Similarly:
means:
Get information about services.
Learning
common PowerShell verbs makes discovering commands much easier.
Getting Help in PowerShell
One of the most important skills for PowerShell administration is
knowing how to use its built-in help system.
You don't need to
remember every parameter of every command.
Instead, use:
For example:
This provides information about the Get-Process cmdlet.
You can also use:
PowerShell also supports searching for commands based on partial
names.
For example:
This can help you discover commands beginning with Set-A.
Updating PowerShell Help
PowerShell includes downloadable help documentation.
To download the latest help files, use:
This updates the help content available to PowerShell.
You
may need to run PowerShell with appropriate privileges depending on your
environment.
After updating the help files, you can use:
This is an excellent habit when learning a new cmdlet.
Practical Example: Get-Date
Let's look at a simple PowerShell command.
This displays the current date and time.
You can also control
how the output is displayed.
For example:
- Get-Date -Format "HH:mm:ss"
This displays the current time in:
Hours:Minutes:Seconds
For example:
The -Format parameter allows you to specify the desired date/time
format.
Saving PowerShell Output to a File
PowerShell
can redirect command output to a file.
For example:
- Get-Date -Format "HH:mm:ss" | Out-File C:\data\time.txt
Here we are using the pipeline:
The result is written to:
This concept becomes extremely important when creating administration
scripts and reports.
Understanding the PowerShell Pipeline
The
pipeline is one of the most powerful features of PowerShell.
The pipe symbol is:
|
It sends the output of one command to another
command.
For example:
The output from Get-Process is passed to more.
Another example:
- Get-Date -Format "HH:mm:ss" | Out-File C:\data\time.txt
The output from Get-Date is passed to Out-File.
As you
progress into PowerShell administration, you will use pipelines extensively.
Checking PowerShell History
PowerShell keeps a history of commands executed during the current
session.
Use:
This displays previously executed commands.
This is useful when:
- You forgot a command you just executed
- You want to repeat a command
- You are troubleshooting
- You are documenting your administration work
For example:
can show the commands that you recently ran.
Checking Disk Information
PowerShell also provides cmdlets for managing and inspecting
hardware resources.
For example:
This displays information about disks connected to the system.
Depending on your system, you may see information such as:
- Disk number
- Disk size
- Operational status
- Partition style
- Provisioning type
For Windows Server administration, disk management is an important area
because administrators frequently work with storage, partitions, volumes, and
file systems.
What Is a PowerShell Module?
A PowerShell module is a package that can contain:
- Cmdlets
- Functions
- Variables
- Aliases
- Other PowerShell resources
Modules extend PowerShell's capabilities.
For example, Windows administrators may use modules for:
- Active Directory
- Hyper-V
- Microsoft 365
- Azure
- Networking
- Windows administration
To see modules available in your environment, you can use:
- Get-Module -ListAvailable
To see modules currently loaded into the session:
Important clarification
A common beginner mistake is confusing Get-Module with "adding a
module."
Get-Module gets information about modules.
To load a module into the current session, you typically use:
For example:
Import-Module ActiveDirectory
What Is a PowerShell Profile?
A PowerShell profile is a script that runs when PowerShell starts.
It
can be used to store personal configuration and customizations.
For
example, you could configure your PowerShell environment so that certain
functions or aliases are automatically available whenever you start a new
session.
This gives you an important advantage:
Your settings and customizations can be loaded automatically in
future PowerShell sessions.
You can check whether a profile exists using:
You can view the profile path using:
What Is a PowerShell Function?
A function is a reusable block of PowerShell code.
Functions
are particularly useful when you repeatedly perform the same operation.
For
example:
function Get-MyComputerInfo {
Get-ComputerInfo
}
After creating the function, you can run:
Instead of repeatedly typing a complicated sequence of commands, you can
create a function and call it using a short name.
Think of a function as:
A reusable shortcut for a set of PowerShell commands.
Functions
become extremely useful as you start writing administration scripts.
PowerShell Knowledge Check
During my learning, I also reviewed some basic PowerShell questions.
1. What cmdlet is used to get information about modules?
2. What command downloads the latest PowerShell help files?
3. What is an advantage of adding a PowerShell profile?
-
A profile allows you to save configurations, functions, aliases, and other
customizations so they can be loaded automatically in future sessions.
4. What is the default Windows PowerShell version commonly associated with
Windows Server?
-
Windows PowerShell 5.1 is the built-in Windows PowerShell version on modern
Windows Server releases, although newer PowerShell versions can also be
installed separately.
5. What is a PowerShell function?
-
A function is a reusable block of PowerShell code that can simplify
repetitive or complicated operations.
PowerShell Commands I Practiced
Here is a quick summary of the commands covered in this learning
session:
My Practical PowerShell Learning
The commands covered in this article are not just theoretical concepts.
I practiced them directly in a Windows environment to understand how
PowerShell behaves and how administrators can use it for everyday system
administration.
Some of the commands I practiced included:
$PSVersionTable
Get-Command | more
Get-Help Get-Process
Update-Help
Get-Date -Format "HH:mm:ss"
Get-Date -Format "HH:mm:ss" | Out-File C:\data\time.txt
Get-History
Get-Disk
These basic commands form a good foundation before moving into more advanced
Windows Server administration.
What's Next in My PowerShell Learning?
After understanding the
fundamentals, the next step is to move from basic commands into real Windows
Server administration.
The areas I plan to explore include:
Windows Server
- Server management
- Windows services
- Event Viewer
- Windows Features
- Server roles
- Storage management
Active Directory
- Users
- Groups
- Organizational Units
- Password policies
- User management
- Group Policy
Networking
- IP configuration
- DNS
- DHCP
- Network adapters
- Firewall
- Connectivity troubleshooting
Automation
- PowerShell scripts
- Functions
- Variables
- Loops
- Conditional statements
- Error handling
- Scheduled tasks
Advanced Administration
- Remote Server Administration
- PowerShell Remoting
- Windows Server automation
- Microsoft 365 administration
- Azure administration
Conclusion
PowerShell is an essential technology for anyone
interested in Windows Server Administration, System Engineering,
Infrastructure Engineering, or IT Operations.
The most important
lesson for beginners is that you don't need to memorize thousands of commands.
Instead, learn how to discover commands, read documentation, understand
parameters, use the pipeline, and build reusable functions.
Commands such as:
- Get-Command
- Get-Help
- Get-Module
- Get-Process
- Get-Service
- Get-Disk
can become your everyday tools as a Windows administrator.
The
next step is to take these fundamentals into a practical Windows Server lab
and start managing users, groups, services, Active Directory, DNS,
DHCP, storage, networking, and Group Policy using PowerShell.
That is where PowerShell starts becoming a real
System Engineer skill, rather than simply another command-line tool.
