← Back to blog Servers

Windows Server 2016 support ends January 12, 2027 and the memory crunch is raising hardware prices: how to plan the migration and IT budget of your Mexico operation

4 min read

On October 23 Microsoft reminded customers that Windows Server 2016 reaches end of support in January, as BleepingComputer reported. After January 12, 2027 there will be no more security patches.

If your company is run from the US, Europe or Asia, that server probably sits in a plant or office in Mexico. It runs the domain, the shared drive and often the local accounting system. And nobody at HQ has looked at it in years.

The timing is awkward. PC shipments dropped 21% because of the memory shortage and, according to HD Tecnología, could fall 27% by year end. Servers and PCs for your Mexico site will cost more and take longer to arrive.

Jan 12, 2027 last day of security patches for Windows Server 2016
21% drop in PC shipments due to the memory shortage
27% possible drop by the end of the year

What end of support actually means

Still running, no longer defended The server works the same on January 13; what stops arriving are the security fixes.

Nothing shuts down. The accountant in Querétaro still opens CONTPAQi and the shared drive is still there.

What changes is that every new flaw stays open for good. Ransomware crews look for exactly that: an old server running Active Directory, the directory that holds every user and password on the network.

In our experience, the 2016 server at a Mexico site is the one nobody wants to touch. It does everything, and the person who set it up left long ago.

Inventory first: what your 2016 server in Mexico does

A list before a quote Roles, apps, versions and who depends on each one; everything else is decided from there.

Before asking for quotes, find out what is inside. It almost never does just one thing.

RoleWhat it looks like on siteWhat to ask
Active Directory (domain)Staff log in with a company accountIs there one domain controller or two?
File sharesThe S: drive or the Shared folderHow big is it and who has access?
Local accounting and payrollCONTPAQi or Aspel, which handle CFDI e-invoicing and Mexican payrollWhich version does the vendor certify for Server 2025?
DNS, DHCP and printingThe front desk printer, the network IPsWhat breaks if it goes down?
SQL ServerReports, point of sale, local databasesIs the SQL version old too?

Also check whether it is a physical box or a virtual machine. The path changes a lot.

Three paths: Server 2025, cloud or ESU

On site, cloud or a bridge Not everything has to go to the same place; each server role can take its own path.
OptionFits whenWatch out for
Server 2025 on new hardwareThe server is several years old and out of warrantyHigher prices and longer lead times; per-core licensing and CALs
Server 2025 on current hardwareThe hardware is recent and supported by the vendorTest drivers and back up first
CloudFiles and email, no heavy local appsA stable internet link plus a backup link
ESUOne app that cannot move yetYearly fee; a bridge, not a destination

A CAL is the access license each user or device needs to connect to the server. It often goes missing from quotes.

ESU stands for Extended Security Updates, the paid program Microsoft sells to buy time. Confirm terms and pricing for 2016 with your reseller (market reference, verify).

Our take: most Mexico sites do well with a mix. Files go to SharePoint or OneDrive under the global tenant, while the domain and the local accounting app run on a small Server 2025 on site.

If Server 2022 looked like a safe middle step, note that it left mainstream support in October.

Why to quote hardware and licenses before December

A quote with a date on it Get the validity period in writing and reserve the hardware; memory and disk prices will not wait.

As Imagen Radio explained, the shipment drop comes from the memory shortage. Fewer parts, higher prices, slower deliveries.

Then add the calendar. In Mexico, activity slows from mid December to early January, and HQ purchase approvals take their own time. Order in late December and the server may arrive after the patches have stopped.

What we suggest:

  • Quote server, licenses and CALs together, in November.
  • Ask for a written validity period, in MXN or USD.
  • If the budget is tight, split it: hardware in 2026, licenses or cloud in 2027.

Migrating without stopping the Mexico site

  1. Full backup and a test restore. If that has never been done, start with backups that actually restore.
  2. Build Server 2025 alongside the old one.
  3. Move roles one at a time: domain, files, accounting, printing.
  4. Work on Friday night or the weekend, local time.
  5. Have someone on site first thing Monday. That is what IT smart hands in Mexico are for.
  6. Retire the 2016 box a few weeks later, not the same day.
ProcessBi team working on servers
Your 2016 server has a deadline; your migration should have one too Foto: Pexels

What about your Mexico site?

Do you know how many 2016 servers you run in Mexico and what each one does? If the answer is roughly, that is where we start.

At ProcessBi we assess your servers, quote hardware and licensing, migrate during off-hours windows and keep everything covered under a plan with a written SLA, invoiced in MXN or USD.

Book your server assessment — we reply the same business day.

Your path

Running IT in Mexico from abroad

61 of 89
  1. PHP2Shell patch ✓ Read You are here 3 min
  2. Unpatched PHP ✓ Read You are here 3 min
  3. Server 2016 ✓ Read You are here 4 min
  4. HTTP2Shell ✓ Read You are here 3 min
  5. Qilin and backups ✓ Read You are here 3 min
  6. NAS ransomware ✓ Read You are here 3 min
  7. Ivanti VPN ✓ Read You are here 4 min
  8. Field services →
Next HTTP2Shell: a critical Brotli flaw forces emergency .NET and PHP for Windows patches — what to update today on the servers of your Mexico operation