Windows Server 2012 or 2012 R2 still in production and out of support
Mainstream support is gone, ESU runs out too. What runs on it is usually a file server, a line-of-business app, or a legacy AD. Continuing without a plan is a ticking item in your processing register.
Try this first
- 1Inventory what runs on it: role, app version, users, integrations
- 2File server: migrate to SharePoint, OneDrive, or a fresh Windows Server
- 3Legacy LOB app: ask the vendor whether it runs on Server 2022 or 2025, or plan replacement
- 4AD: do not just demote a DC, plan FSMO move, replica build, decommissioning, in order
When to bring us in
For apps from vendors that no longer exist, while you stay on 2012, segment the server network-wise and pull it off the internet. Accept it as temporary and log it.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.