Windows Server 2003 EOS: 4 Opportunities For Solutions Providers
July 14 will mark the end of service for Microsoft Windows Server 2003, and this means the end of patches, security updates, and, in some cases, compliance with their industries’ regulations and requirements.
And July 14 is only about two months away.
It’s possible you could be hearing from businesses that put off migrating to another solution until the eleventh hour. A Spiceworks study released in March found only 15 percent of businesses surveyed had fully migrated, 48 percent had partially migrated, 28 percent were planning to migrate, and 9 percent had no plans or didn’t know. Considering millions of businesses used Windows Server 2003, the potential number of upgrade projects probably remains very large.
JK Lialias, director of data center security for Intel Security, points outthat these projects can extend beyond simply installing a new version of Windows Server. He cites an Intel Security solution brief, “The 1-2-3 Security Approach for Windows Server 2003 EOS,” that lists three paths your clients can choose from, as well as providing information on security considerations for each path.
The brief recommends inventorying all Windows 2003 servers and the applications on them and then deciding on the best option:
- Path 1 is upgrading to a newer version — Microsoft recommends Windows 2012 R2. This option includes virtual servers in a private cloud.
- Path 2 is migrating to the public cloud.
- Path 3 is to delay migration and upgrade later.
Your clients will likely need advice on which path to take for each of their servers. “Take it case by case,” Lialias advises. “Be open to customers, and take a consultative approach.” He also says to remember that for your clients, migrating can have both positive and negative implications: “It’s an opportunity to modernize, but it’s a big interruption for business.”
From a partner perspective, he comments, “This is a great opportunity not only to capture the upgrade but also security.” He cited the Verizon 2015 Data Breach Investigations Report that states servers are a top target of hackers. Depending on your clients’ businesses and how they choose to migrate from Windows Server 2003, you could also find opportunities for additional projects and recurring revenue. From among the possibilities, Lialias highlights these four:
- If your client will employ virtualization, add solutions that protect that environment without hampering performance.
- If your client chooses to migrate to the public cloud, add solutions that secure data, provide email protection, and reduce phishing.
- For clients that will not be able to migrate prior to July 14, possibly because they run a business-critical application written in 32-bit, Lialias explains, while they look for alternatives, securing their environment becomes even more critical. He says one option is application control — defining what can operate on the server. “It’s a nice way of controlling what runs to the server,” he comments. “Malware will never be considered a known application.”
- Discuss compliance with your clients. Merchants, for example, who don’t upgrade will not bePayment Card Industry Data Security Standard (PCI DSS)compliant. In addition to security solutions, you can offer services that will help them maintain compliance, such as remote monitoring or risk assessments.
Lialias adds Intel Security partners have access to resources that can assist with the migration from Windows Server 2003.