When people think about important business systems, they usually think about servers, cloud services, cybersecurity and internet connectivity.
What frequently gets overlooked is the computer quietly doing its job day in and day out without attracting much attention. It may not be the newest computer in the building and it may not even be particularly powerful by modern standards, but if it stopped working tomorrow, the consequences could be far greater than most people realise.
Over the years we’ve encountered businesses relying on everything from Windows 95 systems controlling building management software to Windows XP machines running security and personnel tracking systems. We’ve seen workshop computers controlling specialist equipment, industrial systems managing production processes and legacy PCs running software that nobody in the business has attempted to reinstall for years.
One customer operated a sheet metal laser cutter worth well over a million pounds alongside computer-controlled metal bending equipment. Most people looking at the installation would naturally focus on the machinery, but a critical part of the system was the dedicated computer responsible for controlling it. If that computer failed, replacing the hardware might have been relatively straightforward. Restoring the software, configuration and interfaces required to get the equipment working again would have been a much bigger challenge.
The computer itself wasn’t the valuable asset. The machinery and production process that depended upon it were.
Replacing the computer hardware itself would have been relatively straightforward. Replacing the specialised software, drivers, interface cards and configuration required to communicate with the machinery would have been a very different matter altogether. Until that system was restored, a significant part of the production process could have been been affected.
This is something we see repeatedly with business-critical systems. The computer often becomes so integrated into the day-to-day operation that people stop thinking about it as a computer and start thinking about it as part of the machine itself. Nobody worries about the PC because they’re focused on the laser cutter, the rolling road, the dental X-ray system, the security platform or the production equipment it’s helping to run.
Unfortunately, when the computer fails, the business quickly discovers just how important it really was. In situations like these, the computer itself may only be worth a few hundred pounds, while the role it performs could be supporting equipment, processes and revenue worth millions.
That’s why the question isn’t: “How old is the computer?”. The question is: “What happens if it fails?”
Not All Computers Are Equal
If somebody’s everyday office PC fails, it’s generally inconvenient rather than catastrophic.
Files can often be restored from backups or cloud storage, Microsoft 365 can be reconnected, applications reinstalled and a replacement machine sourced relatively quickly. While nobody welcomes the disruption, most businesses can recover from that situation without too much drama.
Business-critical computers are different.
These systems often control or support functions that cannot simply be transferred to another machine at a moment’s notice. In many cases, replacing the physical computer is relatively straightforward. Recreating everything that sits on the computer is where the real challenge begins.
Examples of system we have worked with include:
- Building management systems
- Manufacturing control systems
- Industrial machinery
- Workshop equipment
- Laboratory equipment
- Security and access control systems
- Dental X-ray systems
- Rolling roads
- Specialist motorsport applications
- Database servers
- Test equipment
- CNC machinery
- Production systems
- Industry-specific software applications
- Legacy commercial systems tied to dedicated hardware
- Industrial data acquisition systems
In many cases, the computer has become such an integral part of the overall system that people stop thinking about it as a PC altogether.
The Irony of Older Systems
Interestingly, some of the most important systems we encounter are also some of the oldest.
Believe it or not, businesses still rely on platforms based on:
- Windows 95
- Windows 98
- Windows XP
- Windows 7
- Windows 10
Not because they’ve ignored technology, but because those systems continue performing a task that remains essential to the business.
One company approached us looking for a replacement Windows 95 computer because their building lighting and management system depended on software developed specifically for that platform.
Another relied on a Windows XP system that managed site security and personnel tracking, recording staff, contractors and visitors entering and leaving the premises.
In both cases, the operating system itself wasn’t really the issue. The issue was that the business depended on software that had been designed around that environment. Moving to a newer platform would have involved considerably more than simply installing a newer version of Windows. Depending on the application, it could have meant redevelopment work, replacement software, changes to hardware interfaces, user retraining and a substantial investment of time and money.
The systems continued to perform the function they had been purchased to perform and, from the customer’s perspective, there was little reason to change them.
As the saying goes: “If it ain’t broke, don’t fix it.”
That’s often entirely reasonable thinking. The challenge is ensuring there is a plan for the day when the hardware underneath finally decides it has had enough.
We’ve Seen Some Surprising Examples
Over the years we’ve encountered an astonishing variety of business-critical systems.
Some have controlled sheet metal laser cutters worth well over a million pounds, while others have run dental X-ray equipment, rolling roads, specialist motorsport applications, workshop diagnostic systems, building management platforms and site security systems.
We’ve also seen legacy commercial applications tied to specific hardware, industrial data acquisition systems, CNC machinery, production equipment and dedicated commercial software platforms where the computer had become an integral part of the overall solution.
In many cases, the software had been written years, and sometimes decades, earlier. Nobody had reinstalled it for years and, in some situations, nobody remaining in the organisation knew exactly how the original installation had been performed.
That’s often because nobody has needed to. The system has simply carried on doing its job reliably for years, with no requirement to rebuild it or revisit how it was originally configured. Unfortunately, that can make recovery considerably more challenging when something eventually goes wrong.
The Real Risk Isn’t Always What People Think
To an outsider, many of these systems look like obsolete computers that should have been replaced years ago. The reality is often very different.
What matters isn’t the age of the computer. What matters is the role it performs within the business.
A computer running specialist software may be controlling a production line, a security system, industrial machinery or equipment worth hundreds of thousands, and sometimes millions, of pounds. Replacing the computer itself might be relatively straightforward. Recreating the software environment, interfaces, drivers and configuration that allow everything to work together can be considerably more challenging.
Ironically, the operating system is often the thing people worry about least. If a Windows 95, Windows XP or Windows 7 system continues to perform the task it was purchased for, many businesses see little reason to change it.
If it ain’t broke, don’t fix it.
That’s often entirely reasonable thinking.
The challenge is that while the software may continue working perfectly well, the hardware underneath won’t last forever. Hard drives fail, power supplies fail, motherboards develop faults, memory can become unreliable and electronic components inevitably age over time.
For years, none of this matters because the system simply carries on doing its job. The risk only becomes apparent when a hardware failure finally occurs and information that nobody has needed for years suddenly becomes critically important.
At that point, businesses often find themselves trying to locate installation media, licence keys, supplier information and configuration details that may not have been touched for a decade or more. That’s not a position anybody wants to be in when production has stopped, customers are waiting and staff are looking for answers.
Why We Always Recommend System Imaging
One of the most effective ways of protecting these systems is through system imaging.
Unlike a traditional file backup, which focuses primarily on documents and data, a system image captures the complete computer exactly as it exists at a particular moment in time.
That includes:
- Windows
- Applications
- Drivers
- Configuration settings
- User accounts
- Licensing information
- Security settings
- Business-critical software
In effect, it creates a snapshot of the entire machine.
Should the hardware fail, that image can often be restored onto replacement hardware or, in some situations, a virtual machine far more quickly than attempting to rebuild everything from scratch.
For many businesses, the value isn’t the backup itself.
It’s the reduction in downtime.
Downtime Will Always More Expensive Than Prevention
When discussing business-critical systems, we often find that people focus on the cost of replacing hardware.
In reality, the hardware is rarely the biggest concern.
The real cost is usually the downtime and disruption that follows a failure.
If a critical system becomes unavailable, production may stop, staff may be unable to work, orders may be delayed and customers may be left waiting while the business attempts to recover. Depending on the role of the system, the cost of even a short period of downtime can easily exceed the cost of preventative measures that could have been taken beforehand.
That’s why our recommendation is not to wait for something to fail.
Instead, we look at the areas of greatest risk and address them while the system is still operating normally.
For many business-critical systems, one of the greatest concerns is that the entire operating environment resides on a single storage device. Whether that storage takes the form of a traditional hard drive, an SSD or another type of storage technology makes little difference if it fails unexpectedly. The operating system, application software, drivers, configuration settings and years of accumulated setup information would typically all be stored on that single device.
In many cases, a sensible approach is to create a complete image of the system while it is known to be working correctly and, where appropriate, replace the existing storage device as a preventative measure. The original drive can then be retained as a fallback, providing an additional layer of protection should problems arise in the future.
This approach is often significantly less expensive and far less disruptive than dealing with an unexpected failure and attempting to rebuild a business-critical system under pressure.
The objective isn’t to keep ageing hardware running forever.
The objective is to reduce risk, minimise downtime and ensure that if something does go wrong, recovery can be carried out quickly and with as little disruption to the business as possible.
It’s also important to recognise that successfully recovering a legacy system should not automatically be viewed as a permanent solution. In many cases, recovery simply buys the business time to properly evaluate its options. While it may be possible to restore functionality and keep a critical system operational, there may come a point where the application itself should be redeveloped, replaced or migrated to a modern platform before the next failure occurs.
The goal is not merely to recover from today’s problem.
It’s to avoid creating tomorrow’s emergency.
The Question Every Business Should Ask
Many of the systems discussed in this article remain in service because they continue doing their job reliably every day. When a system is working properly, businesses naturally focus their attention elsewhere rather than discussing replacement projects, software upgrades or redevelopment costs. The computer quietly gets on with its job and the business gets on with theirs.
The more useful question is not: “Should we replace this computer?” but: “What is our plan if this computer suddenly stops working?”
For some businesses, the answer may be straightforward. A replacement machine can be sourced, software reinstalled and operations resume with relatively little disruption. For others, the answer may be far less comfortable. The software may no longer be available. The original supplier may have disappeared. Nobody may know how the system was originally configured and replacement hardware may be difficult to source.
Those are exactly the situations where planning ahead delivers the greatest value. The objective isn’t to replace systems that are working perfectly well, but to ensure that when a failure eventually occurs, the business isn’t trying to develop a recovery strategy in the middle of an outage.
Planning Before a Failure Occurs
The best time to think about recovery is when everything is working normally.
Once a business-critical system has failed, decisions that could have been made calmly and methodically often have to be made under pressure. Staff are waiting, customers are affected and the priority quickly becomes getting the system operational again as soon as possible.
By contrast, a system that is still functioning gives you options.
Because the system is still functioning, Frontline can assess the risks and help put sensible safeguards in place before they become urgent problems. We can create a system image, verify that it can be restored successfully, replace ageing storage devices, document software licences and identify hardware or software dependencies that could complicate recovery in the future. Where possible, we also carry out preventative maintenance on the system itself, helping to extend its reliable service life whilst reducing the risk of unexpected downtime. We can determine whether replacement parts remain available, evaluate how dependent the business is on the system and help establish whether the application remains viable as a long-term solution.
Not every system requires the same approach, but every business-critical system should have some form of recovery strategy.
For some organisations, that may be as simple as maintaining a current system image and a known-good replacement drive. For others, it may involve virtualisation, replacement hardware held in reserve or even a longer-term plan to replace or redevelop the application entirely.
The important thing is that the discussion takes place before a failure occurs, not afterwards.
That’s especially true for systems that have been working reliably for many years. The absence of problems today doesn’t remove the need for planning. In fact, it often creates the perfect opportunity to prepare for the day when the system eventually needs attention.
How Frontline Can Help
Frontline has been supporting businesses since 1989, and over the years we’ve worked with a surprising range of specialist and business-critical systems.
We’ve helped customers running everything from building management systems and security platforms to industrial machinery, workshop equipment, dental imaging systems and production machinery worth hundreds of thousands, and sometimes millions, of pounds.
When a business depends on a system like this, our first objective is to understand the role it performs and the impact its loss would have on day-to-day operations. From there, we can help create a recovery strategy that is appropriate for the system and the business that relies upon it.
That may involve creating and validating a complete system image, replacing ageing storage devices, carrying out preventative maintenance, sourcing replacement hardware, implementing virtualisation or identifying opportunities to modernise the underlying application.
In some cases, the outcome may be reassurance that the existing precautions are already sufficient. In others, it may highlight risks that have simply never been considered because the system has been working reliably for so many years.
The important thing is that the conversation takes place before a failure occurs.
After all, the biggest risk isn’t usually that a system is old.
The biggest risk is discovering how important it was only after it has stopped working.
For users planning on deploying a robust server grade PC running on a desktop OS, consider our machines in the Mission Range.
Related Articles
- Why Backups Matter
- What Happens When a Hard Drive Fails?
- Repair or Replace? How We Help Customers Decide
- Windows 10 Support Has Ended. What Are Your Options?
- Cyber Security for Small Businesses
- Is It Worth Buying a Refurbished Computer?