Windows server 2003 end of life

Microsoft Windows Server 2003 reaches its end of life on July 14, 2015. You can’t afford to have servers running it in your medical office.


728x90 Discount Medical Supplies

 DataCenter[1]

Microsoft Windows Server 2003 will reach its official end of life on July 14, 2015. In practical terms, that means Microsoft will longer support the software, and any security or compatibility issues that arise after that date will not be addressed. If your medical office is still using Windows Server 2003 after July 14, then you are taking a potentially very expensive, and unnecessary, risk.

IT survey

According to a survey of over 1,300 IT professionals conducted by Spiceworks in March 2015, some 63% have either already migrated or partially migrated off of Windows Server 2003, and another 28% were in the planning stages. Most of those surveyed said they are migrating to Windows Server 2012 R2. That’s the good news.

The bad news revealed by the survey is that 22% of the IT professionals surveyed said they do not plan to migrate all of their servers off Windows Server 2003, citing compatibility and cost worries. That means there could potentially be thousands, even millions, of unsupported servers running business operations around the world after the July deadline.

bwindows-server-2003-logo[1]

Security and compatibility

Every time Microsoft declares end of life for one of their software products, there’s a natural tendency for medical offices to resist the migration to alternative, supported, software. For example, there are still a large number of Windows XP PCs operating in the medical office environments.

Medical offices naturally do not want to spend the money and time buying, testing, and deploying new servers when the servers they’re using are working just fine. But this is a very risky and potentially very expensive “non-strategy” to take in the current business environment.

Just in the past year or so, we’ve seen confirmed breaches of servers perpetuated by the governments of North Korea and China. We’ve also seen network security fail to stop Russian organized crime from stealing identification data from retailers. Just about every other week, there’s another widely reported IT security incident.

As an IT professional, these security breaches should make you very wary of your own business security protocols. Can you really afford to have unsupported and potentially vulnerable servers in your network?

 

Liabilities

Target estimates that the data breach it suffered in 2014 will cost the company close to $150 million. Identity thieves, like those in Russian organized crime, fraudulently steal $6 billion from tax refunds annually. In other words, stealing identification data is big business, and business is good.

 

Internet security online business concept pointing security services

Internet security online business concept pointing security services

 

Medical offices, especially ones that collect private identification data from their patients and insurance companies, are expected to take every possible precaution to protect that data. In a lawsuit over a security breach, one of the first things any lawyer worth their salt is going to do is check whether the enterprise’s infrastructure is up to date. Running an unsupported operating system like Windows Server 2003 isn’t going to go well for you.

Microsoft will support each server running Windows Server 2003 for $600 per monthafter the July 14, 2015, cutoff. That can buy you some time to complete the migration to an up-to-date operating system or a cloud solution, but it’s certainly only a temporary fix.

While the timing may be bad for your current situation, the fact remains that Microsoft Windows Server 2003 has reached its end of life. The potential liabilities of running that operating system as an integral part of the business infrastructure far outweigh the benefits of not spending a relatively small amount time and money migrating to something more modern and secure.

Your thoughts

Are you still running Windows Server 2003 in your medical office? Are you planning to migrate off of that OS? If you’re not, why aren’t you concerned about the potentially liability risks? Let us know your thoughts in the contact us below.

 

Support for Windows Server 2003 ends July 14! Save up to an additional $300 on select PowerEdge Servers. Hurry, offer ends soon!

4 thoughts on “Windows server 2003 end of life

  • Good idea to end the support of this server. Windows 2012 is so much better! If anybody needs to upgrade, contact these guys –> https://www.mcnetinc.com/contact-us/ they can help you onsite and remotely. They will give you the best quote and do the job for the right price.

    God bless the United States of America.

  • We currently have a server (SBS 2003 Standard utilizing Exchange 2003).

    We want to retire the it.

    We have purchased a new server (Windows Server 2012 Standard with licenses for Exchange 2013 and SQL 2012).

    Is there a guide that describes how to migrate SBS 2003 to Windows Server 2012 Standard?

    We have about 10 users.

  • There is no one guide as such for migration, but the procedure is similar to other migrations

    1. Install Server 2012 on the new server, join to the domain. ( Upgrade the schema etc… on the old server with 2012 DVD)–> http://adf.ly/1Kec5L

    2. Promote it to a domain controller, make it a global catalog server and a DNS Server

    3. Wait for everything to replicate > move your data.

    4. Install DHCP on the new server (same scope as the SBS 2003), then shut down DHCP on the SBS server and activate on the new server

    5. Transfer the FSMO roles–> http://adf.ly/1KebeO

    6. DC Promo the SBS server out of the domain

    Shut down the SBS server

Leave a Reply