Three months ago we watched Windows XP reach the end of its support life, and plenty of businesses scrambled to replace desktops in the final weeks. The next deadline is already on the calendar. On July 14, 2015 — one year from yesterday — Microsoft will stop releasing security updates for Windows Server 2003.
That includes Windows Server 2003 R2, and it matters just as much for offices on Small Business Server 2003, which a lot of small businesses still depend on for file sharing, user logins, and email — and whose bundled Exchange Server 2003 already lost support this past April. A year may feel like a comfortable runway. For a server, it is not much. Replacing a desktop is an afternoon; replacing the machine that runs your whole office is a project. Here is how to think about it.
Why a server deadline is a bigger deal than a desktop one
An unpatched desktop is a risk to one person. An unpatched server is a risk to everyone, because it holds the things that matter most: shared files, user accounts, line-of-business databases, and often email. Servers also tend to be reachable from every computer in the office, and sometimes from the internet. Once security updates stop, every newly discovered flaw stays open indefinitely.
There is also a compliance side. If you handle credit cards, health information, or financial records, running an unsupported server will be hard to justify to an auditor or an insurer. And software vendors are already moving on; many new versions of business applications do not support Server 2003 at all.
Start with an inventory
Before you pick a destination, figure out what your old server actually does. Over a decade, servers tend to pick up jobs nobody wrote down. Make a list of:
- Roles: domain controller and user logins, file shares, printers, DHCP and DNS, remote access.
- Applications: accounting, practice management, point of sale, anything with a database behind it.
- Email: if you run Small Business Server, Exchange Server 2003 is likely on board too — and it is already out of support.
- Scheduled tasks and scripts that quietly run backups, exports, or reports.
- Who and what connects to it, including copiers that scan to a shared folder.
Pay special attention to older applications. Windows Server 2012 R2 is 64-bit only, and some very old software, especially anything with 16-bit components, will not run on it. Call your vendors now and ask what version they support on modern servers and what an upgrade costs.
Option one: a new server running Windows Server 2012 R2
The most straightforward path is new hardware with Windows Server 2012 R2, Microsoft's current server release. It is a big step up: better performance, better storage features, built-in virtualization, and support through the early 2020s. For a small office, the Essentials edition is designed for up to 25 users and 50 devices and takes over much of what Small Business Server used to do, minus the built-in Exchange.
Your 2003 server is also probably running on hardware that is ten years old. Drives, power supplies, and fans do not last forever, and replacement parts get harder to find. A migration fixes the software and hardware problem at the same time.
Option two: virtualize
Virtualization lets one physical server run several "virtual" servers, each with its own operating system. Instead of one box doing everything, you might run a domain controller, a file server, and an application server as separate virtual machines on a single host using Hyper-V, which is included with Windows Server 2012 R2.
The advantages for a small business are real. Each role is isolated, so a problem with one application does not take down file sharing. Virtual machines are easier to back up and restore as a whole. And when the hardware ages out in five years, moving virtual machines to a new host is far easier than rebuilding a server from scratch. For offices with more than a couple of server roles, this is often the best long-term design.
Option three: move some of it to the cloud
Not everything needs to live on a server in your back room anymore. Email is the clearest example. If you are running Exchange on Small Business Server 2003, moving to Office 365 with Exchange Online is often simpler and cheaper than building a new mail server. You get a professionally managed email system, larger mailboxes, and no more worrying about Exchange updates.
File storage, backups, and some business applications can move to the cloud too, and Microsoft Azure can host virtual servers if you would rather not own hardware at all. For most small offices, though, the answer ends up being a mix: email in the cloud, with a smaller on-site server for logins, files, and the applications that need to be local.
Why starting now matters
We saw it with XP. As the deadline got close, hardware was backordered, consultants were booked up, and software vendors were swamped with upgrade requests. Businesses that started early had time to test and schedule the cutover for a quiet weekend. Businesses that waited did it in a rush, or not at all.
A realistic timeline for a small office might be: inventory and planning this summer, budget decisions in the fall, hardware and licensing by the end of the year, and migration in early 2015. That leaves room for surprises, which server migrations reliably provide.
What to do now
- Confirm which servers in your office run Windows Server 2003 or SBS 2003.
- Inventory every role, application, and scheduled job on each one.
- Contact your software vendors about supported versions and upgrade costs.
- Decide what can move to the cloud, starting with email.
- Choose between a single new server and a virtualized setup.
- Set a budget and a target migration date well before July 2015.
- Make sure your current backups are solid before anything changes.
A server migration done calmly, with a plan, is routine. One done in a panic is where things go wrong. If you would like help mapping out what your 2003 server does and where each piece should land, our server administration team handles these projects regularly. Reach out at info@pinellasit.com and let's get it on the calendar.
