SAMPLE-WSEOS-01 · FICTIONAL DATE 2026-01-12
Example Workshop Ltd · Windows Server End-of-Support Review
Status: Fictional format sample · Domain label: example.test (reserved fictional domain; no real organisation) · Method: read-only review of supplied evidence; no live access.
Scope
41 fictional servers: roles, versions, dependencies and a suggested order, from an inventory supplied by the administrator.
Executive summary
Eleven servers run Windows Server 2016, including both domain controllers, which hold all five FSMO roles. The order matters: identity and name services first, then file and print, then applications and databases together. Seven applications have no vendor statement for a newer Windows Server version.
Evidence reviewed
| ID | Source | Coverage | Status |
|---|---|---|---|
| E-01 | Server inventory export | 41 servers, versions and roles | Provided |
| E-02 | Application owner sheet | 12 applications | Provided |
| E-03 | Vendor support statements | 5 of 12 applications | Partial |
| E-04 | Licence summary | Windows Server and SQL Server | Provided; summary only |
| E-05 | Backup job report | 30 days | Provided |
What was not checked
- Server configuration
- Network paths and firewall rules
- Application code and compatibility
- Prices or quotes from any supplier
Findings
Severity: High means fix first; Medium means plan soon; Low means tidy up.
| ID | Severity | Finding | Evidence | Recommended next step |
|---|---|---|---|---|
| F-01 | High | 11 servers on Windows Server 2016, including 2 domain controllers | E-01 | Map each to its lifecycle date and schedule moves in the order in the plan; check the current Microsoft lifecycle page. |
| F-02 | High | Both domain controllers are on 2016 and hold all FSMO roles | E-01 | Promote new domain controllers by clean install, move roles, then demote the old ones, as Microsoft recommends. |
| F-03 | Medium | The file server name is hard-coded in 14 drive mappings and 9 scripts | E-02 | Document every reference before moving, and plan a name and redirection strategy. |
| F-04 | Medium | 7 of 12 applications have no vendor statement for a newer Windows Server version | E-03 | Obtain vendor statements; move those applications last or plan a test. |
| F-05 | Medium | Print server has 60 queues with old drivers | E-01 | Review which queues are used and plan driver replacement before the move. |
| F-06 | Low | No restore test for 3 of the servers in scope | E-05 | Run a restore test before each move and record the result. |
Fix first
- Plan the domain controller replacement Effort: Medium.
- Collect vendor statements for the 7 applications Effort: Low.
- Inventory references to the file server name Effort: Low.
- Decide on extended security updates versus migration for the last servers Effort: Medium.
- Restore-test the 3 servers Effort: Low.
30/60/90-day plan
- First 30 days: Confirm lifecycle dates; collect vendor statements; reference inventory for file and print.
- By 60 days: Replace the domain controllers; move DHCP, DNS and the file server under change control.
- By 90 days: Move print, then applications and databases; decide on any bridging for servers that cannot move in time.
Customer decision
- Approval: this sample authorizes no changes; no remediation was performed.
- Limit: findings reflect only the evidence listed above, as supplied at the time.
Limitations
This fictional sample demonstrates format, not a real assessment. It contains no real customer data, gives no security or compliance guarantee, and made no change to any system.