Skip to content
Lambert Consulting

Artificial Intelligence: A Cross-Functional Offering

Results first. Infrastructure second.

An assistant for your documents, end-of-line verification, a platform for multiple services. Where artificial intelligence is applied is determined by your data, not by a catalog.

See all solutions
4Comparing Architectures, Criterion by Criterion
2 fieldsSoftware and hardware under one roof
All Use CasesUse cases first, technology last

Our first department

This is what needs to work every morning.

Your servers, your workstations, your phone systems, and your identities. The foundation that no one notices as long as it holds, but that everyone notices the day it fails.

View the department
Multi-siteNational and international projects
3Branches in French-speaking Switzerland
View our client projectsCase Studies and References
Let us know how you're doingGetting a quote is free

How We Work

A piece of advice, not a sales pitch.

Our approach is consultative: we tell you what we think, even when it’s not in our best interest. That’s what makes projects succeed.

About Us
1995First project, using Microsoft SMS
Family-orientedOn a human scale and sustainable

Our Branches

Vaud, headquarters9 Avenue des Baumettes, 1020 Renens+41 21 806 37 15
Valais134 Oscar-Bider Street, 1950 Sion+41 27 552 00 22
FribourgChemin de Montmoirin 18a, 1618 Châtel-Saint-Denis+41 26 322 59 05
Monday through Friday8:00 a.m. – 6:00 p.m.
Contact UsFirst 30-minute consultation, with no obligation

Windows Server 2022 will no longer be supported on October 13, 2026

On October 13, 2026, Windows Server 2022 will transition from mainstream support to extended support. This does not mean the end of support, and it’s important to make that clear from the outset: security updates will continue to be released, free of charge, for several more years. What ends on that date is everything else—and “everything else” matters more than you might think when planning an infrastructure over a five-year period.

Publication Date
4 minReading time
Azure and infrastructureBlog post

What exactly stops?

Under extended support, Microsoft no longer releases new features, accepts requests for enhancements, or provides non-security-related fixes free of charge. Performance issues, incompatibilities with newer hardware, or annoying but non-critical behavior will no longer be addressed without a specific contract.

The same transition to extended support takes effect on the same day Windows Server 2022 Datacenter: Azure Edition and Windows Server IoT 2022. Office LTSC 2021 for Mac also reaches October 13, 2026, but it will no longer be supported at that point: security updates will end on that date.

Why does that change a decision, when nothing breaks?

A server on extended support is perfectly functional. That's not the problem—the problem is what you won't be able to do with it anymore.

Three consequences occur in this order, and rarely any sooner:

New hardware. A physical server purchased in two years will include components whose drivers are designed for recent systems. There is no requirement for a manufacturer to certify a version that no longer receives functional patches.

Third-party software. Our take: Software vendors generally align their compatibility matrices with the current version. A new version of your backup, monitoring, or security solution may no longer be certified Windows Server 2022 long before Microsoft discontinues it.

Expected capabilities. Any infrastructure feature announced after October 2026 will not be included in this release. If your three-year plan involves changes to virtualization, storage, or integration with Azure, it will require an upgrade.

Note: on Windows Server 2022 Datacenter: Azure Core Edition, hotpatching—patches that don’t require a reboot—ends at the conclusion of mainstream support, which is October 13, 2026: something will definitely break on that date for this specific role. Elsewhere, extended support runs through October 14, 2031, and starting in October 2026, the gap will begin to widen between what your current infrastructure does and what the products you purchase afterward will do.

How to Know If This Applies to You

The question isn't whether you have Windows Server 2022. The question is: How much longer do these machines need to last?

  • A server installed in 2022 on depreciated hardware will reach the end of its lifecycle anyway. The migration is part of the hardware replacement process and does not require any additional decision.
  • A server recently installed on new hardware has five or six years of operation ahead of it. That’s the problem: it will continue to operate well beyond the point at which its operating system will receive only security patches.
  • A virtual machine in the cloud has no hardware constraints, but it does have the other two—third-party vendors and upcoming features.

The effort—and it’s modest if you start early—

Upgrading a server operating system is not an migration application-level update. For a standard role—file server, print server, additional domain controller, or simple application server—it can be prepared for and implemented without any major issues, often by setting up a new machine alongside the existing one and then switching over the service.

What drives up costs are servers running outdated applications whose system requirements no one knows anymore, and machines running three services at once because they were set up in a rush. Neither of these issues is discovered the day before; they’re identified through an inventory, and conducting an inventory doesn’t require any decision-making.

What to Do Now

  1. List the servers under Windows Server 2022 and, for each one, the date the hardware on which they run was purchased or created.
  2. Extended support ends on October 14, 2031: Separate the servers whose hardware is due for replacement soon enough to allow for the version upgrade—they’ll handle it on their own—from those that will remain in service beyond that date.
  3. For the latter, check what your third-party publishers currently certify and what they claim.
  4. Include the version upgrade in the multi-year plan rather than in a separate project: that's where it costs the least.

None of this is urgent in the sense that anything would come to a halt. That is precisely why the decision is being made now, while it is still a matter of scheduling and not a necessity.

Other Microsoft deadlines fall on the same day, October 13, 2026, and it’s worth addressing them in the same plan.

Microsoft Sources

After reading

What an article Can't Know

An article describes what applies to everyone. What varies from one organization to another is the inventory: which applications, which accounts, and which pieces of equipment are actually involved in your organization. The inventory determines the scope of the effort, and it cannot be summarized on a single page.

You'll be speaking directly with the engineers who will be doing the work, not with a middleman. We'll respond within 24 business hours.

If the topic has changed

Check what is still true

Announced dates are sometimes postponed, products are renamed, and conditions change. The blog tracks these topics over time: when a rule changes, a new post announces it.

Search for a topic in the blog