Windows Server 2016 End of Support: Your Files Might Survive, But Will Their Links?

Published 15 October 2026

Your Windows Server 2016 exit is ready for sign-off. The files have been moved. The new environment is live. The migration dashboard is glowing green.

Then someone in Finance opens Budget.xlsx. The workbook tries to retrieve current figures from \\FS2016\Finance\Rates.xlsx. Except FS2016 appears to have disappeared.

Both files survived the data migration, but the link between them didn’t. Files, regrettably, don’t send out their own change-of-address cards.

Note that in this article, I’m just using one file as an example. If this situation only happened with one file, that would be a problem but not necessarily catastrophic. The problem is that when it comes to large-scale data migration like the one you did (or will be doing) to upgrade your Windows server or move to an entirely new platform (like SharePoint Online), there are typically thousands of such cases. Now, that can be a catastrophe!

The Server Deadline Isn’t Your Only Deadline

Microsoft says extended support for Windows Server 2016 ends on 12 January 2027. Organizations can choose to upgrade to Windows Server 2025, migrate workloads to Azure or use Extended Security Updates (ESUs) through Azure Arc while completing a longer transition.

The approaching Windows Server 2016 EOL, as it’s commonly called, gives IT managers, MSPs and migration consultants a clear infrastructure deadline.

It also creates a commonly overlooked problem. Before the old server disappears, you need to know which files still contain links to it.

An Excel^™ workbook doesn’t know that the migration was successful. It knows only that it once found Rates.xlsx at a particular address. When that address stops working, the workbook can no longer retrieve current information from the linked file.

Excel files are an obvious concern because nearly every organization uses them. Financial models, forecasts, pricing tools, project trackers and operational reports can contain hundreds or even thousands of links.

But Excel isn’t alone. Word^™ documents, PDFs, CAD files and other business files can also contain links to content stored elsewhere. Some may have been created a decade ago by someone who is now retired, but the links left behind can still be essential.

Some may have been created a decade ago by someone who is now retired, but the links left behind can still be essential.

The Files Moved. Why Didn’t the Links?

Moving a file and updating what’s stored inside it are two very different jobs.

Microsoft’s guidance for migrating file shares to SharePoint, OneDrive and Teams makes that distinction. When using Microsoft’s SharePoint Migration Tool, documents and file structures can be migrated, but the conversion of embedded URLs within content is listed as something that isn’t migrated.

Even when both workbooks reach their new locations, Budget.xlsx may continue looking for Rates.xlsx on the old server.

If that server path no longer works, Excel may continue displaying previously saved values, but it can’t retrieve updated data from the linked workbook.

Both workbooks arrived. The link between them didn’t survive.

If the old server remains available during the transition, the link may continue retrieving data from an outdated copy of Rates.xlsx. The workbook can open and calculate normally, with nothing obvious to tell the user that its formulas are using last quarter’s figures.

A visibly broken link demands attention. A working link to the wrong file may go undetected until the source environment is retired.

Different Options, the Same Link Question

An upgrade to Windows Server 2025 may preserve the server name, share names and folder structure. If so, many UNC paths might keep working. But “might” has no business in a cutover sign-off. Test the actual configuration.

Azure introduces more variables because familiar paths may be retained or replaced, depending on the architecture. Moving from file shares to SharePoint or OneDrive, for example, creates a more obvious change: the files enter a different storage structure, but the UNC paths stored in linked documents aren’t automatically updated.

Extended Security Updates can provide Critical and Important security updates for Windows Server 2016 for up to three years after end of support, giving you more time to plan. Finding links buried inside your files will still require separate attention.

After cutover, will each file link reach the content your users actually need?

Whatever route you choose, the question remains the same: After cutover, will each and every file link reach the content your users actually need?

Don’t Let the Old Server Help You Pass the Test

During server migration testing, a migrated file may open and follow its links successfully because the original server is still available. In that case, the file could be reaching straight back into the old environment rather than finding content in the new one.

Run a controlled test in an isolated test environment, or an approved test window, while preventing the test users or devices from accessing the legacy share. Linked workbook data should be refreshed or updated during the test. Simply opening a workbook and seeing saved values shouldn’t be considered sufficient evidence that its links work.

Start with departments that depend heavily on linked files. Finance is the usual suspect, but engineering, estimating, operations, HR and project teams often build their own intricate webs of dependencies.

Use this migration checklist for each sample:

A test can pass while the file is still reaching back to the old server.

Which file contains the link?
Where does that link point currently?
Where will the referenced file live?
Can the intended user access it?
Does the link work without the old share?
Is the retrieved content current and from the intended file?

One Broken Workbook Is a Warning

Testing a sample can reveal the problem, but it can’t show you the scale of it. One failed workbook might contain three broken links. Elsewhere on the server, thousands of files could still point to old shares, renamed folders or content that will soon live somewhere entirely different.

Waiting for users to find those links turns discovery into a help desk nightmare. Monday morning, Finance reports a broken forecast spreadsheet. At 10:15, Engineering loses access to a critical set of linked drawings. By lunchtime, someone suggests switching the old server back on “just for now.”

That’s how retired infrastructure develops an afterlife.

A pre-migration link inventory gives you an opportunity to identify affected files while there’s still time to act. Its scope should be clear. Which locations were scanned? Which file types were included? Which server names and shares appeared in the results?

That’s how retired infrastructure develops an afterlife.

Without that context, a small number of discovered links could either mean a tidy environment or a search that was too narrow.

Find the Links Before Users Do

LinkFixer Advanced^™ can scan supported file types, identify files containing links and report the destinations recorded in those links.

A link scan reveals broken dependencies before they can cause disruption.

Before a migration, LinkFixer Advanced can protect supported links using its Inoculate process. After migration, its Cure process can restore those links to the files’ new locations.

That lets the migration team deal with affected links before users start reporting them.

For a complex environment, a LinkTek consultant can help interpret the findings, map affected references to their intended destinations and apply the results to your migration design and business priorities.

Give the New Address a Proper Test

The Windows Server 2016 deadline will force plenty of infrastructure decisions before January 2027.

Check embedded links before the old environment is retired. Protect or repair those links, then confirm that the files work in the new one.

A green migration dashboard tells you the files arrived, but it’s the Monday after cutover that tells you whether they still work. It’s better to know that before the old server leaves the building.

Planning a Windows Server 2016 file-server exit? Chat with us online or call 727-442-1822 to discuss how LinkFixer Advanced can help protect your links before cutover, or repair links that are already broken.

By Ed Clark