How to Configure Windows Server 2016 Disk Management

Effective disk management is fundamental to maintaining a healthy and performant Windows Server 2016 environment. Storage is the foundation of almost every server workload, and misconfigured or poorly managed disks can lead to data loss, performance bottlenecks, service outages, and security risks. Windows Server 2016 provides multiple tools for disk management: the graphical Disk Management console, the Diskpart command-line utility, and PowerShell with the Storage module. This guide covers all three approaches for common disk management tasks including initializing disks, creating partitions and volumes, managing dynamic disks, and maintaining storage health.

Understanding Disk Types and Partition Styles

Windows Server 2016 supports two disk types and two partition styles. Basic disks are the standard disk type and support the familiar partition-based storage model. Dynamic disks extend functionality to support software RAID features such as spanned volumes, striped volumes, and mirrored volumes. GPT (GUID Partition Table) is the modern partition style that supports disks larger than 2 TB and up to 128 partitions. MBR (Master Boot Record) is the legacy partition style limited to 2 TB and 4 primary partitions. For new deployments on Windows Server 2016, always use GPT partition style unless compatibility with very old systems requires MBR.

Opening Disk Management

Access the Disk Management console through several methods. Right-click the Start button and select Disk Management. Alternatively, open Server Manager, navigate to Tools, and select Computer Management, then expand Storage and click Disk Management. You can also open it directly by running diskmgmt.msc from the Run dialog.

The Disk Management console displays all connected disks, their partition style, status, size, and configured volumes. Disks that have not been initialized appear as “Not Initialized” in the bottom panel.

Initializing a New Disk

When a new disk is added to Windows Server 2016, it must be initialized before it can be used. In Disk Management, the new disk will appear with a status of “Not Initialized.” Right-click on the disk in the bottom panel and select “Initialize Disk.” Choose the partition style — GPT for disks over 2 TB or for modern deployments, MBR for legacy compatibility requirements.

To initialize a disk using PowerShell, first identify the disk number, then initialize it:

# List all disks and their status
Get-Disk | Select-Object Number, FriendlyName, OperationalStatus, PartitionStyle, Size

# Initialize a specific disk with GPT partition style
Initialize-Disk -Number 1 -PartitionStyle GPT

Creating Partitions and Volumes

After initializing a disk, create partitions and format them as volumes. In Disk Management, right-click the unallocated space on the initialized disk and select “New Simple Volume.” The New Simple Volume Wizard will guide you through specifying the volume size, assigning a drive letter or mount point, and formatting with a file system. For data volumes on Windows Server 2016, NTFS is the standard file system, though ReFS is available for specific workloads requiring higher resilience.

To create a partition and format it using PowerShell:

# Create a new partition using all available space on disk 1
New-Partition -DiskNumber 1 -UseMaximumSize -DriveLetter D

# Format the new partition as NTFS with label "Data"
Format-Volume -DriveLetter D -FileSystem NTFS -NewFileSystemLabel "Data" -Confirm:$false

To create a partition of a specific size (for example, 100 GB):

New-Partition -DiskNumber 1 -Size 100GB -DriveLetter E
Format-Volume -DriveLetter E -FileSystem NTFS -NewFileSystemLabel "Logs" -Confirm:$false

Using Diskpart for Advanced Disk Operations

Diskpart is the command-line disk management tool that provides capabilities not always available in the GUI, including converting disks between partition styles and managing disks in Windows PE environments. Open an elevated command prompt and type diskpart to enter the interactive Diskpart prompt:

diskpart
list disk
select disk 2
clean
convert gpt
create partition primary size=51200
format fs=ntfs label="AppData" quick
assign letter=F
exit

The clean command removes all partition and volume data from the selected disk — use it only on disks where you intend to destroy all existing data. The convert gpt command changes the partition style of a clean disk to GPT.

Extending and Shrinking Volumes

Windows Server 2016 supports extending volumes into adjacent unallocated space and shrinking volumes to free up space. In Disk Management, right-click a volume and select “Extend Volume” or “Shrink Volume.” Shrinking calculates the maximum amount that can be reclaimed, which may be less than expected if files are located at the end of the volume.

Use PowerShell to resize volumes programmatically:

# Get current partition size and maximum allowed size
$partition = Get-Partition -DriveLetter D
$size = Get-PartitionSupportedSize -DriveLetter D
Write-Host "Current size: $($partition.Size / 1GB) GB"
Write-Host "Max size: $($size.SizeMax / 1GB) GB"
Write-Host "Min size: $($size.SizeMin / 1GB) GB"

# Extend the volume to its maximum size
Resize-Partition -DriveLetter D -Size $size.SizeMax

Managing Disk Health and Performance

Regularly check disk health to detect early signs of hardware failure. Windows Server 2016 includes storage health monitoring through the Storage Spaces subsystem. Use PowerShell to check disk health status:

# Check health of all physical disks
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, OperationalStatus, HealthStatus, Usage, Size | Format-Table -AutoSize

Check volume health and available space across all drives:

Get-Volume | Where-Object {$_.DriveType -eq "Fixed"} | Select-Object DriveLetter, FileSystemLabel, FileSystem, Size, SizeRemaining, HealthStatus | Format-Table -AutoSize

Set up a scheduled PowerShell task that checks disk space and sends an alert when any volume falls below a defined threshold. Proactive disk space management prevents the common but catastrophic scenario of a production server running out of disk space, which can crash services, corrupt databases, and cause data loss. Regular disk health checks and proactive capacity management are essential operational practices for Windows Server 2016 administrators.