Windows Server 2016 inventory analyzer
See operating-system versions and server roles, then review Windows Server 2016 exposure by role against the existing planner. Import a CSV or JSON file created from the sample schema or the read-only PowerShell snippet below.
Import an inventory file
Local processing: the selected file is read in this browser tab. The tool does not upload the file, call an API, or retain inventory after you leave or refresh this page. Treat hostnames and role data as sensitive; use a copy with names replaced if appropriate.
Try synthetic examples
Read-only local PowerShell snippet
Run this on each Windows Server host you choose to inventory. It reads the local computer only. Combine the CSV header and rows from each run into one file before importing. It does not make a remote connection or change server configuration.
Download the PowerShell snippet
What the snippet reads
Get-CimInstance Win32_OperatingSystem: Caption, Version and BuildNumber.Get-CimInstance Win32_ComputerSystem: Name (the host name).Get-CimInstance Win32_Processor: NumberOfCores for each processor; the snippet totals those physical core counts.Get-WindowsFeature: installed feature IDs, mapped only to the listed server role slugs.
ConvertTo-Csv only serializes the single row to the console. The snippet does not collect IP addresses, users, domain names, installed software, services, patch history, license keys, credentials or network shares. Exchange and application-specific workload roles are not inferred from Windows features; add a supported role slug manually to the roles field before importing. If no mapped Windows role is found, it uses application as a review placeholder.
The CSV columns are exactly serverName,osCaption,osVersion,osBuild,reportedCores,roles. The roles field uses one or more semicolon-separated slugs from the Windows Server planner, for example domain-controller;dns. Unknown columns and role slugs are rejected.
How to read the estimate
The support timeline uses the Windows Server 2016 Extended End Date listed on Microsoft Lifecycle: 12 January 2027. Microsoft displays the lifecycle timestamp as 13 January 2027 at 6:59:59 AM Pacific Time; that timestamp corresponds to the January 12 end date. The planner's per-role verdicts are starting points, not compatibility checks.
The licensing figure is only an illustrative Windows Server 2025 Standard USD 16-core list-price yardstick for imported Server 2016 rows. It applies one pack per server and rounds reported physical cores above 16 up to another pack. It does not assess editions, virtual machines, CALs, upgrade rights, Azure Hybrid Benefit, discounts, tax or the terms of a licensing agreement. It is not a quote or licensing recommendation.
Sources read 6 November 2026: Windows Server 2016 - Microsoft Lifecycle; Get-CimInstance - Microsoft Learn; Get-WindowsFeature - Microsoft Learn; Windows Server pricing and licensing - Microsoft. The dated price record is from the site's Microsoft list-price data (checked 1 November 2026).
How it works
The PowerShell snippet reads selected local operating-system, processor and installed-role fields. Import its CSV or JSON output here; parsing and estimates run in this tab only. The imported inventory is cleared when you leave or refresh.
Frequently asked questions
Does this connect to my servers?
No. The snippet reads only the computer where you run it, and the browser tool does not connect to servers or send the imported file.
Is the licensing number a quote?
No. It is a dated Microsoft list-price yardstick based on the limited fields imported, not a quote or a licensing recommendation.