If the server that runs Tally in your office was bought between 2017 and 2019, there is a fair chance it runs Windows Server 2016. Windows Server 2016 end of support arrives on 12 January 2027, the last Patch Tuesday on Microsoft’s lifecycle page for the product. After that date Microsoft stops publishing security fixes for it. The server will keep booting, Tally will keep opening, and nothing on screen will tell you anything has changed. That is exactly why it is easy to miss.
This post covers what ends, whether you can buy more time, the three realistic routes for a small office, and a ten-week plan that fits before the date.
What actually ends on 12 January 2027
Mainstream support for Server 2016 ended in January 2022. What has continued since then is extended support, which means security updates. That stops in January 2027. Any flaw found in Windows Server 2016 after that date stays open on your server for good, unless you pay for Extended Security Updates (see below).
For a CA firm the risk is concrete. The server holds client ITR data, GST working files, Tally company data and often scanned PAN and bank documents. Ransomware crews look for unpatched Windows servers that are reachable from the internet, and an out-of-support server becomes a little easier to break into every month. Our post on why regular software updates matter explains the mechanics.
Check which version you have
On the server, open PowerShell and run:
(Get-CimInstance Win32_OperatingSystem) | Select-Object Caption, Version
Windows Server 2016 shows a Caption containing “Windows Server 2016” and a Version beginning 10.0.14393. If you see that, keep reading.
Can you buy more time? Usually not
Microsoft has said Windows Server 2016 will get Extended Security Updates (ESU) for up to three years. Before you treat that as the plan, read the eligibility rules in Microsoft’s ESU FAQ (updated 2026):
- On your own premises, ESU requires active Software Assurance or subscription licences bought through volume licensing or a Cloud Solution Provider. A server licence that came pre-installed with the hardware (an OEM licence), which is how most small offices buy, does not qualify on its own: Microsoft’s FAQ, written for the Server 2012 ESU, says OEM customers can buy ESU only with active Software Assurance or a subscription (for example through a Cloud Solution Provider), and recommends moving apps on pre-installed servers to a supported version. Read the eligibility section again before you count on it; the rules have differed between versions.
- It is not cheap. For Windows Server 2012 R2, ESU was licensed per core, bought a year at a time, and each year cost 100% of the full licence price. Microsoft had not published Server 2016 ESU prices when we wrote this in October 2026.
- ESU is free for servers that run as virtual machines in Microsoft Azure. Moving a Tally server to the cloud is a bigger project than an upgrade, though, and it changes how staff connect.
Microsoft itself calls ESU a “last resort” and a temporary bridge. For most CA offices the realistic answer is to move to a newer Windows Server.
Three routes, and which one fits
| Route | What it means | Good fit when | Watch out for |
|---|---|---|---|
| In-place upgrade | Install Windows Server 2022 or 2025 over 2016 on the same machine, keeping data and settings | The hardware is healthy, under warranty and meets the new version’s requirements | Needs a full backup first; old drivers and odd software can break; you still need a new licence |
| New server, fresh install | Buy a server with 2022 or 2025, then move Tally data, shares and users across | The current box is five or more years old, or out of warranty | More planning; both servers run side by side for a while |
| Cloud server | Run Windows Server in a cloud data centre and connect staff to it | You already want to move away from an office server | Monthly cost, internet dependency, data location and a new remote-access setup |
Pick the target version with its own end date in mind. According to Microsoft’s lifecycle pages, Windows Server 2019 is supported until January 2029, Windows Server 2022 until October 2031 and Windows Server 2025 until November 2034. Moving to 2019 now buys barely two years, so 2022 or 2025 is the sensible target.
Microsoft’s upgrade path table (2026) shows that a 2016 server can be upgraded in place directly to 2019, 2022 or 2025. The same page lists the conditions: back up first, keep the same language, you cannot move down from Datacenter to Standard (Standard to Datacenter is allowed), and every Windows Server upgrade needs its own licence. Windows Server 2025 also needs a processor that supports the SSE4.2 and POPCNT instructions (see Microsoft’s hardware requirements). Some servers from the Server 2016 era will not qualify, which settles the choice for you.
The cost people forget: Remote Desktop licences
If staff use Tally by signing in to the server over Remote Desktop, each user or device needs a Remote Desktop Services client access licence (RDS CAL). These are tied to the server version. Microsoft’s RDS CAL compatibility table is blunt: Windows Server 2016 RDS CALs cannot be used to connect to a 2019, 2022 or 2025 session host. Upgrade the server and you also need new RDS CALs, installed on a licence server of the same version or later. There is a 120-day grace period, after which sessions stop.
We have not given rupee figures here, because licence prices depend on edition, core count and reseller. Ask for two written quotes that list each item separately: the server licence, RDS CALs for every person who signs in remotely, any new hardware, and your IT vendor’s hours.
Check Tally and everything else before you move
TallyPrime is rarely the problem. Tally’s recommended system configuration lists 64-bit Windows 7, Windows Server 2008 R2 or above, so Server 2022 and 2025 are within range. The things that break are usually around it:
- TDL add-ons and customisations from your Tally partner
- Digital signature (DSC) token drivers and the utilities for the income-tax and GST portals
- Printer and scanner drivers, especially for older multifunction devices
- Backup software, antivirus and any payroll or tax software installed on the server
Write the list down, ask each vendor in writing whether their current version supports your target Windows Server version, and test on the new server before the cutover. Keep the old server switched on, read-only and off the network for a few weeks after the move, in case something was missed.
A ten-week plan
- Week 1: confirm the version, list every application and the people who connect remotely, and test that last night’s backup actually restores.
- Week 2: choose the route and target version; get quotes for licences, RDS CALs, hardware and vendor time.
- Weeks 3 to 6: order, build and test. Open real Tally companies, print, sign a document with a DSC, run a backup.
- Weeks 7 and 8: cut over on a weekend, away from your busiest filing dates. Have staff test from the office and from home.
- Weeks 9 and 10: harden the new server and retire the old one properly: wipe its disks, and remove its accounts and firewall rules.
A new server starts with new defaults, so do not assume your old settings came across. Go through the basics in five simple steps to secure your Windows server: Windows Firewall on for all three profiles, Network Level Authentication on, sensible lockout and password rules, and Remote Desktop closed to the internet. If staff reach the server from home, put them on a private connection such as Prixl Guard or a VPN rather than an open RDP port; our RDP guide explains why.
Prixl Warden runs on Windows Server 2016 or newer, and its security audit (29 checks, covering RDP, the firewall, risky ports, password and lockout policy, Defender and Windows Update age) is a quick way to confirm the new server is set up as you intended.
If you cannot make the date
Some offices will still be on 2016 in February. If that is you, reduce the damage an unpatched server can do while you finish the move: make sure Remote Desktop cannot be reached from the internet, keep one backup copy offline or immutable, remove software nobody uses, and set a firm migration date. Then keep that date. An unpatched server only gets riskier the longer it runs.
Start your 30-day free trial of Prixl Warden to audit your server’s settings before and after the move.
