--- title: "Windows Server 2016 End Of Support: Can Your CMDB Find Every Server?" description: Windows Server 2016 support ends on 12 January 2027. How to prove your CMDB has found every server still running it, and route each one to an owner. image: https://www.apexconfiguration.com/hubfs/AI-Generated%20Media/Images/Modern%20Data%20Center%20with%20Amber%20Warning%20Light.png --- [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [tel:+442080588135](tel:+442080588135)[mailto:contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [CMDB Data Quality](https://www.apexconfiguration.com/blog/tag/cmdb-data-quality)[ServiceNow](https://www.apexconfiguration.com/blog/tag/servicenow) [Vulnerability Management](https://www.apexconfiguration.com/blog/tag/vulnerability-management)[ServiceNow Discovery](https://www.apexconfiguration.com/blog/tag/servicenow-discovery) # Windows Server 2016 End Of Support: Can Your CMDB Find Every Server? [![Krzysztof Chrzanowski](https://www.apexconfiguration.com/hs-fs/hubfs/krzysztof-chrzanowski.webp?width=40&height=40&name=krzysztof-chrzanowski.webp)](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) by [Krzysztof Chrzanowski](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) 8 min read Oct 11, 2026, 9:00:00 AM Last updated on 11 Oct 2026, 09:00:00 Windows Server 2016 end of support falls on 12 January 2027. After that date Microsoft stops issuing security updates for it, unless you pay for Extended Security Updates. Your configuration management database (CMDB) can tell you where Windows Server 2016 is still running, but only if you query it properly and then test the answer against sources the CMDB didn't write. A single filter on the operating system field will give you a number. It won't tell you what that number missed. ## Key Takeaways - Windows Server 2016 extended support ends on 12 January 2027. After that, security updates stop unless the server is enrolled in the paid Extended Security Updates programme. - A single filter on the operating system field returns a believable number that is usually too low, because different sources write different values. Filter on the operating system version, 10.0.14393, as well as the name. - Four populations hide from the first report. They are servers discovery reached but couldn't log into, servers it never reached, stale records, and Windows Server 2016 inside vendor appliances. - To prove the list is complete, compare the CMDB with at least two inventories built independently of it, matching on serial number first and then host name. Publish the size of the gap alongside the register. - A register only moves if every server has an owner who is still employed. On one manufacturing estate, a patch task went to a former employee and a server was later compromised. - Sequence the upgrades from dependency data, and keep the register honest with a weekly delta report, a build gate, an exception register and a tracked gap. This article sets out the method we use to build a migration register that an infrastructure team can plan against. It covers the query, the four populations that hide from it, how to route each server to someone who will act, and the controls that stop the list decaying between now and January. ## Why the first Windows Server 2016 query returns too few servers The obvious query runs against the Windows server class and filters on an operating system value containing "2016". On most estates it returns a believable figure. On most estates that figure is too low. The operating system value is written by whichever source last updated the configuration item (CI). Discovery writes one string, Microsoft Configuration Manager writes another, and a spreadsheet loaded during the original implementation may have written a third. It's common to find "Windows 2016 Standard", "Microsoft Windows Server 2016 Datacenter" and "Win2016" sitting in the same table. Filter on the operating system version as well as the name. Windows Server 2016 reports build 10.0.14393, and that value is far more consistent than the free-text name. Run both filters side by side. Any server that matches one and not the other is a normalisation problem, and it's worth fixing before the number goes anywhere near a steering group. Then look at classification. The query only sees servers in the Windows server class. A machine that discovery could reach but couldn't log into sits somewhere more generic, with no operating system recorded at all. ## Four populations that won't show up in the first report Each of these needs its own check. None of them will surface by refining the original query. | Population | Why it hides | How to find it | | --- | --- | --- | | Servers discovery reached but couldn't log into | A failed credential leaves the device classified from a port scan alone, in a generic computer class with no operating system | Report on CIs in the generic computer class discovered recently, then read the discovery error log for authentication failures against those addresses | | Servers discovery never reached | An address range missing from the schedules, or a network segment with no discovery server able to see it | Reconcile the CMDB against hypervisor, cloud and Configuration Manager inventories | | Stale records | The server was upgraded or retired, but the CI still carries old values from a source that no longer runs | Flag any operational Windows server that has missed two consecutive discovery cycles | | Windows Server 2016 inside vendor appliances | Recorded by product name, with the underlying operating system never captured | Check support contracts and ask vendors directly, then record the answer against the CI | The appliance group is the one teams forget. Storage management consoles, building management systems and some broadcast and manufacturing control systems run on a Windows Server build the vendor chose years ago. You may not be allowed to patch them yourself, but you still need to know they exist and who is accountable for them. ## Proving the Windows Server 2016 list is complete A CMDB can't audit itself. To prove coverage, compare the CMDB server population against at least two inventories that were built independently of it. The hypervisor inventory is usually the most reliable for virtual servers. For cloud-hosted machines, the Service Graph Connectors for Microsoft Azure and Amazon Web Services bring instance data in through the Identification and Reconciliation Engine, so the records share identifiers with discovery. Microsoft Configuration Manager is a strong third source for anything it manages, and it has its own Service Graph Connector. Match on serial number first, then on host name. Sort every server into one of four groups: - In the CMDB and in the independent inventories - In the inventories but missing from the CMDB - In the CMDB but in none of the inventories - In one inventory only The second group is your hidden population. The third is a mix of stale records and genuinely physical servers that no hypervisor knows about, and you'll need to tell the two apart before January. Publish the size of the gap alongside the register. A migration plan for a known count of servers, with a stated number still unaccounted for, is far more defensible than a plan that implies the count is complete. ## Routing each server to someone who will act A register only moves if every line has an owner who is still employed and still responsible. That sounds obvious. It's where end-of-support programmes quietly stall. On one manufacturing estate of around four million CIs, ownership was held on technical services and cascaded down to the servers beneath them. Nobody had built an off-boarding step into that process. Several listed owners had left the organisation. When a vulnerability was found in the software the organisation used to move large data files between sites, the patching tasks went to one of those former employees. The servers stayed unpatched. One was later compromised, an attacker got into the network, data was stolen, and the incident made national news. The fix had three parts. We helped the client design an off-boarding process that reassigned ownership before an account was disabled. We put certification in place for critical ownership data, with unanswered tasks escalating to the owner's manager. Then we audited ownership against the human resources system and ran a six-month clean-up of missing and incorrect owners. For Windows Server 2016 you don't need the whole programme before January. Run two checks this week: 1. Compare the owner and support group on every server in the register against active users and active groups. Any server owned by an inactive account goes straight to the configuration manager for reassignment. 2. Run a certification campaign in CMDB Data Manager scoped to the register, asking each owner to confirm the server is theirs and still needed. Escalate anything unanswered after a week. The second check also surfaces decommissioning candidates. A server nobody will claim is often a server nobody uses. We go further into this in our article on [what happens when CI owners leave](https://www.apexconfiguration.com/blog/succession-planning-for-ci-ownership-what-happens-when-owners-leave). ## Sequencing the upgrades from dependency data Not every Windows Server 2016 machine carries the same risk. The relationships in the CMDB tell you which ones matter most, provided they exist. Pull every application service that depends on a server in the register. Sort the servers by the criticality of the highest-rated service above them. That gives you an upgrade order the business can understand, and a basis for arguing about change windows. Then look at the servers with no upstream relationships at all. They fall into two groups, and the difference matters. Some are genuinely unused and can be retired, which is the cheapest migration there is. Others support something important that was simply never mapped. Treat every unrelated server as the second kind until its owner proves otherwise. Raise each upgrade as a change against the CI itself. Change impact analysis will then use the same relationships you used to plan, and any gap in the map shows up as an incident you can trace, instead of a mystery. Servers that can't move in time are candidates for Extended Security Updates. That's a paid bridge, so each one should carry a named owner, a recorded decision and a target date for leaving the programme. Record the decision against the CI so it doesn't live only in a spreadsheet. ## Keeping the register honest until January A register built in September is out of date by November if nothing maintains it. Four controls keep it current. **A weekly delta report.** Servers added to or removed from the Windows Server 2016 population since last week, with the source that made the change. Unexpected additions usually mean a discovery range has just been fixed, or someone has built a new server from an old template. **A build gate.** Any change that creates a new server on Windows Server 2016 after a date you choose goes to the change advisory board with a justification. Old templates have a habit of outliving their deadline. **An exception register.** Appliances, vendor-controlled systems and anything on Extended Security Updates sit in one list, each with an owner and a review date. They stay inside the count instead of disappearing from it. **A key performance indicator (KPI) that tracks the gap.** The difference between the CMDB count and the independent inventory count, reported weekly. If it isn't falling, the register is still missing servers. After 12 January, keep watching vulnerability scanner detections that don't match any CI. Each one is a host the scanner has seen and the CMDB hasn't. Our article on [how bad CMDB data leads to false patch compliance](https://www.apexconfiguration.com/blog/false-patch-compliance-cmdb-data) covers that reconciliation in detail. ## How Apex helps Our two-week CMDB health baseline scores which of your CIs are trustworthy and which are guesses. For an end-of-support programme, that tells you whether your Windows Server 2016 count can be believed, which classes and sources are dragging it down, and which owners are no longer valid. The output is a scored report you can take to your change advisory board. Where the gap between the CMDB and your independent inventories is large, our discovery and integration coverage review traces it back to the address ranges, credentials and integrations that caused it. It's scoped at the initial consultation against your estate and requirements. You can [book a CMDB diagnostic call](https://www.apexconfiguration.com/cmdb-diagnostic-call) to talk through your Windows Server 2016 register, or [book a meeting](https://www.apexconfiguration.com/book-a-meeting) with one of our consultants. ## Frequently asked questions ### When does Windows Server 2016 end of support happen? Extended support ends on 12 January 2027. After that, Microsoft stops releasing security updates for Windows Server 2016 unless the server is enrolled in the paid Extended Security Updates programme. Mainstream support ended in January 2022. ### How do I find Windows Server 2016 servers in ServiceNow? Filter the Windows server class on both the operating system name and the operating system version, which is 10.0.14393 for Windows Server 2016. Then check the generic computer class for machines discovery reached but couldn't log into, and reconcile the result against your hypervisor, cloud and Configuration Manager inventories. ### Why doesn't my CMDB count match Microsoft Configuration Manager? Each source sees a different part of the estate and writes values in its own format. Discovery credential failures, duplicate CIs and stale records all move the CMDB count in different directions. Matching on serial number and host name shows you which servers sit in which source, and why. ### Should we buy Extended Security Updates? That's a commercial decision for each server that can't be upgraded in time, and it's worth making one server at a time. Record the decision, the owner and a target exit date against the CI, so the cost stays visible and the server doesn't slip out of the migration plan. ### What about Windows Server 2016 inside vendor appliances? Patching is usually the vendor's responsibility under the support contract, but the risk still sits with you. Record the appliance as a CI with its underlying operating system, a named owner and the vendor's stated plan, so it stays visible in your vulnerability and change processes. *Written by Krzysztof Chrzanowski, Apex Configuration Group.* Book a free call to discuss how Apex can help you on your journey to a better CMDB   [![\CMDB Diagnostic Call\](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/147949153/interactive-378363509978.png)](https://www.apexconfiguration.com/hs/cta/wi/redirect?encryptedPayload=AVxigLLKjVMwrHcs6KKhcQzg6fb0qncXqXXvD6eUhadlDSsjnOUAucvFqHGwtwBhyf5hU3xt0V9WHXVEk%2BKriSDXjbN%2BF8qISs9jmWTbJxbCSCS0n8f649O4ocPSWcTeINN6TtbqU4W56ts%2FfpfUfK8guUbUQ%2BCZ1ZAtjlp%2Bv7otvZB2KYufPKO6coAShY1RxrjLoyCD1IviGONx264pYYSWJcEBHAH1DxG7BUXH0UMZ0wE%3D&webInteractiveContentId=378363509978&portalId=147949153) - Recent - Topics - Archive Recent ### Recent Topics ### Topics - [ServiceNow (37)](https://www.apexconfiguration.com/blog/tag/servicenow) - [CMDB (28)](https://www.apexconfiguration.com/blog/tag/cmdb) - [CMDB Data Quality (12)](https://www.apexconfiguration.com/blog/tag/cmdb-data-quality) - [Case Studies (6)](https://www.apexconfiguration.com/blog/tag/case-studies) - [Change Management (5)](https://www.apexconfiguration.com/blog/tag/change-management) - [Duplicate CIs (5)](https://www.apexconfiguration.com/blog/tag/duplicate-cis) - [Service Mapping (5)](https://www.apexconfiguration.com/blog/tag/service-mapping) - [CI Ownership (4)](https://www.apexconfiguration.com/blog/tag/ci-ownership) - [Compliance & Audit (4)](https://www.apexconfiguration.com/blog/tag/compliance-audit) - [IT Governance (4)](https://www.apexconfiguration.com/blog/tag/it-governance) - [Incident Management (4)](https://www.apexconfiguration.com/blog/tag/incident-management) - [ServiceNow Discovery (4)](https://www.apexconfiguration.com/blog/tag/servicenow-discovery) - [Vulnerability Management (4)](https://www.apexconfiguration.com/blog/tag/vulnerability-management) - [Agentic AI (3)](https://www.apexconfiguration.com/blog/tag/agentic-ai) - [Data Model Design (3)](https://www.apexconfiguration.com/blog/tag/data-model-design) - [Enterprise Risk Management (3)](https://www.apexconfiguration.com/blog/tag/enterprise-risk-management) - [IRE (3)](https://www.apexconfiguration.com/blog/tag/ire) - [Problem Management (3)](https://www.apexconfiguration.com/blog/tag/problem-management) - [Service Graph Connectors (3)](https://www.apexconfiguration.com/blog/tag/service-graph-connectors) - [Configuration Management (2)](https://www.apexconfiguration.com/blog/tag/configuration-management) - [Cyber Security (2)](https://www.apexconfiguration.com/blog/tag/cyber-security) - [Dependency Views (2)](https://www.apexconfiguration.com/blog/tag/dependency-views) - [IT Cost Optimisation (2)](https://www.apexconfiguration.com/blog/tag/it-cost-optimisation) - [Manufacturing (2)](https://www.apexconfiguration.com/blog/tag/manufacturing) - [Broadcast & Media (1)](https://www.apexconfiguration.com/blog/tag/broadcast-media) - [CI Reconciliation (1)](https://www.apexconfiguration.com/blog/tag/ci-reconciliation) - [CMDB Remediation (1)](https://www.apexconfiguration.com/blog/tag/cmdb-remediation) - [CSDM (1)](https://www.apexconfiguration.com/blog/tag/csdm) - [IT Asset Management (1)](https://www.apexconfiguration.com/blog/tag/it-asset-management) - [ITOM (1)](https://www.apexconfiguration.com/blog/tag/itom) - [Managed Services (1)](https://www.apexconfiguration.com/blog/tag/managed-services) - [Operational Efficiency (1)](https://www.apexconfiguration.com/blog/tag/operational-efficiency) - [ServiceNow Advisory (1)](https://www.apexconfiguration.com/blog/tag/servicenow-advisory) See all Archive ### Archive - [October 2026 (10)](https://www.apexconfiguration.com/blog/archive/2026/10) - [September 2026 (16)](https://www.apexconfiguration.com/blog/archive/2026/09) - [August 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/08) - [July 2026 (4)](https://www.apexconfiguration.com/blog/archive/2026/07) - [June 2026 (3)](https://www.apexconfiguration.com/blog/archive/2026/06) - [May 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/05) See all ### Subscribe by email Share this [Share on X](https://x.com/intent/post?url=https://www.apexconfiguration.com/blog/windows-server-2016-end-of-support-can-your-cmdb-find-every-server&text=Windows+Server+2016+End+Of+Support%3A+Can+Your+CMDB+Find+Every+Server%3F) [Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https://www.apexconfiguration.com/blog/windows-server-2016-end-of-support-can-your-cmdb-find-every-server&t=Windows+Server+2016+End+Of+Support%3A+Can+Your+CMDB+Find+Every+Server%3F) [Share on LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https://www.apexconfiguration.com/blog/windows-server-2016-end-of-support-can-your-cmdb-find-every-server&t=Windows+Server+2016+End+Of+Support%3A+Can+Your+CMDB+Find+Every+Server%3F) Previous story [← Known Errors Need CIs: Stopping The Same Outage Twice](https://www.apexconfiguration.com/blog/known-errors-linked-cis) ![Krzysztof Chrzanowski](https://www.apexconfiguration.com/hs-fs/hubfs/krzysztof-chrzanowski.webp?width=64&height=64&name=krzysztof-chrzanowski.webp) By [Krzysztof Chrzanowski](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) Co-owner and Operations Director at Apex Configuration Group, based in Wrocław, Poland. Before co-founding Apex, Krzysztof worked as a Senior Configuration Manager (CMDB) at Warner Bros. Discovery,… [Full profile & credentials →](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) ### Get Email Notifications [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png)](https://www.apexconfiguration.com/) ServiceNow CMDB specialists delivering enterprise-grade implementation, remediation, and managed services. Address: 20 Wenlock Road, London, England, N1 7GU VAT Number: 505 0347 31 Company Number: 15871442 Email: [contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [Follow Apex Configuration Group on LinkedIn](https://www.linkedin.com/company/apex-configuration-group) Services - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - [Health Dashboard & Reporting](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) Company - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - [About](https://www.apexconfiguration.com/about-apex) - [Blog](https://www.apexconfiguration.com/blog) Resources - [Contact Us](https://www.apexconfiguration.com/contact-us) - [CMDB Diagnostic Call](https://www.apexconfiguration.com/cmdb-diagnostic-call) - [Book A Meeting](https://www.apexconfiguration.com/book-a-meeting) © 2026 Apex Configuration Group. All rights reserved. ServiceNow is a trademark of ServiceNow, Inc. We are not affiliated with or endorsed by ServiceNow. - [Terms](https://www.apexconfiguration.com/terms) - [Cookies](https://www.apexconfiguration.com/cookie-policy) - [Privacy](https://www.apexconfiguration.com/privacy-policy) ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#organization", "@type" : [ "Organization", "ProfessionalService" ], "address" : { "@type" : "PostalAddress", "addressCountry" : "GB", "addressLocality" : "London", "addressRegion" : "England", "postalCode" : "N1 7GU", "streetAddress" : "20 Wenlock Road" }, "alternateName" : "Apex Configuration Group", "areaServed" : "GB", "contactPoint" : { "@type" : "ContactPoint", "areaServed" : "GB", "availableLanguage" : "en", "contactType" : "customer service", "telephone" : "+44 20 8058 8135" }, "identifier" : { "@type" : "PropertyValue", "propertyID" : "UK Companies House company number", "value" : "15871442" }, "image" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/Configuration-data.webp", "legalName" : "Apex Configuration Group Ltd", "logo" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png", "name" : "Apex Configuration Group Ltd", "sameAs" : [ "https://www.linkedin.com/company/apex-configuration-group", "https://find-and-update.company-information.service.gov.uk/company/15871442", "https://www.crunchbase.com/organization/apex-configuration-group-ltd" ], "telephone" : "+44 20 8058 8135", "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#website", "@type" : "WebSite", "inLanguage" : "en-GB", "name" : "Apex Configuration Group", "publisher" : { "@id" : "https://www.apexconfiguration.com/#organization" }, "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@type" : "WebPage", "description" : "Windows Server 2016 support ends on 12 January 2027. How to prove your CMDB has found every server still running it, and route each one to an owner.", "inLanguage" : "en-GB", "name" : "Windows Server 2016 End Of Support: Can Your CMDB Find Every Server?", "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" }, "url" : "https://www.apexconfiguration.com/blog/windows-server-2016-end-of-support-can-your-cmdb-find-every-server" } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/", "name" : "Home", "position" : 1 }, { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/blog/windows-server-2016-end-of-support-can-your-cmdb-find-every-server", "name" : "Windows Server 2016 End Of Support: Can Your CMDB Find Every Server?", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Krzysztof Chrzanowski", "sameAs" : [ "https://www.linkedin.com/in/krzysztof-chrzanowski-cmdb/" ], "url" : "https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski" }, "dateModified" : "2026-10-11T08:00:00+0000", "datePublished" : "2026-10-11T08:00:00+0000", "headline" : "Windows Server 2016 End Of Support: Can Your CMDB Find Every Server?", "image" : [ "https://147949153.fs1.hubspotusercontent-eu1.net/hubfs/147949153/AI-Generated%20Media/Images/Modern%20Data%20Center%20with%20Amber%20Warning%20Light.png" ], "mainEntityOfPage" : { "@id" : "https://www.apexconfiguration.com/blog/windows-server-2016-end-of-support-can-your-cmdb-find-every-server", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" } } ```